LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Using of MGI read write anything

Solved!
Go to solution

To the OP:  your example worked just fine for me here, including the Enum.  Any change I made and saved could be seen in the text file and came back correctly on the next load.  I tested with LV 2016 and MGI R/W Anything 2.1.4.4, but I've generally found MGI R/W Anything to work fine with enums for more than a decade. What specific problem are you having?

 

Back in the early-ish days of DAQmx, I once tweaked a low-level type resolution case structure to add support for DAQmx physical channels and terminals, but later changed over to the practice of defining my typedef'ed cluster to use simple strings for such things so I could use the MGI toolkit without mods.

 

 

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
0 Kudos
Message 11 of 14
(1,230 Views)

@Kevin_Price wrote:

To the OP:  your example worked just fine for me here, including the Enum.  Any change I made and saved could be seen in the text file and came back correctly on the next load.  I tested with LV 2016 and MGI R/W Anything 2.1.4.4, but I've generally found MGI R/W Anything to work fine with enums for more than a decade. What specific problem are you having?

 

Back in the early-ish days of DAQmx, I once tweaked a low-level type resolution case structure to add support for DAQmx physical channels and terminals, but later changed over to the practice of defining my typedef'ed cluster to use simple strings for such things so I could use the MGI toolkit without mods.

 

 

-Kevin P


Everything is saved and reloaded correctly.
Numbers and strings are written correctly to the input cluster but I can't manage to write the saved value back to the enum in the input cluster. In the output cluster in saved value in displayed correct.

0 Kudos
Message 12 of 14
(1,223 Views)

For each of the property nodes you write to in the "Load" case, double-click its top bar to highlight it on the front panel.  I think you'll quickly see what the problem is...

 

A better general alternative is to right click the input cluster control, select "Create->Local Variable", and wire to it to update the whole cluster all at once.

 

 

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
0 Kudos
Message 13 of 14
(1,209 Views)
Solution
Accepted by topic author Heino

@Kevin_Price wrote:

For each of the property nodes you write to in the "Load" case, double-click its top bar to highlight it on the front panel.  I think you'll quickly see what the problem is...

 

A better general alternative is to right click the input cluster control, select "Create->Local Variable", and wire to it to update the whole cluster all at once.

 

 

-Kevin P


I have seen my mistake.
With the local variable it works also.

Thank's for support

 

Heino

0 Kudos
Message 14 of 14
(1,187 Views)