Store_Parameters

Address:

8960 (2300H)

Type:

DWORD

Access:

Write Only

Unit:

Range:

Value	Domains
65766173H	Whole domains
1001H	Variables_Stored_Block_1 domain (User_Long_Vars[0 to 15])
1002H	Variables_Stored_Block_2 domain (User_Long_Vars[16 to 31])
1003H	Variables_Stored_Block_4 domain (User_Float_Vars[0 to 15])
1004H	Variables_Stored_Block_3 domain (User_Long_Vars[32 to 47])
1005H	Variables_Stored_Block_5 domain (User_Long_Vars[48 to 63])
1006H	Variables_Stored_Block_6 domain (User_Long_Vars[64 to 79])
1007H	Variables_Stored_Block_7 domain (User_Long_Vars[80 to 95])
1008H	Variables_Stored_Block_8 domain (User_Long_Vars[96 to 111])
1009H	Variables_Stored_Block_9 domain (User_Long_Vars[112 to 127])
1010H	Whole standard objects (Objects_Stored_Block_x domains) and whole labelling objects (Labelling_Objects_Stored_Block_x domains)

Default Value:

Store Supported:

Description:

This object supports the saving of drive parameters in non volatile memory. On reception of the correct signature the drive stores the current parameters values in non volatile memory. At the next drive switch on the parameters starting value will be equal to the value stored in non volatile memory.

Notes:

The storing process takes about 4÷5 (worst case) seconds to be completed. If a further store parameters command is sent before the completion of the previous one, the drive will not answer to the communication interface until the previous storing process is completed. The non volatile ram is really written only if data have changed compared to the previous store process. It is possible to know if a store procedure is in process by checking the bit #2 of Drive_Register_Extended object.

The non volatile memory can be written for a limited number of times (typically 100,000 times), when reached that limit F4 errors (see Appendix B – Display Status) can occur, and the drive should be sent to Kollmorgen for reparation.

If a write overrun is detected it will be signaled on KM Space_Warning_Inserted object first as Warning_Write_Overrun and later as Protection_Write_Overrun on KM_Space_Emergency_Inserted that inhibits any further write on the EEprom