This helps determine if the polls from your SCADA system are arriving at your data logger, and if your data logger is responding.įollow these steps to use DevConfig to see the Modbus polls: Your data logger, in turn, makes analog measurements and then stores them in its Modbus Holding and Input registers every second.īut what if your SCADA system does not successfully receive data from your data logger? What can you do now? You can use Campbell Scientific’s Device Configuration Utility (DevConfig) to monitor the incoming traffic to your data logger.
Your SCADA system is set up to poll your data logger every second for the contents of its Modbus registers. In our last Modbus blog article, we used an example with a data logger that was set up to make analog measurements and provide the data to the SCADA system through the Modbus TCP/IP protocol. At times like this, you may wonder: Where is the problem with the communication? Is the problem at the SCADA system (Modbus client), the data logger (Modbus server), or somewhere in-between? Normally, the process of setting up the communication between your data logger and SCADA system is smooth, but there are occasions when technicians in the field discover that the data is not arriving at the SCADA system as expected.
This is often accomplished by configuring the data logger as a Modbus TCP/IP server, which we discussed in the “How to Access Live Measurement Data Using Modbus” blog article. In this article, I’ll quickly share with you one method that I have found to be both helpful and a time-saver.Ĭampbell Scientific data loggers provide measurement data to SCADA (supervisory control and data acquisition) systems throughout the world. Have you ever set up a Campbell Scientific data logger as a Modbus server and discovered that your data was not arriving at your SCADA system as you expected? You may have quickly realized two things: troubleshooting the communication problem is not an easy task, and there are many different approaches you can take.