parts are mostly 0603 with a few 1206 here and there. (there aren’t any 0402 - that would have been mean!) and while the parts can look sparse, the routing to pivot from the board interconnects to the teensy was super-tricky and i needed the space. there are four layers of transit going on all over the place; here is just one side of the TXo’s back board:

that said - i’ve learned so much since i routed these boards. would certainly do things differently now. but it was a great project to learn on - and everyone here was so supportive in helping me along the way.

i really don’t mind the 0603 size given that i use stencils and a reflow oven. might be different if i was placing each part by hand:

3 Likes

I stand corrected. 4 layers? Wow - yes you crammed a lot into a tiny width here.

During the design of TXi, were you ever tempted just to stick an I2C ADC chip on it instead of the teensy? Teensy seems like a lot of overhead for that role. TXo certainly looks like it requires every ounce of the teensy, though!

no - but i was tempted to do a lower-power arduino, but decided that keeping it on the same platform made the most sense from a DIY perspective. the tooling that has been created for the teensy (especially the bootloader on the MKL04/02) makes ground-up builds and modifications very approachable.

yes, the 3.2 is massive overkill for the TXi. the speed is put to some use making reads as responsive as possible. back when i was designing them, i2c reads over the bus was unexplored territory. i figured making reads to be as fast as possible so that there was little to no impact on the teletype’s timing would be a good thing. ignorant and paranoid? yes.

ASIDE: as a consolation, the TXo uses every drop and then some of the Teensy 3.2/3.6 with its extended features. in addition, because of the teletype’s decoupled and programmatic control, all changes are run at audio rate for maximum smoothness and responsiveness. (audio rate on the unit is 25 kHz / 15.625 kHz for the TXo+ / TXo, respectively.) this means that SLEW is buttery-smooth. :slight_smile:

if i ever do a refresh, i certainly would simplify things a great deal and move everything on-board with processors that are tuned to the demands of the individual modules. might be less fun to DIY at that point as you will need toolchains and programmers…think diy mutable challenging.

2 Likes

Ok so I’m sorry I suck
Can someone please tell what or how to get the pin headers I copied the bom cart and apparently none of this was in my mouser cart when I received my order

There is no “official” source for the pin headers. I’ve always purchased precision/machined headers on eBay. I would use the headers discussed above if I were building one today:

Good luck!

1 Like

Not sure if this is the correct place to post, but my TxI has been acting up. It seems the I2C connection is very unsteady – before I screwed it in it would connect fine, and TT could read the knob values. However, after screwing it in all the values read as 0. I repeated this ‘take it out, wiggle the connector, test values, screw it in, test values’ this a dozen times just kinda hoping it would work…

Any likely culprits or good next steps?

Edit: I’ve tried with multiple cables, and tested the cables as well. Other modules are doing fine connections to TT.

I’d make sure your boards are staying seated when it goes in the case (and that nothing is touching the TXi that would short). You might try wrapping a zip tie or string around the PCBs to keep them locked together.

2 Likes

I have a question about TO.OSC.WIDTH x y. In the Teletype manual, it is mentioned that it only works with wavetable 3000 (btw cool DJ name). How does it work with the Txo+? There wavetable 3000 seems to show no changes with varying width.

Was a very simple problem at the end of the day – my new case is shallow and while the TxI ‘fit’ on the same row as the power board, the I2C cable was getting tweaked a bit. Moved out to a new row and we’re good. Thanks for the reply – I’ll be more careful about these details in the future.

TO.OSC.WIDTH

Wow - I’m super glad you asked. Looks like I optimized it out of the code in March of 2018. Oops. (facepalm)

I’m a little full up at the moment - but I have this fix on the docket for a small update when I have the time to test it fully.

Cheers!

b

2 Likes

Great, thanks for that.

Might not be the best place for this question, but…

Could anyone advise how I might produce a uni-polar (ie 0-5V) LFO on a TXo CV output?

1 Like

Not sure you’re looking for this. Found it in the manual. TO.OSC.CTR x y For example, to create a sine wave that is centered at 2.5V and swings up to +5V and down to 0V, you would do this:

TO.CV 1 VV 250
TO.OSC.CTR 1 VV 250
TO.OSC.LFO 1 500

3 Likes

Cool, thank you! Will try that.

Hi! Im working on a scene for teletype where i use a txi pot to change the waveform of one of the TXO outs.

Since i have a txo+ that includes more waveforms, what should be the range of the pot?

I have followed the Teletype talk tutorials and the range is 0 - 4095 but i dont know what range is should use for the txo+ since it has more wafeforms?

Thanks!

1 Like

Does anyone know which side of the power cable connects to the TXn as it’s only 4 pins?

Edit: Figured it out by looking up the pin configuration of a Eurorack cable and saw that it doesn’t matter which side :slight_smile:

The bpcmusic docs talk about the basic waveforms:
Imgur

The Telexo+ store page states:
Imgur

Presuming the CV outputs are capable representing 16383 different values between 0 and 10V.

That leaves us with 327 divisions of 16383 but I’m not sure if the waveform set utilizes the whole range…That’s a new waveform approximately every 50 possible values.

I have no understanding of the technical details pertaining as to how it’s cross-fading or interpolating between waveforms, or as to the content or order of the waveforms.

I’ll try when I get my TXo+ hooked up later this month.

1 Like

Thanks @adnauseam ! Maybe @bpcmusic can give us a hint?

I am trying to add a second TXi to my system, Im a bit confused on how to connect it properly. I have tried i2c cables from each txi to a txb “hub”, as well as txb-teletype-txi-txi daisy chain. When trying to daisychain Im not sure what to attach the i2c cable to between the two txi’s, i2c to i2c? i2c to “address”…
any help is appreciated