![]() ![]() Your highest priority registers will be polled most often by your RTU, while the registers with a lower priority are polled less often. With prioritized polling, you can group your registers into different priority categories. One of our clients was concerned about this, so we developed an Modbus-polling RTU with a prioritized polling function. Prioritized Polling Gives You the Most Important Modbus Information First Knowing the running temperature of your generator is thus more important to you than knowing an obscure device statistic. A generator will cease to run if it overheats, for example. After all, every device has a number of conditions upon which the proper functioning of the device depends. It's likely, however, that you are more concerned with some alarms than others. In the example above, each of the registers is polled once approximately every 20 minutes. Large Register Counts = Long Polling Loops The amount of time it will take for your RTU to complete its polling loop is 20 minutes (1 second x 1200 registers = 1200 seconds / 60 seconds = 20 minutes). It takes your RTU approximately 1 second to poll each register. Depending on how many registers your RTU is polling, the amount of time it takes for your RTU to complete its polling loop will vary.įor example: say your RTU is monitoring a total of 1200 registers across several remote devices. Once your RTU has polled all registers it is monitoring, it has completed what we call its polling loop. After a register has been polled, your device repeats the process for the next register in the polling queue. If the register indicates a problem (low fuel, high temperature, etc.), then an alarm is set on the RTU to tell you that something is wrong. ![]() In essence, the RTU requests a value (a "register") on one of your remote devices. Modbus masters and Modbus-processing RTUs monitor alarms by means of a process called polling. For best results treat us like your engineering department. ![]() Your new firmware functions will run on our proven hardware and benefit from our remote-monitoring expertise.DPS can develop custom firmware to meet your very specific technical requirements.Treat DPS Like Your Engineering DepartmentĮven if you don't need to process large amounts of Modbus, remember that: But what DO you need? Remember that we can customize a solution that will directly meet your unique needs. You may not need to process large amounts of Modbus. This helped one of our clients monitor hundreds of registers spread out over several devices while focusing primarily on the few that matter the most. low fuel, high temperature) according to YOUR prioritization.ĭPS recently developed a new way to prioritize the polling of thousands of Modbus registers. This new interpolated method of polling Modbus registers optimizes data retrieval of important values (ex. New Custom Firmware Feature: Prioritized Modbus Polling ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |