Welcome to the Trance/EDM/Festival/LEDs sub-section of my blog
![]()
I came suitably equipped with blinkies :)
![]()
I need to carry my batteries like this when I board planes :)
![]()
I found out my batteries need anti-stress protection
![]()
I just had enough time to add my name and face
![]()
some people took the job seriously
![]()
and what's a badge without SAOs
![]()
cool idea, changing RF into sound
![]()
this time I had to port my code to an RP2350 which was much more challenging than planned
![]()
and how I got to meet so many DJs thanks to it
![]()
action shot, with my older code that didn't refresh the badge quickly enough
And these are the old 64x64 panels:
![]()
with 64x64 P3.5, you can of course see the bigger pixels
![]()
as I mentioned, they broke easily
![]()
here the bottom right corner is broken
![]()
wrote some extra code to shrink the graphics on 128x128 displays
![]()
the other bad news is that it's pretty battery hungry and I need 2x70Wh for a full night
![]()
the panel + 2 LED strips took around 100Wh for 7H, pretty hungry but 2 70Wh batteries do the job
![]()
for comparison, my full front and back outfit (without extra LEDs) took 125Wh for the same 7H-ish
![]()
not the most professional setup, but ok for the first time ;)
![]()
my 2nd prototype uses raw panels and a nice metal frame done by Hongren Su from Azerone
![]()
the 2 kinds of panels look the same from the display side (and yes, they work with USB packs that can do 12V USB-PD)
They had multiple performing stages, including a huge outdoor one, where the performers continued under the rain, props to them: And OMG, the monkey from mainstage was absolutely impressive:
Day 1 without the rain, allowed for drone shows
![]()
4 displays in sync, outfit front and back, and 2 backpacks :)
I got to meet another LED euthusiast who had the exact umbrella I needed ;)
![]()
arrived just before sunset, not many people, yet
Create /etc/udev/rules.d/99-garmin-passthrough.rules with
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="091e", ATTR{power/control}="on", ATTR{power/autosuspend}="-1"
save and run "udevadm control --reload-rules; udevadm trigger"
this ensures linux will not autosuspend the port which in turn causes the montana not to shut down, allows virtualbox to grab the port, hand it over to windows, and have basecamp work again. Yeah!
kernel: [94868.932764] usb 3-5: new high-speed USB device number 34 using xhci_hcd kernel: [94869.136992] usb 3-5: New USB device found, idVendor=091e, idProduct=0003, bcdDevice= 0.01 kernel: [94869.136998] usb 3-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 kernel: [94869.740855] usb 3-5: reset high-speed USB device number 34 using xhci_hcdTurns out the problem was this, as explained by The entire crash and shutdown loop was driven by the kernel's runtime USB autosuspend dropping link power at the 2-second mark. When no host kernel driver binds to the interface, the kernel suspends the port. The Montana firmware interprets that link drop as a physical cable disconnect, terminates storage negotiation, executes an emergency waypoint flush, and turns off. Keeping the link energized via ATTR{power/autosuspend}="-1" completely resolves the failure mode, allowing any VM to claim the device without racing against link power down. The montana is wrong, but garmin support made it clear that because it works on windows, they were not super interested in diagnosing or fixing it. Maybe with this page, they'll consider a fix, but in the meantime, the workaround is this:
Create /etc/udev/rules.d/99-garmin-passthrough.rules with
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="091e", ATTR{power/control}="on", ATTR{power/autosuspend}="-1"
save and run "udevadm control --reload-rules; udevadm trigger"
this ensures linux will not autosuspend the port which in turn causes the montana not to shut down, allows virtualbox to grab the port, hand it over to windows, and have basecamp work again. Yeah!