Member Login
Search
Past & Future Posts
Sponsored Communities
Neat Stuff

Visit our shop for nerds in control lifestyle products.
Cool stuff
Thermal Overload
The threads that wouldn't die...
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
Fortune
Let the machine do the dirty work.
-- "Elements of Programming Style", Kernighan and Ritchie
-- "Elements of Programming Style", Kernighan and Ritchie
RSS Feed
www.control.com/rss
from the Automation department...
Modbus Master CommunicationModbus Master Communication between 4 slaves. Modbus Master is communicating with single slave (means RXD, TXD is blinking with both systems, but it can't read the values from Slave). Could anyone help me with this to shotout?
Modbus requires that all of the units, i.e. the master and slaves, have their confiqurations the same: baud rate, parity, etc. Also be sure your addressing is correct. If you are trying to read or write to invalid registers you will not get a response.
Ajith,
I have found when trying to establish serial communications for the first time it's a good idea to slow the baud rate right down, e.g. 1200 or even 300. That way it's more forgiving if there's a timing issue. Then I try different combinations of Stop bits and Parity until it starts to work. Once you have them talking the same language then increase the baud rate.
Another trick I use is a laptop with a terminal emulation program running connected in parallel to TXD and Gnd to display first of all the messages coming from the master then RXD and Gnd to see the response. With this setup it's easy to spot if the messages are good or garbage.
If the connection is 485 the laptop's RS-232 is able to see the signal on a 485 negative wire from memory (I might have the polarity wrong but it soon becomes apparent).
Hope this is useful,
Roy
I have found when trying to establish serial communications for the first time it's a good idea to slow the baud rate right down, e.g. 1200 or even 300. That way it's more forgiving if there's a timing issue. Then I try different combinations of Stop bits and Parity until it starts to work. Once you have them talking the same language then increase the baud rate.
Another trick I use is a laptop with a terminal emulation program running connected in parallel to TXD and Gnd to display first of all the messages coming from the master then RXD and Gnd to see the response. With this setup it's easy to spot if the messages are good or garbage.
If the connection is 485 the laptop's RS-232 is able to see the signal on a 485 negative wire from memory (I might have the polarity wrong but it soon becomes apparent).
Hope this is useful,
Roy
From Control Engineering magazine...
Related articles from Control Engineering magazine- ODVA, DeviceNet: New CIP specs; ControlNet added; 2009 meeting
- Embedded, wireless devices, dynamic IP routing
- Listen in: Wireless developments for Air Force may influence industrial applications
- Easier implementation: Kits for cable testing, wireless products
- Inside look: How MTL Instruments fits with Cooper Industries
- Ethernet hardware: Switches and more
- Frost & Sullivan awards honors many automation, controls companies
- ABB update: User conference, exhibition, flow, SCADA, wireless
Above articles copyright 2008 Reed Business Information. Subject to its Terms of Use.
Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2008 Control Technology Corporation. All rights reserved.
Users of this site are benefiting from open source technologies, including PHP, PostgreSQL and Apache. Be happy.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Patronize our advertisers!



