Technical information

W24 Parameter Update
2-74 AT+i Commands Reference Manual May 31, 2008
• RP_GROUP - If the RPF Group Name parameter contains a value, the RPF file must
include an RP_GROUP definition and its value must be identical to the RPF value.
Otherwise, the parameter update file will be rejected. Nevertheless, if the RPF parameter is
set to the special value (*) (match any), the RPF file will be accepted with any value of
RP_GROUP, as well as without any value at all. The RPF Group Name parameter can be
viewed and changed by sending an AT+iRPG? command to W24.
• RP_DEST - If the RPF file contains this parameter, the parameter update file will be rejected
unless the value given in this parameter is identical to the unique ID of the W24 it was sent
to. The unique ID can be viewed by sending an AT+iRP5 command to W24, but cannot be
changed. This feature facilitates sending a parameter update to a specific W24 controller
only.
• RP_START_FROM_FACTORY_DEFAULTS - This flag defines the initial value of
parameters. A YES value will initially restore all W24 parameters to their factory default
values before processing the new RPF file values.
Uploading a Parameters Update File to W24
By default, receiving and processing a parameters update file is disabled in the W24. To enable
this option, the RPG parameter must be set to some value. If a value other than (*) is set, the value
must match the parameters update file RP_GROUP value. This feature facilitates group updates,
and can be used as a password to secure parameter updates.
A remote parameters update file can be uploaded to W24 using W24's internal configuration site.
The nonvolatile parameter RPG controls the parameter update. If it does not contain a value, the
update process is effectively disabled. If it contains an (*), it is fully enabled. If it contains a
value, the update process is restricted to RPF files containing that value in the RP_GROUP
header parameter.
Note: See “Sample Parameter Update File” for a sample RPF file.