"Pinger" diagnostic program to test robot network.

[PhilBot]

Hi

After configuring my fair share of new FRC2009 networks, I realized that a tool that showed me the current state of my robot network would have been reallllllllly helpful.

So I decided to flex my new LabVIEW muscles and create such a tool.

I've attached the resulting "Pinger" program.

Simply enter your team number at the top and it will continually ping where your various devices should be. Green means OK, Red means Not found.

I find that if you start at the top of the list and work down you can validate your network from the PC to the robot.

I also added a box at the bottom for checking "unconfigured" devices. This can be used to check for any device on the default "192.168.1.x" network. Keep in mind that the PC has to be on this network to see these devices.

Note: your robot may seem to run fine with only some of the BIG LEDs green, but to get ALL the functionality (Dashboard etc) you should strive to get ALL the BIG LEDs green.

[Russ Beavis]

Phil,
Is there any way to "see" the camera that's attached to the other Ethernet port of the cRIO?

Are there any configuration bits that could also be extracted and displayed (eg cRIO status regarding run-on-startup programs, camera configuration settings, cRIO and DS and other software versions)?

Great tool!!

THANKS!!
Russ

[PhilBot]

Phil,
Is there any way to "see" the camera that's attached to the other Ethernet port of the cRIO?


Hi Russ.

I think the cRIO code has to read the camera and route it to the PC, as in the way the dashboard operates. But... That's what the Dashboard is for :)

I just wanted a go/no-go test to let me know the network components were at least ready to run.

Once the network is running, all the other tools can be used.

Phil

[WGRAY]

Great job! used it to verify all my connections. Thanks

[PhilBot]

To make it easier to keep track of program updates, I've added the Pinger program to a white paper I just uploaded.

To get the latest version jump to:

http://www.chiefdelphi.com/media/papers/2177

Or search White Papers for "GaCo Pinger"

Phil.

[keen101]

wow cool program. Could really come in handy. :D

One question though, since this was written in labview, could you release the labview "source code"? Maybe even put in in a VI?

I'd rather have this embedded into the dashboard instead of having to run a separate application. Thanks.

[PhilBot]

One question though, since this was written in labview, could you release the labview "source code"?

I'd rather have this embedded into the dashboard instead of having to run a separate application. Thanks.

I really didn't think anyone would be that interested, but I've added the Source to the White paper. Hoepfully, since you've asked for it, you'll take the time to download, unzip, and view the program.

The latest dashboard (Update 2.0) already includes the code to check your local IP to ensure that it will receive robot data.

I personally don't think that the other ping statuses belong on the dashboard.
Pinger is really only needed to get up and running. Once your network is properly setup, it's not needed anymore. On the other hand, the dashboard is really needed to test your robot functions, and will be constantly changing as you develop your code. Having the extra overhead of all that pinging will just slow it down.

Feel free to add it, but I really think it's best used as a stand-alone program :)

[Mark McLeod]

Very nice, immediately useful application of LabVIEW.
I downloaded the source posted and only got an executable.

[PhilBot]

I downloaded the source posted and only got an executable.

Oops, that was an early zip. The latest one was in a different folder.

I uploaded the latest, but can't seem to delete the original attachment.

Use the one that says "Full Source".

Phil.

[keen101]

cool. thanks.

Having the extra overhead of all that pinging will just slow it down.

I hadn't thought about that. I will keep that in mind. Thanks again.

[Marlfox]

thank you for the pinger!!!I freakin love you :D the only problem is that our cRIO is not pinging back to us, so we must have a problem with the cRIO. were re-imaging it now. I will be back if it doesn't work :)

[lynca]

thank you for the pinger!!!I freakin love you :D the only problem is that our cRIO is not pinging back to us, so we must have a problem with the cRIO. were re-imaging it now. I will be back if it doesn't work :)

I have also seen problems with the cRIO not pinging back in a timely manner. I will ping the cRIO and get "unreachable" 3 or 4 times before the cRio returns a response. During those tests , I can always ping the DS, Router and Bridge with no problem.

[dqmot17]

I was also trying to make a program with a vbs script that does that. It comes to something like this:set WshShell = CreateObject("WScript.Shell")
PC = Not CBool(WshShell.run("ping 10.2.47.6 -n 1 -w 150 " & vSystemIdentifier,16,True))
DS = Not CBool(WshShell.run("ping 10.2.47.5 -n 1 -w 150" & vSystemIdentifier,0,True))
router = Not CBool(WshShell.run("ping 10.2.47.4 -n 1 -w 150" & vSystemIdentifier,0,True))
bridge = Not CBool(WshShell.run("ping 10.2.47.1 -n 1 -w 150" & vSystemIdentifier,0,True))
cRIO = Not CBool(WshShell.run("ping 10.2.47.2 -n 1 -w 150" & vSystemIdentifier,0,True))

If PC = True and DS = True and router = True and bridge = True and cRIO = True Then
'successful
msgbox "It is Working",vbOkOnly
end if

if not PC = True and DS = True and router = True and bridge = True and cRIO = True then
'Unsuccessful ping
msgbox "Somthing is not Working"
End If
If PC = False then
msgbox "Please fix PC adress",vbRetryCancel
End If
If DS = False then
msgbox "Please fix DS adress",vbRetryCancel
End If
If router = False then
msgbox "Please fix Router adress",vbRetryCancel
End If
If bridge = False then
msgbox "Please fix bridge adress",vbRetryCancel
End If
If cRIO = False then
msgbox "Please fix cRIO adress",vbRetryCancel
End If