Login Page - Create Account

Support Board


Date/Time: Wed, 05 Mar 2025 19:46:55 +0000



Post From: Malformed DTC EncodingResponse

[2022-01-16 16:05:52]
User322148 - Posts: 17
Thanks for replying (especially on a Sunday).

This is right at the start of a new connection on port 11098 for Historical Data. No other data has been sent.

Wireshark capture of Encoding Request:

0000 10 00 06 00 08 00 00 00 04 00 00 00 44 54 43 00 ········ ····DTC·

Wireshark capture of the Encoding Response:

0000 0b 00 07 00 08 08 1a 03 44 54 43 ········ DTC

The message coming back should not be length 0x0b, it is stating a size which is not documented.

I have no problem whatsoever on the Listening Port 11099.

I'm not in a better position, because if the encoding request is correct, which it looks to be, the server should not return that message. In fact, it should never send a message type 0x07 with length 0x0B, regardless of what junk someone fires at it. It should *always* be 0x10. I have attached a Wireshark PCAP file that shows the above behaviour.

I'd be delighted to be proved wrong, but I don't think I am.
Private File