No connection through Ethernet jacks on DS

[mprikril]

I posted a thread on the FIRST forum earlier this week (before I posted here) and have heard nothing back from anyone at FIRST or NI

To answer the other questions, I did not flash my cRIO, only update the firmware on the DS and changed my team number.

[Mark McLeod]

Originally Posted by mprikril

I did not flash my cRIO, only update the firmware on the DS and changed my team number.

Argggggg.
(I mean that in a nice way of course)

They must both be done at the same time or they won't communicate.
The OTB version on the cRIO doesn't talk to the firmware upgrade on the DS.

[mprikril]

I had this problem BEFORE I update the DS firmware.

The OTB benchtop tests did not work before that was done.

I will flash the cRIO and see what happens

[Mark McLeod]

Well, you can never go back to testing the OTB, so updating the cRIO will at least get you back to where you can debug the original Jaguar problem.

With the cRIO updated you'll get an additional status light on the Digital Sidecar to help tell you what's happening. A fast blink means no communication, a slow blink means it's in Disabled mode, and a solid light means it's enabled in either Teleop or Auto modes.

One reason the Jaguars will blink is if they aren't connected to an activated PWM output. With the default code you're now downloading I think just pwms 1&2 on the first cRIO digital module are enabled. I was with a team last night where a third party must have moved the DB37 cable to the second module and no one had noticed. As a result their Jaguars were blinking too.

There are lots of combinations that will prevent the code from operating as advertised (including failed hardware), so work your way through triple checks without introducing new complications.

[mprikril]

Originally Posted by Mark McLeod

Well, you can never go back to testing the OTB, so updating the cRIO will at least get you back to where you can debug the original Jaguar problem.

With the cRIO updated you'll get an additional status light on the Digital Sidecar to help tell you what's happening. A fast blink means no communication, a slow blink means it's in Disabled mode, and a solid light means it's enabled in either Teleop or Auto modes.

One reason the Jaguars will blink is if they aren't connected to an activated PWM output. With the default code you're now downloading I think just pwms 1&2 on the first cRIO digital module are enabled. I was with a team last night where a third party must have moved the DB37 cable to the second module and no one had noticed. As a result their Jaguars were blinking too.

There are lots of combinations that will prevent the code from operating as advertised (including failed hardware), so work your way through triple checks without introducing new complications.

I am getting a "no communication" blink on the Jaguars - regardless of the position of the enable switch on the DS

If I connect my laptop to port 1 on the cRIO, I can ping 10.0.0.2. If I connect my laptop to either jack on the DS, I get no response pinging 10.0.0.5 (or 10.0.56.5 if the team number is changed).

[Mark McLeod]

That's not good.
The Jaguars are the least of it.
Just work at getting the "No Comms" message off the DS.

You should be able to at least ping the DS while connected to the ETH2 port.
I assume your PC is set to 10.0.56.6
PC mask set to 255.0.0.0
Disable any firewall you may have running for testing.

You should have your cRIO IP address set to 10.0.56.2 and your DS set to 10.0.56.5 at this point in the testing.
DS ETH1 port connected to the cRIO port 1


P.S.
When you updated the cRIO with the FRC cRIO Imaging Tool the settings you were supposed to use would not have resulted in an IP address of 10.0.0.2

Under "Format Controller"
Select Image = FRC_2009_v2.zip
Device name = FRC-cRIO-56
Team ID = 56

[mprikril]

Originally Posted by Mark McLeod

That's not good.
The Jaguars are the least of it.
Just work at getting the "No Comms" message off the DS.

You should be able to at least ping the DS while connected to the ETH2 port.
I assume your PC is set to 10.0.56.6
PC mask set to 255.0.0.0
Disable any firewall you may have running for testing.

You should have your cRIO IP address set to 10.0.56.2 and your DS set to 10.0.56.5 at this point in the testing.
DS ETH1 port connected to the cRIO port 1


P.S.
When you updated the cRIO with the FRC cRIO Imaging Tool the settings you were supposed to use would not have resulted in an IP address of 10.0.0.2

Under "Format Controller"
Select Image = FRC_2009_v2.zip
Device name = FRC-cRIO-56
Team ID = 56

I realize the issue of not being able to ping the DS. I have tried it with my PC at 10.0.0.6 and 10.0.56.6. Similarly, I have tried pinging both 10.0.0.5 when the team number was set to 0000 and 10.0.56.5 when the team number was set to 56.

When I flashed the cRIO, I did set the team number and thus the IP to 10.0.56.2. I was mentioning some work I did earlier, before flashin the cRIO when the IP was still set to the default of 10.0.0.2.

All of this makes me think something is broken inside our DS.

[Mark McLeod]

I agree with you on your diagnosis. I'd talk to FIRST (Kate) about returning the DS for warranty repair.

[mprikril]

Originally Posted by Mark McLeod

I agree with you on your diagnosis. I'd talk to FIRST (Kate) about returning the DS for warranty repair.

Started that process since just after I posted the first time and noticed that it might not be a set-up issue.

It just stinks that we won't be able to do anything for several more days

Ah well, if it was easy then everyone would do it. Many thanks for the help - we at 56 appreciate it