SOFTWARE CONFIGURATION
148
   MATRIX 320
Multidata ID-NET Network Configurations
The  Multidata  ID-NET  network communications  between  Master and  Slave  are  man-
aged by the application job (configuration) using the pass-through feature. A pre-config-
ured job is loaded with the correct pass-through settings for both the Master and Slaves
when the Default Multidata Configuration is selected from the Internal Network Setting
feature.
1. Complete the configuration of all the application parameters
 (including Image Set-
tings) and save them to the Master with an application specific name.
Optionally, checking the Save on Slave Device box can be helpful to save all the current
individual Slave configurations with the new  configuration  name. This does  not clone
any parameters. If not checked, Slave configurations will remain as Temp configurations
and you will be warned that changes to the Master have not been saved to the Cluster.
For Multidata configurations, the option to Clone Master configuration on Slaves must
not be checked.
Figure 93 - Saving Multidata Configuration to Master
The jobs must not be cloned because the Master and Slaves have different input/output
communication channels. The readers are also working independently from each other,
often on separate stations with different code reading requirements, different operating
modes, etc.
2. Connect to each Slave reader via Ethernet (see note below), and set all the config-
uration parameters of each Slave device.
NOTE
If  necessary,  Slave  device  photometric  (Image  Settings)  parameters
must be configured separately through DL.CODE. This is preferably done
through each device’s Ethernet TCP/IP channel. If Slave devices are not
connected  to  Ethernet  you must  temporarily  (manually) connect  them
one by one to perform Image Settings.