-
Notifications
You must be signed in to change notification settings - Fork 2
Network topology (old)
uakotaobi edited this page Mar 19, 2017
·
1 revision
- In the normal configuration, the router from last year (MAC: AC86743BE0A0) uses two Ethernet ports and a wi-fi connection to work between the driver-station, the RoboRIO, and the NVIDIA Jetson.
- The router connects via wifi to the driver station. This connection allows us to communicate with the robot.
- One Ethernet port (18-24vPOE) is used to connect the router to the RoboRIO. This connection is the intermediary.
- One Ethernet port (802.3afPOE) is used to connect the router to the NVIDIA Jetson. This connection sends information from the Jetson to the rest of the system via the XML Parser.
- The Jetson additionally connects via USB to a USB Hub. This hub connects us to the two cameras we plan on using.
- In this configuration, our router from this year (MAC: AC86746AD620) connects to the game router via wifi. This changes our set-up slightly.
- The Driver station connects to the Game Router via ethernet. The game router controls when each method of the code is run (robotInit, autoInit, telePeriodic, etc.)
- The Game Router then connects to our router via wifi. Information is passed from the driver station, thorugh the game router, to our router.
- Our router has two Ethernet ports, which are used in the same manner as the normal testing version. The RoboRIO is connected via port 18-24vPOE, and the Jetson is connected via port 802.3afPOE.
- The issue occurring during this configuration is that the NVIDIA Jetson is not appearing on the network. The source of this issue is unclear. Possible solutions will be at the bottom of the article.
- In this configuration, we are using the new router (which is configured and therefore does not allow us to connect directly to it via wi-fi), but we do not have access to the game router.
- The RoboRIO port is the same, as per rule R63. Port 18-24vPOE is used.
- This configuration has an Ethernet connection to the driver station via port 802.3afPOE. This leaves no Ethernet port to connect to the Jetson.
- This causes various complications. We cannot work with the Jetson at all, as we are not allowed to have wireless connection at this point. Possible solutions may be related to solutions for the issues with Field Configuration.
- Switches are allowed on the robot. Old routers may be used as a switch, provided that it does not assign IP addresses.
- The proposed plan is to use an old DAP-1522 router and stop it from assigning IP addresses.
- The Router from this year connects via Ethernet to the RoboRIO on port 18-24vPOE.
- Ethernet port 802.3afPOE is then used to connect to the altered DAP-1522 via LAN 1.
- The NVIDIA Jetson is then attatched to the DAP-1522 via LAN 2.
- When off the field, we can use the LAN 3 port to connect the Robot to the Driver Station
- When on the field, the Driver Station is connected to the Game Router via Ethernet. The Game Router then connects to our router via wi-fi.
- How will the use of the switch affect our connection the Jetson? Because it assigns no IP address, the connection would be read as the connection to the switch router, not the Jetson. Food for thought.
To turn one of our old D-Link wireless routers (specifically, the one with a MAC address of C8:D3:A3:46:53:E8) into a bridge:
- Access http: