9/11/2007 5:03 AM | |
Posts: 20 Rating:
|
Rosa, Thanks for your help. I will try out your suggestion first thing in the morning. I think it will work. |
9/11/2007 4:43 PM | |
Posts: 191 Rating:
|
Ok!! please post again if this is not what you are looking for.. feedback helps! please always rate the answers you receive. ROSA |
9/11/2007 9:04 PM | |
Joined: 3/27/2006 Last visit: 5/16/2023 Posts: 90 Rating:
|
M memory is volatile because it cannot be part of the Data Block. Stick with V memory if you need it to be retentive or you want to be able to suck it back for backup on your laptop. On jobs in which it is not cost-effective to use a battery backup I wrote code that detects a change in setpoint. When a change is detectedthe programwrites the new setpoint to EEPROM memory. This means it updates the onboard storage of the data block you loaded previously. This eliminates all concern for "safe" setpoints similar to the data block method while providing the next step: instantrestoration of the running values. An example program is attached. AttachmentEEPROM.zip (381 Downloads) |
"I never let a cowboy make the coffee." |
|
Follow us on