VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Saving Models Variables versus Saving Models Parameters

Hi, 

I am currently using the API Start Data Logging vi to save to TDMS a list of channels as defined in the system definition files. This works fine. Channels are acquired/produced on the RT target, and they end up on the host in a TDMS file.

 

Now, I am trying to go a little further by saving to file the models parameters (defined as such in the sys def file.) Passing their path to the API Start Data Logging vi returns an error saying the path is unknown... Is there some way around this, or should I just save the parameter on the host side instead, since it is where they are set up?

 

Thx.

L.

0 Kudos
Message 1 of 6
(6,186 Views)

Hey L.,

 

You can poll the model parameters using a combination of Get Parameters List and Get Parameter Value from the API. Then you can log that information to file in anyway you choose. If you have more questions, please let me know. Have a great weekend!

John B.
Embedded Networks R&D
National Instruments
Certified LabVIEW Developer
0 Kudos
Message 2 of 6
(6,167 Views)

Thx.

 

So this means that the parameters can only be saved from the host side, correct ?  Is there any mechanism to save them from the RT side ?

Thx.

L.

0 Kudos
Message 3 of 6
(6,150 Views)

Hey L.,

 

If you want to edit the parameters of your system definition file, you will need those to be saved on the host side.

 

If you are interested in logging data directly to the RT side, you can look into using the Embedded Data Logger.

 

Hope this helps!

 

Joe S

Applications Engineer

National Instruments

 

0 Kudos
Message 4 of 6
(6,137 Views)

Thx Joe. 

Just to clarify, I do not need to "edit" the parameters. I just want to save them in a coherent manner with the channels which are saved via the API. So if I understand you well, the Data Logger Custom Device does not allow saving models parameters ?

L.

0 Kudos
Message 5 of 6
(6,134 Views)

Hey L.,

 

The Embedded Data Logger is capable of logging almost anything, including model inports, exports, execution variables, and model parameters. It may be more powerful than you need for this application, but if you are planning to implement some other logging down the line it's definitely worth checking into. If you have more questions, let me know. Have a great day!

John B.
Embedded Networks R&D
National Instruments
Certified LabVIEW Developer
0 Kudos
Message 6 of 6
(6,118 Views)