How to save a STRING to NV?

[spittet]

Hi,

I'm using the DM1000T screen for the first time. I would like it to create a Wifi AccessPoint with a specified SSID and Password that would be stored in NV memory and that could be changed from ServiceTool.

None of the Non-Volatile Memory Dynamic component seems to accept a STRING value type.

So, how do you store a parameter of String type in NV memory that could be changed from Service Tool as a parameter?

I know I could store each char as a U8 using a single NV component for each and then concatenate them into a String, but because the SSID and PASS are 32 and 64 char long respectively, I do not think that this is the best solution.

Let me know if you have a potential solution for this.

Have a good day!

[Marbek_Elektronik]

Hi,
we create text strings from display. We have 4 Lines and 36 characters per line and wie select with all the keys. It works as fast as with mouse.

You arr right: Service tool can't handle text arrays. I have tell helpdesk this years ago and there is no possibility select "ascii".
Or, is it possible in new V12? I am using 11.6.

[Tor]

Hi,

This would be great to have, a NV memory for Strings that can be changed in the Service Tool. But as Marbek_Elektronik pointed out, this has been a wish for a long time, and it seems to be very complicated to implement into PLUS+1 GUIDE.
There's the "Set Value" component that handles strings, and you can read strings in service tool with a checkpoint. The step to have a NV memory that handles string doesn't seem to be a very big step?  =)

I'm sorry, but I don't have any better solution for you in this matter.
As long as these issues comes up from you guys, we can point out to the developers that this is what the customer wants. So keep it up.

Have a nice day.

[acmall]

+1 vote for NV memory components that can store strings. I store operator input text on a DP720 for one of our machines which requires 140 individual NV memory components.

For me this would have been a better use of developer time than the changes to the user interface in V12.

[FluidPowerTom]

I'd be checking to see if STRING type variables will save as RETAIN variables in the Structured Text POU.  That'd be by far the easiest way.

[spittet]

I'd be checking to see if STRING type variables will save as RETAIN variables in the Structured Text POU.  That'd be by far the easiest way.

I tried it and, unfortunately, it seems that a variable of String type cannot be set as "RETAIN" in ST. I got the following message in the "Compiler Messages" during compilation (that aborted) :

Code: [Select]

st_SavedString_data has a non-basic type, and can therefore not be backed by Non-Volatile memory
I joined the test project to this post

[acmall]

See this post from Nilla about limited support for RETAIN: -
https://www.plus1forum.danfoss.com/index.php?topic=1157.msg3763#msg3763

[Sergio-DEK]

I agree. Expanding the support for NV and RETAIN variables is long overdue.

[macbahi]

Hi All,

I downloaded the program SaveStringNV and I modified.

It's working but the data it's not saved as in NV.
when the controller is off,  the SaveString data it's not saved .

Please are you finding a why to save string?

I need that to integrate a password in our program for customers. 

Thanks in advance for your help

With best regards

[FluidPowerTom]

It sounds like the only way to do it with Danfoss hardware may be to set up an ASCII lookup table and actually save the values as number arrays.

[jonbhanson]

I would also like to store a String in NV.

I want to store an alphanumeric serial number to my controllers.  Not being able to save strings to the controller is very limiting.

[acmall]

String is supported as a data type for NV memory since Guide 2024.1.

From the release notes: -

[P1TOOL-2393] Feature:
Support for U64/S64/F64/F32 data types in non-volatile memory and Diagnostic components. (W00650)
Support for strings and arrays in non-volatile memory (W00026, W00046, W01529).
The Cloud component group is now available for being used also on hardware without Cloud support as long as the Cloud enable property is set to False (F), and now support the new types as well. (W01400).
Use the Cloud Set Value and Set Pulse components if you need Namespace support for Set Value or Set Pulse (W01409, W00037, W00440)
All Checkpoint components now support the string data type (W00638).
New types also supported as Module signals.
Access to the typed Hardware and Module input components has been restored in the Component Tab (W00254, W00129, P100006877).

If these new features are used, GUIDE will generate a P1LHX output file instead of an LHX file. (Requires a new Service Tool version to download.