Troubleshooting
If you are unable to complete the installation, it might be due to one of the following issues.
Issue: Your network is running a DHCP server that is responding to the reader's initial request. Solution: Check whether this is really the case, as described in Essential Checks Before Setup. If yes, reconfigure the DHCP server so that it does not respond to the reader's MAC address. |
Issue: Your machine has multiple network interfaces and the AngleID Config Tool has been given the wrong interface when it opened network sockets. Solution: Find out which interface you are using by starting the AngleID Config Tool and checking the IP address on the front page. This is the IP address that the tool's network sockets have been bound to. If this is not the address you expected, you can configure the tool to use the required IP address, as described in Installation. |
Issue: Your AngleID Config Tool has been configured to disable reader administration, or one of the network protocols used by the reader is being blocked by a firewall on your machine or your network. Solution: When the tool starts, check the Logging tab. This tab shows a list of all the servers and data sinks inside the tool, and prints out the port that each one has bound. If you do not see a port number for each of the servers then there is something in your machine's configuration that is stopping the AngleID Config Tool from binding to the ports it needs. For a list of ports that the AngleIDConfig.exe program must be able to access, see the platform.conf file (in the Files folder of the product distribution). If the ports have all been bound, you can run the AngleIDTester.exe program on another machine to trace down which protocol traffic is being blocked:
To identify problems with your setup, check the Logging tab (or the file that was written for the installation session that failed), and compare the output that you receive with the output from a normal installation session. |
The AngleID Config Tool window is designed for viewing at a size of 1360 x 768 pixels on any modern display. If your screen is smaller than 1360 x 768 pixels, then you might have problems using the tool.
It might be likely that your screen has high-enough resolution, but you have selected to scale up the size of all your applications. On many laptops, a scale factor of 125% is the default setting applied to all applications, even if it makes the application interface bigger than the screen. If this is the case, assuming that you want to keep the default scaling for all your other applications, we recommend that you disable DPI scaling on the AngleIDConfig.exe program.
-
In the product distribution, go to Files. Right-click AngleIDConfig.exe, and then click Properties.
-
In the Properties dialog box, click the Compatibility tab and then select the Disable display scaling on high DPI settings check box, shown in the following screenshot.
If your readers fail to boot, normally with error LED sequence Red Green Red Green or Red Green Orange Red, it may be because when the boot server sends out Ethernet packets they are being discarded by the configuration machine’s network interface.
This is because whilst Ethernet interfaces should support an MTU (maximum transmission unit) of 1500 bytes, some VPNs will support less than this size, breaking programs that require 1500 bytes. The solution provided below ensures that when the boot server sends out Ethernet packets to the readers, they won’t be discarded. This is achieved by changing the configuration of the Ubisense boot server to reduce the MTU it requires.
The solution has two steps:
- Find the MTU size for your network interface by using the command
netsh interface ipv4 show subinterfaces
. You will get output that looks a bit like this:
$ netsh interface ipv4 show subinterfaces MTU MediaSenseState Bytes In Bytes Out Interface ------ --------------- --------- --------- ------------- 4294967295 1 0 1044671 Loopback Pseudo-Interface 1 1500 1 464370283 142018308 Wireless Network Connection 1500 5 0 0 Local Area Connection
- If the MTU size is less than 1500, then set the parameter ls_boot_server_blocksize_limit in platform.conf to (MTU size – 32). For example, if the MTU size is 800, then platform.conf should have a line:
ls_boot_server_blocksize_limit: 768
AngleID readers that have a static IP setting will always send ARP announcements when they start up. So to find the IP address of an AngleID reader, put it on the same network as your PC and power cycle it. Wait for it to start up, then execute arp –a
on your PC. You will get an output that looks a bit like this:
C:\Windows\system32>arp -a
Interface: 10.42.5.84 --- 0xb
Internet Address Physical Address Type
10.42.1.1 00-1a-8c-50-89-5c dynamic
10.42.1.112 00-50-56-b1-63-92 dynamic
10.42.4.12 00-11-ce-01-01-e0 dynamic
10.42.4.14 00-11-ce-01-06-e1 dynamic
10.42.5.4 78-2b-cb-9b-74-d0 dynamic
10.42.5.34 f0-1f-af-6a-3e-59 dynamic
This gives you the IP address for the given MAC. To find other suitable network settings, execute ipconfig
on your PC. You will get output similar to this:
C:\Windows\system32>ipconfig Windows IP Configuration Wireless LAN adapter Wireless Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : ubisense.local Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ubisense.local Link-local IPv6 Address . . . . . : fe80::4c97:6f8e:c6cd:4301%11 IPv4 Address. . . . . . . . . . . : 10.42.5.84 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : 10.42.1.1
This gives you a suitable subnet mask and gateway to use for the reader network configuration. So, for example, in the AngleID Config Tool, to set the address parameters for 00:11:CE:01:01:E0
, you should use the following:
IP address | 10.42.4.12
|
Subnet mask | 255.255.0.0
|
Gateway | 10.42.1.1
|
|