Loaded up a TT and pair of expanders for my trip to AUS into one of @c1t1zen’s USB powered Euro Lunch Boxes. Looks amazing; thought I would share:

The whole thing runs off an external USB battery I ordered from Amazon. I’ve since wired up both of the TELEX’s Teensy so I can work on firmware easily. I’ve a companion little rack with an O’Tool, BASTL mixer and speaker for when I need to look and listen.


Quick Update:

  • All of the panel and PCB reservations have shipped. Can’t wait to see the units in the wild.

  • I’ve updated the TELEX Microsite with some additional build notes for those doing DIY to help them avoid some tricky gotchas

  • Planning to add the collection of commands discussed above, @trickyflemming, this week.

  • Once I’m done with that, I’ll do a pull request for the TT code, @tehn + @sam

  • Back to hardware production on the weekend - jet lag willing.


TELEX HANDY LINKS
TELEX Microsite | Ordering Process Details | Crazy Verbose Status + Timeline
Open Source Repository | Printable Command Reference

16 Likes

Cool!

I forgot about these kits. I’ve been mulling installing a TT setup in one of the Pulp Logic cases with a battery, but I rather like the idea of these a lot–and a lot more economical. They power nicely off of a portable USB battery I imagine…no? Any problems with sag using a battery…err, if you’ve tried it?

1 Like

im late to the thread cuz i just got my teletype last week… this project is awesome and this thread is an awesome diary of an awesome project =)

1 Like

having received the pcbs and panels for the telexI/O, was pretty stoked to see these handy tools included! Thanks Brendon, love the knurled nut tool!

4 Likes

OMG @tehn… I hope it doesn’t hurt your feelings too much to see this…

@bpcmusic how many iterations did it take getting the hex driver dimensions right? I literally bought 4 different drivers before I found one that actually fit the nuts we use, and McMaster shipped us a box of 8 rather than the one i ordered…

2 Likes

@Galapagoose The knurled driver was my design in OpenScad and it took a couple of passes. They get chewed up quite quickly and are quite disposable; they are best used for the end or beginning bits only.

The hex driver was a print off of Thingiverse. There are three that I use and they work amazingly well (and haven’t scratched a single panel):


Had a bit of play today with the TXo at the hotel making some silly drum sounds. The integrated metronome and clock divider was creating triggers that executed scripts for each of the sounds. The BD was the most interesting as it used the oscillator’s portamento to do a downward drop of the frequency. Noise sources with different envelopes and rates created the click for the kick, the “snare” sound and the hats.

Silly - but a lot of fun to play around with. The battery powered lunchbox is quite amazing. Thx again to @c1t1zen (and @TomWhitwell) for the genius behind that thing.


Got to meet up with @alexwhite and experience some Aussie hospitality today. Thanks again for the visit and the opportunity to see some beautiful exhibits at the museum! Oh, and check out his beautiful 12":


Oh yeah, and this happened - up-close and totally personal:

They are such beautiful animals. I got to sit inches from them as they fed. Most of them had just molted, so their coats were stunningly fresh and blue.

Also got to meet some of their friends:

Those crested penguins are quite comfortable around people and rather bold. Not to mention, stunningly beautiful.


So, while I was mostly in Sydney this week for business, I got to cap it off with some amazing Aussie flair. Looking forward to coming back in a few months.

Tomorrow, back to LA and the solder-paste grind. :slight_smile:

Cheers!

b

19 Likes

Back on the ground in LA to miserable (and lovely) rain. Still a little high from hanging with the Fairy Penguins.

Got some good firmware work done on the plane with my lunchbox (from @c1t1zen). Details after the pic.

The Firmware and Command Reference have been updated. Here are the highlights:

TO.TR.WIDTH 1-n α	time for TR.PULSE; α percentage of TR.M

This allows you to set the duration of the TR pulse to be a percentage of the rate of that TR’s independent metronome (TO.TR.M). This tracks tempo changes to maintain its relative width.

TO.OSC.CYC 1-n α	targets the cycle length for the oscillator to α (milliseconds)
TO.OSC.CYC.S 1-n α	targets the cycle length for the oscillator to α (seconds)
TO.OSC.CYC.M 1-n α	targets the cycle length for the oscillator to α (minutes)
TO.OSC.CYC.SET 1-n α	sets the cycle length for the oscillator to α (milliseconds)
TO.OSC.CYC.S.SET 1-n α	sets the cycle length for the oscillator to α (seconds)
TO.OSC.CYC.M.SET 1-n α	sets the cycle length for the oscillator to α (minutes)

