I performed a successful sysex dump/patch of the FCB1010 using the mountain utility editor no problem. Went exactly as planned, but naturally decided I wanted to tweak the presets a little to improve my workflow while playing...
But when I went to send the new dump (via green button in editor UI/pedal 7 engaged on FCB), instead of the FCB green config light flashing, a separate red dot flashes in the digital number display and the FCB returns an empty sysex message (F0 F7). Exiting global config on the FCB with the down button saves nothing, I don't think it's even receiving the data to begin with.
To troubleshoot I used python and the mido library to code receive/send functionality myself to rule out the mountain util. But I have the exact same outcome... the FCB flashes the red dot, returns an empty sysex message (F0 F7), and no data is saved.
FYI: I can program manually still using the foot pedals; I can receive sysex dumps from FCB no problem (through the mountain utility and my python scripts); I am connecting the FCB with midi cables through an AXE I/O one USB interface.
I can't find anything online, or anyone else who has this issue. Figured I'd just ask here if anyone knows what might be going on.
Can a sysex dump from the editor corrupt memory/the chip? Why did it successfully receive a dump once but never again?