Description of NEPO_DIA and TEPO_DIA DFB configuration variables
(Original Document)
About us
Description of variables
The following table describes the public variables:
Name
Type
Description
CONFIG
INT
Type of actuator configuration.
This word is used to configure the type of actuator command (see following table). By default, CONFIG = -1 (this value is deliberately faulty in order to make choosing the actuator type mandatory).
The default value is -1.
NBSENS_I, NBSENS_O
INT
Position monitoring.
These 2 words are used to define how the DFB monitors "input" and "output" positions respectively:
  • NBSENS_I (or NBSENS_O) = 0; position is not monitored,
  • NBSENS_I (or NBSENS_O) = 1; position is monitored with SENSOR_I (or SENSOR_O) input,
  • NBSENS_I (or NBSENS_O) = 2; position is monitored with SENSOR_I (or SENSOR_O) input (working state of all sensors) and public variable NOSENS_I (or NOSENS_O) (resting state of all sensors).
The default value is 1.
ROTATION
EBOOL
Movement type.
This bit defines a rotating movement when set on 1.
This parameter does not exist for the TEPO_DIA DFB
The default value is 0.
ONEWAY
EBOOL
Movement sequence.
When on 1, this bit defines a rotating movement with the possibility of linking up several movements in the same direction.
This parameter does not exist for the TEPO_DIA DFB
The default value is 0.
SIMUL
EBOOL
Simulation mode.
When on 1, this bit sets the DFB into modeling mode.
The default value is 0.
Selecting the actuator type
The CONFIG internal constant value is used to select the actuator and order type. The following different configurations are possible:
CONFIG
Actuator
Command
Command logic
0
monostable actuator, single order ( ORDER_O )
single request ( REQ_O )
order if requested (type 1)
1
monostable actuator, single order ( ORDER_O )
two requests (REQ_O, REQ_I)
order maintained until reverse order (type 2)
2
monostable actuator, single order ( ORDER_O )
two requests (REQ_O, REQ_I)
order if request and order clash in position, unlocking on reverse request or loss of position (type 5)
3
bistable actuator
two separate orders (ORDER_O, ORDER_I)
two requests (REQ_O, REQ_I)
order if requested (type 1)
4
bistable actuator
two separate orders (ORDER_O, ORDER_I)
two requests (REQ_O, REQ_I)
order maintained until reverse order (type 2)
5
bistable actuator
two separate orders (ORDER_O, ORDER_I)
two requests (REQ_O, REQ_I)
order if request and position not achieved (type 3). The pre-actuator reacts on a pulse, pointless to maintain an order
6
bistable actuator
two separate orders (ORDER_O, ORDER_I)
two requests (REQ_O, REQ_I)
order maintained until reverse request and in position (type 4)
7
bistable actuator
two separate orders (ORDER_O, ORDER_I)
two requests (REQ_O, REQ_I)
order if request and order clash in position, unlocking on reverse request or loss of position (type 5)
8
multistable actuator with two separate orders (ORDER_O, ORDER_I)
two requests (REQ_O, REQ_I)
idem 4
9
multistable actuator
two requests (REQ_O, REQ_I)
idem 6
10
multistable actuator
two requests (REQ_O, REQ_I) and absence of request
idem 5
Intermediate stop permitted (absence of request)
11
multistable actuator
two requests (REQ_O, REQ_I) and absence of request
idem 7
Intermediate stop permitted (absence of request)
NOTE: CONFIG = 8 to 11 : intermediate stop possible through the default selected in RST_ORD.