LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Actuating a left mouse click on another computer

I have a simple single axis serial motion control project. I move x distance and snap a picture and repeat the steps 1000 times. However, the motion control is on one computer and the picture is taken by another. I'd like to be able to force  a left mouse click on the picture machine, from the motion control machine.  This is supposed to be a very quick solution as a predessor to a final solution and getting it accomplished quickly is the task. If anyone has any other suggestions as to accomplishing this, I'd love to see them. (my first post)
0 Kudos
Message 1 of 4
(2,647 Views)
Need a bit more information first...

Are you looking for a LabVIEW-based solution? Is LabVIEW running on both of these computers? What is supposed to receive the left mouse click on the picture-taking machine?
0 Kudos
Message 2 of 4
(2,638 Views)
For some reason it will not let me sign in from home as sigmanut, but I'm back...
Thanks for the quick reply.
More detail on the application. This seems like a science fair approach but I using this approach because I'm famaliar with WinBatch and need to get it done quick....   I'm using LabView (on computer #1) to control the motion and hopefully output a switch to another computer (#2) to simulate a left mouse click.  On computer #2 I have WinBatch, a windows macro routine that will click a button to snap the picture, click another button to save the results to a filename, again to specify file type and once more to save the file. Then go back and be ready for the next picture.
 
0 Kudos
Message 3 of 4
(2,628 Views)
You can certainly use LabVIEW to send a message to another application via a Windows API call - if you search this forum you'll come across several examples that show how to do this. Unfortunately I don't know how to extend that for a remote computer. You could do if it you had a small LabVIEW app running on the remote computer that's simply listening for a message from computer #1. You woudn't need the development environment installed on computer #2 - all you would need is the run-time engine, which is free. The LabVIEW app running on computer #2 would then send the message locally to WinBatch.

Perhaps someone else has a better suggestion?
0 Kudos
Message 4 of 4
(2,613 Views)