MDX unresponsive episode

[ignis32]

I just had a concerning episode with my MDX. Without any reason, my MDX lost connection while in the middle of looking into UI of my pedalboard. I had not been even changing anything, just was looking into the pedalboard, to make a screenshot for the forum topic.

After several power-on poweroff cycles without wifi or usb network connection working, I’ve noticed that physical UI was unresponsive as well, with no reactions to the knobs or buttons. Tempo bpm button was blinking however.

Something wrong was with an upper part of the screens -

It looks like it had not been drawn properly:

1. Part of the “X” from the duo x logo had stuck in the place where master volume should appear on the right screen
   This happened every time I powered the unit.

2. on the left screen pedalboard name did not appear, so i think it is the same - partial leftovers from the boot up screen. I am not sure about this one if it happened every time, but that’s probable.

Unplugging all the perpherials did not help. it was the same even with nothing but power plugged, and even tried alternative power source just in case if power brick got broken.

Also I had heard relay click in the moment when it usually do not happen, like delayed for a minute or something, or maybe that was a reaction to my random buttons tapping.

After a about twenty power cycles, I’d been able to boot properly once (maybe or not it is related to my attempts to tap endless knobs during power up, at least this only proper loading happened that way, i recall tapping both endless knobs before successful boot, as i was trying to recall recovery mode combination), I’ve used this opportunity to make a full backup.

After making a backup I’ve tried to load a pedalboard from the All pedalboards list using physical UI and got into the same unresponsive state immediately.

Powercycles did not help for about another five times, so I switched MDX to recovery mode and flashed factory reset image, and restored my data from the usb flash.

So far it seems to work fine again, I’ll update later for sure if something would go wrong again.

That was a quite unpleasant hour spent, and I am not still sure if it is an end of the story.

[khz]

With my DuoX this also occurred once with certain self-made pedalboards. That the DuoX does not start properly had to do with this pedalboard, possibly something stupid connected or something.

Did/can you start your DuoX with another pedalboard?

If not, as a last possible option, you can also manually force an empty pedalboard:

Start ModDuoX with empty pedalboard

if ssh still works, you can delete /root/data/last.json which will reset that last loaded pedalboard. then a hmi-reset; reboot should make your system come back to life again. would be very welcome if you could share the pedalboard that causes the issue, so we can fix it. let us know if you need help on that (sharing could be via targz uploaded here, since the PB fails to load correctly it is likely you wont be able to share it online within the web UI) thanks!

Maybe your problem could be similar.

[ignis32]

It might be something like that, but:

1. I had no network access during the failure to change anything via ssh.
2. I had been using this pedalboard without any changes for a couple of weeks and had not changed anything in it before the failure, basically I’d loaded just fine with that pedalboard just to take a screenshot - there were no changes done. Failure happened when I was looking into a functional UI and trying find a good zoom on the particular part of the pedalbord.
3. After factory reset I’ve restored same pedalboard back from usb flash and it does not cause problems now yet.

Overall, if it is caused by the pedalboard, it is not that direct, to my guess.