How to insert a failure signal from MPS3 bus monitor to the Cnet through digital input module IMDSI02 ?
Voted best answer
Hi,
Can you clarify? There are a couple of signals that you could be referring to.
The MPSIII bus monitor you mention provides the Power Fail Interrupt (PFI) signal that is intended to shutdown the cabinet in the event of an undervoltage condition. If the PFI is connected to the MMU and it activates due to an under voltage condition all controllers and communications are halted in the cabinet so if the DSI is in the same cabinet as the power supply then the input will not be processed. The PFI signal uses an open collector transistor output with a maximum specified supply voltage of +5.25V. If you want to connect this signal to a DI as well as use the PFI you may need to use something like this (Phoenix MINI MCR-SL-UI-REL - 2864480) to avoid loading the circuit and causing false PFI activations.
The power system status signal (PSS) on the rear of the power chassis provides a general alarm for the power, fans, temperature etc also using an open collector transistor output. Normally the NIS via the NTCL/NICL PSS1/PSS2 terminals provide a current limited +5V supply which is then connected to the power system status, fan tray etc. The connected devices use either an open collector transistor or a simple contact to pull the 5V supply from NIS down to common. The maximum collector voltage is specified as Vcc and not an actual voltage so in the past I have dropped a 5.1V zener diode across the PSS terminal to common to protect the power chassis from possible overvoltage.
In both cases the PFI / status signals use open collector outputs so the connected device is responsible for limiting the current to prevent equipment damage.
Other options...
At the moment I am using 5Vdc solid state relays (Phoenix Contact DEK-OE-5DC/48DC/100 Series , 5V dc Solid State Relay, Screw Terminal) and a current limiting resistor on the input side to do something similar for connectivity server cubicles interfacing the cubicle PSS to DCS IO remote from the cubicle.
If you have Hnet installed another solution might be to use the terminals on the bus terminator (PHAMSCTER20000) and trigger the SOA bit within the controller. A MODSTAT block to read the status bit connected to a DOL will work OK.
If you have HN800 installed another solution might be use the SA / SB inputs on the module power connector of the first connected device which should map back into the controller (I haven't tried it yet). You might still need to interface the signal to provide 24Vdc to be connected to the SA/SB terminals. Again a MODSTAT block to read the status bit connected to a DOL should work OK.
BR,
Alan
Can you clarify? There are a couple of signals that you could be referring to.
The MPSIII bus monitor you mention provides the Power Fail Interrupt (PFI) signal that is intended to shutdown the cabinet in the event of an undervoltage condition. If the PFI is connected to the MMU and it activates due to an under voltage condition all controllers and communications are halted in the cabinet so if the DSI is in the same cabinet as the power supply then the input will not be processed. The PFI signal uses an open collector transistor output with a maximum specified supply voltage of +5.25V. If you want to connect this signal to a DI as well as use the PFI you may need to use something like this (Phoenix MINI MCR-SL-UI-REL - 2864480) to avoid loading the circuit and causing false PFI activations.
The power system status signal (PSS) on the rear of the power chassis provides a general alarm for the power, fans, temperature etc also using an open collector transistor output. Normally the NIS via the NTCL/NICL PSS1/PSS2 terminals provide a current limited +5V supply which is then connected to the power system status, fan tray etc. The connected devices use either an open collector transistor or a simple contact to pull the 5V supply from NIS down to common. The maximum collector voltage is specified as Vcc and not an actual voltage so in the past I have dropped a 5.1V zener diode across the PSS terminal to common to protect the power chassis from possible overvoltage.
In both cases the PFI / status signals use open collector outputs so the connected device is responsible for limiting the current to prevent equipment damage.
Other options...
At the moment I am using 5Vdc solid state relays (Phoenix Contact DEK-OE-5DC/48DC/100 Series , 5V dc Solid State Relay, Screw Terminal) and a current limiting resistor on the input side to do something similar for connectivity server cubicles interfacing the cubicle PSS to DCS IO remote from the cubicle.
If you have Hnet installed another solution might be to use the terminals on the bus terminator (PHAMSCTER20000) and trigger the SOA bit within the controller. A MODSTAT block to read the status bit connected to a DOL will work OK.
If you have HN800 installed another solution might be use the SA / SB inputs on the module power connector of the first connected device which should map back into the controller (I haven't tried it yet). You might still need to interface the signal to provide 24Vdc to be connected to the SA/SB terminals. Again a MODSTAT block to read the status bit connected to a DOL should work OK.
BR,
Alan
Answers
Usually one would use the TCL01 PSS1 & PSS2 inputs for this purpose, but you should be able to use DSI02/22 also.
Never tried this myself, but it seams feasible:
You would have to connect the MPSIII's +24VDC to the DSI02 channel's "+ terminal", and then connect the "- terminal" to MPSIII "status out" .
A powersupply/fan fault will then close the MPSIII's staus relay, and the DSI02's input will change from "0" to "1" since the DSI02 now has an reference to MCOM.
Hope this helps, try it out in an simulator and let us know how it goes, as this modification will be necessary for others when upgrading to ENM01 modules and PN800
Never tried this myself, but it seams feasible:
You would have to connect the MPSIII's +24VDC to the DSI02 channel's "+ terminal", and then connect the "- terminal" to MPSIII "status out" .
A powersupply/fan fault will then close the MPSIII's staus relay, and the DSI02's input will change from "0" to "1" since the DSI02 now has an reference to MCOM.
Hope this helps, try it out in an simulator and let us know how it goes, as this modification will be necessary for others when upgrading to ENM01 modules and PN800
Add new comment