The Bluetooth device scan with the Anybus Wireless device will show “Error, couldn’t scan for any Devices” when it does not find any Bluetooth devices. Sometimes this can happen even when there is a Bluetooth device within range.
- Anybus Wireless Bridge II - Ethernet (AWB3000 and AWB3010)
- Anybus Wireless Bolt - Ethernet RJ45 PoE (AWB2030)
- Anybus Wireless Bolt Serial (AWB2010)
- Anybus Wireless Bolt CAN (AWB2020)
- Connection to the Anybus Wireless device configuration page
- At least one Bluetooth device in discovery mode and within range
IN THIS ARTICLE
BOLT CONFIGURATION BEST PRACTICES:
There are some best practices for setting the Bolt up for Bluetooth connections.
- WLAN (WiFi) should be disabled if it is not being used to save valuable resources, like memory and wireless bandwidth.
- To disable WLAN, the ‘Enable’ check box in the ‘WLAN Settings’ section should be unchecked. Any time this is changed, ‘Save and Reboot’ needs to be selected to implement the change.
If a Bolt is scanning for a non-Anybus Bluetooth device and unable to find it, or getting the “Error, couldn’t scan for any Devices” error, it may be because the Bolt is only searching for other Anybus devices.
- The Bolt uses a device filter to only search for other Anybus devices by default.
- This is controlled by register 2006:
- The command ‘ATS2006=0’ will clear the filter:
- Now the Bolt should find the non-Anybus device: