Flotilla "ShipShape" Update: Dip in and try the pre-release ( NEW: Updated Python API )

So if I install the firmware update to test out Shipshape, will the device still work with the old rockpool?
Thanks
Paul

Iā€™m fairly confident it will, but Iā€™m not sure if any weirdness might occur. Youā€™re better either waiting a little while longer, or using the downgrade script provided in pre to downgrade your dock again.

Any semblance of back/cross compatibility is going to be wiped out with the next push up to the ShipShape pre-release. Iā€™ve had to make some significant changes.

Ok, Iā€™ll probably leave it for now. An ETA on the release?
cheers
Paul

Iā€™m running 1.1.

I had a minor brainwave when listening to this weekā€™s Bilge Tank. You mentioned that it was a good idea to up the current limit on the Pi when using Flotilla. It doesnā€™t look like the Flotilla install script does this automatically so I added max_usb_current=1 to my /boot/config.txt manually and tried the motors/joystick combination again.

A dramatic improvement! The lag and hanging we encountered previously has all but disappeared.

Also, the Rainbow now works with the slider (albeit with a second or so delay between a change in position generating a corresponding change in brightness).

I still noticed that with more than 5-6 rows in the Rockpool, response time to any change in input seemed to increase. I also managed to hang everything by swapping a few components in and out. A simple restart of flotilla server fixed things.

1 Like

thanks for the heads upā€¦ and yes, I think the script could enable the max_usb_current setting to save you the hassle, weā€™ll sea to that (pun intended).

Good to hear itā€™s sped up, but Iā€™m still confused that thereā€™s as much slowdown as youā€™re reporting!

How many rules are you running when this happens? On a Pi 2 thereā€™s a perceptible delay, but nothing even approaching a second. Do you run any other services on your Pi, what do you see in the CPU load percentage? Or are you, perhaps, using an alternate browser?

The Pi reports approx 66% CPU most of the time Flotilla is running once you add a few rules.

With just two rules, the lag is almost unnoticeable. Add in a few (5-6) rules and the lag kicks in:

Hereā€™s a movie of the rainbow and slider

Hereā€™s one of the motor/joystick

For both of these movies there were 7 rules in total.

This is very useful. Thanks!

I replicated your setup, albeit on a smaller display, and hit about 30% CPU load with some moderate lag.

I think the problem in your case is that the browser is bogged down redrawing the graphs on every single one of those rules, so it just canā€™t keep up the data rates. This comes from having a full-screen browser on a high resolution display. The poor Pi just canā€™t keep up.

I think Iā€™ll have to significantly slow down the redraw rate of the graphs under certain circumstances, so the system is kept responsive.

Unfortunately thereā€™s no easy way to have lots of shiny graphs in a browser on the Pi and keep solid performance. Iā€™m already doing sneaky rendering tricks to try and speed it up.

I suspect shrinking the size of your browser window will speed things up immensely in the short term. Even my desktop PC has a bit of trouble keeping up with it full screen. There may be more performance gains to be had, however, but Iā€™m going to get this release pushed out to everyone before I start tweaking things like that any further!

You could add a button to turn on and off the moving graphs. Call it turbo mode or something. It could be something to turn on once youā€™ve debugged your app and want to just run it. Also it would have the benefit of passively letting the user know that the lag issues are related to the browser and not some deficiency in the Flotilla.

Hello,
Iā€™ve also tried the pre-release, but would like to know if I can revert the dock firmware so that it will work with the stable release.
Why? Two issues Iā€™ve found:

  • cookbook doesnā€™t work with the pre-release, and I need to show some quick recipes to keep the kids interested at the beginning
  • on the Pi2 running raspbian, rockpool hangs on ā€œconnectingā€ when using the default epiphany browser. If I install chromium and set it as default (with ā€œupdate-alternativesā€) it connects, so at least there is a workaround, but it isnā€™t very practical to install and configure as default

Thanks!

yes, you can revert the firmware, thatā€™s in part why ā€˜preā€™ does not overwrite the daemon and has to be launched manuallyā€¦

head over to https://github.com/pimoroni/flotilla-offline (or git pull if already cloned locally) and run the firmware ā€˜uploadā€™ script.

On the next reboot, all should work again. If not, re-run:

curl https://get.pimoroni.com/rockpool | bash

ā€¦ that should get you back on track (including access to cookbooks)

This is a bug. It should absolutely work in Epiphany. Iā€™ve found and fixed this, so you should ( if you cloned from GitHub ) be able to ā€œgit pullā€ to get the fix. Otherwise re-download as a zip.

Cookbook is on the back-burner at the moment, but it will be updated to work with the pre-release once the pre-release becomes the main release.

It now loads in Epiphany, but mine (on pi2 and pi3 with newest jessie) doesnā€™t display the modules in rockpool. Need to try python again with shipshape, but I donā€™t think rockpool is working as intended. I do see lots of options that I can use, but none apply to the hardware.

yes, the latest (shipshape) rockpool broke Epiphanyā€¦ @gadgetoid fixed it in the master repo but I donā€™t think it has made itā€™s way into ā€˜preā€™ yet as there are a couple of other bugs being worked on.

ā€¦ you can grab it from https://github.com/pimoroni/flotilla-rockpool/tree/shipshape in the meantime (just overwrite the rockpool folder in your ā€˜preā€™ git clone)

btw, there is now a script to automate installation of the python API and firmware upgrade, just run:

curl https://get.pimoroni.com/flotilla | bash

This is specifically for SHIPSHAPE users at this point, DONā€™T use if you donā€™t wish to leave behind the cookbooks and step into the moving waters. The shoreline is in view though, so nowā€™s a good time to jump aboard and try out the latest and greatest ;-)

actually, the latest rockpool IS available in the ā€˜preā€™ repo, so it should work again in Epiphany. Make sure you ā€˜git pullā€™ the latest or rebase your install so that it is fully up-to-date.

sigh you are correct, current rockpool does not work in Epiphany, which seems to break if you look at the code from less than an inch away.

For the time being it might be best to install and use an alternative browser such as Iceweasel or Chromium - weā€™ll update this thread when we catch that bug!

In the end Iā€™m sticking with pre for now. The kids are way too busy with school to be able to play much, but they have already voted for the pre-release over the stable oneā€¦ :)

1 Like

Tried it today on my mac running El Capitan and worked seamlessly. The automated python install didnā€™t work on the mac, but once Iā€™d installed the python libraries, all worked like a dream - python and rockpool, which was lovely to use. Going to try rockpool with my 7 year old later on.