As there is a General Scan mode, all Slave Tags have their individual scans respected if there is an In Advise of an Individual Scan Tag for its respective Profile. Readings and writings performed by these scan times do not influence reading and writing scan times of the General Scan mode, that is, the service using an Individual Scan does not restart the remaining time for the General Scan service. This individual scan without influencing the General Scan mode is the desired behavior for readings and writings provoked during the interval among general scans, which would de-sync the expiration of all Tags at the same time. The General Scan mode handles, therefore, updates of all In Advise Tags of all Profiles on events among equal intervals for all. If there is one or more Tags with an expired individual scan, these ones are grouped and added to a cache list, obeying the following connection strategy:

1.The Slave starts its respective Driver object, by enabling an automatic connection to a backup IP address.

2.The IOKit module of the respective Driver object of the Slave is automatically in charge of trying a main or a backup IP address, according to the configuration for automatic connection management.

3.The Slave performs the processing of all Tags on the cache list. As Tags are successfully processed, they are removed from that cache list.

4.This list of Tags in Individual Scan mode also retries n times, as configured on the properties tab, while there are Tags on that cache list. For each retry, the Profile releases the resource if there is other concurrent Profile to it.

5.The processing of individual Tags ends with the success of the whole group or by reaching the end of retries.