|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Robot Communication and External CPUs during Competitions
Our team is doing vision processing for the first time, using an Nvidia Jetson TX1 to do our vision processing. Currently, we are connecting the camera and the Jetson to the network that we're setting up using the radio in our lab. To run the Python OpenCV script on the Jetson, I simply SSH into the Jetson terminal from the driver station and run it before starting the robot program.
I'm a little unsure of how the network is set up at the field during competitions, and I know that radios cannot setup their home network on the field. I was wondering if I will still be able to SSH into the Jetson using its static IP and if I can use the same IP of the camera as I did when it was connected to the radio's network. Also, is it legal to run a separate process such as SSH on the driver station or does the robot code need to start the Python script on the Jetson automatically? |
|
#2
|
|||
|
|||
|
Re: Robot Communication and External CPUs during Competitions
Why wouldn't you want to either start the program on startup (whenever power is on) or to start when a command is sent over network tables?
|
|
#3
|
|||
|
|||
|
Re: Robot Communication and External CPUs during Competitions
Quote:
Quote:
Quote:
If you have problems with your DS on the field, they may give you the Stock driver station to use. That will not have your other programs loaded onto it. If you are planning for all contingencies, don't assume you can run SSH from the Driver Station. Have the Jetson automatically start running the program upon bootup. |
|
#4
|
|||||
|
|||||
|
Re: Robot Communication and External CPUs during Competitions
Quote:
|
|
#5
|
|||
|
|||
|
Re: Robot Communication and External CPUs during Competitions
How can I run a program on startup?
|
|
#6
|
|||
|
|||
|
Re: Robot Communication and External CPUs during Competitions
Unless he's using SSH while connected to the FMS, he should be fine since you have to plug in with Ethernet to connect to the robot at events anyway.
|
|
#7
|
|||
|
|||
|
Re: Robot Communication and External CPUs during Competitions
Most teams place their robot on the field in a powered off state. Needing to tether while powering on is not advisable.
|
|
#8
|
|||
|
|||
|
Re: Robot Communication and External CPUs during Competitions
I didn't even notice this was on the field. I thought this was just for general maintenance. In that case, I would go with everyone else and recommend an autorun script and a static IP.
|
|
#9
|
|||
|
|||
|
Re: Robot Communication and External CPUs during Competitions
Quote:
Definitely not advisable as it won't be allowed once the robot is on the field excepting an official Field Timeout if the robot is in back-to-back matches (immediate replay or in Playoffs). |
|
#10
|
|||
|
|||
|
Re: Robot Communication and External CPUs during Competitions
Well, the Jetson eLinux (which I've never used) is basically Ubuntu 14.04 (which I do use) so I'd guess add it to the /etc/rc.local script before it reaches the "exit 0" line.
/path/to/program.py & The ampersand disconnects it from the terminal and lets it run the background. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|