Graphics

 View Only
Expand all | Collapse all

Datalinq UDP feed

  • 1.  Datalinq UDP feed

    Posted 10-04-2022 05:39
    Hi everyone,

    I'm about to Datalinq to a UDP stream feed in order to receive a clock data exchange to create a game timer.

    Does anyone has any experience with this? Should I connect to a text field or to a clock/timer widget?

    As usual, any help is appreciated, thanks!

    ------------------------------
    Paulo Dias
    Flying Warrior GFX
    ------------------------------


  • 2.  RE: Datalinq UDP feed

    Posted 10-05-2022 00:45

    Datalinq does support UDP data broadcasts. 

    Most likely it would use the ASCII Datalinq source - you will have create the field parser for the clock in the ASCII Datalinq setup.
    Do you have any documentation about the formatting of the clock data?
    If you do not - You could also setup the ASCII datalinq source, set it to UDP, and then enable the DataLogger (ASCII). If you capture some raw data of the UDP source using the Datalinq server and then post a copy of the Datalinq Server log we could probably help you create the field parser. 
    Or you could use something like telnet or Docklight Scripting to captue the data and give us a sample of that. 




  • 3.  RE: Datalinq UDP feed

    Posted 10-05-2022 02:04
    Thanks for the answer Garner!

    I actually have the documentation about the formatting (attached). I have a test in a couple days so I would really appreciate your help setting this parser up as I have no experience with this whatsoever.



    ------------------------------
    Paulo Dias
    ------------------------------



  • 4.  RE: Datalinq UDP feed

    Posted 10-05-2022 11:03
    Can you provide the full documentation? I can't see what the start of packet is, and the documentation may have examples of transmitted data. 

    Just throwing something together based on the "Running Time (without 1/10 seconds)" transmission protocol format (I doubt this will work it will need tweaking). 


    I've highlighted where to enable the Data Logger. This should only be used to capture data for analysis, don't leave it enabled during normal operation. 

    We will need to know what the start packet is of the transmission.


  • 5.  RE: Datalinq UDP feed

    Posted 10-06-2022 05:31
      |   view attached
    Hey Garner, here is a screenshot of the trace log, which was provided by the scoring/timing provider. I couldn't upload the actual log (unsupported file)...

    They also said that the clock feed is actually an emulation of the ALGE Timy protocol.

    If I get the time feed to work on Datalinq, should I bind it to a text object or to a widget timer, in order for me to be in sync?

    Thanks again,


    ------------------------------
    Paulo Dias
    ------------------------------



  • 6.  RE: Datalinq UDP feed

    Posted 10-06-2022 14:31
    That doesn't look like the formatting of the transmission protocols from before, but the princible is the same, you just need to build the field parser for it in the ASCII Datalinq setup. I'm not familiar with the ALGE Timey protocol. 

    You will bind the clock data to a text object.


  • 7.  RE: Datalinq UDP feed

    Posted 10-07-2022 17:00
      |   view attached
    Hey Garner, thank you so much for the help. I setup the UDP field parser like you recommended and it worked perfectly!

    Now, the second part of the data I need to read (scores, leaderboard info, etc) is a TCP ASCII scoring data feed. This part I couldn't get it to work on my test.

    I used the same ASCII Datalinq Source, with the right port and it didn't receive any data. I've tried many combination of 'start of packet' and 'end of packet' and still no luck.

    The provider gave me his IP address but I didn't see anywhere to plug that info in Datalinq.

    The protocol os attached. Any help is appreciated...

    ------------------------------
    Paulo Dias
    ------------------------------

    Attachment(s)



  • 8.  RE: Datalinq UDP feed

    Posted 10-07-2022 17:01
    I also tried using the XML/JSON TCP Datalinq, where I was able to input the port and his IP address. The provider saw me establish a connection but I still received no data in the browser.

    ------------------------------
    Paulo Dias
    ------------------------------



  • 9.  RE: Datalinq UDP feed

    Posted 10-07-2022 17:15
    The XML/JSON TCP Datalinq is definitely the one you want to use. Did you try changing the encoding to ASCII? 


    Otherwise I would say enable logging and send us the log file.


  • 10.  RE: Datalinq UDP feed

    Posted 10-07-2022 17:19
    Hmmm..it may also be because the data is not being terminated with a NULL character...I think it would be worth asking the provider if each transmission is terminated with a NULL character.


  • 11.  RE: Datalinq UDP feed

    Posted 10-08-2022 06:45
    I did try encoding to ASCII and same result, no data.

    I enabled the logging but couldn't find a log folder in the system. Where should I find it?

    Another question, under "TCP client", do I put the provider's IP address? That seem to work in terms of connecting to it.

    Lastly, I did ask the provider about the data being terminated with a NULL character.  I'm waiting for response on that... I'll keep you posted.

    Thanks Garner

    ------------------------------
    Paulo Dias
    ------------------------------



  • 12.  RE: Datalinq UDP feed

    Posted 10-11-2022 14:11
    Hi Garner,

    The scoring provider said that "the messages do not include a NULL character at the end. You have to check for the „</data>" element to identify the end of a message."

    Is there a way to work around this? Or to use the TCP datalinq option to pull this data?

    I'm stuck on what to do to make this work...

    Thank you,


    ------------------------------
    Paulo Dias
    ------------------------------



  • 13.  RE: Datalinq UDP feed

    Posted 10-12-2022 03:13
    There is no workaround. The data provider should offer the option to terminate their messages with a NULL character. If they want to transmit XML data over TCP in a generic and widely adopted way they should support terminating messages with a NULL character. 

    The Datalinq Logs will be in one of there locations:
    C:\Program Files\XPressionStudio\DataLinqServer\logs
    C:\Program Files (x86)\XPression Datalinq Server\logs
    C:\ProgramData\Ross Video\XPression\DataLinqServer\logs