You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi and thanks a lot for the effort in trying to get an interface to the Robomow!
I was very happy to learn that you already wrote some code for NodeJS, which I discovered after trying to convert the Android code myself first. 😅
I have successfully connected and authenticated with the robot, but then I can't get it to do anything. I try to fo forward, backward etc but nothing happens - even though the command appears to be sent. Any idea what I'm doing wrong?
On another note, maybe create a seperate repo for creating this as a Node module? I would be willing to help and collaborate something. What method did you use to reverse engineer the protocol?
Update: Renamed to reflect the real issue.
The text was updated successfully, but these errors were encountered:
Hey i'm also interested to the node implementation and what you used to find the corresponding commands for forward, backward, left and right. I would be interested to start, stop and send the robomow home, but i was not able to capture the traffic from my android phone using the Bluetooth HCI snoop log.
ciryon
changed the title
Robot won't move
Seperate node repo
Apr 12, 2020
Hi and thanks a lot for the effort in trying to get an interface to the Robomow!
I was very happy to learn that you already wrote some code for NodeJS, which I discovered after trying to convert the Android code myself first. 😅
I have successfully connected and authenticated with the robot, but then I can't get it to do anything. I try to fo forward, backward etc but nothing happens - even though the command appears to be sent. Any idea what I'm doing wrong?
On another note, maybe create a seperate repo for creating this as a Node module? I would be willing to help and collaborate something. What method did you use to reverse engineer the protocol?
Update: Renamed to reflect the real issue.
The text was updated successfully, but these errors were encountered: