### Using a Modstat to troubleshoot your system A Modstat (Module Status) provides information about a controller and verifies proper network communication with the controller.
Click for details below To obtain a Modstat Modstat field descriptions
3. #### To obtain a Modstat You can get a controller's ModStat in the following places: ExecB controller—In the WebCTRL® or SiteBuilder application OptiFlex™ controller—In the WebCTRL® application or the controller's setup pages In the WebCTRL® application Use one of the following methods: Right-click a controller on the Network tree, then select Module Status. Select a controller on the Network tree. On the Properties page, click Module Status. NOTE You cannot get a Modstat if running WebCTRL Design Server because it cannot communicate with controllers. In the SiteBuilder application (ExecB controller only) Use a USB Link Kit to connect your computer to the controller's Local Access port. See To connect to a device's Local Access port. In SiteBuilder, select Configure > Preferences. On the Connections tab, select the computer Port that the USB Link Kit cable is connected to, and Baud Rate to one of the following:
   Local Access port | Baud Rate
   5-pin Rnet | 115200
   8-pin round | 38400
Right-click the controller in SiteBuilder's Network tree, then select Module Status. In the controller's setup pages (OptiFlex™ controller only) Connect an Ethernet cable from a computer to the controller as shown below. If your computer uses a static IP address, set the address to 169.254.1.x, where x is 2 or greater. If it uses a DHCP address, leave the address as it is. Turn off the computer's Wi-Fi if it is on. Open a web browser on the computer. Navigate to http://local.access or http://169.254.1.1 to see the controller setup pages.
#### Modstat field descriptions NOTE Modstats vary for different types of controllers. The list below describes all information that could appear on any Modstat. If a description differs between different generations of controllers, the generation is noted.
Field | Description
--- | ---
Date/Time | Date and time the Modstat was run
CM | The controller's rotary switch address (MAC address)
Model Name | Identifies the Product Type
Device Instance | A unique ID assigned to the controller
Driver built | When the driver was built
Downloaded by | When and where the last download was performed
Application Software Version | The name of the first control program that is downloaded
Flash Archive Status | Shows the validity, date, and time of the most recent archive of parameters and status to the controller's permanent flash memory. The archive takes place once a day.
# PRGs initialized # PRGs running | If applicable, the number of control programs that were downloaded vs. the number that are running. If these numbers are not the same, the controller has a problem such as lack of memory.
Firmware sections in flash memory | The name, version, and date of the driver
Reset Counters: | ExecB controller: The number of times each of the following events have occurred since the last time the controller was formatted. OptiFlex™ controller: The number of times each of the following events have occurred since the last time the controller was commanded to clear the reset counters. See NOTE below this table.
Power failures | Interruption of incoming power
Brownouts | Low-level incoming power
Commanded boots | Includes commands issued from the WebCTRL® interface such as the zap manual command, plus commands issued during a memory download.
System errors | Error in the controller's firmware or hardware
Watchdog timeouts | Watchdog is firmware that monitors the firmware for normal operation. If watchdog detects a problem, it restarts the firmware.
S/W Watchdog timeouts | Watchdog is firmware that monitors the application firmware for normal operation. If the watchdog firmware detects a problem, it restarts the application firmware.
H/W Watchdog timeouts | H/W Watchdog will restart the controller if it detects a severe problem with the controller's operating system
System status | Gives the current status of the controller's operation.
Network status | Gives the current status of the controller's networks.
System error message history | ExecB controller: High-severity errors since the last memory download or format. Shows the first 5 and last 5 messages. OptiFlex™ controller: High-severity errors since the last memory download. Shows the most recent 10 messages. See NOTE below this table.
Warning message history | ExecB controller: Low-severity errors and warning messages since the last memory download or format. Shows the first 5 and last 5 messages. OptiFlex™ controller: Low-severity errors and warning messages since the last memory download. Shows the most recent 10 messages. See NOTE below this table.
Information message history | ExecB controller: Information-only messages since the last memory download or format. Shows the first 5 and last 5 messages. OptiFlex™ controller: Information-only messages since the last memory download. Shows the most recent 10 messages. See NOTE below this table.
Manifest revision | Firmware revision
Installed bundles | Components of the firmware
ARC156 reconfigurations during the last hour | An ARCNET network normally reconfigures itself when a controller is added to or taken off the network. The Total field indicates the number of reconfigurations in the last hour. Initiated by this node indicates the number of reconfigurations initiated by this controller. Typical sources of the problem could be this controller, the controller with the next lower rotary switch address, any controller located on the network between these two controllers, or the wiring between these controllers. An excessive number in these fields indicates a problem with the network.
BACnet comm errors in the last 7 days | BACnet communication errors usually indicating dropped packets caused by high traffic on network.
Core (or Main) and Base board hardware | Gives the following information about the controller's boards: Type and board numbers that are used internally by Automated Logic®. The manufacture date and serial number. ExecB controller only: The core board's RAM and Flash memory. RAM is used for driver and control program executables. Flash memory is used for firmware and file storage. See Flash storage size below.
Number of BACnet objects | The number of BACnet objects that were created in the device and the number of those objects that are network visible.
Largest free heap space | Size of the largest piece of unused dynamic memory
Database size | ExecB controller: Size of the controller's memory designated for running programs. Database memory is used for control program parameters, status and history; trends, schedules, and alarms; and driver parameters, status and history. OptiFlex™ controller: Size of the controller's memory.
Flash storage size | The size of the flash memory that is not used by the firmware. This memory is used for file storage and archiving.
| Archive storage size | The amount of flash memory remaining for archival after files are downloaded.
| File storage size | The size of all files (control programs, graphics, driver, etc.) downloaded to the controller. How much information is in these files depends on whether the controller's Download source files option is selected in SiteBuilder or WebCTRL®.
Raw physical switches | The readings used to test the DIP or rotary switches
Network Information | ExecB controller: The various network addresses for a controller installed on an Ethernet. The Current and Assigned addresses will be the same unless: The Assigned addresses were changed in PuTTY. The controller's Default/Assigned DIP switch was moved to the Default position after the Assigned addresses were defined in SiteBuilder. The Enable IP configuration changeover on the on the BACnet Router Properties page is being implemented. OptiFlex™ controller: The various network addresses for the controller. The Current and Assigned addresses will be the same unless the Enable IP configuration changeover on the BACnet Router Properties page is being implemented.
Route Information | BACnet networks that a router is currently routing traffic to. The list changes as BACnet routers are added or removed from the system.
Ethernet statistics | Diagnostic counters directly related to the ethernet communications hardware.
Field | Description
--- | ---
Secondary ARC156 diagnostics | AAR only - The following diagnostic counters relate directly to the secondary ARC156 network communications.
| Rx | READY or STOPPED indicates the present state of the receive process. STOPPED can indicate initialization is in progress. Continued and persistent STOPPED indicates driver or hardware problems.
| Tx | READY or STOPPED indicates the present state of the transmit process. STOPPED can indicate initialization in progress. Continued and persistent STOPPED indicates driver or hardware problems.
| SlaveResets | The number of times the slave processor has been explicitly reset. This is a normal part of initialization and should be a low number.
| RxCmd | The number of completed command receptions from the slave processor. This can be used to gauge the amount of activity between the main processor and the slave processor.
| TxCmd | The number of successful command transmissions to the slave processor. This can be used to gauge the amount of activity between the main processor and the slave processor.
| OverrunErrors | The number of serial overrun errors detected on reception from the slave processor. This is uncommon and should be a low number.
| ParityErrors | The number of serial parity errors detected on reception from the slave processor. This is uncommon and should be a low number.
| FramingErrors | The number of serial framing errors detected on reception from the slave processor. This is uncommon and should be a low number.
| SlaveNotReadyRx | The number of receptions from the slave processor that were discarded during initialization. This should be a low number.
| SlaveNotReadyTx | The number of transmissions to the slave processor that were discarded during initialization. This should be a low number.
| SlaveTimeoutTx | The number of transmissions to the slave processor that timed out. This is uncommon and should be a low number. A high number could indicate a driver or hardware problem.
| SlaveCTSWaitTx | The number of character times elapsed while waiting for the slave processor to be ready to receive a command. This is a normal part of communicating to the slave processor. This number should increment quickly and is commonly a very large number.
| BadLlc | The number of arcnet packets received with an unrecognized logical link control service specified. This should be zero unless non-BACnet devices are connected to the arcnet.
| BadSAP | The number of arcnet packets received with an unrecognized service access point specified. This should be zero unless non-BACnet devices are connected to the arcnet.
| BadServicePrimitive | The number of BACnet packets received with an unsupported service primitive specified. This should be zero.
| NoPacketErrors | The number of BACnet packets that could not be received because of temporary packet memory shortages.
| UpQueueErrors | The number of receptions from the slave processor that could not be queued for processing.
| DownQueueErrors | The number of commands to the slave processor that could not be queued for transmission.
| RxCmdQueueErrors | The number of command receptions from the slave processor that could not be queued for processing.
| PowerOnResets | The number of times the arcnet coprocessor reported a power up event. This number should mirror closely the SlaveResets counter.
| ExcessiveNaks | The number of times the arcnet coprocessor reported excessive naks.
| Reconfigs | The number of times the arcnet coprocessor reported a reconfig event.
| ReconfigsThisNode | The number of times the arcnet coprocessor reported that this node caused a reconfig event.
NOTE OptiFlex™ controller only—If you want to clear the Reset counters and the three message history fields, click the Clear Counts/Logs button on the controller's Properties page in the WebCTRL® application or in the OptiFlex™ controller's setup pages that you access through the Service Port.