Range error

Overrange/Underrange

This functional unit monitors the measured value for exceeding or falling below the nominal FSV, -3.0 V and +3.0 V are monitored in the “±3 V” measuring range.

Parameterization is not possible. The measured value is not limited.

Range Error

The Range Error functional unit monitors the measured value according to 2 limit values (min. and max.), counts overrange/underrange and reports this as an error (error bit in the status). There is no limitation of measured values.
In the default setting, the RangeError limit values are set to negative and positive technical FSV, e.g. in the "±3 V" measuring range to LowRangeError = -3.22 V and HighRangeError = +3.22 V, exceeding the limit is then output as an error in the PDO status and LED.

Limit values cannot be parameterized in all operation modes The limit values in index 0x80nD can be changed in the operation modes: "Integer PDO, Extended Range" and "Real32-PDO" The limit values index 0x80nD are predefined (unchangeable) with the values 0x7FFF / 32767 or -32768 in the operation mode: "Integer PDO, Legacy Range"

Changing the interface or IntegerScaler 0x80nD:12 When changing the interface or IntegerScaler 0x80nD:12 (Extended/Legacy Range), the limit values are reset to the default setting according to the interface!

Resetting to the default setting according to the interface is done by

• an interface change
• or a de-energized setting [(re-)power cycle]
• or the command 0x302n after index 0xFB00:01 (channel 1: n = 0, channel 2: n = 1, ...).
  During execution, "Status" 255 "busy" is displayed in index 0xFB00:02, "0" means "successfully completed"
• and the command 0x3001 "Reset all Counters"

Fig.156: CoE Index FB00, DEV Command

During command execution, "Status" 255 "busy" is displayed in index 0xFB00:02, "0" means "successfully completed".

The firmware responds to an unknown command with

Fig.157: General parameter incompatibility reason, 0x06040043