Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Marc Hanheide
    @marc-hanheide
    Hi @francescodelduchetto
    francescodelduchetto
    @francescodelduchetto
    hello @marc-hanheide
    For anyone with problems on simulation machine about Intel VT-x or AMD-v try all the points in the checklist here: https://forums.virtualbox.org/viewtopic.php?f=1&t=62339
    simondparsons
    @simondparsons
    Hi everyone
    francescodelduchetto
    @francescodelduchetto
    @simondparsons can you see previous messages?
    simondparsons
    @simondparsons
    Yes. You can see all the messages when you navigate to the website (before you log in).
    So, a good mechanism for preserving a record. But totally public... (not a problem, but something to bear in mind).
    francescodelduchetto
    @francescodelduchetto
    Ok good!
    Marc Hanheide
    @marc-hanheide
    Also gitter has a decent android app
    simondparsons
    @simondparsons
    For the "easy installation on a new machine", I still have the problem of the missing repository for ros-kinetic-uol-cmp3103m. Can you tell me which repo it is so I can add it?
    Marc Hanheide
    @marc-hanheide
    @simondparsons can you install ROS packages at all then?
    simondparsons
    @simondparsons
    I went back through the log, and everything else seemed to install ok. The only problem is a failure to find the UoL package
    Marc Hanheide
    @marc-hanheide
    @simondparsons, show the output of sudo apt update and then the output of sudo apt install ros-kinetic-uol-cmp3103m, please
    Marc Hanheide
    @marc-hanheide
    Welcome @TReed1104 , school technician!
    Benjamin Terrill
    @Benjaminh21
    I installed Ubuntu, but when i boot up there is not option to choose which OS to use. It just opens windows straight away
    69 replies
    simondparsons
    @simondparsons
    Good idea--- I figured out what I was doing wrong. I was trying to install on the Linux distro that I use day to day. And that is 18.04. Doh. I'll have to wrestle with one of the virtual solutions if I want to install anything on this machine.
    5 replies
    PEI07088957
    @UnnaturalScientist
    Hi all, I installed ROS and Gazebo earlier today. Had some issues so I made a small video explaining the issues I had. I also included every step I would take, after this, to re-install : https://www.youtube.com/watch?v=cpDYJw0Rtxc
    Marc Hanheide
    @marc-hanheide
    thanks @UnnaturalScientist
    Benjamin Terrill
    @Benjaminh21
    image.png
    198 replies
    PEI07088957
    @UnnaturalScientist

    A summary of mistakes/errors we made while using Virtual Machines


    We followed the steps to install ROS on a virtual machine via https://github.com/LCAS/teaching/wiki/Home-Installation and had some issues with roslaunch or roscore (See @Benjaminh21 on March 20th 13:14). If you have the same issues, this may help. At the very least it will help you avoid some steps we missed, which cost a little time. Nothing crazy.


    * If you do not have a directory for your workspace (e.g. `/catkin_ws/src` ) Step A can help you with making one
    * If you have made these directories, but can not use `catkin_make` and still have the error `E: unable to locate package ros-kinetic-python-roslaunch` skip to Step B and this could help.

    Step A


    In your terminal, create a new directory for your catkin workspace.
    If it works, congratulations. If not, continue to Step B afterwards.

    * `mkdir -p ~/catkin_ws/src`
    * `cd ~/catkin_ws/src`
    * `catkin_init_workspace`  *If this throws an error, go to Step B*
    * `cd ..`
    * `catkin_make`
    * `source devel/setup.bash`
    * `roslaunch uol_turtlebot_simulator maze1.launch`

    Step B


    Creating a build directory in your catkin workspace. So do this from your new workspace
    Name@Name-Virtualbox:~/catkin_ws $. Ok, so, we began by frantically entering these commands:


    * `sudo apt-get install cmake python-catkin-pkg python-empy python-nose python-setuptools libgtest-dev build-essential`
    * `sudo apt-get install ros-kinetic-catkin`
    * `sudo apt-get install -y catkin`

    These will probably state already installed or something about dependancies. Also, this created a build folder in the src directory, which is for catkin build, not catkin_make. So then, we did the following. This was found on the general ROS Install website, for Kinetic http://wiki.ros.org/kinetic/Installation/Ubuntu. This shows how much more streamlined the install on the LCAS wiki is, which is so much easier. Then we did the following in the home directory Name@Name-Virtualbox:~ $ , not Name@Name-Virtualbox:~/catkin_ws $.


    * `source /opt/ros/kinetic/setup.bash`

    A nice command on the site is apt-cache search ros-kinetic. This will show you all of the ROS packages you have installed. After that, this we finally arrived at our solution:


    * `sudo apt-get update`
    * `sudo apt-get upgrade`
    * `sudo apt autoremove` *if neccessary after upgrade*
    * `cd ~/catkin_ws/src` *if you are not within this directory already*
    * `catkin_init_workspace`
    * `cd ..` to `catkin_ws`
    * `catkin_make`
    * `source devel/setup.bash`
    * `roslaunch uol_turtlebot_simulator maze1.launch`

    This should work fine. If not, state any issues below.

    Marc Hanheide
    @marc-hanheide
    What @UnnaturalScientist suggested up there is all correct and valid, but ways more than is needed for a simple submission. There is no need to install anything more than what is documented in the official documentation. All the many packages @UnnaturalScientist refers to are all included when you install sudo apt-get install ros-kinetic-desktop as documented in https://github.com/LCAS/teaching/wiki/Home-Installation
    And, I'd like to add, while it is good practice to create a proper catkin workspaces and packages etc, for a simple solution it is perfectly enough to write one single Python file and run it (outside of catkin and any packages). This is also detailed in the brief
    PEI07088957
    @UnnaturalScientist
    @marc-hanheide Yeah, everything at the beginning of Step B that was "frantically" input was not needed. It did nothing at all to help. I probably did not make that very clear, but tried to insinuate it with "frantically" and then followed by "we finally arrived at our solution" as in, that was the solution and not the stuff before.
    Tom Davies
    @NedBeans0

    So this lockdown has forced me back into trying to get it working on a VM on my laptop haha. I'm aware that the simulator has issues with crashing on startup even on the lab PCs, but every time I try to run it with roslaunch uol_turtlebot_simulator simple.launch the windows all open up but I get a crash error soon after.

    [gazebo-1] process has died [pid 25820, exit code 139, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -e ode /opt/ros/kinetic/share/uol_turtlebot_simulator/worlds/empty_maze.world __name:=gazebo __log:=/home/tom/.ros/log/254ad232-6ddc-11ea-bc8c-080027db349c/gazebo-1.log]. log file: /home/tom/.ros/log/254ad232-6ddc-11ea-bc8c-080027db349c/gazebo-1*.log
    Should I post the log file or there is something obvious I'm possibly missing?

    The simulator window and toolbars open up, and the Gazebo startup message saying 'Preparing your world' appears, but it gets stuck on that and crashes.

    francescodelduchetto
    @francescodelduchetto
    @NedBeans0 Do you get the same error if you launch another gazebo launch file (maze1.launch for example)? Sometimes killing all the gzserver/gzclient processes from the system monitor, before relaunching again, helps.
    Tom Davies
    @NedBeans0

    The same error and exit code appears when launching maze1.launch as well unfortunately. Although the message about the physics appearing after the process dies is maybe notable? It doesn't appear when I try to run simple.launch.

    [gazebo-2] process has died [pid 30202, exit code 139, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -e ode /opt/ros/kinetic/share/uol_turtlebot_simulator/worlds/maze1.world __name:=gazebo __log:=/home/tom/.ros/log/5d02f256-6ddf-11ea-bc8c-080027db349c/gazebo-2.log]. log file: /home/tom/.ros/log/5d02f256-6ddf-11ea-bc8c-080027db349c/gazebo-2*.log [ INFO] [1585061676.815238312, 0.090000000]: Physics dynamic reconfigure ready.

    killall gzclient and killall gzserverdon't appear to find any processes to kill after the simulator is closed unfortunately

    Marc Hanheide
    @marc-hanheide
    @NedBeans0 Can you show a bit more of the output, please? It could be you don't have 3D acceleration running on your VM?
    And that would only show in earlier messages. So, best to simply paste the entire log, briefly. The error message we see here doesn't tell anthing, I'm afraid
    best use ``` to paste multiple lines in verbatim (at beginning and end of your pasted logs)
    image.png
    Tom Davies
    @NedBeans0
    I definitely have 3D acceleration enabled now so hopefully that shouldn't be causing an issue.
    Here is the log that appears in the console, unless you mean one of the logs saved to .ros/log ?
    SUMMARY
    ========
    
    PARAMETERS
     * /bumper2pointcloud/pointcloud_radius: 0.24
     * /cmd_vel_mux/yaml_cfg_file: /opt/ros/kinetic/...
     * /depthimage_to_laserscan/output_frame_id: /camera_depth_frame
     * /depthimage_to_laserscan/range_max: 100
     * /depthimage_to_laserscan/range_min: 0.001
     * /depthimage_to_laserscan/scan_height: 10
     * /robot_description: <?xml version="1....
     * /robot_state_publisher/publish_frequency: 30.0
     * /rosdistro: kinetic
     * /rosversion: 1.12.14
     * /use_sim_time: True
    
    NODES
      /
        bumper2pointcloud (nodelet/nodelet)
        cmd_vel_mux (nodelet/nodelet)
        depthimage_to_laserscan (nodelet/nodelet)
        gazebo (gazebo_ros/gzserver)
        gazebo_gui (gazebo_ros/gzclient)
        laserscan_nodelet_manager (nodelet/nodelet)
        mobile_base_nodelet_manager (nodelet/nodelet)
        robot_state_publisher (robot_state_publisher/robot_state_publisher)
        spawn_turtlebot_model (gazebo_ros/spawn_model)
    
    auto-starting new master
    process[master]: started with pid [32140]
    ROS_MASTER_URI=http://localhost:11311
    
    setting /run_id to b039ca0c-6de0-11ea-bc8c-080027db349c
    process[rosout-1]: started with pid [32153]
    started core service [/rosout]
    process[gazebo-2]: started with pid [32161]
    process[gazebo_gui-3]: started with pid [32172]
    process[spawn_turtlebot_model-4]: started with pid [32182]
    process[mobile_base_nodelet_manager-5]: started with pid [32188]
    process[cmd_vel_mux-6]: started with pid [32189]
    process[bumper2pointcloud-7]: started with pid [32190]
    process[robot_state_publisher-8]: started with pid [32199]
    process[laserscan_nodelet_manager-9]: started with pid [32210]
    process[depthimage_to_laserscan-10]: started with pid [32220]
    /usr/local/lib/python2.7/dist-packages/pkg_resources/py2_warn.py:22: UserWarning: Setuptools will stop working on Python 2
    ************************************************************
    You are running Setuptools on Python 2, which is no longer
    supported and
    >>> SETUPTOOLS WILL STOP WORKING <<<
    in a subsequent release (no sooner than 2020-04-20).
    Please ensure you are installing
    Setuptools using pip 9.x or later or pin to `setuptools<45`
    in your environment.
    If you have done those things and are still encountering
    this message, please comment in
    https://github.com/pypa/setuptools/issues/1458
    about the steps that led to this unsupported combination.
    ************************************************************
      sys.version_info < (3,) and warnings.warn(pre + "*" * 60 + msg + "*" * 60)
    [ INFO] [1585062241.475659859]: Finished loading Gazebo ROS API Plugin.
    [ INFO] [1585062241.478155008]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
    [ INFO] [1585062241.703357413]: Finished loading Gazebo ROS API Plugin.
    [ INFO] [1585062241.704824629]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
    [ INFO] [1585062244.253139125, 0.010000000]: Camera Plugin: Using the 'robotNamespace' param: '/'
    [ INFO] [1585062244.303053988, 0.010000000]: Camera Plugin (ns = /)  <tf_prefix_>, set to ""
    [ INFO] [1585062244.695194925, 0.010000000]: Starting plugin Kobuki(ns = //)
    [ WARN] [1585062244.695716005, 0.010000000]: Kobuki(ns = //): missing <rosDebugLevel> default is na
    [ INFO] [1585062244.700539416, 0.010000000]: Kobuki(ns = //): <tf_prefix> = 
    [ INFO] [1585062244.701375159, 0.010000000]: Will publish tf. [mobile_base]
    [ INFO] [1585062244.715990032, 0.010000000]: Kobuki(ns = //): Advertise joint_states[joint_states]!
    [ INFO] [1585062244.719216293, 0.010000000]: Kobuki(ns = //): Advertise Odometry[odom]!
    Unhandled exception in thread started by 
    sys.excepthook is missing
    lost sys.stderr
    [spawn_turtlebot_model-4] process has finished cleanly
    log file: /home/tom/.ros/log/b039ca0c-6de0-11ea-bc8c-080027db349c/spawn_turtlebot_model-4*.log
    Segmentation fault (core dumped)
    [gazebo-2] process has died [pid 32161, exit code 139, cmd /opt/ros/kinetic ..
    Marc Hanheide
    @marc-hanheide
    OK... I have one suspicion... Try sudo mv /usr/local /usr/local.off. The updates regarding Python 2 and 3 might cause issues here (only crept up very recently)
    Then, you may also try roslaunch gazebo_ros empty_world.launch to only start gazebo and see of that work on its own
    Marc Hanheide
    @marc-hanheide
    Let me know @NedBeans0 if this helps, or maybe @UnnaturalScientist has some tricks up his sleeve I didn't know of
    Alternatively, @NedBeans0 if you really can't get it to work, try the remote access I mentioned in the blackboard announcement
    Tom Davies
    @NedBeans0
    After doing sudo mv /usr/local /usr/local.offI can successfully open up the empty world simulation but I still get the same error on the mazes unfortunately (I hadn't tried the empty world before running that command so unsure if that fixed it). I'll look into the remote access option and see if I can get that working for now. Thank you for the help anyway!
    Marc Hanheide
    @marc-hanheide
    OK, progress. But if the empty world works in principle, then we are "just" in the normal territory of gazebo being a bit unreliable. Just try again (sorry, can't change much about that). It may well be the case that in your system this error happens more frequently (on some systems it never happens, on some notoriously frequently). Always issues killall -9 gzserver before trying just to be on the safe side (also, shouldn't be necessary, but experience shows it's a good idea)
    Cathal-Doherty
    @Cathal-Doherty
    Im trying to get remote access and when I logon, and I have a problem once I logged onto the service. The webpage is empty with the message "You are seeing this page in error, please contact a member of Network Services or the ICT Helpdesk." Any help?
    4 replies
    Cathal-Doherty
    @Cathal-Doherty
    image.png
    image.png