no idea what GUI backend the hardware client uses, but something like wine might be able to run it since the communication is (in theory) over usb
Does anyone know the IP address of the roboRIO while connecting via Ethernet directly to it (without using the radio)?
Itās dynamic. When you do that, it negotiates a Link-Local address. Note this requires the computer Linux to also have link-local enabled. You should use mDNS (e.g. roborio-TEAM-frc.local) to resolve the actual IP.
I made an install script that installs WPILib and OpenDS. See GitHub - ethanc8/FRCLinuxDevKit for more information.
Does anyone know whether the new radio will mess things up, or if the driver station communication protocol will change for 2025?
For the new radio, Iād hope that it does the IP address setting/DHCP/mDNS correctly so that we could easily connect to the roboRIO, but Iām not sure if that still works (my current strategy is to wire the laptop to the radio and the radio to the roboRIO, just using the radio as a router).
If the driver station communication protocol changes, then OpenDS would need to be modified to support that. Is this protocol solely handled by NI Driver Station, or is WPILib also involved in any changes to this protocol?
I know for certain that the radio itself hasnāt particularly changed from the userās perspective. I connect, and I get an ip following the same scheme used in the years past. mDNS works perfectly fine, too, and I think it runs a local dns server for devices, as I was able to connect via (.lan).
AFAIK, NI mostly handles the DS protocol. WPILIb team would likely be notified a bit ahead of time to make changes if necessary, but I personally doubt anything significant would change, minus potentially for 5-digit team numbers if thereās even anything to change.
1 Like