←back to thread

217 points mfiguiere | 1 comments | | HN request time: 0.338s | source
Show context
ethagknight ◴[] No.41842902[source]
To be honest, the autonomous control of the robot seems like the easier part of the equation. (doing it safely in a room with guests, unguided... thats another matter). The physical limitations and packaging are a big challenge, and I dont think I saw Optimus lift anything remotely heavy.. just pull a beer tap.. a decision that probably speaks volumes about current limits of the technology.

To apply my first point to reality: put an Optimus in its current state/capability, on a commercial 0-turn lawn mower, plug Optimus into the mower's power takeoff, and have someone in another country remotely pilot the mower. That right there is worth every commercial lawn service having at least one on their crew TODAY.

The appeal of hot swapping an operator real time on the equipment you already own, whether it's a push lawn mower or a huge mining truck, provides enormous value right out of the gate. Especially in tasks where the Optimus can handle 90% of the task autonomously but needs to step aside or oversight for the last 10% of the job. Compare to a business model that requires purchase of all new very expensive and unique equipment.

replies(4): >>41843438 #>>41843485 #>>41843490 #>>41843507 #
mysteria ◴[] No.41843507[source]
I would imagine latency would be an issue if companies were considering teleoperation using staff in a country with cheaper labor. For example I work with people in India and China and they regularly complain about the several hundred ms of latency they get when using their American VDIs. That off the shelf lawn mower is going to be hard to control safely with all that delay, and there's also the risk of connection drops and the like. You would need a specialized mower with collision detection/etc. to handle this, and at this point you might as well discard the robot and just have a remotely operated mower instead.

However there are cases where this can work well, say in a factory handling dangerous chemicals with the teleoperator in an adjacent room. Or maybe it's doing some sort of task where delays and connectivity loss are acceptable.

replies(2): >>41843595 #>>41843775 #
Terr_ ◴[] No.41843595[source]
Let's see, New York to Mumbai over the Earth's surface is maybe 12,500 km, assume a direct fiber optic cable where light travels noticeably slower than in a vacuum at 200,000 km per second... So a minimum of 62.5 ms one way with the best terrestrial equipment.

While one can play network games at 125 ping, it relies rather heavily on tricks that only work in a virtual environment. (Back in the '90s I used to play with 300 ping, no latency compensation, uphill both ways.)

replies(1): >>41843895 #
1. mysteria ◴[] No.41843895[source]
Realistically it's in the several hundred range. I just did a ping using Vultr's Looking Glass from New Jersey to Mumbai and got around ~240ms on commercial fiber. For people working from home in India (with cable/DSL overhead + distance from the IX) connected to servers in LA I regularly see 300-400ms.

Also keep in mind in a VDI or teleoperation setting there's not only network latency but additional delay from the video encoding, compression/packetization, and decoding on the other side plus a bit of buffer. Honestly I think cloud gaming is a good test case for this - and in my experience that only works well when you have fiber and have the game server in the same city as you (basically <10ms).