Error in terminal emulator

Newsight 2019-07-09 11:04:32 UTC #1

Hey there, can you tell me why do I get this error? i just entered this command and got that error :“roslaunch rosbot_webui demo_rosbot_pro.launch”.

lukasz.mitka 2019-07-09 12:17:30 UTC #2

Hello Newsight,

The errors are caused by problem with serial bridge communication.
This could happen, when CORE2 controller in ROSbot is flashed with wrong firmware.
Please make sure, that you CORE2 controller is flashed with ROSbot 2.0 PRO default firmware.

Regards,
Łukasz

Newsight 2019-07-09 13:08:07 UTC #3

Thanks for letting me know what the cause of the error is.
can you instruct me how do I do that?

lukasz.mitka 2019-07-09 13:16:48 UTC #4

Hello Newsight,

Follow steps in ROSbot - quick start: Programming.
Just note that there is choice of default firmware for ROSbot 2.0 and ROSbot 2.0 PRO, choose the on appropriate for your device.

Regards,
Łukasz

Newsight 2019-07-09 13:44:35 UTC #5

Hey, thank you again, it really worked but I have another question for you. when I keep with the instructions from https://husarion.com/tutorials/howtostart/rosbot---quick-start/#programming, in the Usage section, the command worked but when I tried to type the robot IP on my phone browser(which was on the same network as the ROSbot 2.0 Pro) it didn’t show me anything. It should’ve shown me the interface.
Do you know what should I do?

lukasz.mitka 2019-07-09 13:56:00 UTC #6

Were you able to open the interface from different computer?
Were you able to open the interface locally on ROSbot by opening localhost on ROSbot browser?

Newsight 2019-07-09 14:04:06 UTC #7

you mean from the Husarion cloud? Unfortunately it does not show an interface neither in the cloud and from a different computer.

lukasz.mitka 2019-07-10 08:50:22 UTC #8

I meant typing ROSbot IP in web browser on different computer and typing localhost in web browser running on ROSbot.

Newsight 2019-07-15 07:09:43 UTC #9

I tried it right now. It says that the site can’t be reached on my ROSbot when typed localhost.

Newsight 2019-07-15 07:28:41 UTC #10

And also L1 is not blinking so it’s not the battery that causes the issue

lukasz.mitka 2019-07-16 09:29:48 UTC #11

It looks like the Nginx server is not configured on your ROSbot.

Check contents of /etc/nginx/sites-enabled/default file:

sudo nano /etc/nginx/sites-enabled/default

When following the tutorial, it should have had edited line:
root /var/www/html;
to:
root /home/husarion/ros_workspace/src/rosbot_webui/edit;

If you have it already edited, there is nothing to change.
To exit text editor press: “Ctrl + x”, “y”, “Enter”

Restart Nginx server:

sudo systemctl restart nginx

If Nginx was not running, it will be started with this command.

Now you should be able to view the interface.

Regards,
Łukasz

Newsight 2019-07-18 06:09:59 UTC #12

Job for nginx.service failed because the control process exited with error code. See “systemctl status nginx.service” and “journalctl -xe” for details.

lukasz.mitka 2019-07-18 06:59:54 UTC #13

Hello Newsight,

According to error shown, there is duplicated entry for default server.
Could you post here contents of your /etc/nginx/sites-enabled/default file?

Regards,
Łukasz

Newsight 2019-07-18 07:21:52 UTC #14

It is working now, thanks. I probably edited the file wrong, so I downloaded a new one.
Just wondering, do you know why the camera looks a bit blurry/not shown on a full screen(black scars)? and when I try to move the ROSbot a bit, it shuts down(crashes).

lukasz.mitka 2019-07-18 07:39:49 UTC #15

Below camera view, there is a slider for depth clipping, you can use it to cut off elements which are further than selected distance. It can be switched to raw image from camera.

Regarding the ROSbot shutdowns, few things to check:

Make sure batteries are fully charged.
Make sure that ROSbot is within WiFi range all the time (try using ROSbot in different room or with another access point if possible)

Regards,
Łukasz