Rosbot 2.0 Pro Range sensors / Time of flight randomly stop working

[Patrick]

Hi,

I’ve been working with the Rosbot 2.0 Pro, but I’m encountering an issue with the 4 range sensors (the time of flight sensors).
I launch the rplidar and the rosbot_ekf (all.launch) and it works fine for a while, but then some of the range sensors start publishing -1 values for their range aspect; such as the following:

header: 
  seq: 2843
  stamp: 
    secs: 1578568817
    nsecs: 112711009
  frame_id: ''
radiation_type: 1
field_of_view: 0.259999990463
min_range: 0.0299999993294
max_range: 0.899999976158
range: -1.0

So far it’s been the front left, front right, and rear right. Restarting the rosbot_ekf node doesn’t help. Fully turning the Rosbot off and on again, then restarting the nodes does fix the problem.

I have no clue why it happens, sometimes it’s within minutes of start up, sometimes everything is still fine after 30+ minutes.

What could be the issue and how can this be solved?

-Patrick

[byq77]

Hi,
Thank you for reporting the problem. We will investigate it and issue the fix as soon as possible.

The sensors are initialized after the power cycle/reset so pushing the reset button should help. You don’t need to turn ROSbot off and on again.

Sorry for the inconveniences.

Kind Regards,
Szymon

[Patrick]

Hi Szymon,

Thank you for your reply and the tip. That should save some time when encountering the error.

I’m looking forward to the fix, I wish you good luck

Kind regards,
Szymon

[XvdG]

Hi Szymon,

I am experiencing the same problem with the Rosbot 2.0. Is it also possible to do a software reset? I.E:
If(range/FL<0)
ResetCore2()
As a temporary solution until this is fixed?

Thanks!

[XvdG]

Hi Patrick,

Could you check if the problem persists after turning the distance sensors of and on again by running

rosservice call /config “command: ‘EDSE’ data: ‘0’”

rosservice call /config “command: ‘EDSE’ data: ‘1’”

Xander