Compumotor 6K 4 used to drive goniometer table

[mhaque]

Hello fellow LabVIEw users

I am trying to improve on a goniometer VI that was written some time back for a 6K4 Compumotor. The numerci control button "Move to" rortates the arm on a horizontal surface at the specified angle. I essentially only want to move the goniometer at a certain angle from 0 to 360.

This VI is giving me problems, i.e it runs well but sometimes it stops running all together. I would like to see if it has lost contact with the hardware. There is no way of seeing that now.

I want a critique of the block diagram or any other improvements I can make to the program. I ideally want something that is effiecient readable, scalable etc.

The manuals and communications protocol are attached along with the VI. any criticism would help. Also if someone can point me to an efficiently written VI that has been written already for the 6K compumotor it would be greatly appreciated

Thanks

mhaque

[Deborah_B]

Hello mhaque,

There are a couple other Discussion Forums with threads regarding the Compumotor 6K4; did you see this more recent one? In regards to your code, have you ever tried highlighting the execution on the block diagram or ran the code with breakpoints to try to narrow down a possible problem time-out area? Do you notice it happens more often when a certain cluster button is pushed to be in a specific state?

Also, older, but from same Parker website: VI Library

Regards,

Deborah Y.

[ArchivedPointOnePa]

Late last year and earlier this year I posted a couple messages about an application "stalling" or "freezing".  They include a network communication link to an old CompuMotor 6K controller. The original application was written in LV7.1 and an update to LV2010 had the same problem.  I finally decided that it was a timer synchronization issue for muliprocessor PC that was documented in an MSDN report circa 2004. 

http://msdn.microsoft.com/en-us/magazine/cc163996.aspx

One solution that worked was to programmatically minimize and then restore the application window.  This keep the system from hanging, but isn't good for release, but for diagnostics.  The intermediate solution was to change the PC Boot setup so that it would only run in Uniprocessor mode, at least until we can update the CompuMotor 6K logic as I think that is the likely culprit.

[Kimberly_Wenger_Austin]

Hi PointOnePa,

Thanks for the information.  Glad to hear that you found a solution to your issue.  If you have any further questions about your CompuMotor, feel free to create a new Discussion Forum post or post to your previous threads so that more members will be exposed to it.  Thanks!

Kim W.