#21

Yep, I did power-cycle. It’s more the way it came back to life, briefly, and then froze up that has me concerned. Rebooting now only brings up a ‘dead’ module. :frowning:

I tried re-flashing a couple of times. Mac says it completes the routine successfully, but still no response from Ansible.

#22

to make sure.

  1. flashes successfully as indicated by command line
  2. wait 10 seconds for good measure.
  3. unplug USB A-A cable
  4. power cycle modular case

and then it should be good. i can’t imagine what would go wrong, so if it’s still busted, e-mail info@monome.org

#23

I’ve haven’t tried it on the Ansible that I have at work yet. I’m brave, so I’ll give it a shot on that one. Then I’ll retry like you suggest when I get home tonight on the problem child, er, module.

Thanks.

#24

I was able to successfully update my other Ansible unit. I’ll try the problem child other Ansible tonight.

However…my other Teletype won’t go into firmware update mode. Any other tricks for getting that to happen? Keeps booting up into 1.1.

#25

hold the button harder, might be a bad contact.

try powering up the tt with usb cable connected to computer. try powering up without being connected.

#26

Starting up with nothing plugged into the USB port did the trick. :+1:t2:

1 Like
#27

this works fine for me. so there must be some sort of state information that is getting messed up. please let me know if you can produce a reliably replicable error from a clean boot.

this is a real bug. something about i2c inside the delay buffer is breaking stuff. i’ll look into it.

2 Likes
#28

Kria questions on the Ansible.

  1. Is it possible to change Patterns in sync? Like how you can cue up a pattern change on White Whale?

  2. How do you reset all channels? Both independently setting position on channels and/or getting all channels back in sync…

#29

Resolved the firmware update with my other Ansible. It just worked when I got home tonight. :slight_smile:

2 Likes
#30

home now and retested. did a fresh install of both firmwares. cv and trigger script from above worked but trying to set up a script like
tr.pulse 5
tr.pulse 6
tr.pulse 7
tr.pulse 8

will give me will only give me a trigger on 5 and 7 every time.
reversing the order from 8 to 5 gives me a trigger on 8 and 6.

tr.tog works fine though

#31

I can confirm this behavior (that multiple tr.pulse calls in one script doesn’t pulse the outputs like one would expect).

Looking at both the tt code and the ansible code I don’t see anything obvious.

1 Like
#32

thank you for identifying this-- will get it corrected.

#33

Is it me or there’s no way to have different lengths in Levels ?

#34

Question/feature request on Cycles :
in sync mode, i’d love to be able to set up the rotation direction. Counterclockwise for positive values, clockwise for going the other way round.
Also, a built-in attenuator/offset would be great.
(Should i start new threads for each Ansible app ?)

#35

Bug :
KRIA : Octave is only working on the first track.
EDIT : fixed in 1.0

#36

Kria : how do you change loops for individual track parameters ? Changing the loop here is global…

#37

for features requests, yes please

turn off loop sync on the config page

levels has the same loop positions for all rings. they are sync’d

1 Like
#38

i found this bug in levels mod : in note mode the positions (so the notes) are not saved with the presets :wink:

#39

thanks for spotting, will check

https://github.com/monome/ansible/issues/6

1 Like
#40

docs bump, grid diagrams by @laborcamp

http://monome.org/docs/modular/ansible

9 Likes