This board has only a TX and does not need to be controlled. I directly measure the TX by the osci and if there is no signal the uC will also receive nothing.
I think the linked schematic is also not fully correct
the small IC might be a dual op amp (LM2904) working in single rail mode ?
the pins of the transistors might be wrongly extracted, I assume PIN 18 is driving the gate of Q1 (which might be wrongly depicted as emitter). ON my scope I see a nice 135kHz square output of the (uC) ?
Very strange, but I would not assume a SW bug and I have two devices both don't work so I would also exclude a HW bug ... I have no Idea how to debug ... finding the uC and try to read the code I have never done and would be a lot of effort ... any ideas ?
Is the cyan signal a digital IO to let the uC know that information is available?
Does the uC report any serial data received?
Is your time scale set properly? I can see some yellow bits in the images you have. Are you sure the data isn't being compressed too small to see based on your time scale?
Yes, I assume the cyan signal to be the input to the uC (saturated output of the OpAmp?). Its a nice 5V signal with a the symbol time of 240us which fits to the standard ( FDX-B )
I have not yet debugged the protocol, but somehow it seams something is wrong within the uC (input, processing, output) ... difficult to debug.
OK, I hooked a nano behind this signal and decoded it with this library, worked very nice with my sureoetcare.com token. However it did not decode the card delivered with the boards (EM4305 Test Card).
... very strange, I don't understand what the bug ...