101

Just wanna ask, is it possible to have an op that uses tilt from old Grid 64 as param?

102

Whoo, someone could help me update the Teletype because I’m completely in the dark. I don’t know where to find the dfu programmer. I don’t even know if he still exists.
I am a beginner with Monome products and until then it was fine but stuck on the update? I feel stupid.
Do you have to be very experimented with programming to hope to advance?
Thanks

103

Don’t worry, I’ve been there.
Did you look at this page ? modular firmware updates | monome/docs
You don’t have to be well versed in programming ; for Windows for example, you need to know how to “cd” in the terminal, but that’s about it.
Are you on MacOS, Windows or Linux ? For Windows the files are here : Atmel USB DFU Programmer download | SourceForge.net

104

Thank you, yes I’m on Windows.
In the link you sent, the dfu programmer project is returned to this page:
https://github.com/dfu-programmer/dfu-programmer
And that’s where I’m lost.

105

Oh yes, my bad… It looks like they moved things around a little, and the documentation isn’t up to date everywhere it seems… You can find releases here, but I’m a bit confused because the version names aren’t the same : Releases · dfu-programmer/dfu-programmer · GitHub
Someone more versed into Github and its intricacies might pitch in…

106

Oh yes thank you very much!! I will try with this:)

107

Make sure to use the v0.9.0 release! I think the libusb0 support is necessary.

108

Thanks but AT32UC3B DFU driver update doesn’t work

Capt
Capt1107×947 46.4 KB

109

I had this same issue yesterday with a newer Windows PC. Maybe I can check my other (working) computer and share a copy of the correct driver…

110

Well, I was able to update the AT32UC3B drivers with an old version dfu-programmer of GrrrOwl. Thanks to him.
I then followed all the instructions but the Teletype did not respond to the update and but it is dead module.
Here is the cmd’s message

Capt2
Capt21656×801 56.2 KB

I think it smells bad now.

1 Like
111

Hi,
I’ve installed beta 6 and after that if been unable to reload the saved scenes from the USB. From menu I selected the option to read from USB

I’ve reloaded v 4.0.0 and observed that after inserting USB it says WRITE… READ… If it is writing in the USB and reading after it writes , is it replacing the saved scenes in the USB with blank ones?

I saved an existing scene in other scene number, and verified that if I insert a USB and check in my computer, the txt file has the copied scene. But it I copy that into another txt file (tt11s.txt copied and renamed tt12s.txt, and copied into USB) and I plug the USB into Teletype, the copied scene continues to be blank and the copied txt has not been loaded into the module.

I reloaded beta 6 → no scenes → not loading scenes from usb
I’ve returned to 4.0.0, no loading of scenes I had in my backup.

Am I doing something wrong??

P. S. Ok, I found it!! Thanks to this

I’ll try again

SOLVED!! Insttalled beta6 and loaded scenes from backup USB after renaming scene files

112

Try putting in the 3 lines of commands one at a time while in that directory. It looks like when you copied them in there was no spacing between them, so the programmer didn’t know what to do.

113

Thanks you so much, it seems to work.
Now, I will look at i2c2 and midi communication Haha !

2 Likes
114

is there currently any way to address two w/'s in the same mode? something like the JF1 and JF2 ops for just friends? you can already do this with crow, but i’d like to use TT

115

If I’m not mistaken you can : Mannequins W/ 2.0

116

yeah, that works for crow, but only the w/ on the first/default i2c address will respond to TT w/ ops. there doesn’t seem to be a way to talk to the alternate i2c address. maybe the generic i2c ops is the way to go?

117

Oh, I see. You can play with both receiving the same instructions from Teletype, or have just one following w/ ops and the other being controlled in another manner, but I don’t know if you can adress them separately.
I miss the exact meaning of your question, my bad (I need to work on my english I guess ;))

1 Like
118

i’ve posted a new beta 7 (which should be my last contribution to teletype) which adds support for dual W/ units. you can now take advantage of being able to connect two W/ units at the same time, set the 2nd one to a different address and control them independently. for the synth mode you can also use them polyphonically as an 8-voice synth (you can still control the various synth settings independently).

the new ops:

W/.SEL x

sets target W/2.0 unit (1 = primary, 2 = secondary)

W/1:

send following W/2.0 OPs to unit 1 ignoring the currently selected unit

W/2:

send following W/2.0 OPs to unit 2 ignoring the currently selected unit

W/S.POLY pitch level

same as W/S.NOTE but it switches between primary and secondary units every 4 notes or until reset

W/S.POLY.RESET

resets W/S.POLY note count

we are hoping to also add some documentation improvements before we release 5.0.0 officially.

28 Likes
119

Hi there - I’m on Teletype Beta 2 firmware. I’ve not updated to the official v5 yet as I have gigs but have not had any issues until I tried messing with Arc.

I was trying the Ansible Arc cycles TT OP’s and getting no response on the Arc - I just want to change start and end points randomly and clocking from TT. I’m on the latest Ansible firmware.

I was wondering if someone with an Ansible + Arc could double check that those ops are working Ok.