ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A answers.ros.org

Mismatched protocol version in packet: lost sync or rosserial_python is from different ros release than the rosserial client

indigo

#1

Hello Everyone,

I am new to ROS, I would like to ask for help with my problem:

I am using Teensy 3.6, I always have problem with communication, I fixed some and last week It was working normally. This week I start to receive this error when I run my Teensy as ROS node

[INFO] [WallTime: 1513632615.825940] Protocol version of client is unrecognized, expected Rev 1 (rosserial 0.5+)
[INFO] [WallTime: 1513632616.391569] wrong checksum for msg length, length -257
[INFO] [WallTime: 1513632616.391837] chk is 4
[INFO] [WallTime: 1513632616.955837] wrong checksum for msg length, length 4
[INFO] [WallTime: 1513632616.956110] chk is 255
[INFO] [WallTime: 1513632617.520817] wrong checksum for msg length, length 4
[INFO] [WallTime: 1513632617.521132] chk is 255
[INFO] [WallTime: 1513632618.092081] wrong checksum for msg length, length 4
[INFO] [WallTime: 1513632618.092400] chk is 255
[INFO] [WallTime: 1513632618.653598] wrong checksum for msg length, length 4
[INFO] [WallTime: 1513632618.653886] chk is 255
[INFO] [WallTime: 1513632619.218930] wrong checksum for msg length, length 4
[INFO] [WallTime: 1513632619.219191] chk is 4
[INFO] [WallTime: 1513632619.780296] wrong checksum for topic id and msg
[INFO] [WallTime: 1513632620.348411] wrong checksum for msg length, length 4
[INFO] [WallTime: 1513632620.348672] chk is 4
[INFO] [WallTime: 1513632620.910055] wrong checksum for topic id and msg
[INFO] [WallTime: 1513632621.474895] wrong checksum for msg length, length 0
[INFO] [WallTime: 1513632621.475235] chk is 127
[ERROR] [WallTime: 1513632622.044584] Mismatched protocol version in packet: lost sync or rosserial_python is from different ros release than the rosserial client

any help would be appreciated,

Thank you so much,

Best,

Moaed


#2

Hi,
I also got the same error, in my case it was the simple mistake of reading from a wrong serial port. I had two usb serial connections for two sensors and their hardware device formation on ubuntu tty/ACM* got interchanged. Just changing the devices worked for me.