#36

it sounds like you’re repeatedly running into a known bug which is param reads inside the metro.

is this on a fresh flash of ansible?

#37

I am not sure what you mean: fresh flash of ansible?

#38

apologies-- newest firmware update, with default settings

#39

Ah, yes, fresh flesh - I am just scaling the output range down. teletype the same, nothing saved and just single or two line scripts or live mode commands.

#40

@tehn Now with i2c running better I did a short video exploring the range behaviour of cycles.

This script pushes cycle 1 forward from 0 - 64 which is one full cycle and puches cycle 2 forward by the read value of cylce 1 which is four cycles as cycle one read values have a range from 0 - 255 (to clarify, the movement is just the metro script, cycles it self are setup to move very slow/stand still as you see on three and four):

X ADD 1 MOD X 64
CY.POS 1 X
CY.POS 2 CY.POS 1

Also mind the pattern of the LED glitch - it’s always one cycle doing it after the other. On the first two cycles it is masked by the programmed positions.

I am happy that i2c remote has made a step forward and hope this does help on debugging Ansible.

:+1:

#41

@tehn I am still struggling with cycles. See the strange position read/write behavior above and how cv gets stepped after powering the case down here:

It is possible to fix it by reflashing the firmware but only until the next power down. This does not occur with the Ansible 1 firmware from Dec. 2.

It already is the replacement module I received.

#42

@Leverkusen does the stepping happen if you don’t downscale?

thanks for posting an exact replication video, this helps.

#43

@tehn Yes, it happens regardless of downscaling the range or not - just did it to fit the oscilator range better for the video.

#44

@tehn another thing that frightened me a bit:

When I plug in the update cable as long as the case is powered and then power it down the whole case gets powered via the USB cable and Ansible - all LED’s of all modules in the case are lit then.

This does not happen when I plug in the same update cable when the case is already powered down.

1 Like
#45

definitely power down the case first, and then plug the cable in.

can you confirm that you’re getting stepped voltages for all 4 channels?

#46

Yes, on all four channels.

Could something got damaged by plugging the USB in when still powered?

#47

I’ve noticed this as well, it’s frightening indeed. Any damages possible ?

#48

no, your modules are fine.

@leverkusen can you try flashing new, power cycling, and testing cycles with an attenuator instead of using the scaling? then power cycling and seeing if the stepping happens?

#49

@tehn Don’t know if I got you right - you mean to test if the intermediate use of the scaling function does harm anything?

If so it doesn’t - reflashing fixes everything and a short power cycle breaks it again, even if nothing was touched (apart from nudging the Arc encoder…)

As a similar issue occurs with Earthsea where I experience the old and previously fixed clamping freeze again with the new i2c proven firmware while you can’t reproduce it I wonder if there is something wrong with the update routine?

I just downloaded the homebrew thing again but it did not make any difference (on a MacBook Pro Retina late 2013, OS X 10.11.6).

#50

@tehn

Don’t know if this is any helpful or just displacement activity out of dispair and helplessness but I found an old Windows XP notebook under my table and did the firmware flash from there. But with no success (apart from remembering why I had switched to mac years ago, hell what a plague this was…).

Eventually I got the firmware flashed to Ansible and again on the actual version cycles voltage becomes stepped with the first power cycle (actually the second power cycle if you count the one that is necessary to leave bootloader mode).

Again no problems with the intermediate firmware from early december that is not amongst the github versions.

Is it really that I am the only experiencing this? With two Ansibles? In two different cases?

#51

i’m back in the workshop today and will be looking at your situation after some repairs are completed.

1 Like
#52

Great! If there is anything to try out to support this I am there…

#53

ok, so there’s an initialization bug when you start up in cycles, i finally reproduced the stepping.

immediate fix: switch to levels and then back to cycles.

i’ll get a firmware fix posted soon.

2 Likes
#54

Yes, that works - great!

Thanks for looking into it!

:relaxed:

#55
2 Likes