dimensionalOS / dimensionalOS/dimos
Go2 lan auto discovery & retry in connection.py
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
now with go2 discovery cli https://github.com/dimensionalOS/dimos/pull/1990
we can utilize lan autodiscovery in connection.py if IP isn't specified
connection.py should also retry and not die if go2 rejects a connection attempt (since this is flakey on go2)
active question -
if we discover more then one robot, should we let a user choose? should we write a fancy configurator that has a IP selection menu? atm go2 has a clock configurator registered
unitree/go2/blueprints/basic/unitree_go2_basic.py
.configurators(ClockSyncConfigurator())
(there is no need for configurators if annoying to implement, you can just print all IPs discovered and auto-connect to first one)
Synced from DIM-858 by summer
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with connection.py and the Go2 discovery CLI changes in PR 1990. Read unitree/go2/blueprints/basic/unitree_go2_basic.py and its ClockSyncConfigurator registration to understand the existing configurator flow. Done means discovery works when no IP is supplied, rejected connections are retried, and the behavior for multiple discovered robots is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking, robotics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100