|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
|||
|
|||
|
Re: Connected to Radio, Not Roborio
This may be redundant, but:
Did you statically set the IP address of your RoboRIO to 10.te.am.2? Did you upgrade the firmware and image on the RoboRIO (two upgrades)? Can you ping roborio-TEAM#-frc.local from your DS? |
|
#17
|
|||||
|
|||||
|
Re: Connected to Radio, Not Roborio
We'll be doing a lot of testing today, but I can say our team has experienced this issue several times this weekend.
|
|
#18
|
||||
|
||||
|
Re: Connected to Radio, Not Roborio
Quote:
I am not sure if we upgraded firmware on roborio, I will need to check that. I know we imaged the roborio, but not sure about both steps. Thanks, will need to verify. |
|
#19
|
||||
|
||||
|
Re: Connected to Radio, Not Roborio
Could someone experiencing this problem try flushing their mDNS cache?
Instructions here: https://documentation.cpanel.net/plu...t/view/2719759 Let us know if this helps, I saw this problem last year and it had me flummoxed. Had to turn it off and on again. |
|
#20
|
||||
|
||||
|
You also need to make sure your Ethernet cable is plugged into the farthest point to the right from the power supply, the one marked 802.3af POE
|
|
#21
|
|||
|
|||
|
Re: Connected to Radio, Not Roborio
Quote:
|
|
#22
|
|||
|
|||
|
Re: Connected to Radio, Not Roborio
|
|
#23
|
|||
|
|||
|
Re: Connected to Radio, Not Roborio
Huh I must have missed that part of the update, thanks. I'll get the students to check it's in that port...
|
|
#24
|
|||||
|
|||||
|
Re: Connected to Radio, Not Roborio
That's not what the official advice says. Team Update 8 in particular instructs teams having problems to use the "18-24v POE" port adjacent to the power connector.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|