Remote Development

As the hardware needed for all of our driver development is almost complete, it is important that a remote development option is available to prevent strain on our limited space. Before getting started, it should be noted that remote development requires comfort with the command line or the ability to setup an ssh workflow from inside your IDE of choice.

Conceptually, the remote workflow functions over an SSH tunnel kept open from MEHQ into the engineering network so that it can be accessed via CAE. However, this means that you must have access to the CAE computers to work remotely, and if you do not, send a slack message to @ezraboley so that we can set you up with one.

How To Connect

Some of the steps below will have numbers hidden for security reasons. If you are following this tutorial, great! Just message Ezra Boley, Rohan Daruwala, or Eric Udlis for the specific values.

$ ssh ${CAE_USERNAME}@tux-44.cae.wisc.edu 
$ ssh pi@localhost -p ${HIDDEN_PORT}
$ password: ${HIDDEN_PASSWORD}
$ ssh bone1  # For the beaglebone 1, or ssh bone2 for the beaglebone 2
$ echo "You made it! Good job!"

Choosing a Beaglebone to use

Depending on your hardware requirements, one of the beaglebones may suit your needs better than the other. The capabilities of each beaglebone are as follows:

• Beaglebone Black 1
  • CAN
    • BMS is attached however it must be manually turned on
  • More soon!
• Beaglebone Black 2
  • I2C
    • XSens IMU
    • BMP 180
  • More soon!