Heinzinger electronic GmbH
Phone: +49 (0) 8031 2458 0
www.heinzinger.com
Anton-Jakob-Str. 4, 83026 Rosenheim
Fax: + 49 (0) 8031 2458 58
Germany
Page 70
ERS COMPACT
SYSTem:CONFig:OCD:ACTion
SYSTem:ERRor:NEXT?
SYSTem:CONFig:OCD:ACTion?
SYSTem:ERRor?
SYSTem:CONFig:OPD
SYSTem:LOCK
SYSTem:CONFig:OPD?
SYSTem:LOCK?
SYSTem:CONFig:OPD:ACTion
SYSTem:LOCK:OWNer?
SYSTem:CONFig:OPD:ACTion?
SYSTem:NOMinal:CURRent?
SYSTem:CONFig:OUTPut:RESTore
SYSTem:NOMinal:POWer?
SYSTem:CONFig:OUTPut:RESTore?
SYSTem:NOMinal:RESistance:MAXimum?
SYSTem:CONFig:OVD
SYSTem:NOMinal:RESistance:MINimum?
SYSTem:CONFig:OVD?
SYSTem:NOMinal:VOLTage?
SYSTem:CONFig:OVD:ACTion
SYSTem:SINK:ALARm:COUNt:OCURrent?
SYSTem:CONFig:OVD:ACTion?
SYSTem:SINK:ALARm:COUNt:OPOWer?
SYSTem:CONFig:UCD
SYSTem:SINK:CONFig:OCD
SYSTem:CONFig:UCD?
SYSTem:SINK:CONFig:OCD?
SYSTem:CONFig:UCD:ACTion
SYSTem:SINK:CONFig:OCD:ACTion
SYSTem:CONFig:UCD:ACTion?
SYSTem:SINK:CONFig:OCD:ACTion?
SYSTem:CONFig:USER:TEXT
SYSTem:SINK:CONFig:OPD
SYSTem:CONFig:USER:TEXT?
SYSTem:SINK:CONFig:OPD?
SYSTem:CONFig:UVD
SYSTem:SINK:CONFig:OPD:ACTion
SYSTem:CONFig:UVD?
SYSTem:SINK:CONFig:OPD:ACTion?
SYSTem:CONFig:UVD:ACTion
SYSTem:SINK:CONFig:UCD
SYSTem:CONFig:UVD:ACTion?
SYSTem:SINK:CONFig:UCD?
SYSTem:DEVice:CLAss?
SYSTem:SINK:CONFig:UCD:ACTion
SYSTem:ERRor:ALL?
SYSTem:SINK:CONFig:UCD:ACTion?
3.6.3.5
Interface monitoring
Interface monitoring is a configurable functionality introduced in firmwares KE 2.06 and HMI 2.08. Its goal is to
monitor (or supervise) the communication line between the device and a superior control unit, such as PC or PLC,
and to ensure that the device wouldn’t continue working uncontrolled in case the communication line fails. A failing
line can mean that it’s either physically interrupted (damaged cable, bad contact, cable pulled) or the interface port
inside the device hangs.
The monitoring is always only valid for one of the digital interfaces, the one being used for remote control. It thus
means that the monitoring can become temporarily inactive when the device leaves remote control. It’s furthermore
based on a user-definable timeout which would run out if not at least one message is sent to the device within the
given time frame. After every message, the timeout would start again and reset with the next message coming. In
case it runs out, following reaction of the device is defined:
•
Exit remote control
•
In case the DC output is switched on, either switch the DC output off or leave it on, as defined by the parameter
“DC output after remote” (see
3.5.3.1
)
Notes for the operation:
•
The monitoring can be deactivated or activated anytime via remote control
•
The timeout of the monitoring can be changed anytime via remote control; the new value would only be valid
after the current timeout has elapsed
•
The interface monitoring doesn’t
deactivate the Ethernet connection timeout (see
3.5.3.6
), so these two timeouts
can overlap