Home » Categories » Multiple Categories |
What is the purpose of the UseGuardBand/GuardBandTime or InterCharacterDelay parameters in an MCM module? |
Article Number: 97 | Rating: Unrated | Last Updated: Thu, Jul 3, 2014 at 10:21 PM |
Due to timing variations in various Modbus devices, it is possible for a Modbus master to have problems sending write commands to the MCM slave port while having no issues with read commands. In such cases, the "Use Guard Band" and "Guard Band Time" parameters (in older versions of ladder logic or ProLinx Configuration files) or the "InterCharacterDelay" parameter (in newer versions of ladder logic) can be used to activate an alternate timing scheme that allows write commands to be properly interpreted and appropriate responses sent. To activate this alternate timing scheme in older versions of ladder logic, set the Use Guard Band to "1" to enable this feature and set the Guard Band Time to any value greater than 8 (milliseconds.) Values between 10 and 25 are typical; but certain applications may require even higher values. To activate this alternate timing scheme in newer versions of ladder logic, set the InterCharacterDelay parameter to any value other than 0. Again, typical values are between 10-25; but may need to be higher. Guard Band Parameter With multiple nodes in the network (multi-drop), the module must be able to define the time period used to properly recognize the received data sequence as a valid Modbus message. This time period is defined through the guardband timer parameter. This functionality is only used for Modbus RTU mode, when the module is configured as a slave device in a multi-drop network (RS-422 or RS-485 wiring). In RTU mode, when the module receives sequence of data from another node, it will recognize the end of the message when it detects a 3.5 character gap. The next byte received after a 3.5 character gap will be recognized as the start of a new Modbus message. The 3.5 character gap depends on the port communication settings, especially the baud rate. The higher the baud rate, the lower the corresponding time period equivalent to the 3.5 character delay. To use the default Guard Band Timeout parameter, set the Guard Band Time as follows: Guard Band Time = 0 This configuration will set the module to use a pre-defined time interval for Modbus message recognition calculated for each baud rate. This should provide optimal performance for most applications. The following guard band timer values will be automatically used by the module with the default parameter value (Guard Band Timer = 0) is selected: Baud Guard Band Timer (ms) 110: 350 If you still observe a considerable number of communication errors, try to increase the Guard Band Time value (in milliseconds) until the network performance is improved. |
Attachments (0)
![]()
There are no attachments for this article.
|
Comments
![]()
There are no comments for this article. Be the first to post a comment.
|
Which ProSoft products can communicate with a Honeywell DCS System?
Viewed 1 times since Tue, Jan 22, 2008
How do I get Floating-Point values in a PLC5 or SLC processor from the Modbus module?
Viewed 1 times since Tue, Nov 28, 2006
Baud rate entries greater than 32767 in ProSoft Modules
Viewed 1 times since Tue, Nov 28, 2006
What causes a conditional command to be issued?
Viewed 1 times since Tue, Nov 28, 2006
Which of your products support RS-485 serial protocols?
Viewed 1 times since Wed, Feb 6, 2008
How to avoid slow data updates on a Modbus network with an MVI56(E)-MCM or MVI69-MCM when some Slaves are either not on-line or not functioning correctly?
Viewed 1 times since Wed, Mar 19, 2008
Bulletin 1-5165141 MVI56-MCM getting intermittent communications errors when operating on both ports
Viewed 1 times since Wed, Nov 29, 2006
What is the difference between the MVI56-MCM and the MVI56-MCMR?
Viewed 1 times since Tue, Nov 28, 2006
I was not using both Modbus ports on my MVI56-MCM module, so I set all the port parameters for the unused port to zeros to disable the port and now my module is faulted and will not restart. Why?
Viewed 1 times since Tue, Nov 28, 2006
What is the difference between the 3100-MCM and the MVI71-MCM
Viewed 1 times since Tue, Nov 28, 2006
|