DAT file - read 301 & 302 channel header values

[MauganR]

Hello,

I'm trying to see the channel header values 301 and 302 from the attached DAT file in DIAdem 2024 Q2, but I can't figure out where I can see these values.

Is there any way to display these values for each channel loaded into the Data Portal or somewhere else in the software?

Thanks!

Maugan

[StefanR]

The 301, 302, ... channel header variables are referring to the "register..." properties. These properties can no longer be displayed in the portal (maybe there's a hidden switch) - but can still be reached via the scripting API.

However, instead of using DAT files and "register..." properties, maybe using TDM yould be an option.

With TDM you can create so called "custom properties" (of different data types) with application/customer specific namens.

These properties are visible in the portal, indexed by DataFinder and ...

There's also the option in grouping those properties by using the "~" character - so you can create something like DTS~prop1, DTS~prop2,... That way the properties are grouped and get an own branch (DTS) in the property table.

And there's free C-library which let you create a TDM header (containing the meta data including your properies) which can integrate directly the (already existing) binary files of the DAT file.

Here's the link to the

NI TDM Header Writer C API

:
https://www.asam.net/standards/detail/scdl/

[MauganR]

Unfortunately, we must use the DAT file / format.

We collect data with our equipment and export this data in DAT format so we can import it in DIAdem to do all the post-processing.

Do you know since which version the register properties can no longer be displayed in the portal? Perhaps we can revert back to an older build.

[Brad_Turpin]

Hi MauganR,

It's been a long, long time since the register properties disappeared from the Data Portal.  I haven't tried to look it up, but I'd guess prior to 2010.

How about instead of reverting to an ancient version of DIAdem, you use a load event to automatically run VBScript each time a DAT file is loaded to create duplicate properties for all the register properties, so that they will show in the Data Portal?

Alternatively, we should be able to create a post-processing DataPlugin that is invoked when you load a DAT file into DIAdem, and the post-processing DataPlugin can add those duplicate properties.

I'm headed out on vacation very soon, but afterwards I can help with either of these solutions.

Brad Turpin

Principal Technical Support Engineer

NI / Emerson

brad.turpin@emerson.com

[MauganR]

Hello Brad,

Thank you for your answer.

I'd be interested in creating a VBScript and/or a DataPlugin linked to the DAT file loading into DIADem, so these register properties could be shown one way or another.

As an alternative, is there any other property of the DAT file that my company could use to export/import the values we currently save in these 301 and 302 properties?

If we could find other available properties to export text/numbers, that easily show up when importing a DAT file, then I could have my software team move the values we currently export in 301/302 to these properties.

Thanks!

Maugan

[Brad_Turpin]

Hi Maugan,

Would you be willing to post or email me at least 1 of your DAT/R64 data sets for me to experiment with?  I don't just want to grab whatever example DAT file I can find, because it sounds like you guys are making use of less common DAT header properties-- I want to make sure I can test all the properties you're actually using.

On vacation until July 13 now,

Brad

[MauganR]

Hi Brad,

Sure, please give me your email and I can share a dataset with you.

Thanks!

Maugan

[Brad_Turpin]

Hi Maugan,

I'm back from vacation and ready to help.  You can email me at brad.turpin@emerson.com.

Brad Turpin

Principal Technical Support Engineer

NI / Emerson

[Brad_Turpin]

Hi Maugan,

I have just emailed you a pure VBScript solution that reads the DAT channel header values 301 and 302 and writes those as new channel properties in the respective channels.

Brad