#608

I’ve upgraded to 2.01 but I can’t access the editor in Chrome (83) on Mac OS Catalina

Capture d’écran 2020-07-12 à 17.12.19
Capture d’écran 2020-07-12 à 17.12.191640×888 75.8 KB

Midi Monitor recognizes the device but this web app does not. I’ve tried to disconnect, reconnect again, reload the page.

This test page works https://16n-faderbank.github.io/16ntest.html but not the editor.

Is there another way to configure the device ?

Thanks

#609

well, you could configure the device by sending sysex manually, but I wouldn’t recommend it.

it’s strange that the old testpage works.

Can you direct message me with a screengrab of the web inspector console from the editor page - command+option+i will open the window, click “Console” at the top?

You could also use the Opera browser, which supports webmidi, but it’s somewhat smelly that this isn’t working at all.

1 Like
#610

Yes I can send you a screenshot, I inspected the console earlier, but it wasn’t showing anything, no verbose, no errors. I’ll try again. The previous firmware was a very old one. On my second 16n, it’s worse, it behaves erratically (it lags and then sends bursts of midi messages, not sure if it’s hardware or software related) and is not recognized either. I’m gonna do more tests and I will PM you with all the details

#611

OK. I’ll do my best to investigate, but I’m a bit time-limited at the minute. Can you let me know how you’re connecting the 16n. Also, is it running a Teensy LC, or a Teensy board in it, and is it a board with screws in a “cross” pattern, or just three screws down either side of the board? The latter are very, very rare - I think < 10 people have them - but worth checking. (Those are “1.25” hardware.)

1 Like
#612

Thanks. I’ll investigate too, no worries.
It’s not a 1.25 board. I had these board made in January 2019 just after the files were publicly released, it’s a 1.3x I believe. It uses a Teensy 3.2. I used the corresponding 16n_v201.hex (not the LC one). And I’m connecting the 16n with USB (from the micro USB port to a Mac using a USB-C adaptor to be precise).

I’ve just checked the Console on Chrome again, it’s empty, it shows no messages at all. Same thing with Opera.

Perhaps I should try to re-compile the firmware with Teensyduino ?

By the way is it the normal that the LED of the Teensy blinks when I’m moving a fader ? (Edit: Yes it’s normal, I’ve just seen this option on the config page ; )) )

Edit (solved):

  • :white_check_mark: I’ve just cloned the repo again and re-compiled using Teensyduino, this time it’s working :wink: Chrome instantly recognizes the device.

  • :x: For the test, I’ve re-uploaded the 16n_v201.hex just after, and this time the Faderbank is not recognized anymore by Chrome or Opera but it’s still sending Midi CC (according to Midi monitor).

  • :white_check_mark: Back to normal when I recompile and upload with Teensyduino.

#613

that is weeeeeeeird.

the hexfile should work for everybody (and has been doing elsewhere).

So - yes, the new default is “LED On”, “LED flashes on MIDI data”. You can alter that in the third tab of the editor’s edit view. It’s a good way of knowing the new fimrware is on there.

The only debug thought I had was: the old editor just looks for a MIDI device and receives MIDI data from it, which is why the old editor Just Worked. The new editor does a little Sysex handshake to confirm it’s talking to a 16n, rather than any old midi device. And it looks like because that handshake wasn’t working, nothing else would work regardless. Highly strange.

I think for now I’d like to just note you had an issue, and managed to solve it, and return to it if it emerges again… because it sounds like you have something working?

Do check that the editor will let you customise faders/options - that indicates the sysex transfer is working.

1 Like
#614

Thanks. Yes, absolutely, now it’s working 100%, I can access the config page, (it’s great to have this web interface by the way, thanks). I was able to re-assign the CC numbers, disable the LED etc.

For the second 16n, the one behaving erratically, I’m just going to reflow the Teensy, it was stored on a shelf for months, it’s not supposed to be damaged but it’s probably an hardware issue, a cold joint or something :wink:

#615

Has anyone ordered the aluminum top and bottom panels from Front Panel Express recently? Am I good to simply open the files in FPD and order from there?

#617

Hi,
Im going away for some time and today i plugged my 16n (berlin Modular Version) and updated it with the latest firmware on the github.

When i connect it to teletype via i2c, and do fader x etc… my teletype read values from 0 to -32767, if the fader is in the middle it reads 9559

How can i adjust this range?

Thanks!

#618

Please consult the Teletype manual and look for the FADER.CAL.MAX and FADER.CAL.MIN instructions.

#619

Thanks @desolationjones will do, cheers

#620

I’m afraid I don’t know much about the I2C end of things - I just make sure it doesn’t get changed in releases - so I hope @desolationjones’ advice has helped.

#622

Hi @desolationjones !
I have been trying to get my head around using the 16n via i2c with teletype. When using fader.cal.max and min should i place them on the init script or the metro. I have tried both and i’m quite confused.
Sometimes i set all the fader of the 16n all the way up and run Fader.cal.max on the init script, but then where should i place fader.cal.min? souls i run one (max) set the fader to the top and then set the fader to the min value an run fader.cal.min?
Since i’m mapping lots of teletype things to the fader on the 16n if these are not right, well things don’t work as expected, since i’m using fader.scale on a lot of parameters.
Thanks a lot!

#623

Oh, neither! You should run them once (manually from the live screen) and then leave it alone because the values are stored in Teletype memory. Then you only need to recalibrate if you change devices or notice issues.

1 Like
#624

Hi @desolationjones thank you so much for the quick response and for the info!
Just did it for all the faders and we are golden! Thanks for your support!

1 Like
#625

How are most folks connecting i2c to ER-301? Mounting a little TRS jack to a blank panel?

1 Like
#626

Depending on which of my small cases I’m using I’ve done different things.
For my Pod 60, I drilled a hole in the back( between the small power bus boards) and mounted a jack there. For my Palette I made a cable which connects to the TRS MIDI jack. And for my 7U/62HP typewriter case, I made a small panel for the 1U row.

1 Like
#627

I just straight up squeezed a wire out the side of the modules, since I don’t use racks (I use floating nuts instead) and usually have 1hp on the side:

FullSizeRender

1 Like
#628

I built the 16n AtoV version and it was spitting out midi values and looked to be working 100%. Then I wired the I2C to my TXb and tried reading the faders with my teletype. The faders give crazy numbers, -13264, 6023, 13168… not monotonic, but stable (number stays the same if you leave it alone). Each fader has similar behavior. What should I check? I2C wire is too long, but it can’t be responsible for this…

#629

from what i remember, the latest teletype firmware doesn’t read the value correctly, you need to calibrate it in teletype, using ops FB.CAL.MIN and FB.CAL.MAX

1 Like