they start mjpg-streamer and/or grip on login based on enviroment variables
Isaac wrote more scripts to easily set the variables for the forementioned scripts
Isaac also set the dns addresses of both pis to rpi2-4096-frc.local
Challenges
-Isaac knew nothing about shell scripts before today
Work for Next Meeting
OPEN GITHUB AND SYNC, even if you're not sure you'll be modifying robot code. When meeting is over, COMMIT then SYNC AGAIN. Just do this every meeting.
Find best way to see/modify camera settings. Play with brightness/exposure/etc. to get the best isolation of targets in imagebefore GRIP gets ahold of the stream. Then adjust GRIP file to make the best use of that.
On some websites, they connect the video to the HSV filter twice so that there are two intervals for each. Might want to check this out.
Find way to measure cpu load on Pi. If load looks agreeable with GRIP running full tilt, we can return Jetson.
Get GRIP file to deploy like robot code, from DS->Pi, likely via PSCP & upgrades to our fancyier Wing script
Get mjpeg-streamer & GRIP to run when robot code starts, die when disabled or match over
Find good settings for mjpg-streamer
keep optimizing
Outline new robot code, using WPI commands style
Get second RPi spun up and tested with GRIP, mjpeg-streamer, etc. for practice bot
Check on spike supply and maybe order more
Look for velcro to buy thomas want various strengths/sizes