Got it, thanks!!

I’ll see how I get on, now I have worked through that example I don’t see anything else in the scripts that’s going to cause me any problems. I am pretty confident I’ll be able to get it working correctly.

In my defence, this did start out as an exercise in how to convert these scenes to work with the ER-301 over i2c so I was kinda on track… … … okay… I’lll get my coat and see thee over on Lines :smiley:

Thanks again!!

1 Like

Thanks and copy that apropos off topic. Appreciate all your efforts in this regard!

1 Like

Asked this over on Lines, but maybe here is a better place:

I have been thinking more about the TXi

Is it possible to route the TXi knobs to the ER-301 through i2c without impacting too much on scripting space?

Something like

L 0 3: SC.CV + I 1 TI.PARAM I

in the Metro script?

If so, it’s a super easy way to get a lot of knobs and extra physical inputs on the ER-301 :smiley:

I think the only way that would work would be by polling that input at a very high rate. I guess you could audio rate trigger a script or set metro to a fast tempo.

1 Like

Code space wouldn’t be an issue. The problem would be how fast you update the control. Maybe with a slew on the receiving end, you could avoid sudden jumps(?)

1 Like
L 1 4: SC.CV I TI.PARAM I

…is what you are looking for. (The TXi indexes at 1 just like the Teletype.) I’ve set pretty high rates for M in the past and have had no problems.

I’ve also coded a master mode for the 16n that I’m planning to port over to the TXi at some point. If you load the “master mode firmware”, the TXi sends output to the ER-301, Ansible, and TXo (simultaneously) without requiring the Teletype in the middle.

Apologies if I’ve shared this before; here is a 16n prototype running in master mode controlling the ER-301 primarily, but you can see the CV lights on the TXo and Ansible reacting in the background as well.

3 Likes

Hell yes!!

That’s what I wanted to hear, this is great! I’ve been wanting a control surface for the ER-301 for ages and these are going to do the trick very nicely in a way I am 100% happy with.

This is really taking shape as a really nice system - excellent work :smiley:

1 Like

If you’re using a 16n in master mode, the Teletype can’t be on the same I2C bus can it? I thought I remembered that multi-master isn’t a thing in I2C?

1 Like

That is currently the case. i2c potentially can support it - but the Teletype doesn’t currently. The answer to “why?” and “can it someday?” is that “it is complicated.” :expressionless:

3 Likes

Looks like I need a little help with this integration if anyone is willing. I outsourced the solder work to a local shop since I am out of practice and don’t have great tools. Photo below.

TT boots to firmware 2.3 beta 3D2CCB9.

ER-301 is on 0.3.22, teletype enabled in settings. Slave address 0xB0

I think I have the connections right - photos below.

But if I insert an SC.CV unit, port 1 and issue from TT:

SC.CV 1 V 2

I still get a zero voltage on the SC.CV unit.

What am I missing? Any suggestions for troubleshooting?


Connections look right, but that soldering work looks pretty sketchy :frowning:

Do you have any isopropyl alcohol, find an old toothbrush and use a little alcohol to clean that work up - repeat until all the residue is gone. Then take another photo so we can see what is actually going on.

Don’t panic!

Oh, you are sending a trigger to the appropriate script on Teletype right?

My thoughts exactly.

I just issued the command in live mode. Should that work?

I never use the live mode, so not sure!

How about SC.TR.P 1 with a SC.TR unit?

There shouldn’t be any difference between putting the command in a script and triggering it vs running it in live mode.

1 Like

I would be concerned about the connections there…looks like the shunt is also touching the part above too.

Yeah, I don’t think the i2c is working. I’m pulsing one of the TR 1 on script 1 with the incoming clock just to prove that’s working. I should be seeing a pulse wave on the 301, right? I’ll clean up the solder and post a new pic. Can I put a DMM across this to verify the shunt?

Which connections?

Not really because you will always get a connection, it being a piece of wire or whatever.

as @jonny says it really looks like the component above is involved too, but won’t be able to see properly without giving it a good clean.