Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
i2c bypass debug mode?
#3
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?
Reply


Messages In This Thread
i2c bypass debug mode? - by flel - 10-18-2025, 09:48 PM
RE: i2c bypass debug mode? - by XORadmin - 10-19-2025, 01:31 PM
RE: i2c bypass debug mode? - by flel - 11-21-2025, 01:28 AM
RE: i2c bypass debug mode? - by XORadmin - 11-21-2025, 11:03 AM
RE: i2c bypass debug mode? - by flel - 11-21-2025, 08:33 PM
RE: i2c bypass debug mode? - by XORadmin - 11-27-2025, 02:36 PM
RE: i2c bypass debug mode? - by flel - 11-27-2025, 09:06 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)