I have recently purchased a RosBot 2.0 Pro and worked through the Quick start and basic demo programs. I have got it running but the WebUI demo is very unreliable and unstable. I am not sure if it is my expectations or something in the setup, but it seems if the out-of-the box demo is so fragile what chance do I have of getting something operational. I also have a few challenges with general usage which is probably a separate issue, but I thought it best to load everything in here in case there is some inter-connection… here I go:
It seems I can only use a screen and keyboard if it is plugged in from power up. If I boot and start from a screen/keyboard, then unplug it to try the vehicle if I then re-plug the screen in I get nothing. This makes it hard to see what the messages are when it stops.
I cannot get remote connection to open a screen (from PC or Linux), but I can ‘ssh’. I have been running it from this, but the connection often drops. I don’t know if it is the remote access - or the whole thing dying (I try and Control-C to stop but there is no resposnse… and I cant check given the point above.
The ‘roslaunch rosbot_webui demo_rosbot_pro.launch’ command works and the UI is accessible from a PC or tablet. But the vehicle only stays alive for between 30 seconds and a few minutes before locking up or dying. Sometimes it finishes just turning on the spot, some times it just dies.
I have tried just hitting ‘Explore’ which has worked for a few minutes some times, but usually ends within a minute or so with the vehicle failing. A few times it has travelled to another room and done OK, but it always end in a lockup within a few minutes.
I have tried manually driving it around, but once again, after anything between 30 seconds and 2 minutes - and it is gone. The UI says no messages and the remote shell is not responding.
I have captured a few logs from the screen. I get lots of:
Control loop missed its desired rate of 10.0000Hz… the loop actually took 0.1377 seconds
There are a few messages about ‘unstuck robot’ and one log ended with : Rotate recovery behavior started.
Most of the time when it is alive the map screen looks like the robot is lost. You can see the red outline from the scanner just continually rotating. It look like it should find itself as the scan profile matches the map - but it misses and just keeps rotating. It occasionally lock in but as soon as you move - it is lost again.
I have captured some logs of starting, running and failing (Copy of the ssh session.) Should be accessible here: Log files
So - are my expectations wrong that I should see some pretty reliable and capable operations with the basic demo? I know this is a research tool - but surely the ROS system is more capable than what I am seeing? Do I need help, guidance or a reset on expectations?
Is there anything else I can do to collect logs to help?
Thanks in advance.