cRIO & Lag Issues

[Alan Anderson]

That's not an error. It's only a "warning", and not much of one.

What it's actually telling you is that you have a GOOD link to the D-Link "robot radio" at IP address 10.41.18.1 and a GOOD link to the cRIO at IP address 10.41.18.2, both of which are exactly what you want.

It also tells you that you don't have anything connected to the physical Ethernet connector on your computer, that you don't have an extra router involved in the connection, and you aren't getting commands from a competition Field Management System. All of that is exactly what you should expect from a typical wireless connection to a robot.

So whatever communication and lag problem you're having, it isn't caused by that diagnostic message, and that message isn't saying anything that points to a problem.

[Greg McKaskle]

You shouldn't receive that warning every few seconds. It is only produced when one of those items change. That means that you are guaranteed to get one when you connect and disconnect from the robot, and hopefully that isn't every few seconds.

There are log files produced by the driver station that will show you the messages and other values as you drive the robot. You may want to review those. I'd suggest getting the latest version of the DS from the NI site, driving the robot, and reviewing the log file using the Log File Viewer. If it doesn't make sense, please post the files and I'll help interpret what is in the data.

Greg McKaskle

[Alan Anderson]

Originally Posted by Greg McKaskle

You shouldn't receive that warning every few seconds. It is only produced when one of those items change.

If that's true, then there's apparently something wrong with our setup. Those warnings appear many times a minute on our system, cluttering the diagnostic display, and they always seem to say the same thing.

I'll double-check today to see if any of the ping results are actually shown as changing.

[dieDoktor]

Originally Posted by Alan Anderson

If that's true, then there's apparently something wrong with our setup. Those warnings appear many times a minute on our system, cluttering the diagnostic display, and they always seem to say the same thing.

I'll double-check today to see if any of the ping results are actually shown as changing.

It too shows up for us multiple times during connection. I sure wish the warning could be more descriptive.

[dieDoktor]

Originally Posted by Greg McKaskle

You shouldn't receive that warning every few seconds. It is only produced when one of those items change. That means that you are guaranteed to get one when you connect and disconnect from the robot, and hopefully that isn't every few seconds.

There are log files produced by the driver station that will show you the messages and other values as you drive the robot. You may want to review those. I'd suggest getting the latest version of the DS from the NI site, driving the robot, and reviewing the log file using the Log File Viewer. If it doesn't make sense, please post the files and I'll help interpret what is in the data.

Greg McKaskle

We are currently using Driver Station version 4.0.0.9, we have tried using the Log File Viewer. However, we are not experienced with it, and are not sure how to use it. We choose the file we want to read, but nothing shows up... There is no start button for us to use. We wish we could post our Log Files for you to use and help us, but the forum won't let them be attached. Would anyone be willing to have them e-mailed and checked?

[Greg McKaskle]

The DS is set to ping the robot when the DS is on the Diagnostics tab and when the robot status packets time out. When pinging, the DS will add a message when something about the ping changes. I agree that this is noisy, but it is hoped that this will automatically sniff out what may have disappeared and record it in the log file.

As an example, if the cRIO crashes but the robot doesn't lose power, the status packets will timeout, the DS will start pinging and will clearly show that the radio was present. This helps to eliminate an overall power issue on the robot and points towards a cRIO power or cRIO code issue.

If you have log files, you can email me. If you don't know my email, PM and I'll give you one.

Greg McKaskle