Working code in Windows shows 'Watchdog Not Fed' once deployed

[Jon236]

Originally Posted by Ether

Are these delays being caused by your own code in TeleOp, or do you think something somewhere else is causing the delays?

I would much like to learn from your experience. Would you be willing to post your code, or perhaps PM it to some of the very experienced and helpful LabVIEW experts here?

I would be happy to....you can download it from here (for another few days):

https://www.yousendit.com/transfer.p...RlaFJF QlE9PQ

[kamocat]

Originally Posted by Jon236

Excellent suggestion....we did exactly that in Teleop and saw delays up to 150 ms. The strange behavior here is that the code runs fine under Windows, but once deployed as startup code, it shows 'Watchdog Not Fed' when enabled in either Teleop or Autonomous.

Are there any other differences in the two between how you are communicating with the robot?
(Is a different computer used for the driver station? Are you tethered vs wireless?)

Does your LabVIEW update match your cRIO image?

[Jon236]

Originally Posted by kamocat

Are there any other differences in the two between how you are communicating with the robot?
(Is a different computer used for the driver station? Are you tethered vs wireless?)

Does your LabVIEW update match your cRIO image?

It happens with a cross-over or wireless connection.

It happens with the Classmate or my Asus.

All imaging is up-to-date.

My head is a little flat from banging it on the wall, however.

[kamocat]

Does it happen with a default robot project?

[Jon236]

Originally Posted by kamocat

Does it happen with a default robot project?

No

[kamocat]

Okay, I'll take a look at your code.

EDIT:
I don't see anything that would cause a delay more than 500ms.
I'll see if I can test this on a cRIO.

EDIT2:
Sorry, I can't find my cRIO power supply. It may be awhile before I can test this.