← Table of Contents

CAVe-in-a-Box Setup and Test

Items Needed

• CAVe-in-a-Box.
• Optional: External Monitor.
• Optional: Keyboard + Mouse.
• Optional: External Computer.

Basic Setup

1. Using the acceptance checklist, make sure all antennas and devices are firmly fastened to the box.
   1. Mark off each unit on the checklist.
2. Connect CAVe-in-a-box surge protector to AC power source.
3. On the back of the CAVe-in-a-box, turn on the surge protector.
   1. All units within the CAVe-in-a-box will power on.
   2. Component images and names are in the Component Names document.
   3. Mark results in checklist.
4. Connect Mobile Kit to respective power source.
   1. All units within Mobile Kit will power on.
   2. Mark results in checklist.
   3. After a few seconds, all unit LEDs will be powered on.
   4. Check each unit and mark results on checklist.
5. For the other sections, either an external monitor and keyboard + mouse can be plugged into the NanoPi/V2X-Hub computer or an external computer can be connected to the network switch.
6. The NanoPi has an Operating System and the V2X-Hub pre-installed.
   1. If desired, the instructions for setting both up can be found in the NanoPi V2X-Hub Setup document.
   2. Pre-configured NanoPi Login Information:
      1. Username: pi
      2. Password: pi

Traffic Signal Controller

The following steps show which Traffic Signal Controller settings must be changed at a minimum. Every intersection has a different setup. Therefore, some settings are only examples.

1. The network configuration settings must be changed to communicate with the V2X Hub
   1. Address: 192.168.0.92
   2. Net Mask: 255.255.255.0
   3. Gateway: 192.168.0.1
   4. Ping Server: 192.168.0.146
   5. Refer to figure 8.

2. The Phase Order settings can be found on the home page. Select the symbol and adjust to match your intersection’s phase order.
   1. Barriers separate active phases.
   2. Tap on a phase symbol or empty box to view edit menu.
   3. Refer to example in figure 9.

3. In the Timing Plans settings, all the separate tabs, seen in figure 9, can be changed to match your desired signal timing.

4. There are many other settings available to be changed. Not all need to be adjusted but can be to reflect your desired SPaT messages.

Network Setup

Users connected to the Wireless Router or the LAN Network Switch with an external PC/tablet can ping other devices within the network.

1. Attempt to ping each device within the CAVe-in-a-box. Refer to figure 11.
   1. Example: ping 192.168.0.1.
   2. To stop ping process: <Ctrl>C.

2. External Kit IP addresses are checked later in the process.
3. Check off the box indicating correct IP/Port combinations.

V2X Hub + SPAT Plugin

1. Using the CAVe-in-a-box tablet, open an internet browser and go to:
   1. https://192.168.0.146:19760/
   2. Accept the credentials on the page. Refer to figure 12.

2. Open a new tab and go to:
   1. 192.168.0.146
   2. If using an external computer, you will have to change the IP address in the text box to:
      1. 192.168.0.146
      2. Default is 127.0.0.1 if logging in from the Nano Pi.
      3. Refer to Figure 13 for the text box.
3. Login using:
   1. Username: v2xadmin
   2. Password: V2xHub#1234
   3. Refer to figure 13.

4. Once logged in, Enable the SPaT plugin if it is not already enabled. Refer to Figure 14.
   1. If SPaT is not listed as below, the Enabled, Disabled, and External filters may be toggled on or off to show/hide plugins
   2. Check “Enable SPaT Application” in acceptance checklist.

5. Click on the SPaT row to expand it:
   1. Expand the Configuration row and ensure the values match figure 15.
   2. The SignalGroupMapping section is valid for any standard 4-way intersection.
      1. It must otherwise be changed to match your intersection’s SPaT settings.

6. Select the Messages tab at the top to view the messages being received.
   1. The SPaT-P Subtype will eventually reach a 100 Average Interval.
   2. Check off results in acceptable checklist.
   3. Refer to figure 16.

MAP Plugin

To use the MAP plugin in V2X Hub, a map file must be saved in the V2X Hub file path. The map file is an UPER string saved as a .txt file. An example map file is provided in the MAP folder. If desired, a new map file for an intersection may be created following the ISD MAP Tool instructions. An internet connection is required for creating a MAP. Skip to step 5 if using the provided MAP.

