As we upgrade an old system running Steeplechase and Citect with Devicenet to Wago, I am looking for assistance with determining the IO addressing. Although I have past experience with Steeplechase, I am unfamiliar with Devicenet. I am wondering if the Devicenet Master device contains the necessary information. According to my Steeplechase Handbook, only tag names are used in Steeplechase. Any guidance on this matter would be greatly appreciated.
Is the DeviceNet master required to be on the device running Steeplechase software? My experience with Steeplechase involves mapping data from DeviceNet nodes to tag names. On a different note, I recall a training session on Cutler Hammer's version of Steeplechase where the first exercise was creating a flowchart for a start/stop pushbutton seal and latch circuit. I pointed out the irony of using Steeplechase for a task better suited for ladder logic, especially since the flowchart solution appeared messy. The instructor criticized my perspective as having a negative attitude.
Steve, I may have been mistaken in my terminology. There is a DeviceNet device located near the computer that I initially thought was capable of certain functions, but it could actually be a scanner device. I will be visiting the site next week to access the PC and investigate the devices present. Unfortunately, the previous integrator did not provide any drawings, so we need to locate the addressing information as this facility has numerous IO spread across multiple nodes.
To optimize communication between Steeplechase and a DeviceNet master, a mapping table within the Steeplechase application is necessary. This table will link specific inputs or outputs from a DeviceNet node to corresponding tagnames in Steeplechase, whether Steeplechase is the DeviceNet master or simply communicates with one. This mapping ensures seamless integration and efficient operation of the connected devices.
Thank you, Steve!
Certainly, based on my experience with Devicenet, the Master device will indeed provide the necessary addressing information for your IO devices. That said, the exact approach might vary depending on the specific layout of your network. Make sure to check the manual in detail. As for Steeplechase, it's true that it primarily deals with tag names, but you can usually cross-reference those with the IO addresses via the device configuration panels. Coming onto Wago, their I/O system is pretty straightforward with mapping, so once you know the IO addresses from your Devicenet system, the transition should be fairly smooth.
Absolutely, the Devicenet Master device should indeed house the required information; it essentially bridges the network communication and provides access to the I/O data. Although Steeplechase uses tag names, Devicenet will need to work with actual I/O addresses. Regarding your move to Wago, you might want to use their I/O-Check tool to configure and map I/O addresses. Just remember to double-check any address changes in your PLC and SCADA to ensure data integrity.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: 1. Q: How can I determine IO addressing when upgrading from a system running Steeplechase and Citect with Devicenet to Wago? When transitioning from Steeplechase and Citect with Devicenet to Wago, you may need to refer to the Devicenet Master device for necessary information on IO addressing.
Answer: Yes, in Devicenet, the IO addressing may differ from Steeplechase where only tag names are used. Understanding the structure and setup of Devicenet can help in determining the IO addressing for the upgrade.
Answer: While past experience with Steeplechase can be helpful, familiarity with Devicenet and the specifics of the Wago system will be crucial in determining the correct IO addressing during the upgrade process.
Answer: Seeking guidance from resources such as the Devicenet Master device, manuals, and possibly consulting with experts can assist in understanding and setting up the IO addressing effectively during the system upgrade.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.