The detectors are displayed as normal on the graphic screen. However, upon checking the detailed information, the value was 0, and when inspected on-site, there was no pulse signal. I measured the input/output voltage of the IDNET card on the 4100ES, and it showed 0 volts.
Before calling an engineer, I would like to ask a question. I cannot understand why the output terminal reads 0 volts. I checked for troubles in the 4100ES, but there was no issue related to CARD 5.
Is there an on/off function for the IDNET card? When the engineer came last time, I recall seeing them connect it to the master board and control it using some software program. If this feature exists, could you explain what it does?
Disconnect the IDNET loop wires from the card. All of the programmed devices on the card should go into trouble missing on the control panel and at the graphic screen. If they don’t, I would restart the control panel.
I’m sure this is resolved by now, but if an IDnet channel is down (which would be the case if the card wasn’t outputting the normal 28-32v) then the panel won’t be communicating with the devices and they will show as “normal” when looking at them from the display. But this is only if that idnet channel is completely dead, which should also give an “idnet channel failed” trouble. As soon as even 1 device on the loop is talking, the channel is no longer failed and then any “no answer” or whatever other device trouble will come in.
I’ve unfortunately seen the newer IDNet2 cards freeze up, going unresponsive as described, after a system startup. Sometimes a reboot, or even failing and re-enabling the card (flipping address switch 1 for 5-10 seconds then restoring) will bring it back to life.
Thank you for your response.
It took a long time because I’m working in South Korea.
There are thousands of detectors at my location, and due to indiscriminate interior renovations, there have been many detector errors.
The conclusion was a short circuit.
When I asked the technician why the isolate did not interrupt the short circuit, he explained that there is a limit to what the isolate can block.
If this limit is exceeded, the truesite workstation shows it as “normal,” but the value is 0, there is no LED pulse signal, and when measuring the resistance, it shows 35 ohms.
Now, all that’s left is to find the issue causing the short circuit.
I learned one more thing from this experience:
Don’t blindly trust that a “normal” reading in the program means everything is fine; it is essential to check the value in the detailed information and verify the LED pulse signal on site.