02-20-2007 02:58 PM
02-20-2007 04:07 PM
You probably should put some error handling in there. At the very least create a front panel error indicator so you can tell if an error has occurred at the CAN vi.
To see if the loop running, create an indicator on the loop iteration terminal (the little "I" box in the loop) and rebuild the application. This way you'll be able to verify that the loop is at least running. Just looking at the image, there's no way the top loop only would be stopped unless the "stop 2" button is depressed by default for some reason.
My guess would be something in the CAN card configuration. Is it a 1 or 2 port card? If 2, is each loop using a separate port? Maybe your development machine has the port configured as CAN1 and CAN2 and the new machine is CAN0 and CAN1. That would cause an error in one of the loops.
Try to get some error information and look at the CAN configuration and let us know what you discover.
Ed

Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.