"Update:..." <- > <@jamesmunns:beeper.com> Update: > > I think after reading https://github.com/3ndG4me/socat/blob/3f33a20e3556558c459ece8582d8ef4a7e9f1fb2/socat.c#L1403-L1413, with the input as CRNL and the output as default (raw?), it will drop \r characters, basically dropping any bytes with the value 0x0D. Tried it now with pulldowns, removed the malformed frames message but skips the message from the whole first "loop". Removing crnl shows the first loop messages again. So in my case it works as it shold without crnl + pull-downs but pretty sketchy test to say anything conclusive. The pull-downs are done on the MCU so should not affect the first loop. Yesterday I got the messages from the first loop so all in all pretty flaky.