#13

It’s the same one from the other thread.

The one you’ve already tested for me. (Thanks for that!)

#14

@tehn

I did a few tests now and what I experience with two Ansibles, the official 1.5 and the alternative firmware proposed by @sam is this:

The trigger outs of Levels always freeze within a few minutes with the firmware 1.5 when Ansble is externally clocked at a rational rate. CV is still responding to changes on Arc, changes are displayed correctly - just the trigger outs stick to “on”.

Every other possible combination of interfaces, modules and firmwares never lead to this (at least not within a short period). Grid is stable on both firmwares and Levels is stable on the new alternative firmware. This is consistent over both Ansible modules. They are connected to tt over the powered i2c bus but teletype is currently empty and nothing is plugged in.

EDIT: Clocking from 4ms DLD

1 Like
#15

yes, in my case. clock coming from a uMidi module.

#16

thanks everyone. will be working on this tomorrow. i have a pretty good idea how it’ll get fixed.

1 Like
#17

FWIW, I added a 5th symptom to the list in the first post. I had forgotten to mention the issue of the Grid/Arc going dark.

I’ll also mention that last night’s patch clocking with Pam’s in the quarantine case (with Grid connected) had no issues for the 3+ hours I left it on.

#18

Freshly purchased Grid and Ansible, external clock from 4ms QCD - been running great for a while, but today, I switched the clocking rate from the QCD, and the grid became unresponsive. Unplug, re-plug of grid does the trick.

#19

please try to reproduce it with 1.5.0 as i spent quite a bit of time working out USB hotswapping, as a separate issue a couple months ago. thanks!

Problems with Ansible/Meadowphysics
#20

new test version (danger, flashing your firmware erases your presets): ansible-1.5.1b01.zip (79.4 KB)

update command included.

i’ve been running this for quite some time clocked externally at a high rate (TT digital outputs at 10-25ms)

2 Likes
Is it normal for ansible to freeze after a lot of arc activity?
Does your teletype stop responding after an hour or two?
#21

Thanks, @tehn. I’m testing now.

Can anyone confirm that white LED #4 is not functioning properly? I’m outputting the same CV on all channels, but #4’s LED isn’t following the voltages that I’m measuring coming out of the corresponding jack.

EDIT: The LED isn’t lighting at all, even at max voltage.

#22

Ansible ran all night clocked via Pam’s New with Grid attached and the freezing/unresponsive issues appear to be gone!

Thank you, @tehn!

The LED issue, however, is still present. Later today I will load the firmware on to my second Ansible and report back.

#23

I am running 1.5.1 and am not having the led issue you are experiencing.

#24

I updated the firmware on my second Ansible to 1.5.1.b01 and LED #4 functions properly. All appears to be great with this new firmware update. Thank you again for making the fix so quickly.

I took a look at the PCB on my first Ansible with the LED issue and see that white LED #4 itself is actually missing. I had previously only used this Ansible with Grid, and often stayed low in octaves, so I hadn’t noticed that it didn’t work. But when I tested with Arc, it was immediately noticeable.

Here’s a closeup photo:

ansible-led-missing.jpg4608×3456 2.6 MB

@tehn, should we PM/email about this?

#25

yes e-mail info@monome.org i can replace your module right away.

1 Like
#26

Possibly found another bug in Ansible, this time with MIDI/Voice. I have an OP-1 connected to Ansible and if I power off the OP-1 for a yet-to-be-determined amount of time, and then power back on Ansible stops responding to MIDI input. Nothing is patched into Ansible’s inputs. Only Gate & CV output 1 are being used in Mono mode. Power cycling fixes it.

I’ll continue to pay attention to the details of power off/on duration to see what I notice.

#27

@tehn has the latest code been submitted to github? i’m hoping to start beta testing i2c related teletype/libavr32 fixes soon and want to make sure i use the latest official code.

#28

yes my repo is current. i think the only thing updated was the libavr32

1 Like
#29

To confirm the outcome here:

@tehn’s most recent update, 1.5.1.b01, had a solution. Is this now the recommended firmware to be using with Ansible if you have and use both the most recent Arc and Grid?

Thanks!

#30

i would like to hear from folks about this as well. i had a lockup the other night and couldn’t save my kria composition. ready to upgrade if this is the way to go.

#31

FWIW, @shellfritsch, this patch has solved the aforementioned freeze issue (for me).

I’m currently having some issues with Ansible and the OP-1 (also when swapping between OP-1 and Grid), but the details leading up to the bug are pretty elusive. All I can tell so far is that it occurs whenever the OP-1 is shut down while still plugged in.

1 Like
#32

good to know - i’ll check it out. also see if i can get it to play nice with my op-1. what sort of bug are you experiencing? a lock up?