Multi-IO Expander

[XORadmin]

I seem to be getting an unfortunate buzzing computer noise when using the Device USB connection on Multi-IO. Using the MiDI expander before, never had this issue. I can work around this by using the TRS MIDI on the Multi-IO expander, which has no issue. But what would cause this? I’d prefer to use Device USB connection.

I’ve also tried different USB cables and the issue occurs with all.

That is a classic problem with all kind of USB gear and computers creating ground loops and it depends on your configuration, power distribution and many other cases. 
You just google for ‘usb ground loop audio’ and will find tons of information about it and possible solutions. 

Midi is different as the ports are opto-isolated.

[kriskeyman]

I seem to be getting an unfortunate buzzing computer noise when using the Device USB connection on Multi-IO. Using the MiDI expander before, never had this issue. I can work around this by using the TRS MIDI on the Multi-IO expander, which has no issue. But what would cause this? I’d prefer to use Device USB connection.

I’ve also tried different USB cables and the issue occurs with all.

That is a classic problem with all kind of USB gear and computers creating ground loops and it depends on your configuration, power distribution and many other cases. 
You just google for ‘usb ground loop audio’ and will find tons of information about it and possible solutions. 

Midi is different as the ports are opto-isolated.

Thanks for the info, yeah thought it might be something like that going on. I’d rather spend time with Nerdseq than troubleshoot the issue, so TRS works for me!

[mgd]

I have a problem to get my F8R to work with the NerdSEQ (V2.00A). Maybe I'm simply misunderstanding something otherwise obvious.

I have connected my F8R (Leader) on I2C A. In the MIDI/I2C Setup I've configured I2C Mode == N16 -> NS 1-16.
Pull-Up Resistor A in OFF does not make the LED give a visual indication. Setting it to either 3.3V or 5.0V does make the LED give a visual feedback when I move any slider on the F8R.

In the Mapping Page I've set the following lines:
I2C SCCV # 0 > SETV V A
I2C SCCV # 1 > SETV V B
I2C SCCV # 2 > SETV V C
I2C SCCV # 3 > SETV V D
I2C SCCV # 4 > SETV V E
I2C SCCV # 5 > SETV V F
I2C SCCV # 6 > SETV V G
I2C SCCV # 7 > SETV V H

I2C LRN # 0 > SETV V I

I'm expecting to see the change in values in the variables when I move the sliders of my F8R.

I start the NerdSEQ. Now I'm moving sliders. LED A is shining red. I check the variables page. All Variables are 000. No change in the values while moving the sliders.

I've tried the above for every I2C A ADDRESS from 0 to 7F. No change in any of the variables.

What am I doing wrong?
Or where is the error in my thinking?

Kind regards,
Michael

[XORadmin]

I have a problem to get my F8R to work with the NerdSEQ. Maybe I'm simply misunderstanding something otherwise obvious.

I have connected my F8R (Leader) on I2C A. In the MIDI/I2C Setup I've configured I2C Mode == N16 -> NS 1-16.
Pull-Up Resistor A in OFF does not make the LED give a visual indication. Setting it to either 3.3V or 5.0V does make the LED give a visual feedback when I move any slider on the F8R.

In the Mapping Page I've set the following lines:
I2C SCCV #  0 > SETV V  A
I2C SCCV #  1 > SETV V  B
I2C SCCV #  2 > SETV V  C
I2C SCCV #  3 > SETV V  D
I2C SCCV #  4 > SETV V  E
I2C SCCV #  5 > SETV V  F
I2C SCCV #  6 > SETV V  G
I2C SCCV #  7 > SETV V  H

I2C LRN  #  0 > SETV V  I

I'm expecting to see the change in values in the variables when I move the sliders of my F8R.

I start the NerdSEQ. Now I'm moving sliders. LED A is shining red. I check the variables page. All Variables are 000. No change in the values while moving the sliders.

I've tried the above for every I2C A ADDRESS from 0 to 7F. No change in any of the variables.

What am I doing wrong?
Or where is the error in my thinking?

Kind regards,
Michael

Only use 3.3V pullup. Address 31hex. The f8r might need to be restarted. Led A should only shine on movement.
The variables should change and if set to learn it will recognize the fader on movement.

Latest firmware on F8R?

[mgd]

Only use 3.3V pullup. Address 31hex. The f8r might need to be restarted. Led A should only shine on movement.
The variables should change and if set to learn it will recognize the fader on movement.

Latest firmware on F8R?

F8R FW is 2.0.4, pullup is 3.3V, Address 31hex. I've booted the case with the NerdSEQ and the F8R with these settings. The LED A shines red only when I move any of the F8R fader. However the variables stay on 000 no matter how I move the fader. I've pushed the reset button of the F8R while everything is powered on. No change. I again verified that the 3 I2C cables are connected to the corresponding pins.

[XORadmin]

Attach the project pls

[kriskeyman]

F8R is set as leader in MSW web app?

[mgd]

F8R is set as leader in MSW web app?

Thank you for your suggestion:
As I wrote in my initial post, the F8R is set to Leader in the WebApp and the exported config json says "i2cmaster": true

The setting "deviceId": 4 lets me to believe it might be hex address 34 but I had tried that as well as 31...

Kind regards,
Michael

[Liquidcolor]

F8R FW is 2.0.4

For what it's worth, I found that running 2.0.4 on my MSW XVI 16 channel fader bank was NOT saving any updates from the web config app when powered back up, so it was defaulting back to factory settings. Reinstalling MSW firmware to 2.0.2 solved that and now it's working with the Nerd 100%.

[mgd]

F8R FW is 2.0.4

For what it's worth, I found that running 2.0.4 on my MSW XVI 16 channel fader bank was NOT saving any updates from the web config app when powered back up, so it was defaulting back to factory settings. Reinstalling MSW firmware to 2.0.2 solved that and now it's working with the Nerd 100%.

That's interesting as well. Just for the sake of completeness:
Anyone has experience with FW 2.0.3?

And for reference: The line "deviceId": 4 in the json config file identifies the device as F8R. Changing it to anything else results in the WebInterface refusing to load the config file claiming it is for a different type of device.