Problem with driver station program and lagtime...

[jjauss]

We have been able to successfully run the driver station/dashboard application and run our robot, but every 20-30 seconds, there is a 5 second lag where the driver station stops communicating with the router/bridge/cRIO - we aren't sure which.  The connection re-establishes itself shortly thereafter, with the time on the driver station being 5 seconds or so later.  Is this a driver station problem?  We noticed that the driver station slows the CPU considerably - should it be run off the Classmate only, due to its memory requirement?  We have been running it off of a new HP laptop - with no other applications running.  Thank you for any help!

Team 1182

[Nate.H]

Hi Team 1182,

Does this happen both when you are wireless and when you have a direct connection from the computer to the cRIO over a cross-over cable?

Are there any indications of where the problem may be occuring from the Driver Station diagnostics information (do you lose a specific communications link, like Enet Link, DS Radio, Bridge, Robot)?

You should be able to run the Driver Station executable on a different laptop just depending on the Laptop's specs. If it's new, I would think it would run just fine. I've been running it from my desktop computer without a problem.

Please let me know if it still happens with a cabled connection, and then we can narrow down troubleshooting to the wireless or to the cRIO/computer communication.

Best Regards,

~Nate

[jjauss]

Nate:

We are running the robot project template from labview, and it has been running fine on our robot -

We are primarily getting the lag when we run wirelessly - we do, however, have a small lag when we run the robot directly with the cross-over cable into the cRIO -

The error we get when we run wirelessly is this - the robot code and communication lights go from green to red under the voltage readout -

Under diagnostics, there has been no change in the status of any of the communications links -

We get no error off of the dashboard when we run directly from the cRIO, but the dashboard time seems to lag a bit -

The CPU usage is above 50% from a new HP computer with no other applications running -

So the problem does occur with both, but primarily with wireless control -

Thank you again for your time,

Team 1182