No, deliberately kept it simple. Currently running a 5 step loop, quantised. All still running ok.

@GoneCaving which grid edition are you using?

i’ll try tuning some values differently and get a new version up today.

Walnut 128, just prior to the current slimline version; that’s the 2013 version? Current test is still running fine after an hour.

After heavy using (not a use case) ES gets unresponsive. Multiple power-cycles (> 1min) didn’t help, after a few seconds after Power on ES gets unresponsiv.

can you confirm that reflashing the firmware instantly returns it to working order?

the last long power cycle (>5min) fix it. I’ll try to reproduce it and reflash the firmware to see what happens

Ran fine for about 5 hrs this time, then failed in a similar manner to previous test.

And one more attempt today. 3-4hrs ok, then the played pattern out of sync with the grid, CV values drifting from what had been set (I’ve noticed this previously), and eventually locked up.

CV values drifting even though you didn’t have CV shapes assigned? or do you mean just pitch?

Yes, I mean CV1-3 (mainly CV2) drifting/changing values even though no shapes had been assigned. The pos/pitch seems to behave ok.

it happens again.
no special preconditions, no shapes, recording etc.
Just playing some notes after startup till a total ES freeze

Maybe helpful:
after a couple of minutes, Grids is back to life

  • ES.Edge Output is always high
  • ES.Pos output works
  • No Reaction if I select shape memories on ES and Grids (not the two LEDs)
  • CV change with Pots directly on ES works also shown on Grids

after some more time (I think i unconnect grids)

  • on a first look everything looks ok, “only” the ES.pos out does’t work anymore
  • a short power-cycle fix everything

Marcus

also still experiencing issues, but I haven’t tried the firmware posted in this thread. will update then report back.

new version, adds MIDI support (thanks to @ngwese)

please report slowdowns. i can rapidly post test versions today.

es160321-1.zip (45.7 KB)

6 hours running the most complicated thing i can do, on an old/different previously-reported defective unit. still can’t get a crash.

i know many of you have reported your power specs before, but if you could re-report your power setup perhaps i’ll notice something?

i’m direct-powering (no switch/etc) from a rowpower 40.

Pattern setup to alternate same note, but between two shapes. Quantised and sped up (once). Getting slow down after only a few minutes. Restarted, and managed to get a slowdown straight away.

ES is in a skiff with a 4ms Row Power 30 (https://www.modulargrid.net/e/racks/view/122248). Grid powered by a Switch. Voice in a separate case (https://www.modulargrid.net/e/racks/view/126029).

my setup is uZeus with switch. single 84hp row, well within the power specs.

can you do a quick test for me? here’s a built with the DACs disabled, so you won’t get any CV output. but let me know if this slows down.

es160321-dacs-disabled.zip (45.5 KB)

After running for about 20mins its seems to be consistent. I’ll leave it running overnight and see what it looks like in the morning.

7hrs later, still ticking along, responsive and no sign of a slow down.

well, that’s something!

here’s a new version. halved update frequency on the DACs, but doubled the speed of the SPI update.

es160322-dac-10ms.zip (45.7 KB)

1 Like