General Discussions
Reading specific data from DT80 with LabView

Hi,

I'm new to datataker loggers, but reasonably comfortable in LabView working with a DT80 that is running a job with a number of schedules.

I can read the data i want via TCP/IP using a modified example vi without effecting the running job. I feel it's a bit clunky, obtaining in some cases quite a large array of data from the schedule (B and D), and then indexing in LabView to get what i want.

It's only several of the obtained (acquired) variables from those scheds that i want to work with in LabView. i acquire many, many more than that from the scheds examples i played with either acquired historical data (far too much data) or setup a particular channel and re-wrote the active job, requiring me to install the job firmware again?

Ideally i'd like to read just the channel variables of interest and ignore the rest that are used within the DT80 active job etc.
but importantly, NOT affect the active/installed job in any way.
any pointers/advice etc much appreciated.
thanks in advance.

-j.

Hi, I'm new to datataker loggers, but reasonably comfortable in LabView working with a DT80 that is running a job with a number of schedules. I can read the data i want via TCP/IP using a modified example vi without effecting the running job. I feel it's a bit clunky, obtaining in some cases quite a large array of data from the schedule (B and D), and then indexing in LabView to get what i want. It's only several of the obtained (acquired) variables from those scheds that i want to work with in LabView. i acquire many, many more than that from the scheds examples i played with either acquired historical data (far too much data) or setup a particular channel and re-wrote the active job, requiring me to install the job firmware again? Ideally i'd like to read just the channel variables of interest and ignore the rest that are used within the DT80 active job etc. but importantly, NOT affect the active/installed job in any way. any pointers/advice etc much appreciated. thanks in advance. -j.

Hi jzk,

If you only require a single channel to display in Labview.
You can create a single line reading using low level vi attached to chart vi.

But you need to assign that channel to CV and read this CV in your single line reading.

That will not disturb the job.

Best regards,
Rudy Gunawan

Hi jzk, If you only require a single channel to display in Labview. You can create a single line reading using low level vi attached to chart vi. But you need to assign that channel to CV and read this CV in your single line reading. That will not disturb the job. Best regards, Rudy Gunawan

Hi Rudy,
thanks for the reply, and advice.
i'll experiment and see what i come up with.
thanks again.
j.

Hi Rudy, thanks for the reply, and advice. i'll experiment and see what i come up with. thanks again. j.

i had a look into this last night, i'm only working on it on a casual basis.
anway, i looked at the dt80 low level read line vi? i think that's the one implied?
it returned what appeared to be a complete schedule with all it's parameters.
consequitive running of the vi 'captured' whatever sched was available. thats what it seemed like to me.
this wouldn't give me much improvement to what i have working now using the low level real time acquisition?
i thought about using the datamap, but again i'd have to cycle through the scheds and pluck out data of interest?

i went through all the vi's that i thought might give me what i'm lookign for. i didn't conclude anyhting?
i'm sure the logger can/will respond to how i want to read data from it?

out of the current job scheds, two of them contain parameters i want. all held as cv variables/channels.
can i ask the logger to just give me, 100CV, 120CV and 130CV from sched B and 25CV from sched D?
what i have now works and works well, it'd just be nice to stream line the code. i spend time capturing scheds that i do nothing with?

i had a look into this last night, i'm only working on it on a casual basis. anway, i looked at the dt80 low level read line vi? i think that's the one implied? it returned what appeared to be a complete schedule with all it's parameters. consequitive running of the vi 'captured' whatever sched was available. thats what it seemed like to me. this wouldn't give me much improvement to what i have working now using the low level real time acquisition? i thought about using the datamap, but again i'd have to cycle through the scheds and pluck out data of interest? i went through all the vi's that i thought might give me what i'm lookign for. i didn't conclude anyhting? i'm sure the logger can/will respond to how i want to read data from it? out of the current job scheds, two of them contain parameters i want. all held as cv variables/channels. can i ask the logger to just give me, 100CV, 120CV and 130CV from sched B and 25CV from sched D? what i have now works and works well, it'd just be nice to stream line the code. i spend time capturing scheds that i do nothing with?
47
3
2
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft