2 SafeCom Controller
D60700-07
43
8.
You may wish to delete the static entry again. Enter:
arp -d 194.192.134.86
Note:
If you experience problems completing the software upload, we
recommend isolating the SafeCom Controller and the computer being used for
the upload. This should eliminate eventual network broadcast and network
noise that could otherwise disturb the data being sent to the SafeCom
Controller. One way of accomplishing this could be done by connecting the
computer and controller to the same network switch, and removing network
connections to that switch.
2.10
Monitor link to SafeCom Color Front-end
The status of the serial link between the SafeCom Controller and the SafeCom
Color Front-end is reflected in the SNMP value hrDeviceStatus
(1.3.6.1.2.1.25.3.2.1.5) and can assume the value 2 (Running) or 5 (Down). A
3
rd
party SNMP tool can be used to monitor the status.
The SafeCom server the SafeCom Controller is connected to can write two
related events in its
Event log
:
Frontend has stopped communicating, check device <IP address>,
safeCU state: <state>
Frontend has resumed communication on device <IP address>
The events has SafeCom severity 4 (Warning) and the abstract is Check FE
communication.
2.11
SafeCom Color Front-end, Cotag
2.11.1
Initial configuration via card
A Cotag configuration card need to be used with the SafeCom Front-end, Gotag
initially in order for the reader to accept the customer’s Cotag cards. Follow
the steps below.
1.
Unplug the SafeCom Front-end from power and the connection to the
SafeCom Controller.
2.
Power up the SafeCom Front-end.
3.
Present the SafeCom supplied Cotag configuration card within 4 seconds.
4.
When the reader beeps remove the configuration card (minimum half a
meter away).
5.
Within the next 8 seconds present any customer Cotag card.
6.
When the beep sound the configuration process is completed.
