PLUS+1 Software > Code sharing

Save Constant In Memory Of Display DP600?

(1/2) > >>

Hello friends,

Hello friends
I have a program I get a parameter, compares and calculates me which has been the largest value. But when you turn the display off and re-ignite DP600, the program had forgotten the value calculated before and empiesa from scratch my number more. Is there some method to store the value, and that when I turn on the display resumes the value saved had greater than before to continue the comparison?

Thanks For The Collaboration  ;D


What does the left elements do? Comparator and switch? - I think: nothing!

I would take the max - function.
Then compare the actual and the last value.
If they are not equal, store the max. value in a NV-memory .
In display, it is a FRAM. So you can store unfinitely.

Please try this.
If you need help, please ask.


Hi Jgarzon.

I was putting this together (see below) as Bernd replied, I agree with his comments.

Please be aware of the EE structure during the process

EEPROM write/erase cycles
(all modules except IX012-010, IX024-010)
1 million Minimum valid over entire operating
temperature range.

EEPROM write/erase cycles
(IX012-010, IX024-010)
10,000 Minimum valid over entire operating
temperature range.

FRAM write/erase cycles
(all extended memory modules-MC0XX-XX8)
100 trillion Minimum valid over entire operating
temperature range.

regards Neil

The memory component you are using is for volatile memory.
i.e. RAM, which is lost upon powering off the computer/screen.

What you need is a non-volatile memory component.
It should be in GUIDE under the Components tab -> Connection -> Non-Volatile Memory Dynamic.
In my opinion, it's input/output wires are not convenient or understandable enough for how you would normally use NVM 99% of the time.
So, I wrote a set of wrapper pages around it, for each variable type that I use.
(U8, U16, U32, S16, and S32)
Attached is the wrapper for U32.

These wrappers are a bit wasteful, since the underlying hardware will write an entire 32-bit word, even if you only need 8 bits, but I use little enough NVM that it shouldn't be a problem in my applications.
Keep in mind the above comments for maximum number of write cycles.
I worked out the math last year, and a rule-of-thumb I came to is that if you write to a NVM component less often than every 10 minutes, or 80 times per day, then your NVM will last for twenty years.

Thanks For Your Answers.
Helped Me Pretty  ;D


[0] Message Index

[#] Next page

Go to full version