[chfritz]

Very cool! But I think we can help you improve your video-streaming and teleop (it seems to be pretty low frame rate in the demo). We've built the probably best remote teleop solution for robotics in the market today and it can be embedded anywhere (white-label). Want to get in touch to discuss? You can find my linkedin in my profile.

[apeytavin]

the video stream will get a lot of improvement for sure! the teleop is pretty good already i believe, but happy to chat further. feel free to dm / join discord

[chfritz]

Don't underestimate the challenges of making remote-teleop work reliably and efficiently with low-latency via the Internet: https://transitiverobotics.com/blog/streaming-video-from-rob....

[apeytavin]

webrtc for video stream is what we have in the pipeline for improving the stream yep!

[chfritz]

with congestion control, packet loss mitigation, hardware accelerated encoding, multiple streams, teleop commands on the same channel (required for safety)? Do you host your own TURN server? My point is that robotics companies should focus and push the envelop on the application of their product, not reinvent the wheel on infrastructure and tooling.

[apeytavin]

i don't know if it is that necessary for just phone control, wdyt?

do you have anything plug-and-play for jetson nano?

[chfritz]

I assume you mean Orin Nano? (Jetson nano is EOL and only supports Ubuntu 18). Yes, we have users that run on Orin Nano and it's plug-and-play on any hardware. However note that the Orin Nano doesn't have hardware encoders, so it will take CPU cycles to encode the video, making it a less then ideal choice for teleoperated robots. Cheaper boards like the Orange Pi 5 are a better fit.

All the webrtc-features really only become relevant when you want to control the robot over the Internet, i.e., not just locally where you can assume reliable network.