I’m releasing a pre-release of the 30.0.3 software release that we want to get out in the next few weeks. As always, the OpenROV software is a living ever evolving project that needs your help!
Download: (You will need 7zip to uncompress the image)
- Run from SD Card: http://bit.ly/orov-image-30_0_3-build87
- Flash the BeagleBone: http://bit.ly/orov-image-30_0_3-FLASH-build17
You will need to install the image on a spare microSD card that is 2GB or larger.
Things that we would love feedback on:
- Does the cockpit run smoothly. In 30.0.2 we see issues where you still get a connection latency indicator and motors work, but the connection light turns red and telemetry data stops updating. We are hoping that moving to the latest Kernel fixes that issue.
- Does the system reliably boot every time? No more re-imaging the SD card? We were early movers to the ext4 file system on Linux and it bit us in the butt. A big reason to moving to the latest Kernel was to get all of the fixes over the last 6 months to make the file system reliable.
- Generally, are you seeing anything that has you question the stability of the software.
- Does connecting to the ROV using a DHCP work reliably for you?
- Does connecting to the ROV using http://openrov.local work reliably for you?
This pre-release covers an intensive month of updates to the software imaging process. As a results:
The download image size has been cut nearly in half (359.3 MB vs 656.6MB of 30.0.2) meaning faster downloads and more free space on the image.
The linux O/S has been upgraded to the latest stable linux Debian release code named ‘Jessie’. There are many improvements including a new system for managing services called systemd which brings the boot time to about 30 seconds.
The linux Kernel has also been updated to the 4.1.x series. This is a massive update and with it returns the ability for the BeagleBone black to manage its pins using the cape manager. This means this release SHOULD work on the original beaglebone whites. That’s right, this release should work with the original 2.3/2.4 ROV kits.
Cloud9 works again! This is one of the improvements that I really want to get out and in to everyone’s hands. Not only can you edit all of the code on the ROV via your web browser, you can also debug the running node.js processes, batch upload files to and from the ROV, and much much more. Cloud 9 runs on port :3131 of your ROV.
This image support mDNS. That means you can now connect to the ROV using http://openrov.local:8080 to get to cockpit. To use this from your host machines, you either need Windows 10, Linux, or OS/X, or you need a Windows box that has iTunes installed. If it does not work for you, you can still use IP address.
Internet access fixed. There was a problem with a file that was hosted on the Internet not longer being available that foiled the ROVs ability to tunnel through your browser to get out to the internet. That has been fixed which means you can download plugins again, and the Internet updates can work again.
No more setting your computer to a static IP address! This release has a DHCP server built in on the ROV. Just leave your ethernet connection to DHCP and the ROV will assign it a 192.168.254.x address. It takes my computer 10 seconds or so to get the address from the ROV. If this does not work for you you can always go back to the static IP address as it still works as well.
Improvements for IMU2. Should work on all boards and is smart enough to avoid additional magnetic interference for better heading hold
- *testing fix:*samba is not working. ( https://github.com/OpenROV/openrov-software/issues/462 )
- If you manually try and stop the proxy service because you have directly connected the ROV to a router or your computer via Internet sharing, the proxy fails to stop.
- the external lights indicator shows full on when initially started. The external lights indicator sometimes does not appear ( https://github.com/OpenROV/openrov-software/issues/452 )
- the image does not currently auto-expand to take up the free space on the SD card. If you want to expand, you must manually run the script `sudo /opt/scripts/tools/grow_partition.sh’ and then reboot.
- flashing the beaglebone scripts are not yet working
- IMU2 issues not yet resolved for 2.7 and earlier boards ( https://github.com/OpenROV/openrov-software/issues/455 )
Things we have not tested yet
- Running on a beaglebone white
- Flashing new ESCs
* Over the Internet software updates