#88

Trying to get Teletype to talk to er301

used http://wiki.orthogonaldevices.com/index.php/ER-301/Teletype_Integration#Required_Hardware_Connections

Rev7 board

typed in all commands

SC.TR port α Set TR value to α (0/1)
SC.TR.TOG port Toggle TR
SC.TR.PULSE port Pulse TR using TO.TR.TIME/S/M as an interval
SC.TR.TIME port α time for TR.PULSE; α in milliseconds
SC.TR.POL port α polarity for TO.TR.PULSE set to α (0-1)
SC.CV port α CV target α (bipolar)
SC.CV.SLEW port α CV slew time; α in milliseconds
SC.CV.SET port α set CV to α (bipolar); ignoring SLEW
SC.CV.OFF port α CV offset; α added at final stage

in live mode and got nothing so far.

anyone have a simple script that will work on teletype to test it

1 Like
#89

i think since a recent Teletype firmware the 301 address has changed and must be configured as 0x31 in the ER-301 (as per the bottom of the wiki page you linked, which predates the addresses changes).

#90

still does not work, tried all addresses.

all connections, checked etc.

#91

Thanks, the address was indeed an issue on my side!

#92

detailed info on which address to use:

the above applies to the teletype official latest release 3.0 (please note the version number was changed from 2.3 to 3.0 in the final version).

there is also a corresponding change that needs to happen in er-301 firmware, not sure if it made it to 0.4 but the above will work either way as long as you use the addresses listed in the post above.

3 Likes
#93

Hey everyone! I’m a regular over at Lines, but I’ve been lurking here ever since I submitted an order for a 301 last month. It arrived earlier today and I’m having an absolute blast getting started.

One quick TT question if I may, around some weird behavior I noticed while using the Clocked Doppler Delay. I’m sending SC.TR.PULSE to the clock parameter (via port 1) just fine, but I get a noticeable - albeit temporary - warble in pitch/multiplication when I press the TAB key on the keyboard connected to my TT when switching between live/pattern/scripts; it’s almost as if switching between modes on TT sends a little offset for a split-second to…something. Tried driving the delay clock with a physical trigger from TT instead, connected to A1, but the same thing happens.

Am I overlooking something obvious? :thinking:

1 Like
#94

i assume the delay would exhibit such effect if the interval between triggers fluctuates. are you triggering from a metro script? it’s possible that some actions would result in timing fluctuations but switching modes shouldn’t be one of them (unless HID code runs on higher priority than timers, i’ll take a look). i’ll do some measurements.

6 Likes
#95

That’s exactly it - both triggers were indeed running from the metro script. If it helps you narrow things down, the fluctuation doesn’t occur when I navigate between scripts on TT - only when switching between modes.

Thanks for taking a look! I’m mostly just amazed at how quickly I was able to get TT and 301 talking to one another.

2 Likes
#96

that’s very helpful, thanks! the very likely reason is - it will write the latest mode to flash (so it starts in the last mode used when you power it on), which happens every time you change the mode, but not when you just switch between scripts. i’ll disable it and test.

if this is the actual reason we might need to disable that feature or maybe make it user selectable.

#97

did some measurements and confirmed the issue. continuing the discussion here: https://llllllll.co/t/teletype-3-feature-requests-and-discussion/16219/182

1 Like
#98

Thanks for the follow-up and the detailed description over on lines!

#99

I’m not sure whether I should post this here or on Lines, but I found something odd. I expect the bug is on the Teletype side though.

On the ER-301, I have pink noise gated by a VCA controlled by SC.TR 1, and a sine gated by SC.TR 2. Running this script, I would expect to hear a noise burst on every beat and a sine every 4 beats:

SC.TR.P 1
EVERY 4: SC.TR.P 2

But instead, I hear 3 noise bursts and then the sine with no noise.

This works fine:

EVERY 4: SC.TR.P 2
SC.TR.P 1

As does this:

SC.TR.P 1
SC.TR.P 1
EVERY 4: SC.TR.P 2

And this:

DEL 0: SC.TR.P 1
EVERY 4: SC.TR.P 2

And this works as expected, with both the noise and sine triggering on every beat:

SC.TR.P 1
SC.TR.P 2

But this does not:

SC.TR.P 2
IF FLIP: SC.TR.P 1

And this does:

SC.TR.P 2
IF 1: SC.TR.P 1
1 Like
#100

What happens if you don’t use i2c, and just use patch cables and TR.P instead of SC.TR.P?

1 Like
#101

It works fine that way… but then, today it’s also working fine using SC.TR in every case. :thinking:

I tried starting up Teletype with the default scene I was using before (which rapidly polled the 16n Faderbank and passed along values via SC.CV), and then switching back to my test scene but that didn’t cause it to fail.

#102

I finally built my microsystem and have the teletype, er-301, and telexi playing nicely. It’s very very very cool.

However, I don’t think sc.cv.slew is working. If I do it over wires, I hear the slew. If I do it over I2C, no slew. I’m on the latest release of everything (so er-301 0.4.20, teletype 3.10). Can anyone confirm? I will post to lines as well.

#103

I haven’t had issues here. I’m on the same TT and 301 firmware. Can you confirm you set slew with “sc.cv.slew [port value] [slew value]” and have the port value configured correctly on the 301? If you use the sc.cv.set command, slew is ignored.

#104

There is no slew at all with the sc.cv.slew command afaik. I’m not using offset either.

#105

Can you post the TT scene you are running and what is connect over i2c to the 301? I’m not in front of my system right now, but I’ll try and reproduce what you have later tonight.

1 Like
#106

Just upgraded TT to 3.1.0 this week, and I can’t reproduce a problem with slew using the SC.CV Unit either. Seems to be fine for me - slews as expected. Sounds like you’ve confirmed it using patch cables. Worth reflashing both devices to see if that resolves it? I’m not sure what else to suggest.

1 Like
#107

Hi, I posted the scene in the other thread via a link to the lines forum. The only difference is changing all cv commands to sc.cv and all tr commands to sc.tr…

I will try reflashing and seeing if that works. Thanks.