Skip to content

Electrical Testing with Software

Grant Geyer edited this page Sep 11, 2021 · 2 revisions

Testing with Software

Part of Training.

Testing your board, embedded code, or connection is an important part to verifying proper function of your work. While this may seem daunting, it is actually pretty easy after you learn the setup. NOTE: this will cover testing in the ROV system. Testing your work in isolation with more standalone scripts won't be covered here.

Setup:

  1. Power the router (plug the wall adapter into an output and the barrel jack into the router) and turn it on. It will take some time to boot
  2. Connect the ROV's tether or a ethernet cable directly from the Raspberry Pi to the router and connect to it yourself (either over wireless or ethernet).
    1. Log into the wifi network if doing so. Talk to your friendly, neighborhood software team for the password.
    2. Optional, but highly recommended: plug the internet access ethernet cord from the ceiling into the router's input port (the blue one). This will let you connect to the internet.
  3. ssh into the pi. For ROV X13 Triton, the pi in the logic tube is 192.168.1.3 and the pi in the box is 192.168.1.4. The passwords are the default passwords. You can do this multiple ways:
    • Run ssh [email protected] from a bash prompt
    • Set up a putty connection
    • Use WinSCP (only for file transfer. You'll probably still need one of the above options).

Congratulations! You are now into the pi!

Testing Embedded

There are a number of scripts in the Core software repository (such as these in X13-Core) that are useful for testing embedded code in a similar manner as to how it will be run while in the water. Read through the script you want to run, and run it with python scriptname.py. Many have additional command line arguments that you can read about by running them with -h or --help. If you find yourself needing to edit them, you can do so with nano or vim.

Testing Cameras

In ROV Triton's architecture, cameras are set to stream by default through ffmpeg and ffserver. When on the same network, navigate to 192.168.1.3:8090/status to see the ffserver status page. From there you can navigate the streams (the address of which escapes me right now). These addresses are set in the ffserver.conf file and can be changed.

Seeing Router Connections

Go to 192.168.1.1 (the IP address of the router) and login (with the router username and password given to you by your best friend from the software team (BFFST)). From their if you click connected devices or connections, you can see what is connected to the router.

Clone this wiki locally