Can someone assist me with a question on how to calculate the total number of I/Os in an I/O list? Should I include soft signals from modbus, or only count the hardwired signals?
Are you working with RSLogix software and in need of comprehensive connection information? Look no further than the Logix5000 Task Monitor, which provides in-depth I/O data.
I am not specifically seeking a loop diagram. Rather, I am curious about whether vendors typically consider only hardwired 4-20mA signals or if they also include signals received through Modbus from various PLCs when determining the total I/O count. Can you clarify this distinction for me in the I/O count list?
I am referencing the document labeled I/O list for the count.
When creating an IO list for maintenance technicians and contractors involved in building solutions, it is advisable to exclude network signals and focus on developing a communication map that outlines the data flow between PLCs. This map should include details such as frequency, size, and addresses of data being sent or read. When it comes to the hardware IO list, it is beneficial to include columns for Tag, Description, Direction (In or Out), Type (digital, analog, frequency), HART compatibility (Yes/No), I.S. certification (Yes/No), signal ranges (0-10V, 4-20mA), and the variables being measured along with their respective ranges. Additionally, for digital inputs, it is important to specify the normal and detected states (High, Low, etc.).
The effectiveness of using a list depends on its intended purpose. In my previous job, we utilized I/O lists as a valuable resource in the process of creating project proposals. Through continuous refinement, we established a systematic approach that allocated specific timeframes for different inputs and outputs, as well as additional time for loops and sequences. It was important to distinguish between "soft points" and "hard points" in order to accurately account for the varying configuration requirements.
When quantifying the total number of I/Os in an I/O list, it's generally essential to include both hardwired and soft signals. Hardwired signals relate directly to physical channels on the hardware, whereas soft signals are more like virtual I/O lines which can carry extra information as they are typically created within software such as a PLC or DCS program. Although they don't map directly to physical inputs and outputs, soft signals can influence the system in significant ways like hardwired signals do. Hence, for a comprehensive understanding and count of I/O signals, you should include both types.
Sure, happy to help! In general, when calculating the total number of I/Os, you should include both the hardwired signals and the soft signals from Modbus. It's important to consider all connectivity points because each route of communication, whether hardwired or software-based like modbus, is an I/O that the system has to manage. Therefore, don’t forget to count the soft signals alongside the hardwired ones.
✅ 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: - Yes, it is recommended to include both modbus soft signals and hardwired signals when calculating the total number of I/Os in an I/O list to have an accurate count of all inputs and outputs.
Answer: - Modbus soft signals are virtual signals that represent data points from external devices, and including them in the total I/O count ensures that all communication interfaces and data points are accounted for in the system design.
Answer: - Modbus soft signals are typically software-based and communicate over a network protocol, while hardwired signals are physical connections between devices. It is essential to identify and distinguish between the two types of signals when creating an I/O list.
Answer: - When including modbus soft signals in I/O calculations, ensure that the communication protocol and data mapping are correctly configured to accurately reflect the inputs and outputs in the system. Additionally, consider factors such as network latency and reliability for proper signal processing.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.