#338

Thanks for the heads up! Was looking at the monome order page daily, ordered now from AH

#339

sure, i totally understand the need for careful appreciation of potentially disrupting additions.

Another thing while i think of it, the blank screensaver is not interrupted by a grid input.
But I guess it is already addressed by the forthcoming grid control mode.

#340

i considered adding this, but figured that people might still want the screensaver running while using grid. to exit in this case without reconnecting keyboard you could just use the front panel button.

#341

So I’m making headway with the grid ops! I have a variation of an MLR thing happening. One fader row selects a different loop in the ER301, another fader selects whether it’s played forward, backwards, rrand, or drunk. Fun! I’m just gonna keep going, do sequence variations, etc…this is gonna be so cool!

HOWEVER…I am a little confused about one thing. I thought when you defined a fader, the level for course faders was the nominal background level? None of my fader buttons are lit except when a location is selected. Do I need to manually ‘draw’ the fader with g.rec?

1 Like
#342

yep, you’re totally correct, it’s a bug. i’ll have a fix included in the next beta. and yeah, for now you can just use G.REC with level of -2 as a workaround.

2 Likes
#344

My teletype just instantly died (stopped powering up, no leds light up screen all black) after i attempted to plug the grid to it (not powered externally) to test a scene i was working on.
I’m aware that i should power the grid externally (had already ordered the cables to do so) but i had no idea i could fry the teletype by trying this :confused:
Is there anything i can do?

Thanks.

Faderbank Run: See top post for status
#345

have you tried powering it up again with grid disconnected?

1 Like
#346

Yeah :confused: also tried connecting it to my laptop to try and reflash it but laptop wouldn’t recognize it.

#347

i’m afraid we need @tehn’s help at this point… i’ll message you.

1 Like
#348

got your email @esquilofreniko

sorry to hear this. we should make a bigger warning. i wouldn’t have expected the 5v regulator to kill itself (this is certainly what happened).

but luckily it’s an easy fix (one SOIC8 IC). you’ll need to send it in.

the real question— is your grid ok? if not that might suggest further damage to the TT.

2 Likes
#349

yep, updating all the relevant threads and the wiki.

1 Like
#350

Thank you for fast response, got your email!
The grid is fine, i tried connecting it to ansible after that and it all worked as expected.

#351

since we now have a confirmed case that grid can indeed damage teletype when connected directly i’m going to suggest adding an explicit action that a user has to perform in order to enable grid integration.

basically, teletype will not output anything to grid by default. in order to enable it you will need to use a special shortcut (like Alt-Shift-Ctrl-G or something similar) which will take you to a screen that will reiterate the warning and ask you to confirm. this confirmation will not be saved and will need to be done each time a teletype is turned on (and will not be available as an op for obvious reasons). grid visualizer will work regardless of this setting.

9 Likes
#352

Maybe showing my ignorance, but how could this prevent damage to the TT if the voltage is always available on the port? Overcurrent is overcurrent. Unless there is a MCU-controllable relay/FET/etc?

This is probably best handled with a hardware revision, unfortunately. Are there polyfuses on the USB power lines? I know that’s a popular method to protect PC USB ports.

#353

grid draws more power when LEDs are on. i think (hope) that there are no circumstance under which a non lit grid would cause damage to teletype. so the idea is to not have any LEDs on until an explicit confirmation is received.

#354

Oh that is indeed a good point!

#355

Hmmm.

I’m battling with myself on a response because I totally get the point for this - but it feels naggy to have it appearing on the first grid access after every TT restart. Making it a one-time-only kind of thing seems less painful (only the first time you use the grid op ever). Though, I know that opens up risk for units that are purchased on the used market. And, yes, I know I could comment the thing out in the source and build my own firmware version without it. :slight_smile:

Regardless, I think my vote is for a one-time-only warning - if there is room in flash to store the status.

EDIT: Oh, and @esquilofreniko , super-sorry to hear about your TT. Hope it gets up and running soon…

5 Likes
#356

yeah, my thinking behind not storing the confirmation was teletypes changing owners, and to a lesser extent people moving tt to a different case or something like that. it will be naggy for sure but just feels like a lesser evil - i feel really bad because of what happened to @esquilofreniko

and perhaps it doesn’t have to be all that naggy… since it only matters if a grid is connected then the way it could be done - as soon as it’s connected (or if tt is powered up with grid already connected) it will show the confirmation screen, and to confirm you’ll have to push 3 buttons together, something like that.

1 Like
#357

At this point i almost always have my grid and TT connected, far more often than a keyboard. I completely understand needing a protective barrier, but every power up seems… inconvenient.

Edit: Should we consider an “Expert Firmware” version, à la Batumi?

4 Likes
#358

Really sorry to hear about your Teletype @esquilofreniko

However I agree that confirming every time would be a real drag.

4 Likes