(ansible) 3.0.0 release

[eblomquist]

ansible

currently says it is for 2.0.0.

Is there a new doc coming for 3 or does the doc need updating?

Thanks to @tehn and @csboling and the rest of the wonderful crew for all you do!

I’m so looking forward to getting this installed soon…

[yoyosandshoes]

Really exciting! Thanks for all the hard work

[jakecarter]

20 chars of “Sweet! Thank you!”

[jasper_ryder]

I’m having a hard time getting ansible to consistently (connect to?) sequence JF’s.

Can anyone who has a ansible<crow<JF’s setup verify this is working consistently for them?

Occasionally it works but after power cycle I have to do a bunch of plugging/unplugging grid/ ansible leader pad turned on/off combos, and throw a Norns in the mix to get it going again. I’ve run the ii.pullup and reset commands in druid as well.

Sometimes it works, most of the time it’s not. Norns is running Awake and it is sequencing JF’s as normal.

Edit: Is there a way for ansible leader mode to not automatically be on after power-cycling?

[csboling]

@eblomquist

currently says it is for 2.0.0.

I updated the docs yesterday but missed this spot.

@jasper_ryder

ansible<crow<JF

Will investigate this shortly. Are these 3 devices all you have on the bus?

[scanner_darkly]

i had similar issues with polyES and orca’s heart in leader mode with crow on the same bus:

Polyphonic earthsea for trilogy/ansible and er-301/just friends/txo

partial success. i’m able to reproduce the issue with ansible running polyES + jf + crow setup. i was able to get it working for a short while while crow was still running the initial first script by running druid and executing: ii.pullup(true) ii.jf.mode(1) i tested with orca’s heart first and the above fixed the issue. what’s strange though is that switching OH to a different i2c device and back (which also tells jf to set mode to 1) made it stop working again, and repeating the above didn’…

[jasper_ryder]

Correct, just the three on the bus. I do have two ansibles and have swapped them in the bus with the same results. Thank you for your time and efforts on the new firmware!

[EqualTemperament]

You have my gratitude for all of the effort you’ve put into ansible and teletype @csboling! Having played with much of this during beta, I can already say they are excellent and useful improvements!

[Prnts]

No problems here getting JF to connect with crow also in the i2c chain. Only issue I’m having right now is getting the er301 to take. Anyone have any luck using lets say Kria with the er301?

**edit got it sorted. Wow this is so nice. It really really changes things for how I can sequence samples on the er-301

[gnome666]

@Prnts

It really really changes things for how I can sequence samples on the er-301

do tell

[jasper_ryder]

Hi,

So you are using the JF, Crow, ER-301 and Ansible chain without anything else in the chain like a powered bus board?

Thanks

[Prnts]

My i2c chain has ansible, crow, tt, JF, w/, ER-301

I didn’t have any issues sending to JF or ER-301 from ansible.

[jasper_ryder]

I think your tt is the reason why you are not having issues. Having the crow supply the pullup resistors in the chain is maybe the problem in this chain.

I’d be curious if you separate your TT from the chain what results you would have? I know fiddling with i2c wires isn’t fun so if you aren’t up for messing with it at all I totally understand.

[csboling]

@jasper_ryder

if you separate your TT from the chain

In my case also having Teletype connected makes everything work fine. When I have crow, W/, Ansible, and Just Friends on the bus, the procedure that seems so far to work consistently is:

• make sure leader mode is disabled, then tap the preset key to exit the preset page and save leader mode settings to flash.
• reset the case (I’m using a Tiptop Mantis)
• now enable leader mode.

This seems to work every time, at least with my current I2C wiring (all three modules are on a single 3x2-pin ribbon cable). As opposed to @scanner_darkly’s experience with multipass apps linked above, I am able to toggle leader mode off and on in this case and it still works. I am even able to send ii commands from crow simultaneously.

If I have leader mode enabled when I power Ansible on, it’s not able to communicate. In some cases I can still get crow to talk to Just Friends if I mess with the jf.mode.

If I replace JF with TXo, I can’t get it to work. If I then add either or both modules to the bus and add Teletype, it works again. I’m not too sure what’s going on here but I’m certainly intrigued, for now I would say probably a powered busboard or Teletype is the best bet. Interested to hear if the procedure above works for others or there’s something case / bus specific about this behavior.

[jasper_ryder]

Hi @csboling,

Thanks for looking into this. I am not having luck so far and have run into a strange issue with crow. Every time I restart the case now the pullups are low. I am unsure how to get crow back to starting with them high. Here is a snapshot of what I’ve been seeing. It’s funny JF’s makes a little sound like it wants to go when ansible leader mode is selected but then nothing happens. I have ordered a mini powered bus board though and hopefully that cures all of this.

[scanner_darkly]

i did get a short sound too at some point, i think after executing jf.mode on crow.

interesting that it works with teletype - i’m going to do a test with teletype and a test with a busboard. will also try running multipass on teletype itself.

[Galapagoose]

Just to clarify, the ii lines are low message from crow doesn’t mean the pullups are off, rather it happens when an i2c message failed because the bus was in the busy state for too long. I can see how the error message is confusing if pullups are already enabled.

The issue is likely insufficient pullup current as crow’s pullups are very weak and typically only work for 1 or 2 devices on the bus (though it is highly dependent on which devices). I believe a powered busboard will solve your problem.

[David_Rothbaum]

@tehn

NEW : i2c leader mode for controlling Just Friends, TELEXo, or ER-301 from ansible

wow, this is amazing. thank you.

[jasper_ryder]

Thanks for the clarification on all that. Sounds like the powered bb is the ticket. I’m glad I was able to find one as there were only a couple available from the place selling pre-built ones.

[disquiet]

Thanks. I think I’ve managed the Ansible 3.0 update correctly. Two notes, from my experience today on Windows:

First, I couldn’t use the cmd (Command Prompt) app, even in administrator mode, to do this, but I did manage to use the (new, beta) Windows PowerShell. (I have no doubt I was doing something incorrect in regard to Command Prompt, but so be it.)

Second, when running dfu-programmer it required me to put .\ before dfu-programmer (i.e., .\dfu-programmer etc.) for it to function. I am clueless in terminal mode, so I just follow instructions and hope not to erase reality.

Otherwise, it all seems to have worked. Is there a way to test out the Ansible to confirm what version of the firmware it’s running? Thanks.