No connection through Ethernet jacks on DS

[mprikril]

We seem to have a problem with our Driver's Station.

We were running through the steps required in the benchtop test and can not get past section 2.3.1.2. The DS does not appear to be communicating with the cRIO via the ethernet cable. Flipping the switch on the dongle changes the display of the DS to "Enabled" but the cRIO does not respond - the Jaguars still blink yellow.

The equipment is wired as required and we have LEDs indicating the appropriate devices are powered correctly. These were then verified with a meter.

I believe the ethernet jacks on the DS are not working because I can comminicate directly with the cRIO using the orange crossover cable connected directly to my laptop. I can not communicate to the DS from my laptop nor can I communicate the the cRIO by connecting both the cRIO and my computer to the DS as noted in the documentation.

I get no respose if I ping the IP for the DS.

I see no blinking LEDs on the ethernet jack of my laptop when I connect it to either Ethernet jack of the DS.

How do I know if my unit is damaged? Additionally, what we do if we were shipped a defective DS?

Many thanks

[mprikril]

Just as a note, we have tried this with multiple ethernet cables. I can verify that an ethernet cable works by connecting my laptop to a wall jack. I then use the same cable to connect to the DS and it does not work.

[tdlrali]

Is this before or after updating the DS?
(You could always try re-flashing the update by just repeating the process).

[mprikril]

It didn't work from the start, so I updated the firmware and it still didn't work

[Jim E]

I would take your concerns to the FIRST forum that deal with the new control system. Perhaps they can provide more information and describe the procedure to receive an RMA number.

[tdlrali]

@"I updated the firmware" - Did you update the cRIO, and set all the team numbers/IPs?

[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).