#403

@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
#404

So you saw them! :penguin:

In NSW?

Full report please! :grin:

1 Like
#405

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

It was AMAZING!!

1 Like
#406

Wow, totally missed those!

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

1 Like
#407

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
#408

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
#409

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
#410

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)

#411

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

#412

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…

#413

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

#414

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.

#415

probably best to continue this discussion in the ansible bug thread (could you link it? i can’t seem to find it).

in any case, i would say that the telex additions and the ones i’m working on should not introduce any new issues as these are all new operators, not changes done to the existing ones. some shared code is changed too but again these are additions, not modifications, so while the risk of introducing new bugs is non zero it’s still very very low.

#416

Oh, there are so many Ansible (and Earthsea) bug threads and some of it might belong in the i2c bugs threat. It’s all scattered around the forum I suppose and my attempts to collect together die not work out:

http://llllllll.co/t/official-ansible-thread-for-discussion-feedback-and-bug-reports/5321

After all I did not mean to discourage the commitment to the expander software - picked up my PCB’s from the customs office today…

EDIT: How do I just post a link to another thread?

#417

@Leverkusen Ansible 1.4.1

i’m sorry to report that i’m simply not going to have time for preset import/export anytime soon-- it’s a big feature. but hopefully you’ll find this version stable.

#418

Success! First TXi up and running. Now to finish the others…

2017-02-24 00.41.18-1.jpg4048×3036 2.14 MB

9 Likes
#419

Back in the mists of time there was a post about using a dfu-programmer command to grab in the installed firmware from White Whale. Would that work in this instance as a possible workaround?

#420

As a non-DIYer, I’m jealous to see you reaping the rewards of your DIY skills :wink:

Nice work!

2 Likes
#421

Congrats!!! That is damn-exciting to see. Can’t wait to see your TXo shining in that case!! :slight_smile:

1 Like
#422

It’s really not that hard! I recommend trying it out if you’re interested. I only picked it up recently.

The initial investment is about $100 or so for a mid-range soldering iron, wire cutter, wire stripper, mini screwdrivers, solder, desoldering wick, and a selection of common components.

It’s very relaxing. I find myself playing fewer video games at night. It’s also a fun way to make some hobby income, as people have been hiring me to build Nonlinear Circuits and Random*Source modules. It’s pretty bad from a $/hr standpoint, but from a “I would have been doing this or video games anyway” outlook, it’s awesome. That, and I’m not sitting in front of a screen.

3 Likes