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

Hi!

I have a SS connected to an ER301 with the pullup resistors. To try to have input readings in TELETYPE, I’ve removed the resistors and connected to the TELETYPE. With the FADER command I’m able to have readings from the faders, but they don’t go in a linear way. If I increase the fader I get, let’s say, “-18000”, then “32000”, then “45”, then a negative value again …

Does anybody what I’m doing wrong? I’ve flagged the “master” on the firmware … With the ER301 the movement of the faders were translated into smooth and gradual changes …

EDIT: Solved! Didn’t know about the calibration process … :roll_eyes:

1 Like
#29

Ok perfect, please what is the calibration process ?

#30

You need to put the faders at their minimum and max position and run the calibration commands. You can automate the calibration for all minimum and maximum levels using this in Teletype:

L 1 16: FB.C.MIN I
L 1 16: FB.C.MAX I

I’ve discovered that I can use the SS to transform external CV’s into I2C protocol to be read by TELETYPE using the FB command. There’s some delay in the signal, but is working fine. So by doing this I’m able to sequence, for example, the different synth voices of JUST FRIENDS sequenced by a NERDSEQ or ER101. Putting the faders at its max position and doing a callibration of an incoming CV signal translates its value into a FB value. Like having 4 TXi’s connected …

3 Likes
#31

Ok thank you. I just forgot to upgrade my teletype. Perfect I have to test it now :blush:

#32

this may not be the best thread, but my searching seems to say this is the most relevant topic and all the right people are already here and discussing the same hardware so…

I’ve got a Sweet Sixteen Mk2 which I’ve flashed with v2.0.1 and I’m noodling around with it connected to crow. I had a bit of a typical I2C debugging session as I found that the values were always wrong… until I plugged the S16 into the editor and took a closer look.

It looks like the midi values (and I2C) values are reversed. ie: all the way down is 127, all the way up is 0. I double checked that the invert 180deg isn’t on, and I didn’t take notes but I think what I observed is that when 180deg flipped then things worked as you’d expect.

I’m also not 100% sure that I’ve read and understood correctly that the 2.0.1 firmware is expected to fully support the S16 hardware, so @M4ngu @infovore please correct me if that’s a bad assumption.

Seems like this could be a fairly small fix, and I’m a competent programmer so I don’t mind taking a look myself, but I also don’t have any of the software infrastructure around to be developing this code (read: I don’t even know what I’d need as of right now.)

#33

Yes, the hardware for Sweet Sixteen differs from the original 16n fader bank, which is detailed on Github:

“Another important modification in this part of the circuit is the addition of negative voltage references and that now is a summing inverting gain circuit (for that reason the FLIP option in the firmware is necessary for this version of the hardware, as in the minimum position of the fader the voltage read by the Teensy will be 3,3V and in the max position it will be 0V)”

For the Sweet Sixteen I’d recommend the 16n 2.0.1 firmware from my Github repository as it has some small fixes:

  • the channel numbers are not reversed if the ‘rotate’ is active
  • calibration of the high value is now possible when the ‘rotate’ is active