Axel WOLF 1MS, Руководство пользователя, Страница: 175 / 229

TECHNICAL APPENDIX
| TECHNICAL APPENDIX 175
16.11.10
Smart Scan General Description
The SMART-SCAN mode has been strongly modified and tested in the last release. Here a little general description for
understanding and testing the definitive behavior .
In general the SMART-SCAN mode locks the scanning sequence before rising an alarm and it waits a defined time
(actually fixed for every service). In general with all services having the "Timeout" parameter in place of the "Validation"
in SMART-SCAN the behavior is different. The "Timeout" (as name and notation) is used because we intended that the
service is complex or non always available on the channel and instead of a validated error condition, we are searching
a valid condition before "Timeout" expires. This condition generates trouble in scanning situations, so doesn't exist a
sampled out of range data, but a waited event missing in the defined timing.
SMART-SCAN is able to wait up to six services at the same time (concurrently) handling the scanning sequencer and
masking the alarms under verification. At first it tries to sample the event in the scanning time, but at the end of the
timeout, before rising the alarm, waits a time (about the double of the normal period expected for the kind of service) and
decides to rise the alarm or not.
Example: CT service test inside a scanning list of 4 frequencies.
The 4A group will be searched for 600 seconds in every frequency. At the end of the 600seconds per stations (that's
means 2400 seconds) we are lucky and on three frequencies and we have found the 4A group, but in one them we have
not been able to sample a 4A group.
At the end of the "Timeout" in normal SCAN-MODE the CT alarm is raised for the unlucky station, the one in which the
random scanning routine failed.
In SMART-SCAN mode instead, the scanner will lock on the unlucky frequency and it will wait up to 130 seconds
(defined Smart Wait time for the CT service) to verify if really the service isn't available. If the waiting stage has success,
the scanner restarts, and it will try again to catch another 4A in the next 600 seconds with a normal scanning sequence.
If the waiting stage fails the alarm is raised and the scanner restarts to loop.
In the previous releases in the next loop (failed SmartWait case), the SMART-SCAN locks again trying to solve the
alarm, instead in the last release for the next 30 minutes (only for the frequency and the service with the alarm raised)
the loop will continue like a normal scan mode avoiding to lock the normal scanning sequence and trying to sample a
valid 4A .
So, in the last release the SMART-WAIT will try only one time every "RETRY SMART WAIT" time to lock the sequence
and verify an alarm after the previous one failed. This behavior will allow to avoid locking situations for the other stations
in the scanning list and with a one or more fails in a scanning list, the average looping will be guaranteed.
Please test it and give us suggestions to improve it (if necessary) or report buggy behaviors .
The SMART-WAIT state is visible on the web page as a red line under the Channel Number. The service/services with
the problem will be displayed inside the brackets. In the current release max 2 services are displayed at the same time,
in the final one will be 3.