Awesome write up, I use the Cerevo Liveshell for one car, but really want to add one to another car we race. I find there's issues with the gopro sometimes disconnecting.. So I love the idea of a single unit/device..
Thanks! Yes, I've found that relying on WiFi and/or Bluetooth is a problem, even when the devices are close. We have a bunch of other gear in the car that I'll write up in a separate blog post for telemetry that can be finicky because it's all connected wirelessly.
Any thoughts around making it as a SSH server so you can connect to the car if there's any issues with the camera and restart the unit ?.. My experience is these setups almost never last the entire day of racing without messing with it during a pitstop or two..
I too was concerned about having access to the Raspberry Pi during the race so I had also configured a reverse SSH tunnel to be able to access it behind the mobile hotspot's network address translation layer. I'll write up how this worked on the blog entry.
In the end however I didn't really end up making any configuration changes while the car was on track, but it was nice to have the option.
A couple of questions..
- Can you also get this to save to the SD card at the same time ?
Yes, it's definitely possible by changing the ffmpeg command line to output to two locations. You could even upload to two different RTMP network locations simultaneously like RaceCast.me and FB Live (given enough cellular data speed).
- Can a PI3 run multiple camera's, I was thinking of using it as a cheap second camera too, or is it better to just buy another set of Hardware.. and save the output the the SD card device, and not stream it..
I was using the Raspberry Pi's own camera module, but it would be possible to have it run another simultaneous upload (or record to SD) for a second USB-connected camera as well. You could add a second supervisord service that uploaded this additional feed to RaceCast.me (under a separate RaceCast.me account).