E_MBUS_Error
Error messages.
TYPE E_MBUS_Error :
(
eMBUS_no_error := 0,
eMBUS_busy := 1,
eMBUS_Disabled := 3,
eMBUS_FBKL6781_Disabled := 4,
eMBUSERROR_CIField_wrong_72hex_expected := 101,
eMBUSERROR_no_data_received := 102,
eMBUSERROR_error_checksum := 103,
eMBUSERROR_error_in_head_data := 104,
eMBUSERROR_usiAddress_over_250 := 105,
eMBUSERROR_send_error := 106,
eMBUSERROR_received_address_wrong := 108,
eMBUSERROR_cMBUS_MaxCom_below_1 := 109,
eMBUSERROR_iComId_over_cMBUS_MaxCom := 110,
eMBUSERROR_manufacturer_sign_wrong := 111,
eMBUSERROR_baudrate_wrong := 112,
eMBUSERROR_ReceiveBufferFull := 113,
eMBUSERROR_E5hex_no_received := 114,
eMBUSERROR_no_stop_character := 115,
eMBUSERROR_length_wrong := 116,
eMBUSERROR_wrong_terminal := 117,
eMBUSERROR_Terminal_is_not_initialized := 118,
eMBUSERROR_stSecAdr_udiIdNumber_wrong := 119,
eMBUSERROR_missing_parts_telegram := 120,
eMBUSERROR_no_stop_character_received := 121,
eMBUSERROR_too_many_characters := 122,
eMBUSERROR_TimeOut_FB_KL6781 := 123,
eMBUSERROR_TimeOut_MeterFB := 124,
eMBUSERROR_COM_PARAMETERCHANGED := 201,
eMBUSERROR_COM_TXBUFFOVERRUN := 202,
eMBUSERROR_COM_STRINGOVERRUN := 210,
eMBUSERROR_COM_ZEROCHARINVALID := 211,
eMBUSERROR_COM_INVALIDPOINTER := 220,
eMBUSERROR_COM_INVALIDRXPOINTER := 221,
eMBUSERROR_COM_INVALIDRXLENGTH := 222,
eMBUSERROR_COM_DATASIZEOVERRUN := 223,
eMBUSERROR_COM_INVALIDBAUDRATE := 16#1001,
eMBUSERROR_COM_INVALIDNUMDATABITS := 16#1002,
eMBUSERROR_COM_INVALIDNUMSTOPBITS := 16#1003,
eMBUSERROR_COM_INVALIDPARITY := 16#1004,
eMBUSERROR_COM_INVALIDHANDSHAKE := 16#1005,
eMBUSERROR_COM_INVALIDNUMREGISTERS := 16#1006,
eMBUSERROR_COM_INVALIDREGISTER := 16#1007,
eMBUSERROR_COM_TIMEOUT := 16#1008
)
END_TYPE
Name | Description |
|---|---|
eMBUS_no_error | No error at the function block. The function block does not currently query a meter. |
eMBUS_busy | The function block is querying a meter. |
eMBUS_Disabled | The function block is disabled. |
eMBUS_FBKL6781_Disabled | The function block FB_MBUS_KL6781() is disabled. |
eMBUSERROR_CIField_wrong_72hex_expected | The 7th byte in the answer telegram contains the CI field. In this byte the hexadecimal number 72 is expected. It stands for variable data structure, low byte is sent first. Only this data structure is supported. |
eMBUSERROR_no_data_received | No data was received. |
eMBUSERROR_error_checksum | The answer telegram includes a checksum (sum of all bytes from byte 5). The received checksum does not match the calculated checksum. This happens if the protocol was not received cleanly (e.g. in the event of interference on the cable or if the cable is too long). |
eMBUSERROR_error_in_head_data | The first 4 bytes are not included in the checksum. These 4 bytes are monitored separately. |
eMBUSERROR_usiAddress_over_250 | Addresses higher than 250 are not permitted. The input usiAddress of the meter block has been assigned a value above 250 (exception: address 254. This address can be used if only one meter is connected). |
eMBUSERROR_send_error | Error message for error during sending. |
eMBUSERROR_received_address_wrong | Received address does not match the sent address. |
eMBUSERROR_cMBUS_MaxCom_below_1 | Reserve |
eMBUSERROR_iComId_over_cMBUS_MaxCom | Reserve |
eMBUSERROR_manufacturer_sign_wrong | The answer telegram includes a manufacturer sign. This sign is allocated to the meter blocks. This message appears if the received manufacturer sign does not match the function block used. |
eMBUSERROR_baudrate_wrong | Input eBaudrate of the function block was assigned invalid values. Only E_MBUS_Baudrate are allowed. |
eMBUSERROR_ReceiveBufferFull | The receive buffer of the serial interface is full. This may happen with long telegrams and/or long cycle times. The PLC is unable to read the data quick enough from the receive buffer, resulting in data loss. The situation may be resolved by reducing the cycle time. |
eMBUSERROR_E5hex_no_received | No single character E5 hexadecimal was received after initialization of the meter. |
eMBUSERROR_no_stop_character | No end character in the data array. |
eMBUSERROR_length_wrong | Number of received characters <> the length field. |
eMBUSERROR_wrong_terminal | Incorrect terminal connected. |
eMBUSERROR_Terminal_is_not_initialized | The terminal is not initialized. This message usually means that there is no connection to the terminal. Terminal linked to the variables in the System Manager? Terminal plugged in incorrectly? Clean all, rebuild all and read again in the System Manager? |
eMBUSERROR_stSecAdr_udiIdNumber_wrong | The input variable stSecAdr.udiIdNumber is not assigned |
eMBUSERROR_missing_parts_telegram | Not all telegram values were received. |
eMBUSERROR_no_stop_character_received | No stop character was received (16hex). |
eMBUSERROR_too_many_characters | Too many characters were received. |
eMBUSERROR_TimeOut_FB_KL6781 | Timeout FB_KL6781. |
eMBUSERROR_TimeOut_MeterFB | Meter block timeout. |
eMBUSERROR_COM_PARAMETERCHANGED | Input parameters have changed during reception. |
eMBUSERROR_COM_TXBUFFOVERRUN | String > transfer buffer. |
eMBUSERROR_COM_STRINGOVERRUN | End of the string. |
eMBUSERROR_COM_ZEROCHARINVALID | String may not contain any zero characters. |
eMBUSERROR_COM_INVALIDPOINTER | Invalid data pointer, e.g. zero. |
eMBUSERROR_COM_INVALIDRXPOINTER | Invalid data pointer for ReceiveData. |
eMBUSERROR_COM_INVALIDRXLENGTH | Invalid length for ReceiveData e.g. zero. |
eMBUSERROR_COM_DATASIZEOVERRUN | End of the data block. |
eMBUSERROR_COM_INVALIDBAUDRATE | Invalid baud rate. |
eMBUSERROR_COM_INVALIDNUMDATABITS | Invalid data bits. |
eMBUSERROR_COM_INVALIDNUMSTOPBITS | Invalid stop bits. |
eMBUSERROR_COM_INVALIDPARITY: | Invalid parity. |
eMBUSERROR_COM_INVALIDHANDSHAKE | Invalid handshake. |
eMBUSERROR_COM_INVALIDNUMREGISTERS | Invalid num register. |
eMBUSERROR_COM_INVALIDREGISTER | Invalid register. |
eMBUSERROR_COM_TIMEOUT: COM | COM timeout. |
Requirements
Development Environment | PLC library to include |
|---|---|
TwinCAT from v3.1.4020.14 | Tc2_MBus from 3.3.5.0 |