ardupilot / soloscripts

Please visit Open Solo, which is the new location for this cool stuff. https://github.com/OpenSolo/documentation

soloscripts's Issues

Update golden image to 3DR's final 2.4.2 FW and current ArduCopter

Issue

The solo's stock golden image is a deliberately unflyable and non-functional file system. The 3DR Solo app then prompts the user to do a preflight update. This downloads firmware from 3DR's servers, copied it down to the solo and controller, and executes the installation routines. The most current and final from 3DR is version 2.4.2 of the file system, Linux kernel, STM32, etc. It also includes ArduCopter-Solo v1.3.1.

This stock golden image is not compatible with the Pixhawk 2.1 or ArduCopter 3.5. Therefor you cannot do a factory reset after installing the Green Cube. The requirement for an over the internet update is also very limiting. If you have a problem in the field without an internet connection, you're grounded. And finally it relies on 3DRs firmware servers to provide that update, and they may not be there forever.

Requirements

We need to replace this with a modern and operational golden image.

• Must not require 3DR servers. We cannot rely on those always being around and we cannot build or modify the solo moving forward depending on them being there. This new golden image must cut that requirement out.
• Must be immediately flyable after pairing and calibrating. Must not require immediately going online to do updates. Sure, it may not be the latest and greatest as things advance over time. But it needs to be a stable and flyable file system. If someone has to factory reset in the field with no internet, they can still fly.
• Must be fully compatible with the Pixhawk 2.1 (Green Cube) and ArduCopter 3.5.x.

To Do:

1. Create a new golden image for the Solo that contains the current 3DR 2.4.2 firmware

• Include the modified python files needed for Green Cube / AC35 compatibility
• Include a solo build of ArduCopter 3.5.x

2. Create a new golden image for the controller (Artoo) that contains the current 3DR 2.4.2. At this time, nothing else is modified on the controller. But if anything does get modified in the meantime, it should be included.

3. Create deployment package(s) to install this update via the Solex app.

• Solex currently can only deploy to Solo. Need to add ability to deploy to controller
• Matt already has a rough process and package made for Solo. Needs fine tuning.

4. Document the deployment process for users to follow once alpha and beta testing is done. Add to ArduPilot solo wiki.

Firmware deployment process update

Issue

We need a process/procedure for deploying firmware updates to the users. The existing Solex app FW updates method is very well suited for this already. It needs to be updated to allow deploying to the controller too as today it can only deploy to the solo.

The solex process loads files onto the solo according to the directory structure in the /install/ directory. So you can load replacement files or full tar.gz packages wherever you need to put them. It always has the ability to fire off shell scripts before and after. So the preinstall script can do any necessary setup, then the files load, then the postinstall script can fire off the update procedure to do something with the files. Mainly calling the --update-prepare and --update-apply functions in sololink_config.

To Do

• Add the ability to force a parameter reset as part of the deployment. Some python and mavlink magic can do that along with a slight modification to the sololink_config file.
• Add the ability to deploy to the controller via Solex. This goes along with the same requirement for the golden image update in #4

Add "boat mode" UI to Solex

Issue

Many Solo users are excited about the green cube and ArduCopter 3.5+ because they want to operate off a boat or other moving vehicle. To do this, the user needs to disable INS_GYR_CAL. It would also be wise to force enable Return to Me if the mobile device has a GPS. There may be some other odds and ends to toggle as well that I can't think of off the top of my head.

There is currently no user friendly way to do this stuff in any application. Adding the functionality to Solex would fill the void. Tagging @kellyschrock.

To Do

• Make a Boat Mode UI in the Solex Vehicle Settings menu. Enabling boat mode should set those required parameters and application settings. Likewise disabling Boat Mode should put them back to normal.
• There should be some kind of indication on the HUD overlay or across the top that the vehicle is in Boat Mode. I know real estate is getting slim on the screen. But it is important information for the user to know since it affects operations.
• The UI needs to be inhibited if the Solo is not a Pixhawk 2.1 running ArduCopter 3.5+. I think that INS_GYR_CAL parameter is not part of the old stock 3DR firmware so looking for that might be the way to check.