#34

not possible to type something with stick inserted :slight_smile:

but long button press would be an intuitive option…

#35

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

I don’t know how you juggle it all.

#37

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

#38

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

#39

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.

#40

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

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

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

#43

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

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

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

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.

#47

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

1 Like
#48

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

:slight_smile:

#49

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?

#50

Yep. During the first go-round, I tried 5 different sticks that I already owned, none of them worked. Purchased one recommended by @tehn, still didn’t work. None of them worked until the test firmware with the load delay. Now I’m back to all of them failing again.

#51

Just out of interest, did they all start working with the delay?

#52

the latest firmware should have the delay fix included. perhaps we could try increasing it and see if that makes a difference. @sam - do you want to give it a try?

this is the commit that introduced the delay and retries:

#53

I think I’m going to try a git bisect, I’ve never actually used it anger before, so it’ll be a learning experience :stuck_out_tongue:

My USB stick didn’t work at first, then started working with the delay fix, and has now stopped. I’d like to get to the bottom of it. Looking at the code, I have a suspicion the issue may be a change in libavr32, but hopefully I’ll be able to nail down an exact commit with bisect.

2 Likes