Login Page - Create Account

DTC Protocol Discussion Forum


Date/Time: Tue, 02 Jun 2020 04:53:30 +0000


Discrepancy in message type 117 for JSON Compact formatting

[2020-01-16 20:58:05]
User258363 - Posts: 3 | Ending Date: 2020-02-07 [Expired]
Hello, I wasn't sure to post this in SC support or here so I will try here first. I am consuming messages in JSON format for now and I noticed that the format for message type 117 doesn't match the header file ordering. This is the definition for type 117 from http://dtcprotocol.org/DTC_Files/DTCProtocol.h

struct s_MarketDataUpdateBidAskCompact
  {
    uint16_t Size;
    uint16_t Type;

    float BidPrice;
    float BidQuantity;
    float AskPrice;
    float AskQuantity;

    t_DateTime4Byte DateTime;

    uint32_t SymbolID;

...

but in the JSON message I am seeing the ordering looks more like message type 108. Below is a copy and paste of the 117 message from SC DTC server. As you can see, the symbol id (1102) is printed first while in the "DTCProtocol.h" for message type 117 has it listed last.

{"Type":117,"F":[1102,331000,283,331025,137,1579206344]}

Is this expected? I would think the header file needs to be updated.
[2020-01-21 09:41:08]
DTC Engineering - Posts: 282 | Ending Date: 2015-09-08 [Expired]
We have verified this discrepancy. Not sure why the SymbolID is last in the binary structure, it should have been first. So the JSON ordering is correct.
Date Time Of Last Edit: 2020-01-21 09:41:28

To post a message in this thread, you need to login with your Sierra Chart account:

Login

Login Page - Create Account