1. Following the ISD Message Creator tool instructions, move your file into the V2X Hub computer.
2. Via USB flash drive:
   1. Insert your USB containing the folder into the computer.
   2. Move the file to one of the locations provided in steps 3 and 4
3. Via Ethernet:
   1. Connect external computer to kit’s network switch.
   2. Change external computer’s wired settings to be within the CAVe network.
   3. Open a terminal in your external computer.
   4. cd <directoryContainingFile>
   5. sudo scp file_name pi@192.168.0.146:/home/pi/V2X-Hub/configuration/arm64/MAP/
   6. If prompted: Yes
      1. Note: If an error appears, simply copy and run the recommended command
   7. Password: pi
4. If your kit does not contain a single-board computer (NanoPi, RaspberryPi, etc.) follow for amd64:
   1. cd <directoryContainingFile>
   2. sudo scp file_name <username>@192.168.0.146:/home/<username>/V2X-Hub/configuration/amd64/MAP/
   3. If prompted: Yes
   4. Password: <password>
   5. Username and Password are noted within the box, due to various computers being used
5. Return to the Plugins tab in V2X Hub and ENABLE the MAP plugin if it is not already enabled.
6. Check “Enable MAP Application” in acceptance checklist.
7. Click on the MAP row to expand it.
8. Expand the Configuration row and ensure the values match figure 17.
9. Change the file name in the Value section to match your .txt file.

10. Select the Messages tab at the top to view the messages being received.
11. The MAP-P Subtype will eventually reach a 1000 Average Interval.
    1. Refer to figure 16 from the previous section.
12. Check off results in acceptable checklist.

DSRC Message Manager

1. ENABLE the DSRCMessageManager plugin if it is not already enabled. Refer to figure 18.
   1. Check “Enable DSRCMessageManager Application” in acceptance checklist.

2. Open a Terminal and enter:
   1. ssh rsu@192.168.0.40
   2. If prompted to continue connecting, enter: yes
   3. Password: rsuadmin
   4. Refer to figure 19.
3. The Terminal is now logged into the MK5 RSU. Type:
   1. sudo fim –l
   2. Refer to figure 19 for an example output.

4. The firmware should point with “AR” to mk5-15.Release.69988-RSU.sqsh. or a later release
   1. Refer to figure 19 above.
5. To ensure GPS is running, enter:
   1. date
   2. The output should be the current date and time.
   3. If date is not correct, move box to a location with better signal.
6. To ensure Map and SPaT messages are being transmitted from the RSU, enter:
   1. ifconfig
   2. From the output, interfaces cw-mon-txb will be seen in the list.
   3. Refer to figure 20.
   4. Run: tcpdump –i cw-mon-txb –xx | grep “00 13”
   5. Stop the process with <Ctrl>c.
   6. Refer to figure 21 for output.
   7. Run: tcpdump –i cw-mon-txb –xx | grep “0012”
   8. Stop the process with <Ctrl>c.
   9. Refer to figure 22 for output.

7. If neither command runs the correct output, refer to RSU document for troubleshooting.
8. Verify forwarding BSM and Mobility messages are set:
   1. The RSU forwards BSMs—received from the OBU—over to V2X Hub, using port 26789.
   2. tcpdump port 26789
   3. Refer to figure 23 for output.

Message Receiver

To ensure BSMs are being received by V2X Hub, transmission from the OBU is first tested.

1. Using the tablet or an external computer, connect to the CradlePoint router using the information provided inside the external kit.
2. Follow the separate instructions provided to test the BSM transmission from the OBU.
3. Once BSM transmission is verified, open V2X Hub on the NanoPi.
4. Enable the MessageReceiver plugin if it is not already enabled.
   1. Refer to figure 24.

5. Click on the MessageReceiver plugin to expand it.
   1. Expand the Configuration row and ensure the values match figure 25.

6. Navigate to the Messages Tab and verify that BSMs are being received.
   1. The BSM subtype will eventually reach 100 average interval.
   2. Refer to figure 26.

Previous | Next