Manchester Extension dosen’t support all 0 data.
Can you help this problem?
@sooseok.sim1 Sorry for the trouble with that! This looks quite similar to a known issue with our Manchester analyzer documented in the link below:
Can you help share a copy of your capture file (in .sal file format)? I’d be happy to run a quick test on my end.
I’m sorry for attaching file,because I can’t update file our company security policy.
But you can find the image,
The decoder is unable to process leading zeros (e.g., 0x00 or 0x000000) immediately after the SYNC(preamble). However, non-zero data is being decoded without issues.
Please let me know your email. I will send you this file.
I tried to make dll with https://github.com/Alex-the-Smart/DPAUXAnalyzer .
This is good for decoding with 0x00 or 0x0000 or 0x000000 or the other 0.
but basic Manchester Extension have som sync problem.
I attache file. with manchester Extension
saleae_update_v0.1.sal (5.3 KB)
@sooseok.sim1 Thanks for sending that over. I’m glad to hear you have a workaround in the meantime as well. After reviewing your capture file, this looks similar to the bug report I posted previously above.
I added some notes with your capture file details, and changed the title of the bug report to include a note that the Manchester analyzer also fails to decode 0x00 transactions (in addition to the 0xFF issues that we documented previously).