Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to detect docks? #10

Open
Vela-zz opened this issue Nov 1, 2024 · 0 comments
Open

How to detect docks? #10

Vela-zz opened this issue Nov 1, 2024 · 0 comments

Comments

@Vela-zz
Copy link

Vela-zz commented Nov 1, 2024

I subscribe events under DockTracker, it hardly return anything,
it always return event like,
{ "timestamp": "2024-11-01 07:45:25", "class": "DRDockTracker", "key": "docks", "data": { "docks": [] } }
only in rare chance, the docks attribute under data will have data like {id: xxxx, 'x': ...., 'y', ....}, in that time, the id of docks always change between the event frame.
{ "timestamp": "2024-11-01 08:02:58", "class": "DRDockTracker", "key": "docks", "data": { "docks": [ { "id": 448832, "x": -0.5798128884851664, "y": -0.2213428348470345, "angle": -0.24407396378455457, "health": 30, "detections": 84, "docking": false, "forkBehind": true } ] } }
I wonder how the robot detect the dock? and what the attribute means like detections, docking, forkBehind and health ?

Another question is that, when I want to use navigate.target command, and send request body like {'dock':'forward', 'dockId': [ID OF DOCK]}, cause the system reboot. what is the right format of the body to the navigate.target command to let it go back to the dock?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant