iroboteducation / root-robot-ble-protocol Goto Github PK

Hi,

I'm using https://github.com/shamlian/root-robot-sdk to control my Root robot and was trying to use the drive arc command, that is listed here in the staging spec.
There is no effect and no response when I run the command.

I went deeper and sent raw data to the robot but I get nothing more.
I was trying the following packet as an example:

[1, 27, 10, 0, 0, 2, 88, 0, 0, 0, 100, 0, 0, 0, 0, 0, 0, 0, 0, 60]

Is there something that I'm not doing well, or is it related to the staging state of the specification?

I have no problem with other commands, like drive distance ([1, 8, 10, 0, 0, 0, 100, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 182]).

Thanks

Hi,

I am implementing the root protocol in a library and I'm facing issues with two responses of the robot.

Command 0.11 - Get Enabled Events Response

I always receive an empty bitfield from this command. The enable/disable event commands work but Get enabled events keeps returning an empty bitfield.

Is this a known issue?

Command 4.1 - Color Sensor Data Response

With this command, I don't know how to handle the color data I receive, either with ADC or mV format. Is there a way to map the data with RGB colors or is it only brightness data?

Also the protocol says that the result for ADC format is on 12 bits but I get significant bits in the 16 bits of the color data.

Thanks

When we get information about the battery state, it would be helpful to know whether it is actively being charged. Root turns off when charging due some toy-specific requirements, but that is not the case for Create 3 or other potential robots using this protocol. I propose we add a charging status byte for Device 14 messages. Something like:
0 = no charger connected (backward compatible with Root)
1 = charging
2 = charging complete

In the future, we could even consider additional states like charging error, fast charging, slow charging, etc. that would be good for the controller to know.

Description from #5 as follows;

Command 4.1 - Color Sensor Data Response

With this command, I don't know how to handle the color data I receive, either with ADC or mV format. Is there a way to map the data with RGB colors or is it only brightness data?

Also the protocol says that the result for ADC format is on 12 bits but I get significant bits in the 16 bits of the color data.

Hi - I am working with some art students who are getting a slew of errors trying to run this BLE protocol.
Is the irobot_edu_sdk available to be downloaded and run locally?

Description from #5 as follows;

Command 0.11 - Get Enabled Events Response

I always receive an empty bitfield from this command. The enable/disable event commands work but Get enabled events keeps returning an empty bitfield.

Is this a known issue?

I guess it's a copy-paste mistake, but I don't understand
https://github.com/iRobotEducation/root-robot-ble-protocol#command-5---play-sweep

I am currently intrgeating the protocol into Terrapin Logo. Questions:

• I am not sure how the color sensors work. Your app seems to use 5 areas, but how would these match to 32 color sensors. Also, how would I use the color light settings, if at all? Any info would be welcome.

• Saying does not seem to work. I tried a simple "HI", but no sound and no response.

Terrapin Logo is a Web app using Web Bluetooth with Chrome 70. I noticed that requesting a device descriptor returns a device with no name, and Chrome's selection dialog displays the bot as Unknown device (oddly enough, this happens on the first connect attempt after a page load; subsequent attempts display the device name just fine). See attached image.

Please also note that no implementation of Web Bluetooth supports listening to advertisements yet.

Regards, Michael

I cannot find the description for navigate command, but I guess it does exist because there is a response with command 17
Command 17 - Navigate to Position Finished Response

Is there any documentation on which commands will work for a rt0? Some are working fine for me (e.g. motor commands) but some are not (e.g. Get Battery Level, Get Position, Get Acceleration). I'm not sure if they are unsupported on the rt0 or if I'm doing something wrong (quite possible!). It would help to know which I should expect to work.

Thanks!

I hope this is something simple that I'm missing, but I can only get my Root to respond to a few motor commands (drive distance and right motor speed). For clarity, here's what I'm sending to the Root for each different command I'm trying:

drive_distance: <Buffer 01 08 00 00 00 00 64 00 00 00 00 00 00 00 00 00 00 00 00 da>
right_speed: <Buffer 01 07 00 00 00 00 64 00 00 00 00 00 00 00 00 00 00 00 00 5b>
rotate_angle: <Buffer 01 12 00 00 00 17 70 00 00 00 00 00 00 00 00 00 00 00 00 99>
reset_position: <Buffer 01 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fa>
drive_arc: <Buffer 01 27 00 00 00 1c 02 00 00 00 c8 00 00 00 00 00 00 00 00 41>

The first two work, and the other three don't. I don't get anything transmitted back from the Root on the failed commands either. I'm assuming maybe my checksum values are wrong, but I'm using the same crc library for generating all the checksums. Any ideas on what I might be doing wrong? FWIW, I have put the robot in ROOT BOOT mode and updated the firmware, just to be sure that wasn't the cause. And I can use the coding website and app to rotate the angle, so the Root definitely works from that perspective. Thanks for any assistance you can provide!