{"searchBar":{"inputPlaceholder":"Search by keyword or ask a question","searchBtn":"Search","error":"Please enter a keyword to search"}}
{}

Welcome to the Schneider Electric Website

Welcome to our website.

Select your location

Welcome the the Schneider Electric French website. It looks like you are located in the United States, would you like to change your location?

Traduisez en francais
{"support":{"yesButton":"Yes","noButton":"No","feedback":{"title":"What can we do to improve?"},"submitButton":"Submit","successMessage":"Thank you for your feedback","title":"Was this helpful?","feedbackPercentLabel":"of people found this helpful","captcha":{"error":"Please check the box"}}}
Search FAQs

Allocation and purpose of the extra bytes that get setup when using the Generic Modbus DTM

Issue
 
Why do we add 2 unused bytes in the input or output when we add a io scanner line in the DTM browser/device list for M580 when using a Generic Modbus device?
 
 
Product Line
 
M580, BMENOC, M340
 
Resolution
 
The behavior is due to the fact that it was incorrectly defined in M340 and also current M580 Version of master DTMs. (The definition of M340 was carried to M580!).
 
M340 and M580 both have memory constraint of 32 bit alignment. Due to this, the algorithm for DDT/DDDT for M340/M580 was written to make sure all the structures are Modulo 4.
Ie: All structures created from master are made multiples of 4.
 
In the  below example although 1 register is configured and expected is 2 bytes structure, because of above algorithm remaining 2 bytes are packed with bytes which leads to 4 bytes (with 2 bytes padding at end).

Explore more

Can't find what you are looking for?

Reach out to our Customer Care team to receive information on technical support, assistance for complaints and more.
Explore more