Hello Roger,

I have a DT85 interfaced with LabView. I created 2 schedules, one at 5 seconds and the other at 15 seconds. I use low level Datataker driver to read real time data with 'Read RT' and 'Read line conn' to read the rest of the info I need as a string. Those 2 icons are Inside a While loop in LabView and that's about it.

The issue I have is that when looking at DeTransfer and comparing the incoming lines of information that show in DTransfer and the ones that show in LabView, LabView seems to be missing about every 2 lines of information. How would I go about in getting all lines of info onto LabView? Can you tell me how the communication of DTransfer over TCP/IP is programmed so I can try duplicating the same architecture in LabView?

I have asked LabView forums and can't get a decent answer.

Thank you,

Richard

Hi Richard,

Can you send me your Labview design via email for review?
I will contact you directly.

Best regards,
Rudy Gunawan

Hi Richard,

Within each of those VIs you have mentioned, the way the driver parses the data is based on the return string in fixed format mode.
Also it reads the data until it sees a character return.

If it is missing some data, the LabVIEW application may be conducting another operation, or another situation where this may occur if the data is returned back in historical mode, and the DT85 may be sending back an immediate response, which does not quite fit the format.

Apologies for the numerous assumptions without seeing the application.
I will talk to Rudy further about the code, and it may take me a little while to respond, as I'll work on the question outside work hours.

However if you wish to understand further of how the driver parses the strings returned from the dataTaker, I made sure the VI, DT8x DecodeRecord.vi was documented and tested as much as I could. However I may have missed a test scenario.

Have a look into the VI, and see the documentation and the Tech Note, "TN-0046-A1 - DT80 Series fixed format mode"
For the documentation, refer to the link, which is also within the driver itself.

Cheers,
Anthony