I have to say it is a bit annoying that a critical part of the process is listed as item 6 in the ‘how to start’ tutorial … and that key software cannot be pre-loaded or scripted. My ‘out of the box’ experience is not going very well …
I went through the quick start … I had a permissions error with the github steps so i had to sudo those steps. Is that normal or a problem? I am worried now all the steps there are set as SU only.
If i run the Load firmware project, I can then get past the connection - thanks. But I am now at a blank screen …
Does the load firmware process have to be run every time (annoying - can it be automated) or this this a one-time installation?
The UI Example in the IDE compiles with warnings - which a bit of a worry - but does appear to load - but when I connect I am only getting a blank screen. The same with the UI Example and FirstTry.
I can’t connect with a remote desktop. I can ping the vehicle (IP address) so I am confident it is there, but remote connection fails and a web browser gives a error 404.
if I connect with a screen and keyboard - and I run rosbot_webui demo_rosbot_pro I get:
husarion@husarion:~$ roslaunch rosbot_webui demo_rosbot_pro.launch
[demo_rosbot_pro.launch] is neither a launch file in package [rosbot_webui] nor is [rosbot_webui] a launch file name
The traceback for the exception was written to the log file
Sorry - lots of questions in here! I hope you can help!