How to pre-program NEPO_DIA and TEPO_DIA DFBs
(Original Document)
About us
General
This operation defines NEPO_DIA and TEPO_DIA DFB functioning.
Procedure
The following table describes the procedure for pre-programming NEPO_DIA or TEPO_DIAfunction blocks:
Step
Actions
1
Select the type of actuator, defined by the CONFIG internal constant : monostable (ORDER_I unused) or bistable (ORDER_O and ORDER_I used).
2
Select the movement type, defined by the ROTATION constant : translation or rotation. If the rotating movement is chosen, the "input" and "output" sensors are merged and the ONEWAY constant defines whether the movement is in one or two directions of rotation.
3
Select the type of orders given to the actuator.
These orders are applied to the actuators according to the following equations for "output" movements. These equations are the same for "input" movements (replace _O with _I and vice versa) :
Order if requested (type 1)
Order stored up to reverse request (type 2)
Order if requested and up to position (type 3)
Order stored up to reverse request and position (type 4)
Order if request and order clash on position (type 5)
4
Select how the physical positions and the element of the operating section are being monitored by the DFB.
It is defined by the NBSENS_O and NBSENS_I internal constants.
5
Select the action of the DFB on detection of an error:
  • SET_ERR data defines the error which sets the ERROR bit to 1,
  • RST_ORD data defines the faults which engage ORDER_I and ORDER_O outputs,
  • RST_FB data defines the faults which switch the DFB into "recalibration" mode.
The setting of a bit in either RST_ORD or RST_FB to 1 selects the error associated with the bit of the same rank in STATUS0.
  • ORD_MNT data defines whether or not orders should be re-activated following the disappearance of the indication in STATUS0, or following faults which have set orders to 0 during a movement.
  • NEW_REQ data defines whether new requests are needed after a fault which has set the DFB to "recalibration" mode. By default, new requests are demanded.
6
Select the movement duration.
  • IMAX_I and IMAX_O data define the maximum duration of "input" and "output" movements,
  • IMIN_I and IMIN_O data define the minimum duration of "input" and "output" movements.
The values express times on a N x 100 ms base, where N is the value of the BASE. On DFB initialization, these values are copied into RMAX_I, RMAX_O, RMIN_I and RMIN_O.
If IMIN_I and IMAX_I information (or IMIN_O and IMAX_O), which define movement duration, are on 0, the DFB will learn this duration.
NBSENS_O and NBSENS_I internal constants
The table below describes the coding of NBSENS_O and NBSENS_I internal constants.
NBSENS_O or NBSENS_I
Monitoring
0
Non-monitored position. This position is considered reached if the DFB is waiting for it to do so, or non-reached if the DFB is not waiting for it to do so. Any fault associated with this position (sensor not reset, not expected, etc.) will not be indicated.
In other words, this means that if a position is selected that is not monitored, the DFB will stop the movement (towards this position) as soon as the RMAX_I or RMAX_O time limit has been reached and will examine the EPO potentially. On the other hand, on initialization or recalibration, the reference point can only continue from a monitored position.
1
Position monitored via SENSOR_O or SENSOR_I input.
2
Position monitored physically with several sensors.
The DFB checks the position with 2 information sources: SENSOR_O (or SENSOR_I) and NOSENS_O (or NOSENS_I), with :POSITION_O = SENSOR_O . NOSENS_O and POSITION_I = SENSOR_I.
NOSENS_ISENSOR_O or SENSOR_I represents the working state of all the sensors.
NOSENS_O or NOSENS_I represents the resting state of all the sensors.
NOTE: The two positions cannot be chosen, and both cannot be monitored. If this is the case, the DFB indicates that there is a configuration fault (STATUS1) and becomes unusable