RFID Reader Interface User's Guide2.3 Extending the ReachMobile Reader26 Function Manual, 02/2009, J31069-D0198-U001-A1-0076Nevertheless, this means, we can always rely on getting an event during startup – no matterwhat.Great, we now know when we are started. Normally, you start an underlying reader serviceduring startup of your client via StartReader() and you stop it again during shutdown of yourclient with the StopReader() function of the RFID reader interface causing the reader serviceto terminate as well.If you shut down your client application without calling StopReader() first, the underlyingreader service keeps running. The next time you start up your client and call StartReader(),no startup sequence of the reader service will occur because it is still running.The downside of this behavior would be that you are again without a trigger to start working.The good news is that the RFID reader interface knows that a reader service was alreadyrunning before and initiates a "Reconfiguration : Reconnect" notification. So, you as a clientcan react and reinitialize your application.And again, you can rely on always receiving an event during the RFID reader interfacestartup.Back to practiceSo much for the theory, now back to practice. The notification means of the RFID readerinterface is its Alarms event. As a client you have to add an event handler best before you doanything else with the interface.The alarm handler function has to comply with the following prototype that defines thespecial RfAlarmArgs parameters.public void AlarmHandler(object sender, RfAlarmArgs alarmArgs)Before starting the reader we add the alarm handler:RfReaderApi.Current.Alarms += new RfAlarmHandler(this.AlarmHandler);Now we are ready for take-off. We compile, deploy and run our test application to theRF610M and use our new "Start RF-MANAGER" menu item.