For the TELEX, it is set at 400k in the code - but the Teensy can do a lot faster.

This is the library that I used - optimized for the Teensy and based on the Arduino Wire library:

https://forum.pjrc.com/threads/21680-New-I2C-library-for-Teensy3

I don’t think we will need to do anything to the rates due to the nature of the protocol:

1 Like

now i remember you mentioning 400k before - this is interesting, when i tried 400k it was much less stable… but perhaps only the rate set on i2c master matters?

… the latest extreme test has been running with no crash for over 24 hours now.

2 Likes

i let it run for almost 54 hours before finally turning it off - no crash! at this point i feel it’s ready for beta testing but it makes sense to wait for 2.0 to be finalized as there are still some changes being made there and i want to make sure they’re all incorporated before we start beta testing this version.

if anybody wants to give it a try now though this would be super helpful. i’m also including updated ansible firmware here - it is important to update both as the older ansible firmware can still cause teletype to crash!

same for trilogy - if you use the latest official firmwares they might cause issues when using remote commands. i’ll post updated versions for each when we start beta testing, if you’d like to try it now just let me know and i’ll send you whichever one you need.


what to test? just try everything, throw anything you want at it. if you get it to crash it’s not necessary to retry it with the official 2.0 version - just post the description of your setup and the script (although if you have scripts that don’t work with the official version but work with this one please post that as well - it’ll be good to have additional confirmation that the fixes actually do work!)

teletype.hex (327.8 KB) c47eaaf

ansible.hex (225.1 KB) 85184e4

the teletype firmware includes all the latest changes to the official 2.0 version as of today (dedicated keys for pattern and live pages). remember that flashing firmware deletes your presets!

3 Likes

How do both the Ansible and the teletype firmware versions proposed above relate to the teletype beta / release candidate published by @sam today here:

And the fixed Ansible 1.5.1.b01published by @tehn here:

?

I am getting lost a bit what to install and test now…

to expand a bit…

@sam’s and @tehn’s versions you linked are the latest official beta versions. at this point we should concentrate on testing those versions. the ones i posted here are only for people willing to try my fix for teletype crashing under a heavy load (such as audio rate triggers or i2c commands in a fast metro script, for instance). my fix also includes improvements for keyboard response and screen refresh.

if your teletype doesn’t crash with the official version i’d use those versions. if you can get it to crash and have the time and desire to try my version this would be very helpful - but i am not asking for beta testing my version yet - i will do this once 2.0 is officially released. when that happens my version will include everything from the latest official versions and will likely include other stuff so that it can be considered 2.1 and will be tested as such.

for those who want to try the versions i posted - both ansible and teletype include everything from the official versions as of today (teletype rc1 and ansible 1.5.1b01).

3 Likes

this is great - thanks for testing it! are you using the latest earthsea version (posted in the earthsea lock up thread) or the one i posted earlier in this thread?

1 Like

excellent, thanks again for testing! the reason i asked about the version - there were some additional changes since the version i posted here but sounds like they didn’t introduce any new bugs, which is good.

re: loop mode affecting start/stop - not sure about this one and i don’t have my es connected to i2c yet, so can’t test, perhaps somebody else can comment if this existed before?