Stored settings provides a way for the user to save default key settings to the Indy Modules. On boot up these settings will automatically be loaded in to the specified keys, thereby eliminating the need for the Host to issue any type of set for those keys.
The settings XML file has a Settings root with any number of setting sub-elements.
<?xml version="1.0" ?>
<Settings>
<setting>
<key>E_IPJ_KEY_1</key>
<bank>0</bank>
<values>0</values>
</setting>
<setting>
<key>E_IPJ_KEY_2</key>
<bank>0</bank>
<values>0</values>
</setting>
...
<setting>
<key>E_IPJ_KEY_N</key>
<bank>0</bank>
<values>0</values>
</setting>
</Settings>
This example will:
Note
E_IPJ_KEY_ANTENNA_TX_POWER has a Bank Count of 1 so the bank tag is used. The other keys have a Bank Count of 0 so the bank tag is omitted.
<?xml version="1.0" ?>
<Settings>
<setting>
<key>E_IPJ_KEY_REGION_ID</key>
<values>E_IPJ_REGION_CHINA_920_925_MHZ</values>
</setting>
<setting>
<key>E_IPJ_KEY_ONBOOT_START_ACTION</key>
<values>E_IPJ_ACTION_INVENTORY</values>
</setting>
</Settings>
This example will:
<?xml version="1.0" ?>
<Settings>
<!-- Set up a 3 channel table for Japan -->
<setting>
<key>E_IPJ_KEY_REGION_ID</key>
<values>E_IPJ_REGION_JAPAN_916_921_MHZ_NO_LBT</values>
</setting>
<setting>
<key>E_IPJ_KEY_REGION_CHANNEL_TABLE</key>
<values>6, 18, 12</values>
</setting>
<setting>
<key>E_IPJ_KEY_REGION_CHANNEL_TABLE_SIZE</key>
<values>3</values>
</setting>
<!-- Set up a GPI Inventory Start on Port 4 (bank 4) -->
<setting>
<key>E_IPJ_KEY_GPIO_MODE</key>
<bank>4</bank>
<values>E_IPJ_GPIO_MODE_INPUT_ACTION</values>
</setting>
<setting>
<key>E_IPJ_KEY_GPIO_STATE</key>
<bank>4</bank>
<values>E_IPJ_GPIO_STATE_LO</values>
</setting>
<setting>
<key>E_IPJ_KEY_GPIO_HI_ACTION</key>
<bank>4</bank>
<values>E_IPJ_GPI_ACTION_START_INVENTORY</values>
</setting>
<setting>
<key>E_IPJ_KEY_GPIO_DEBOUNCE_MS</key>
<bank>4</bank>
<values>10</values>
</setting>
<!-- Set up a GPI Inventory Stop on Port 1 (bank 1) -->
<setting>
<key>E_IPJ_KEY_GPIO_MODE</key>
<bank>1</bank>
<values>E_IPJ_GPIO_MODE_INPUT_ACTION</values>
</setting>
<setting>
<key>E_IPJ_KEY_GPIO_STATE</key>
<bank>1</bank>
<values>E_IPJ_GPIO_STATE_LO</values>
</setting>
<setting>
<key>E_IPJ_KEY_GPIO_HI_ACTION</key>
<bank>1</bank>
<values>E_IPJ_GPI_ACTION_STOP_INVENTORY</values>
</setting>
</Settings>
Note
In this example GPI triggering will not start until a start command is issued with an E_IPJ_ACTION_GPIO argument
A stored settings XML file must be converted to a loader image before it can be used. Stored settings loader images are like any other application image and can be loaded as such.
The Indy Demo Tool’s “Image Loader” tab has controls for stored settings.
Note
To create a stored settings image the Indy Demo Tool must be connected to the IRI device
Note
All values in a settings file that has been saved via the Indy Demo Tool will be in decimal format
If the Indy Module does not have any stored settings then using the Indy Demo Tool save settings button will result in a file as follows.
<?xml version="1.0" ?>
<Settings/>