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
Budget cuts forced us to sell all the power cords for the servers.
RSS Feed
www.control.com/rss
from the Allen Bradley ControlLogix department...
Active DH+ Nodes on 1756-DHRIOHow do I tell when two ControlLogix's communicating via DH+ loose communication?
I have found that someone posted the following answer in a previous old post:
The methods I use in SLC5, PLC5 and ControlLogix is first monitor the Active Node status bit, which is a status bit in SLC5s and PLC5s, and by using a CIP attribute MSG to the DHRIO module with ControlLogix. Next set up a "heartbeat" bit in the MSG between PLCs, have the bit toggle at a rate that suits your message rate, and monitor this with a timer.
My question is:
What are the class/instance/attribute codes to configure in the ControlLogix message to monitor the active DH+ nodes using the 1756-DHRIO? Also is this a CIP generic message? Is this CIP message pointed directly to the 1756-DHRIO module?
I have found that someone posted the following answer in a previous old post:
The methods I use in SLC5, PLC5 and ControlLogix is first monitor the Active Node status bit, which is a status bit in SLC5s and PLC5s, and by using a CIP attribute MSG to the DHRIO module with ControlLogix. Next set up a "heartbeat" bit in the MSG between PLCs, have the bit toggle at a rate that suits your message rate, and monitor this with a timer.
My question is:
What are the class/instance/attribute codes to configure in the ControlLogix message to monitor the active DH+ nodes using the 1756-DHRIO? Also is this a CIP generic message? Is this CIP message pointed directly to the 1756-DHRIO module?
From Control Engineering magazine...
Related articles from Control Engineering magazine- OPC: Painless migration, classic OPC DA to OPC UA, partership
- Easier: panel designs, short-circuit current rating compliance
- MechatronicsZone road show kicks off
- Partnership: Advanced, interoperable motion control, machine tools
- Protect intellectual property: Encrypt firmware, control code
- Portable computing: Operators can be mobile with rugged HMI
- Whitepaper: Small form factor HMIs evolve
- Remote control: Get behind firewalls—securely
- Report asks: Will DIN-rail PCs with I/O revolutionize industrial PCs?
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!



