Skip to main content

Data Source Issues

This section covers problems related to data sources and data points in Mango. Data sources are the primary mechanism for collecting data from external devices and systems, and issues in this area can range from communication failures to unexpected data loss.

Common Data Source Issues​

  • Data Points Disappear After Upgrade -- Data point values disappear from views or charts. Covers causes including purge settings, module version mismatches, database issues, and clock synchronization problems.

  • Modbus Point List Requirements -- Reference guide for the information needed to configure Modbus data sources, including register types, data types, offsets, and validation procedures.

  • Modbus Troubleshooting -- Troubleshoot Modbus TCP and serial communication issues including connection refused, timeout errors, wrong register addresses, byte order problems, and IO log analysis.

General Data Source Troubleshooting​

Data Source Won't Enable​

If a data source fails to enable or immediately disables itself after being enabled:

  1. Check the data source's event log for error messages. Navigate to the data source editor and look at the recent events section.
  2. Verify that the communication parameters are correct (IP address, port, baud rate, etc.).
  3. Confirm that the target device is reachable from the Mango server. Use ping or protocol-specific tools to test connectivity.
  4. Check the ma.log file for detailed error messages that may not appear in the UI.

Points Show "Unreliable" Status​

When data points display an unreliable status indicator, it means Mango has not received a valid value within the expected timeframe. Common causes include:

  • The data source poll rate is too slow relative to the device's response time.
  • Network connectivity issues are causing intermittent communication failures.
  • The device has gone offline or is not responding to requests.
  • The point locator configuration (register address, OID, node ID, etc.) is incorrect.

Communication Timeouts​

Frequent timeout errors in data source polling typically indicate network issues or device overload. To diagnose:

  1. Check network connectivity between the Mango server and the target device.
  2. Increase the timeout value in the data source configuration.
  3. Reduce the number of data points being polled in a single request if the device cannot respond quickly enough.
  4. Check if a firewall or security device is blocking or throttling the communication protocol.

Data Source Disabled After Restart​

If a data source that was enabled before a shutdown appears disabled after Mango restarts, it may indicate that the shutdown was not clean. Mango records the enabled state of each data source and restores it on startup, but an abrupt termination can prevent this state from being saved correctly. Re-enable the data source manually and ensure that future shutdowns use the proper shutdown procedure.