EtherCAT variant handling
This library is used to influence the arrangement of the slaves connected to an EtherCAT network.
TB_ECT_Manager
TB_ECT_Manager
This block makes it possible to influence the arrangement of the slaves when the field bus is started. Slaves can also be declared as optional. Thus, e.g. a maximum number of slaves can be configured, but these can be adjusted and rearranged by the software at runtime. In addition, there are other settings, which are described below.
Eingänge
| Name: | Type: | Description: |
|---|---|---|
| x_Execute | BOOL | A rising edge starts the execution of the block. The procedure described in the description is followed. |
| _Options | ECT_OPTIONS_STRCT | Options for the behavior of the block at startup can
be defined here: x_StartMotionAfter: TRUE, if the block is to start Motion Control after the fieldbus start x_Set_EoE: Set EoE settings for the nodes x_DifferBetwBM5AndBM3: If TRUE, then with a BM5000 axis with the product code of a BM3300 worked. |
Ausgänge
| Name: | Type: | Description: |
|---|---|---|
| x_Busy | BOOL | Indicates that the function block is being processed. |
| x_FieldbusBoot_Done | BOOL | TRUE if the fieldbus has been started successfully. x_Busy then goes to FALSE. |
| x_StartMCCore_Done | BOOL | Motion Control started successfully. |
| x_Error | BOOL | Error on the block. |
| _ErrorInfo | ERR_INFO_STRCT | Structure with error details:
_FBs_ErrList: Displays
the error number associated with the internal function
block. Error details can then be viewed in the
corresponding library. x_MandatorySlaveMissing: TRUE if a mandatory slave is missing on the fieldbus dw_MandSlaveMissProdCode: Indicates which mandatory slave is missing i_MandSlaveAtNodeMissing: Displays the number of the node that is missing dw_ProductCodeNotValid: Displays the product code which is not valid is or does not match the configuration. x_SlaveIsMissing: TRUE if a slave is missing x_MoreActSlaveThanSetInCfg: TRUE if more slaves of a configured product code were found on the fieldbus than originally configured. |
Ein-/Ausgänge
| Name: | Type: | Description: |
|---|---|---|
| _ECT_SetConfig | ECT_SETCFG_ARRAY | With this structure, the block is given the required
fieldbus configuration. Each array index represents a
node (index 1 = node 1, ...). The block is thus used
to transmit the fieldbus configuration from ProMaster. The following setting options are available for each node: dw_ProductCode: Product code (Info from ProMaster can be viewed) dw_IPAddress: IP-Address dw_SubNetMask: Subnet mask x_Optional: Optional = TRUE ui_EbusGroupNr: Group number of the IO terminal block |
| _ECT_ActConfig | ECT_ACTCFG_ARRAY | In this structure, the information of the slaves found on startup on the fieldbus is collected. This structure is only for display / diagnosis. Again, each index corresponds to a node on the fieldbus. |
| _Base | ECM_PLC_MA_BMSTRUCT | DPRAM interface to the EtherCAT. For PCC =% MB3.2016384 |
TB_ECT_Manager
TB_ECT_Manager
This block makes it possible to influence the arrangement of the slaves when the field bus is started. Slaves can also be declared as optional. Thus, e.g. a maximum number of slaves can be configured, but these can be adjusted and rearranged by the software at runtime. In addition, there are other settings, which are described below.
Eingänge
| Name: | Type: | Description: |
|---|---|---|
| x_Execute | BOOL | A rising edge starts the execution of the block. The procedure described in the description is followed. |
| _Options | ECT_OPTIONS_STRCT | Options for the behavior of the block at startup can
be defined here: x_StartMotionAfter: TRUE, if the block is to start Motion Control after the fieldbus start x_Set_EoE: Set EoE settings for the nodes x_DifferBetwBM5AndBM3: If TRUE, then with a BM5000 axis with the product code of a BM3300 worked. |
Ausgänge
| Name: | Type: | Description: |
|---|---|---|
| x_Busy | BOOL | Indicates that the function block is being processed. |
| x_FieldbusBoot_Done | BOOL | TRUE if the fieldbus has been started successfully. x_Busy then goes to FALSE. |
| x_StartMCCore_Done | BOOL | Motion Control started successfully. |
| x_Error | BOOL | Error on the block. |
| _ErrorInfo | ERR_INFO_STRCT | Structure with error details:
_FBs_ErrList: Displays
the error number associated with the internal function
block. Error details can then be viewed in the
corresponding library. x_MandatorySlaveMissing: TRUE if a mandatory slave is missing on the fieldbus dw_MandSlaveMissProdCode: Indicates which mandatory slave is missing i_MandSlaveAtNodeMissing: Displays the number of the node that is missing dw_ProductCodeNotValid: Displays the product code which is not valid is or does not match the configuration. x_SlaveIsMissing: TRUE if a slave is missing x_MoreActSlaveThanSetInCfg: TRUE if more slaves of a configured product code were found on the fieldbus than originally configured. |
Ein-/Ausgänge
| Name: | Type: | Description: |
|---|---|---|
| _ECT_SetConfig | ECT_SETCFG_ARRAY | With this structure, the block is given the required
fieldbus configuration. Each array index represents a
node (index 1 = node 1, ...). The block is thus used
to transmit the fieldbus configuration from ProMaster. The following setting options are available for each node: dw_ProductCode: Product code (Info from ProMaster can be viewed) dw_IPAddress: IP-Address dw_SubNetMask: Subnet mask x_Optional: Optional = TRUE ui_EbusGroupNr: Group number of the IO terminal block |
| _ECT_ActConfig | ECT_ACTCFG_ARRAY | In this structure, the information of the slaves found on startup on the fieldbus is collected. This structure is only for display / diagnosis. Again, each index corresponds to a node on the fieldbus. |
| _Base | ECM_PLC_MA_BMSTRUCT | DPRAM interface to the EtherCAT. For PCC =% MB3.2016384 |
