MC200CM changes between v3 to v4.30
Are there changes in version 4+ of the MC200CM on how the communication between 2 converters work?
I noticed that:
1. connecting the TX to the RX of the same unit reports the FX light
2. for 3 units, a, b and c; connecting the a-TX to b-RX does not light FX of either a or b. Additionally connecting c-TX to a-RX does not causes FX of a to light up. Most importantly, no data gets from a to b. This all happens even if all 3 units have working ethernet links (TP lights blinking).
I have read about the second experiment working in version 3 while using force, so I am wondering if the conditions required to send data have changed.
@Fae the reason I asked what has changed in version 4 is becaused these 2 projects got 1 way links working in version 3 by having a third converter hooked to the sender, so that it sees a signal in its Rx:
- wavestone-cdt/dyode: A low-cost, DIY data diode for ICS (github.com): specifically its v1 (full) version,
- EBUJOLD/data-diode: Summer internship project for Virginia Space. Created a data diode for one way communication! (github.com)
While I no longer need to experiment with the above, the difference does makes me wonder if the change in v4 can have implications in normal 2 ways links if one of the directions breaks/fails (affecting UDP traffic in the other direction).