The good news:

DEVICE.FLIP flipped my screen upside down.

The bad news:

DEVICE.FLIP again does not seem to switch it back.

Tried a power cycle and tried to issue the op again but I’m still upside down.

EDIT: Please disregard the italicized bad news. I was typing DEVICE.FLIP into one of the scripts instead of the immediate command window. Apparently I don’t read so well upside down. :slight_smile: Seems to be good, and I’ll do some more testing.

3 Likes

15 Likes

super tempted to change it so that to flip it back you have to type PILF.ECIVED

12 Likes

Here’s the correct way to mount a teletype in a vertical case. Not a single cable in the way. Bliss. Thank you @scanner_darkly !

8 Likes

Pretty happy with with my tt in a vertical case in the bottom row as is, but thank you so much having made this an option!!

Just flipped mine over and it works like a charm. Thanks scanner_darkly !

But I need to stick a reminder to back up my scenes at the top of my “how to update” text file :expressionless: So much for my attempt to impersonate Ryoji Ikeda… :wink:

1 Like

Yep - me too. I think my scenes sound better the second time around though :wink:

sorry about that! i’ll make sure to include the usual warning whenever i post a new firmware.

No need to apologise! I would’ve done it even with a warning. I think I’m beyond the critical age where I can ever learn that I should back up before upgrading anything :slight_smile:

3 Likes

Also want to report that the new firmware did solve the problems with my Vortex keyboard missing key presses etc.
Works like a charm!

Thank you!

1 Like

I try the DEVICE.FLIP command but that don’t flip the screen… :thinking:

EDIT: I update the firmware
all work fine
thank you!!!

it’s not in the official 3.0 release (it was added after), are you using a beta posted here: Teletype 3.+ feature requests and discussion?

EDIT: I update the firmware
all work fine
thank you!!!

With the latest 3.0 firmware, device.flip turns off my trigger inputs :-/ Had to flip it back to get them to work…If I get some time i’ll look into it.

Can you try the build in this post? I think I broke this when adding SCRIPT.POL and it was fixed shortly after release.

1 Like