Troubleshooting during development
The following list helps you troubleshoot typical issues that come up when developing a custom application.
If you come across a hardware issue and want to return a reader, please use our RMA form.
I'm debugging my application and need more information about an error.
Please see our error codes overview to learn how to search for more information.
Something's wrong in the communication between my app and the reader.
If you use the SDK, you can use its logging mechanism to analyze the communication.
Unidirectional polling via RS-232 is no longer working.
You've probably started BALTECH ID-engine Explorer or another tool of BALTECH ToolSuite while testing the RS-232 interface. When these BALTECH tools scan for RS-232 ports, the reader switches to BRP, i.e. unidirectional communication is stopped.
Close all BALTECH tools and do a power-on reset on the reader.
Ethernet readers can no longer be found via SLP after a few minutes
This may happen if the routers/switches have IGMP snooping enabled, but there's no IGMP querier in the network.
Routers/switches use IGMP snooping to forward multicast SLP requests from the host to the readers. For this to work, an IGMP querier is needed: It sends periodic requests into the network that cause the host to regularly renew its membership in the relevant multicast group. If there's no IGMP querier and thus no renewed membership, the routers/switches will stop forwarding the host's multicasts to the readers after a timeout. Thus, the readers won't respond to SLP requests anymore.
There are 2 ways to solve this issue:
Disable IGMP snooping on the routers/switches. Look for an option containing the key word(s) IGMP, IGMP Snooping, or Multicast. For details, please check the operation manual.
Set up an IGMP querier in your network. For details, please check the operation manual for your routers/switches.