108
Curtis 1232E/34E/36E/38E & 1232SE/34SE/36SE Manual, os 30
24 NOVEMBER 2015
they can be defined as bit (On/O) by using the P_User_Bit variables. ese
variables are typically written to EEPROM through the 1313 handheld or 1314
PC programmer interface (i.e., when a user changes a parameter setting using
the programmer). ey can be used in the VCL code, but changing a P_User
(or P_User_Bit) value with VCL will only change the variable value in RAM
and will not change the value in EEPROM. us, these variables are intended
for creating and defining programmable parameters only.
type quantity range
RAM 420 variables User1 – User120
AutoUser1 – AutoUser300
NVUser EEPROM 15 variables NVUser1 – NVUser15
Block EEPROM 38 blocks NVM3 – NVM40
(15 variables each)
Parameters EEPROM 150 variables and P_User1 – P_User150
10 variables of 8 bits P_User_Bit1 – P_User_Bit10
each (80 bits)
VCL can modify the control mode parameters in RAM by using the VCL
variable name for the programmable parameter. For example,
Brake_Rate_SpdMx = 3000 ;Change Brake Rate to 3.0sec
will change the RAM value of the Speed Mode Express’s Brake Rate; the new
value will be used in determining the braking rate. However, the value of the
parameter’s stored EE value remains unchanged; when the controller is turned
o, the RAM value will be lost. e next time the controller is powered back
on, the “old” value of Brake Rate will be restored from EE memory. To save
this RAM value in VCL, you must use the NVM_Write_Parameter function
((i.e., NVM_Write_Parameter(Brake_Rate_SpdMx)).
Parameter values that are changed by using the 1313 handheld or 1314 PC
programmer are saved directly to EE memory. e 1313/1314 changes will be
retained and restored the next time the controller is powered back on.
8 — VCL
To Next Page
Loading...
Need help?
General
