#6

1 hour into clocking with Pams in the quarantine case and all is fine. This is going to get tedious adding one module at a time. I’ll report back when I have more data.

1 Like
#7

Sure, definitely - I was not trying to cloud things up. I don’t recall ever clocking my module externally. This happened to me a couple months ago.

I remember that I was switching between Kria and Meadowphysics when it happened. I could perhaps use the debug header on mine to help troubleshoot this further and see if I can reproduce it.

1 Like
#8

I have a similar issue with ansible. When I have it clocked externally from a mutable instruments grid module ansibles’ cv’s eventually freeze. It usually does not take very long for it to happen. I have to powercycle to fix the issue.

I have not experienced this with ansible using it’s internal clock.

I started a previous thread about this so just reiterating in this thread. Definitely looks like an external clock bug.

#9

i can confirm these problems to with external clocking but i have only just started to figure this out so ill take exact notes next and consequent failures (I suspect an easy fix though as its pretty evident now)

#10

Yes, I am experiencing a similiar thing - at the moment trigger outs of Levels are stuck while Arc is still responsive and CV out works accordingly to Arc settings.

#11

I can’t help but feel some of these issues may relate to things we’ve been fixing on the Teletype in the other thread.

I wonder if someone who has been experiencing problems could try the firmware hex in this zip file (you’ll need the update-firmware.command from an existing firmware release).

ansible.zip (79.4 KB)

It comes from here. It might not make any difference, but that’s something useful to know too.

2 Likes
#12

Is this the old new alternative Ansible firmware known from the other thread or a new new one? At the moment I am crosschecking both versions on this issue.

1 Like
#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