i2c bypass debug mode?

[XORadmin]

Ok so there is some weird behavior trying to forward commands from Teletype to ER-301 via NerdSeq. I have it setup as follows:

Leader: Teletype
Followers:
Crow 0x60 (wired to Teletype + NerdSeq)
Just Friends 0x70 (wired to Teletype + 16n)
16n 0x34 (wired to JF)
NerdSeq 0x31 (NS>Teletype on bus A, wired to Crow; Out merge on bus B, wired to ER-32)
ER-301 0x32 (wired to NerdSeq)

If I send SC.CV and SC.TR from NerdSeq to ER-301 (Multi-IO track) this works exactly as intended.

However, SC.CV and SC.TR commands from Teletype are not properly merged to bus B (which has the ER-301) when in "Out Merge" mode.

If I send SC.CV commands on the Teletype there is definitely signal merged into NS bus B, as both i2c A and B lights are blinking red. Indeed, if I switch bus B mode to "out", the red i2c bus B light on the multi-IO does not turn on (but A stays on). However, there seem to be an issue that only an initial CV pulse is actually sent to the ER-301, and any subsequent pulses are not.

Furthermore, for some reason, sending SC.TR commands (and anything other than SC.CV) does not trigger the Multi-IO bus B front panel light to turn on in "Out Merge" mode.

Could there be a bug/issue with how the merging is done?

Is it possible to have crow/teletype wired directly to both ER-301 and NerdSeq? And NerdSeq independently to the ER-301 as well?

I see the issue and for now I am only passing SC.CV with the merge command (most probably having in mind back then that one would have a faderbox as master which should be used in the nerdseq but also completely passed further). The command also is merged with the fixed 0x31 address which would be used for a first ER-301. 

Wiring the teletype/crow to both NerdSEQ and ER-301 while also acting as a leader to the ER-301 (double leader system) can work but it goes wrong once the signals collide = Teletype/Crow and NerdSEQ trying to send something to the ER301 at he same time.

From the manual:

"NerdSEQ I2C (Follower) ← Teletype (Leader Mode)
There is no Teletype integration at the moment but this is planned after the upcoming Teletype Firmware release (V5.0). But it can be used already with the Teletype in a minimal way. The Teletype Commands SC.CV can be used already to change parameters in the NerdSEQ. The NerdSEQ port would then be set to be a follower, Address 0x31 (or 32, 33) and as a 16n input."

 
So there is no benefit currently using the teletype mode. One basic idea was to make the NerdSEQ varibles available in the Teletype (it could poll them) but since there was never any deeper discussion rather than 'we should do it at some point' this is left open until then. 

I could implement the merge of all commands coming from the I2C port (in fact I got this commented out/disabled in my code), but keep in mind here that you would need to take care of the addresses (by definition...thats I2C, a follower acknowledges if it sees it's own address). A follower port can receive it's data only on one port (eg 0x31) and if you would for example receive 0x32 it would be ignored and so also not passed to a ER301 which is set to 0x32. Only 0x31 would be passed to 0x31. 
Even though they are theoretical workarounds for it (just listen and acknowledge to every address or to more than one address or just listen but no acknowledge etc..) it would not work out well. It would introduce much more 'why doesn't it work' situations than they are already.