I’m having trouble with this again. I can’t seem to get 1.4.0/1.4.1 to read/write.

From what I can tell, it seems that Teletype is booting faster than it did when using the “delay” firmwares which worked for me. Am I imagining things? Is it possible that it’s failing now that I have more i2c devices connected somehow?

this is possible, yes.

the usb import/export needs to be rewritten in general, to do the operation whenever a usb disk is detected, hence avoid this whole startup wait thing. let me see if this might be something i can flip quickly

2 Likes

Hi, any news on when to expect a new TT version with working USB read/write?

Potentially stupid non-coder question: Does it have to automatically detect USB stick insertion? Would it be easier on the coding side to let the user tell TT when a stick has been inserted – e.g. by typing in e.g. “USB” in Live mode after USB stick insertion (which would then trigger the read/write routine)?

1 Like

not possible to type something with stick inserted :slight_smile:

but long button press would be an intuitive option…

it’s more of a code structure issue-- it was easy to hack in a startup routine to detect for a usb disk. having a persistent detection and a modal switch isn’t difficult, it’s just a bigger job than a task that can be wedged between other rapid tasks.

i’ll make sure this gets taken care of soon, but “soon” is unfortunately weighed against all of the other feature requests and needs, ah.

1 Like

I don’t know how you juggle it all.

Thanks much for the answer, good luck with all the task…and thanks so much for doing all this!

Oh, does that mean it is not possible to save/load before updating teletype at the moment?

I just realised there have been some updates since 1.1, but I’m too afraid to mess up things with my TT. For me, it’s not a big deal for now, since Ansible doesn’t seem to be available in Europe. I would like to try Just Type, though, but if that means I would be back to no being able to export/import scripts, I prefer to stay on 1.1.

1.1 can export scripts. you may need to try a few different flash drives.

also just type is pretty unstable presently, but @Galapagoose will soon have a v1.0 ready soon

1 Like

Yes, I know. With the delays you introduced, it works for me, with some flash drives. That’s why I’m not updating TT anymore.
How difficult is it to add the same reading and writing delays to the new updates (1.2 to 1.4)? Can’t those lines just be copied and pasted? Or perhaps you could point out where and how we can add them ourselves in the code, so we could try different delays until we find the best ones that work for us?

1 Like

It’d be awesome If adding the delays back into the code would do the trick!

This has stopped working for me too.

I’m trying to figure out why… I’m wondering if we can try and narrow down which versions the USB read / write is definitely working.

There is a funky trick using the git source control tool that can help you figure when a particular bug was introduced. But in order to use it I need to know the most recent known working version.

2 Likes

This is a pretty serious issue for me. Right now, I have a blank Teletype as I updated the firmware to work with the Telex modules. I don’t want to write any new scenes if there’s not a stable way to backup my progress.

My two options at the moment are to downgrade the firmware and not use the expanders or wait until this gets figured out, neither of which are pleasant options.

1 Like

fwiw - just tried it again, no issues here using the latest TT version and an old Kingston 8gb stick, so sounds like it didn’t just stop working, but got less reliable.

2 Likes

1.4 or 1.4.1?

Grrrrr. I think I’m just resigned to having to yank my Teletype from my main case and bring it over to the computer for a serious debugging session.

1.4.1+ (the latest official 1.4.1 plus the 2 remote commands i added that have been merged to master)

1 Like

Ah, that’s good to know - so there is hope and we just have to quest for the magick stick…

:slight_smile:

I’ve tried both my USB sticks. At least one of them definitely used to work.

Others on this thread, is that your experience too? Sticks that used to work have stopped working?