#8

The only relevant Teletype operations are FB 1 through FB 16 to read the value of each fader. If you have multiple faderbank devices and can adjust their I2C addresses, you can use FB 17 through FB 64 to access up to three more devices.

1 Like
#9

Ok so no chance to read the input of sweet sixteenā€¦
Thank you a lot @desolationjones for your help :blush:

#10

Oh I apologize for the misunderstanding, but those inputs are attenuated by the faders and that signal becomes the fader value. So you CAN read the inputs.

1 Like
#11

Ok perfect. Sorry, I was not enough explicit.
Thank you @desolationjones.
By the way itā€™s not possible to have a Ā«continuous readings Ā» of the value input from the SS for sending it to a, for example, ER301 modulation.
So, the solution can maybe is, to read it in the Metro script with a high speed metro ?
Am I right ?

#12

Correct. Hereā€™s the simplest metro script for sending all 16 values to ER-301:

L 1 16: SC.CV I FB I

I have had good success with metro rates as fast as M 25 (fastest allowed normally) but you might have luck with even faster rates using the experimental M! OP instead. This can take you as fast as M! 2 but I guarantee you will not have stable operation below 20 mS.

1 Like
#13

WoW perfect. Thank you @desolationjones for the command. I will test it this night.
Wonderful :+1:

#14

@M4ngu any update on fixing this?

#15

Iā€™m actually working on it, but Iā€™m getting really weird issues. Sorry for this brutal delay btw

2 Likes
#16

Just uploaded a new version to GitHub, the new one can be compiled without the #master thing, also values on the i2c wonā€™t have any offset if pitch bend is selected as a midi controller. The code is a little cleaner too. Iā€™m actually having an issue: when the #master is active I get no midi (at least in the trs out) but it has to be something from my computer/compiler/libraries or whatever, because I get the same issue with other 16n firmware versions, which are not modified by me at all.
Let me know if it works.

2 Likes
#17

(Iā€™m looking into the TRS midi / master issue over on the main branch this weekend)

1 Like
#18

Hi again.
I have plug the sweet sixteen to the teletype for the first time and I try to read the value from SSixteen with FB 1, FB 2 etcā€¦ but there is nothing. Only the value 0.
When I plug the SSixteen to my ER301 it communicate but with teletype I have nothing.
Please is there something to configure ?

#19

Itā€™s strange because the values are transmitted to the TXo (the Leds bright on TXo) but I find nothing on the Teletype

#20

The communication with ER-301 requires master mode (aka ā€˜leaderā€™ in the new firmware) & i2C pull-up. For Teletype the Sweet has to be in ā€˜followerā€™ mode (no master) and without the pull-up (Teletype has its own). Itā€™s all described in the 16n user guide:

#21

Thanks for your answer and help @M4ngu but should I connect the teensy or the usb front cable ?
I try both but the device is not detected, the editor ask me to connect a controller via usb.
Please, Is there a particular configuration that I need to do on the sweet sixteen (jumper or other) ?
Itā€™s strange because my DAW find the sweet sixteen but not the editorā€¦
I use Chrome for itā€¦
The 16n fader browser test page recognize it but not the configuration tool pageā€¦

#22

Your unit then is probably flashed with an earlier version of the firmware. You should go to Github and flash the Teensy with the 2.0.1 version. Here you have compiled .hex, all you need is download and use the Teensy loader flash the Teesny:
https://github.com/16n-faderbank/16n/releases/download/v2.0.1/16n_v201.hex
and here you have all the versions:

1 Like
#23

Hey ! Here we go ! Thatā€™s it ! Itā€™s work now !
Thank you for this precious help :blush:

All the best,

Jeremy

1 Like
#24

Hey @M4ngu, Iā€™m loving the Mk1 Sweet Sixteen I just picked up!

I just have one question regarding polarity. When I have the faders all the way up, the leds light up, but Iā€™m seeing the minimum value in the web editor with v2.0.1 from Faderbank/16n flashed.

I noticed that there are a few different versions on your github, Sweet-Sixteen, but someone mentioned that I may need to flash it with a separate, Sweet 16 specific hex to get it working correctly.

I havenā€™t had a ton of luck compiling stuff with teensy before, but before I went down that path, I noticed youā€™d suggested above that someone grab v2.0.1 from Faderbank/16n .

Any help would be super appreciated!

Also, heads up the ā€œDownload the source code hereā€ link below the ccā€™s diagram on your site is broken: https://www.tesseractmodular.com/manuals/sweet-sixteen-manual#h.p_RE-CxcQ3ERIl

#25

UPDATE: compiled successfully and saw the comment:
// - channel numbers are not inverted when 'rotate' is active
in the .ino.

After setting rotate flag, Iā€™m good to go. Thanks for your time!

1 Like
#26

so itā€™s working fine, correct?
I need to update some info in the Tesseract Modular website btw

#27

Yes! And Iā€™m thrilled @M4ngu

I may have to do a bit of calibration as the cv values show up in teletype all over the place, but Iā€™ll have to revisit without my infant son on my lap

For reference I have a txb as the main hub, txo, txi, teletype, crow, audible, just friends and w/, but I only tested with tt (Follower) and er301 (leader) (er301 is in a separate skiff with txb connecting to main ii skiff)

I have the monome trilogy to mess with eventually, but I think not all of mine have the headers, and Iā€™m waiting patiently for xorelectronics nerdseq expansion.

1 Like