Post by dizzeesatchel on Jun 21, 2023 17:44:19 GMT
Ok, resolved now
For future reference, if people need to reset/setup their module, or update, there are two ways to do it:
if you want to develop your own scripts
you'll need to install the packages for SSD1306, europi and europi_contrib as described in the original programming instructions, using Thonny. Using this method you'll be able to save files and changes to the Pico's internal storage and run it BUT you might find that a long list of scripts exhausts the available memory. In my testing, with Pam's installed, i removed the test scripts Hello_World and Knob_playground and the Consequencer script and that was enough memory saved to let the menu load normally. (I chose Consequencer because it's also a large script, and Hamlet is very similar to it anyway)
You don't have to delete the scripts from the device, it's enough to comment them out in the menu file. You can comment out a line by placing a # symbol at the beginning:
if you're happy to just use the scripts already included
you can simply install by using the attached .uf2 file.
Connect the pico to your computer while holding down the BOOTSEL button on the pico. It should appear on your computer as an attached drive (called RP2 i think).
Drag and drop the .uf2 file onto RP2 and it'll install and eject, ready to use.
This method is a little lighter, so you can have all the scripts at your disposal, and as a bonus it loads the menu quite a lot faster too.
Hi team: some of you who've updated to the latest firmware may have had trouble getting the Quantizer script to load. This is due to a bug introduced upstream (ie. not my fault )
I've prepared a new .uf2 which addresses the problem (it was a simple typo)
Separately, i'm aware that even with quality pots, some builds don't quite exhibit the full knob 'range' from clockwise to counter-clockwise. This isn't really noticeable in many of the scripts, but some with more precise controls can suffer: for example when using Turing Machine, turning knob 1 fully clockwise should set the sequence probability to "locked" and turning it fully counter-clockwise should set it to "looped". If the range isn't quite there you'll never fully reach those values! Happily there's a "deadzone" variable available to counter this - in the latest firmware i've tweaked it a bit, so you might see improvements in getting the whole range. If however you're still having issues there's a version which is adjusted a little further still - aeuropi-v1.9.2-extend-deadzone.uf2