Erle Robotics "azul" for Erle-Brain 2.0

3689670929?profile=original

Listening to the feedback provided recently we (at Erle Robotics) have decided to start new batch of releases about the  Debian-based operating system that our brains wears. The image includes:

  • Latest APM binaries for copter, plane and rover included (service launches copter by default)
  • mavros preinstalled and launched at init setting up different bridges for additional ground control stations.
  • ROS Indigo preinstalled and launched at init
  • Integrated camera images available directly through a ROS topic.
  • Different lasers, lidars and RGB cameras supported (additional devices supported).
  • WiFi hotspot mode preconfigured on wlan0 network interface with DHCP. The default SSID is erle-brain-2 (more)
  • WiFi infraestructure mode preconfigured on wlan1
  • Zeroconf stablished to be able to reach the brain through erle-brain-2.local from different connections (more).
  • Graphical User Interface (GUI) (more)
  • ROS 2.0 support (read more).
E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • @sander from our community had a few recommendations that will be included in the next release. Here's a sneak peak:

    3702121297?profile=original

  • Hello,

    Does that mean that HDMI output cannot be raised while the autopilot is running, or that if you connect the HDMI then the autopilot may be unstable.

    No, HDMI can be raised while having the autopilot up and as far as i've been able to mess with the system load, I don't see any impact on the autopilot performance.

    The issue is that there's right now a race between the apm and lightdm services that blocks the second one when both daemons are enabled. So simply by typing:

    sudo systemctl restart apm.service

    Will get you the GUI. I've updated http://erlerobotics.com/docs/Artificial_Brains/Erle-Brain_2/Getting... to reflect this.

    For debugging purposes (eg MAVProxy/mavros configuration) it would be nice to at least have some basic functionality of the autopilot to reflect your changes realtime.

    I do agree and we're trying to get it all in the next release. Particularly like to include APMPlanner 2.0 and MAVProxy tools with all the graphical dependencies solved.

  • Hello Victor,

    If I read the GUI documentation correctly, you need to disable the autopilot in order to have GUI on the HDMI.

    Does that mean that HDMI output cannot be raised while the autopilot is running, or that if you connect the HDMI then the autopilot may be unstable.

    For debugging purposes (eg MAVProxy/mavros configuration) it would be nice to at least have some basic functionality of the autopilot to reflect your changes realtime.

  • A flying Linux box !!!

    Excellent. :-)

This reply was deleted.