app_weld_set_interface_eip_m2r_other

Definition
DRFLEx.h within class CDRFLEx, public section

bool app_weld_set_interface_eip_m2r_other(CONFIG_DIGITAL_WELDING_INTERFACE_OTHER pConfigdigitalweldinginterfacemonitoring)
{
    return _app_weld_set_interface_eip_m2r_other(_rbtCtrl, pConfigdigitalweldinginterfacemonitoring);
};

Features

This function configures the communication interface for using a welder that supports EtherNet/IP communication. It sets up the interface for additional or custom data signals that go from the welder to the robot controller (M2R), beyond the standard monitoring or process data.

You can define supplementary functions or signal mappings required for specialized welding control or feedback.

This configuration handles communication data sent from the welder to the robot, and the specific mapping should follow the signal datasheet provided by the welding equipment manufacturer.

Note

To properly use the EtherNet/IP-based welding interface, all 8 interface setting commands must be configured:

Arguments

Argument Name	Data Type	Default Value	Description
pConfigdigitalweldinginterfacemonitoring	CONFIG_DIGITAL_WELDING_INTERFACE_OTHER		Digital welding interface other data configuration structure (M2R: Welder → Robot)

Each field within the structure defines a communication mapping parameter as shown below:

Field Name	Data Type	Description
_bEnable	unsigned char	Enable flag (0: Disabled, 1: Enabled)
_nDataType	unsigned char	Data type (0: On/Off, 1: Selection, 2: Value)
_nPositionalNumber	unsigned char	Data precision (0: 1, 1: 0.1, 2: 0.001)
_fMinData	float	Minimum data value
_fMaxData	float	Maximum data value
_nByteOffset	unsigned char	Communication data byte offset (1-255)
_nBitOffset	unsigned char	Communication data bit offset (1-255)
_nComnDataType	unsigned char	Communication data size 0: 1-bit(Disable Low) 1: 1-bit(Disable High) 2: 2-bit 3: 4-bit 4: 8-bit 5: 15-bit 6: 16-bit(short) 7: 32-bit(int)
_nMaxDigitSize	unsigned char	Effective data size (bit)
_tOption1 … _tOption10	CONFIG_DIGITAL_WELDING_IF_MAPPING_DATA	Mapping of other data items 1-10

Return

Value	Description
0	Error
1	Success

Example

// Create a structure for defining EtherNet/IP M2R "Other" signals and assign values
CONFIG_DIGITAL_WELDING_INTERFACE_OTHER otherData;
memset(&otherData, 0x00, sizeof(otherData));

otherData._tOption1._bEnable = 1;    // Enable other data interface
otherData._tOption1._nDataType = 2;    // Value type
otherData._tOption1._nPositionalNumber = 1;    // Decimal precision
otherData._tOption1._fMinData = 0.0f;
otherData._tOption1._fMaxData = 100.0f;
otherData._tOption1._nByteOffset = 15;   // Byte position
otherData._tOption1._nBitOffset = 0;    // Bit start position
otherData._tOption1._nComnDataType = 4;   // 8Bit
otherData._tOption1._nMaxDigitSize = 8;    // Effective data size (bit)

// Map the remaining user-defined signals (_tOption2 ~ _tOption10) to the following bytes
CONFIG_DIGITAL_WELDING_IF_MAPPING_DATA* options[] = {
    &otherData._tOption2, &otherData._tOption3, &otherData._tOption4,
    &otherData._tOption5, &otherData._tOption6, &otherData._tOption7,
    &otherData._tOption8, &otherData._tOption9, &otherData._tOption10
};
for (int i = 0; i < 9; i++) {
    *options[i] = otherData._tOption1;
    options[i]->_nByteOffset = 16 + i;   // Bytes 16 to 24
}

// Apply configuration
bool result = Drfl.app_weld_set_interface_eip_m2r_other(otherData);

This example demonstrates how to configure custom EtherNet/IP feedback channels from the welder to the robot controller, allowing additional analog or status signals beyond the standard monitoring set. These fields are typically used for vendor-specific extensions such as custom welding quality metrics or torch diagnostics.