This article will describe how to configure the Anybus Wireless Bolt and Wireless Bridge II family of products to log events for troubleshooting purposes.
- Anybus Wireless Bolt family
- Anybus Wireless Bridge II
- Firmware 2.05.00 or newer is required.
- All examples in this article use the IP address 192.168.0.99 (default) for the Anybus wireless device.
IN THIS ARTICLE
- Open the AT Commands section in the web interface
- To capture all WLAN Events bit 0, 1, 3 and 4 (0001 1011 = 27) in register 1013 need to be set so entering ATS1013=27 and clicking 'Send' will start the capture. The response should be 'OK'.
Register 1016 sets the event levels to log, so ATS1016=2 will log both Warnings and Errors.
The reporting interval in milliseconds in set in register 3007. ATS3007=10000 will log every 10 seconds.
- To add status info every 60 seconds ATS1018=60 can be entered (setting 0 will disable).
- To reboot the AWB AT*AMREBOOT should be entered.
- The most recent events (still in RAM memory) can be seen by entering AT*AMLOG?
- To see all logged events (writes logs from RAM to Flash), the browser should be pointed to http://192.168.0.99/cgi/log.csv
- To clear the log:
- AT*AMLOG=0 (Clears events in RAM)
- AT*AMLOG=1 (Clears events in Flash)
Understanding the Event Log
- The AT Commands Reference Guide and the Bolt's Help section (http://192.168.0.99/help.shtml) contain more information about the settings and commands above as well as information about the events. For example, on page 103, register 1013 (Diagnose mode) is explained, showing what the abbreviations represent.
2. WSIND code lookup:
0 - STATUS_STOPPED
1 - STATUS_STARTED
2 - STATUS_ERROR
3 - STATUS_DISCONNECTED
4 - STATUS_CONNECTING
5 - STATUS_CONNECTED
6 - STATUS_CONNECTION_FAILURE
7 - STATUS_AP_UP
8 - STATUS_AP_DOWN
9 - STATUS_AP_STA_ADDED
10 - STATUS_AP_STA_REMOVED
11 - STATUS_80211r_REASSOCIATING
12 - STATUS_80211r_REASSOCIATED
13 - STATUS_80211d_SCAN_IN_PROGRESS
14 - STATUS_80211d_SCAN_NOT_IN_PROGRESS
3. WSDIS code lookup:
0 - STATUS_DISCONNECTED_UNKNOWN
1 - STATUS_DISCONNECTED_NO_BSSID_FOUND
2 - STATUS_DISCONNECTED_ASSOC_FAILURE
3 - STATUS_DISCONNECTED_AUTH_FAILURE
4 - STATUS_DISCONNECTED_MIC_FAILURE
5 - STATUS_DISCONNECTED_ROAMING
4. The command AT*AMDUMP? can be entered to read the debug dump log. Most of the info would need to be interpreted by the developers, but the reset reason can sometimes be helpful. The value is a combination of bits from this bitmask:
_BOR (0x0001) // Power on / Power down reset or Brown out reset.
_PIN (0x0002) // Pin reset
_POR (0x0004) // Power on / Power down reset
_SFT (0x0008) // Software reset
_IWDG (0x0010) // Independent Watchdog reset
_WWDG (0x0020) // Pin reset
_LPWR (0x0040) // Low Power reset
For example, a reset reason of 7 means BOR+PIN+POR which is probably a power cycle.
The following AT Commands can be copied and pasted into the AT Command window to get started logging right away (the AMLOG commands will clear the current log):