EN16 stuck with purple LEDs after flashing firmware 1.3.1 and 1.3.2

Flashing firmware 1.3.1 and 1.3.2 on my EN16, results in “Bootloader connection lost” message and device stuck with purple LEDs on (I am usually using page 1 with blue LEDs) right after flashing (device becomes completely unresponsive).

Both manual and automatic updates result in the same issue. Reverting to 1.2.39 solves the problem.

My PO16 is not experiencing the same issue (firmware 1.3.1 seems to be OK). Haven’t tried to flash 1.3.1 or 1.3.2 yet on my two PBF4 devices.

Grid Editor version: 1.5.5

Thanks for reporting this issue!

Are you using D51 or ESP based modules?
image
In this example E-32 means ESP32.

Can you export the configuration for the EN16 as a profile and share it with us for debugging?

Also it would be helpful if you could check whether the same issue happens if you clear the configuration before the update!

I hope we can resolve this issue soon!

If it is ESP32 based that please try manually updating to this firmware build: Release Grid v1.3.3 (2025-05-11-1441) · intechstudio/grid-fw · GitHub

Thanks for your reply.

My EN16, as well as my other devices (1x PO16, 2x PBF4), are all ESP32 based.

I tried to manually update my EN16 with firmware build 1.3.3 - before and after clearing each page configuration - but I am still facing the exact same issue in both cases.

Here is my configuration profile: grid-editor://?config-link=xeVrWP5DrNMK3uiS3pH7

Reverting back to firmware build 1.2.39 solves the problem.

Update: Issue still persists after manually flashing firmware build 1.3.4 (device stuck with purple LEDs on).

Please try a factory reset before the update to see if it helps!

Yes, I did with each version (1.3.1, 1.3.2, 1.3.3, 1.3.4) with no success.

Hi guys! I also run into lots of issues since the update. the modules will randomly disconnect and get stuck. I already tried to NVM erase it and so on but nothing helped.

I am using E-32 based modules. PBF4 PO16 BU16 and EN16 all ran into issues.

reverting back to 1.2.39 resolves it it for now

What issues have you run into on the EN16 and the BU16?

All of them got stuck at some point meaning, they got unresponsive and/or disconnected from each other, especially the ones not directly connected via usb but connected to another module through the magnets.

We just pushed a Nightly FW release, you should be able to update to that by enabling the option under Preferences/Developer Options/Nightly Firmware Update . Please try it if you can, the patch fixes the following problems:

  • instability issues with PO16, EF44 and PBF4 that sometimes prevented boot or storing changes
  • immediate_send() being improperly encoded, and therefore becoming non-functional in some cases (you can test it with the 64CTRL and 16CTRL profiles)

Let me know if you still experience issues after updating!

The nightly FW release doesn’t change the problem on my side (did the automatic nightly FW update) both with and without factory reset.

EN16 device (ESP32 based) still unresponsive with fixed purple LEDs on. Reverting to 1.2.39.

Hello. In my case, I connected three PBF4s to AbletonLive and ended up in the same situation. (Mac OS latest version Macbook)

First, as mentioned in the previous topic, if the grid editor is not launched, the midi signal will not be sent. I managed to restore it to factory settings and restore it.

However, as you wrote in this topic, suddenly, while playing Ableton, one of the three modules connected by USB cable lit up purple, and after that, it did not respond to anything I did.
I initialized it, rolled back the firmware version and grid editor version one by one, and verified it, but it did not work.

I watched the flow of the midi signal with midi monitor (external free app). Of course, I connect not only PBF4 but also various devices with midi. I noticed that one of them, the novation Launchkey mini25 mk4, was constantly sending midi clock.
I turned off the midi clock transmission of the Launchkey mini25 mk4.

I’m currently on v1.5.6 of the grid editor and v1.3.4 of the module firmware, and the problem seems to be resolved.
I think it could also be caused by a midi clock or other midi signal being sent and received all the time.
You don’t have the same equipment, so I don’t know if this applies to you, but I hope my experience helps.

I’ve also had a lot of trouble with the new firmware. My PO16’s would take a very long time to start and then become unresponsive (either with LED’s stuck on blue/purple, or as I set them up but still nothing is output or changes). I also had issues with immediate_send whereby the string sent was not properly recognised, and it would show syntax errors about unknown characters. Had to revert to 1.2.39 for now

Have you tried factory reseting the module and then updating to the latest Nightly Firmware? The above-described issues should all be resolved.

I have. Didn’t help at all I’m afraid

What are the serials of the modules starting with purple LEDs and remaining unresponsive?