Hi,
I made a post last week in Instrument Control about creating a motion control program for two Automation Direct Stepper motors that runs on a cRIO 9045. I have since taken the advice from that post and converted my program over to a queued message handler design using the LabVIEW provided template. However, I am still having some issues...
First and foremost, the motors I have cannot store a subroutine within their local memory. This means I have to call a series of timed commands to the motor over RS485 in order to get the motion profile that I want (6 x 6 inch raster down and then back up over a 4 minute time period, 2 minutes down, 2 up). I am finding that when I send the message to begin this run in my Event Loop, the stop and exit button of my UI doesn't work and my motors continue to run, even though I thought I called the stop command to them by pressing my "Stop All" boolean. Can anyone guide me towards a remedy for this problem? A stop motion button is imperative in order to prevent damage to my linear actuators.
Secondly, I am very new to LabVIEW, and even more so to Queued Message Handler design. I did use the template, but are there any suggestions as to how I could optimize the flow of my QMH system? Eventually, after I get down the motion control portion of this code, I will need to add some pressure regulator control as well as a few other relay controls.
I have attached my QMH vi, my RT code to operate my network stream, and the sub VI I would like to use to run my full motion program.
I look forward to hearing all responses and I want to thank you in advance for your help. I will be glad to provide more detail as needed.
