Interesting. I thought layer 3 routing was required to get that to work. But I guess if the gateway is 10.0.100.2 for the DS’s and the FMS, I guess that can cross over the vlans inside the AP.
Yes. There is layer 3 routing, but, that’s handled at the AP instead of the Cisco switch.
The DS will have 10.xx.yy.4 as their gateway (the AP)
The FMS server will have 10.0.100.2 as its gateway (the AP)
Ah. It wasn’t clear in those release notes that it also did the layer 3 routing. That’s very helpful.
I just tried connecting, and I believe I am doing something wrong, but not sure what:
What do you think? Am I missing something? Do I need to configure something in the DS?
I have commented out #836-#840 lines in the arena.go file and rebuilt CA
(I am using an HP switch, not a Cisco switch, and I haven’t actually connected the VH-109 to the switch, but I still think I did something wrong).
I’m not networking expert so others please correct me, but based on the previous two posts by @kiettyyyy and @Thad_House , the VH109 programmed as a practice access point (VH-113) does the layer3 routing between VLANS so it must be plugged in for the DS and CA server to see each other’s traffic.
I’d keep going if I were you!
2 Likes
Does this setup require reconfiguring manually the teams for each driver station before each match?
It requires assigning teams to Driver Stations via the UI in Cheesy Arena that runs Test Matches.
2 Likes
Here’s what you missed.
Configure port 24 (the one connected to Cheesy Arena) to be an access port on your admin VLAN (looks like you are using 99)
Port 23 should be configured as a trunk with your admin VLAN (99 in this case) set as the native VLAN.
It will work. We have done this in our test lab at work. In our case we had an old box and lots of NIC cards laying around, plus we wanted to run other stuff on the “router” box (DNS, DHCP, etc) – so it made sense for us. If none of that is true, the $26 box from Amazon looks pretty appealing .
1 Like
Thanks for the help!
It works for me now, I can use the CA UI to start/abort a match with “FMS connected” message at DS but I tried to disconnect everything and reconnect it and then something strange happened, the driverstation could Enable/Disable the robot.
As you can see in the image below, there is communication between the robot and the DS and its going threw the switch and the FMS doesnt recognize it:
When I look at the CA terminal it tells me that 5987’s DS has successfully connect at R2. But, the CA UI show the connection as “red” as you can see below:
Here is another picture showing that I am able to enable/disable the robot:
What am I doing wrong?
I assume you are running the latest version of the firmware?
@kiettyyyy Could this be the missing port restrictions?
I am running the latest CA and the latest (beta) version of VH-109/113.
For me, the interesting part is what changed when I turned the machine off and then back on. Everything looks the same, but the CA doesn’t recognize something
The beta says the firewall is disabled. So I think its expected.
I really do wish the firewall was just configurable options. Theres basically 4 useful configurations, and it’d be nice if every build supported all 4, and it’d be easy to switch between them without having to guess which firewall whatever build of the firmware you’re on is using.
2 Likes
The Practice AP firmware doesn’t have a firewall, which means the DS can talk to the robot without being controlled by FMS.
Is there a way to fix this issue?
The firewall isn’t a requirement here. We had it completely off in 1678’s case.
What I’d check and see:
- Is the Cheesy Arena server assigned to 10.0.100.5?
- Is the Cheesy Arena server setup with a netmask of 255.255.255.0 and gateway of 10.0.100.2?
- Are the driver stations setup with DHCP? If so, are the assigned gateways 10.xx.yy.4?
- Can the driver stations ping 10.0.100.5?
Yes
Yes
Yes and the DS can ping 10.59.87.4. Do I need to manually assign the ip/getway of the DS?
I dont remember for sure but I belive the answer is no.
Double check that the DS has a gateway of 10.59.87.4. If you can’t reach 10.0.100.5, the driver station will not show “FMS Connected”
@DavidMasin does say he gets the FMS connected message, at least initially? But then when he unplugged and repluggs the DS in, it reverts to and maintains local control.
@DavidMasin is this description accurate?
I am having the exact same problem as @DavidMasin although on CA the “DS” and “Rbt” columns are gray.
I can enable the robot through ds. The fms computer and ds have the correct ip and gateway settings that were mentioned. The ds doesn’t show “fms connected” and I am not able to ping 10.0.100.5.
I used a network analyzer on the fms computer and saw that it receives a ping request then sends a response but, the ds does not receive the response.