Regarding the issues with the instrument panel signals!
Thread Content
Dear experts: Hello, I have a question. If a remote temperature transmitter is part of a complete set of equipment (with its own PLC) and is connected to our DCS via communication lines, then are the I/O points considered part of the DCS’s I/O? --------I’m not sure if I explained it clearly.
Thank you, expert. Your comments have always been sharp, long, and incisive. Thank you for being lenient with your writing:lol
This post was last edited by yuchenchf on 2016-5-17 at 16:56. All communication points can be referred to as COMs, while what we usually call IO points are those that are connected via wired connections. Communication points do not require any IO channels, meaning there is no need for hardware setup or associated costs. This ‘best answer’ is way too simple; why don’t I get marked as the best responder every time I reply? . .
You understand that it’s PLC communication that sends data to the DCS; those are the communication points, or in other words, the software-based connections
Mainly, you were slow, but looking at this answer, yours is indeed the best. Hurry up!
No, this signal does not need to be connected to the card holder
Although soft points do not occupy IO channels, they still take up system memory, just like hard points.
I have a question: communication doesn’t require hardware or costs – how is that possible? What interfaces, what protocols?
This doesn’t count as a temperature I/O point; a Modbus communication module is required
Not counted as an IO point; on our end, it is indicated in the index table with a note stating that it is provided by the manufacturer and communicated to the DCS. When counting exception cables, communication cables need to be included in the count.
Anyway, images still need to be produced; without them, there’s no work to be done, and nobody knows what to do.