Allows you to target or set crazy-slow cycle rates for the oscillators. You supply the time you want it to take to complete a single cycle in milliseconds, seconds or minutes.

TI.IN.MAP 1-n α β	maps the IN values to the range α - β
TI.PARAM.MAP 1-n α β	maps the PARAM values to the range α - β

This allows you to remap the values for the IN and PARAM values to whatever you would like. The TXi has a lot of processor to spare, so it made sense to give it some more work to do. It is also pretty easy to simply set up the range that you want. For example:

TI.PARAM.MAP 1 0 100

Will return values 0 to 100.

TI.PARAM.MAP 1 50 -50

Will return values that are inverted, starting at 50 and going to -50 at full turn.


EDIT - COULDN’T STOP TWEAKING

Added a couple more things before closing it out. An additional new command:

TO.TR.M.COUNT 1-n α	sets the number of repeats before deactivating (0=infinity)

You can do some fun things with this. :slight_smile:

Also - created an exponential brightness curve for the TXo CV LEDs so that they show more variety of brightness. They were not showing great variety before - this was very evident on the plane.

The CV LEDs are now closer to the Teletype’s curve now - though the TXo shows some very dim states before the Teletype begins to light up its CV LEDs. I think this is preferable as the Teletype takes a while before its LEDs light up.


Pretty handy! Thanks for the ideas @trickyflemming!!


Next step - merge (if needed) and a pull request for the TT’s code.

13 Likes

So let me get this right.

You go on a vacation and productivity bump before and after…

Hmmm…

Take vacation plz!

Incredibly inspring, and looking forward to my units. Already clearing space for them in the Teletype row.

4 Likes

@tehn + @sam - submitted a pull request for my Telex branch. Everything required for Telex support should be in there. I merged the upstream Teletype branch to my master fork and then merged that with the Telex branch.

Saw some problems with the Travis CLI in the “simulator” and “tests” folders. Went and updated their Makefiles and now everything looks to be passing.

Let me know if you need anything else.

Cheers!

b

3 Likes

So you saw them! :penguin:

In NSW?

Full report please! :grin:

1 Like

@Larrea - Scroll up - posted a pair of pics from my visit. :slight_smile:

It was AMAZING!!

1 Like

Wow, totally missed those!

I’ll probably PM you later about this. Really interested in the details of your penguin-related trip!

1 Like

Yes! I was there a couple years ago. Went to Philip Island and watched the penguins in the evening as they emerged from the water en masse and noisily climbed up the beach. :slight_smile:

2 Likes

Significant milestone today: the mainline Teletype Firmware was just updated with support for the TELEX modules. Big thanks to @scanner_darkly (especially for his thoughtful performance suggestions), @sam and @tehn for helping it out the door.

I’ve pushed a TELEX Firmware Release to coincide with the Teletype release. For those of you with units, you will want to load these on your modules so that you are in sync.

On the road for business for the next couple of days. Jet lag and a cold had me down last weekend so I lost a little SMD time (made up for it with some firmware work and testing). I’m hoping to rock it this weekend in order to keep my planned pace. Prepped up to do the TXi back board; I’ll let you all know how it goes.

Cheers!


TELEX HANDY LINKS
TELEX Microsite | Ordering Process Details | Crazy Verbose Status + Timeline
Open Source Repository | Printable Command Reference

10 Likes

Perfect timing! I’m finishing up the TXi builds tonight, possibly the TXo builds.

I saw that the git branches have been merged. Will there be an official, pre-compiled version of the Teletype firmware posted under Releases soon?

1 Like

i was hoping to get another change in before that (working on it today), in the meantime i can build a hex file and post it here (it won’t have the default scenes though, if that matters to you)

Thanks! No rush, though. I won’t get a chance to test these until late tonight.

There was a plan mentioned in the i2c debugging thread to get the tt firmware fixed and working before adding new stuff and I wonder if this is still planed - I am a bit worried that the system could be getting more unstable again by adding a lot of new features and then the bugs would be harder to track…I would really wish for a fully functioning monome remote system if I could since it never really did for me…

i haven’t been keeping close track but i thought most of the bugs were fixed. are there still some outstanding?

I did not use it much over the last weeks out of a bit of frustration and cause I wanted to wait for a somehow temporary final firmware update before programming new stuff on the modules but what comes to my mind spontaneously is:

crashes/performance hick-ups on hotplugging controller,
still skipping i2c remote commands at regular tempo ranges,
read/write value ranges on cycles do not match (64 vs. 255),
crashing on startup with scripts adressing non active modes on Ansible via i2c.