locked
Serial Port getting spurious wrong/corrupt data. RRS feed

  • General discussion

  • I'm viewing incoming serial port data using a sniffer in Windows. I'm also using a hardware sniffer between the cable and the PC. Every so often, the data do not match. Examining the differences shows that the sniffer is reading the data correctly and Windows is not. I know this because I'm controlling the incoming data source. I need to find out if there is a problem with the low-level serial port driver in Windows.

    Here are the data...

    Hardware sniffer - 01 23 00 00 3F 1D 00 80 51 03 C5 00 C0 00 8C 03 2C 01 F3 01 23 03 00 00 00 00 00 00 6D 00 6D 00 E8 01 0E 01 5A 4E
    Windows -            01 23 00 00 3F 1D 00 80 51 03 C5 00 C0 00 8C 03 2C 01 F3 01 23 03 00 00 00 00 00 00 6D 00 6D 00 E8 01 0E 00 00 AB D0
    Monday, June 8, 2009 9:31 PM

All replies

  • Hi,

     

    Thank you for your post.

     

    May I know the detail information about the software (manufacture, name, version, etc.) and device (brand, model) you are using to sniff the data?

     

    As I know, Microsoft has no such software and device. Therefore, I suggest you contact the support of the software and the device regarding this issue. This should be a effective way.

     

    Thank you for your understanding. Hope this issue will be resolved soon.


    Nicholas Li - MSFT
    Friday, June 12, 2009 9:32 AM
    Moderator
  • Hello Nicholas,

    Thanks for your reply.

    The problem is not with the sniffer because I'm in control of what is being sent to the PC and I know what the correct data should look like. Here is my procedure:

    1) Repeatedly send the following string from a custom hardware platform to the windows PC using RS-232 at 9600 baud:
    01 23 00 00 3F 1D 00 80 51 03 C5 00 C0 00 8C 03 2C 01 F3 01 23 03 00 00 00 00 00 00 6D 00 6D 00 E8 01 0E 01 5A 4E

    2) Verify that windows is getting the same string

    I'm also sure it's not a problem with the sniffer because I wrote my own custom sniffer using .NET 3.5 (C# app using SerialPort class) and it sees the same corruptions as the freeware serial port sniffer.

    Keep in mind that the strange data happens only once in a great while. I have probably a 99% success rate. I've simply debugged as far down as I can go and don't know how to debug the Windows Serial Port driver.
    Monday, June 15, 2009 5:45 PM
  • Hi,

     

    Thank you for your update.

     

    I suspect this is related to development, therefore, it is recommended that you go to our MSDN Forums for help:

     

    MSDN Forums

    http://social.msdn.microsoft.com/forums/en-US/categories/

     

    Thank you for your understanding and cooperation. Hope the issue will be resolved soon!

     


    Nicholas Li - MSFT
    Wednesday, June 17, 2009 10:02 AM
    Moderator