#define _7TACOM_IO_WRITE_ERROR_LEN  0x4501
//Cause: Driver failed to write expected number of characters to COM port or Modem
//Action: Check modem setup and cables.

#define _7TACOM_IO_READ_TIMEOUT  0x4502
//Cause: Driver failed to read a reply from  expected number of characters to COM port or Modem
//Action: Check modem setup and cables. If the timeouts are consistent then there might me mismatch between the PlantID specified in 
//        IGSS and the PlantID in the substation. These ID's *must* match otherwise the substation dosn't answer requests from IGSS and thus
//        consistent timeouts will occure.

#define _7TACOM_IO_BCC_ERROR 0x4503
//Cause: The driver received telegram from the RTU with an incorrect checksum.
//Action: Check modem and communication settings. Check quality of line and make sure RTU is running correctly.

#define _7TACOM_IO_INCORRECT_FRAMING 0x4504
//Cause: The driver received telegram from the RTU with incorrect framing.
//Action: Telegrams are supposed to start with STX and end with CR and contain one '#' sign before the checksum.
//        Check modem and communication settings. Check quality of line and make sure RTU is running correctly.

#define _7TACOM_TOO_MANY_DATA_REQUESTED_PICURE 0x4505
//Cause: The driver was requested to read more data from a picture than the picture actually contains
//Action: Check RTU picture definition and make sure all requested picture values are present in station.
//        The sub code of this error contains the picture number (e.g. 1: Picture 1, 2: Picture 2 etc.)

#define _7TACOM_INCORRECT_RESPONCE_FORMAT_PICTURE 0x4506
//Cause: The driver was received a WGS (Picture) response telegram with too few values.
//Action: Check RTU picture definition and make sure all requested picture values are present in station.
//        The sub code of this error contains the picture number (e.g. 1: Picture 1, 2: Picture 2 etc.)

#define _7TACOM_ERROR_INVALID_HANDLE 0x4507
//Cause: The communication handle (modem or serial port) used by the driver was invalid
//Action: Check that modem connection is established and stabil.

#define _7TACOM_UNSUPPORTED_READ_FUNCTION 0x4508
//Cause: The driver is requested to read data from an unsupported data type.
//Action: Please verify that all addresses are valid.
//        The number of the data type is in the sub error code.
//        Supported data types are: 0: PICTURE, 1: REPORT, 2: SETPOINTS, 3: HISTORY

#define _7TACOM_UNSUPPORTED_WRITE_FUNCTION 0x4509
//Cause: The driver is requested to write data to an unsupported data type.
//Action: Please verify that all addresses are valid.
//        The number of the data type is in the sub error code.
//        Supported data types are: 3: SETPOINTS, 5: MACHINE CONTROL

#define _7TACOM_INCORRECT_RESPONCE_FORMAT_REPORT 0x450A
//Cause: The driver was received a WGD (Report) response telegram with an unexpected number of values.
//Action: Reports are supposed to have exactly 5 values for each report element.
//        Check substation report definition.
//        The sub code of this error contains the actual number of values received

#define _7TACOM_TOO_MANY_DATA_REQUESTED_REPORT 0x450B
//Cause: The driver was requested to read more data from a report than the report actually contains
//Action: Check RTU report definition and make sure all requested report values are present in station.
//        The sub code of this error contains the index of the requested value in the report.

#define _7TACOM_NDA_REPLY 0x450C
//Cause: The driver received a NDA (No Data) reply from the substation. This indicated that the requested data is not 
//       present in the substation. E.g. User tried to read data from a non existing picture or data from a non extisting report.
//        The sub error code indicates the type of data: 0: PICTURE, 1: REPORT, 2: SETPOINTS, 3: HISTORY.
//Action: Check substation definitions and make sure all requested values are present in the station.

#define _7TACOM_SCE_REPLY 0x450D
//Cause: The driver received a SCE (Error in telegram) reply from the substation. This indicated that the request sent by the driver
//       was not understood by the substation. 
//        The sub error code indicates the type of data: 0: PICTURE, 1: REPORT, 2: SETPOINTS, 3: HISTORY.
//Action: Contact 7T technical support.

#define _7TACOM_TOO_MAY_SETPOINTS 0x450E
//Cause: The driver received a telegram reply from a substation with more than 128 indexed setpoints. 
//        The driver only supports up to 128 setpoints.
//Action: Contact 7T technical support.

#define _7TACOM_SETPOINT_INDEX_TOO_HIGH 0x450F
//Cause: The driver was requested to write a setpoint with too high index. Index must be less than 128.
//       The sub error code contains the rejected index for reference.
//Action: Please check addresses of setpoints.

#define _7TACOM_SETPOINT_TYPE_UNKNOWN 0x4510
//Cause: The driver was requested to write a setpoint to an index with unknown type or text type.
//       The sub error code contains the rejected index for reference.
//Action: Please verify that all used indexes are defined in the substation and that no indexes of text type are used.

#define _7TACOM_TOO_FEW_HISTORY_VALUES 0x4511
//Cause: The driver received a history telegram with too few values in a history record.
//Action: Please verify that history channels are defined and active in the substation.

#define _7TACOM_INVALID_HISTORY_TIMESTAMP 0x4512
//Cause: The driver received a history telegram with an invalid time stamp.
//Action: Please verify that substation is functioning correctly and that the real time clock in the substation is correct.

#define _7TACOM_OUT_OF_HISTORY_BUFFERS 0x4513
//Cause: The driver was temporary out of buffers while fetching historical data from substation.
//Action: Increase number og buffers for the driver in System Configuration application (Advanced Pane).

#define _7TACOM_INVALID_NUM_ALARM_PARAMETERS 0x4514
//Cause: The driver received an alarm telegram (ALR) with an incorrect number of paramters. There should always be exactly 15 parameters.
//       The subcode contains the actual number of parameters.
//Action: Check substation configuration.

#define _7TACOM_INVALID_ALARM_TIMESTAMP 0x4515
//Cause: The driver received an alarm telegram with an invalid time stamp.
//Action: Please verify that substation is functioning correctly and that the real time clock in the substation is correct.

#define _7TACOM_OUT_OF_ALARM_BUFFERS 0x4516
//Cause: The driver was temporary out of buffers while fetching alarm data from substation.
//Action: Increase number og buffers for the driver in System Configuration application (Advanced Pane).

#define _7TACOM_IO_INVALID_PORT_HANDLE 0x4517
//Cause: The modem or serial port handle was reset during communication.
//Action: Retry the opeation at a later time and check that modem connection is stabil and phone lines are OK.

#define _7TACOM_INVALID_MACHINE_CONTROL_COMMAND 0x4518
//Cause: The driver was requested to send a machine control command with an invalid content.
//       Supportted commands are: 0 (F-command), 1 (N-command), 2 (B-command) and 3 (M-command)
//       Sending any other value than 0,1,2 or 3 will give this error.
//       For reference the subcode contains the code of the command the driver was requested to send.
//Action: Review the configuration of the commands that are sent as Machine Control Commands.



#define _7TACOM_RX_DLE_ACK_FAILED      0x3c01
//Cause: Expected two byte DLC ACK sequence not received
//Action:


#define _7TACOM_RX_DLE_ETX_FAILED      0x3c03
//Cause: Expected two byte DLC ETX sequence not received
//Action:

#define _7TACOM_RX_WRONG_LEN           0x3c04
//Cause: Received less than two bytes
//Action:

#define _7TACOM_DB_NICHT_VORHANDEN     0x3c05
//Cause: Single byte received with invalid value 0x14
//Action:

#define _7TACOM_GET_DB_ADDR_LENGTH_ERROR   0x3c06
//Cause: First response to a write command had invalid length
//Action:

#define _7TACOM_GET_DB_ADDR_FAILED     0x3c07
//Cause: First response to a write command contained wrong DB in byte 6
//Action:


#define _7TACOM_SYNC_ERR               0x3c08
//Cause: Byte 4 in received message contain invalid DB value
//Action:


#define _7TACOM_COM_WRITE_ERROR        0x3c09
//Cause: Failed to write to COM port
//Action: Check windows errorcode in subcode field
//Subcode:WINH.H

#define _7TACOM_COM_READ_ERROR         0x3c0a
//Cause: Failed to receive from COM port
//Action: Check windows errorcode in subcode field
//Subcode:WINH.H

#define _7TACOM_COM_CLEAR_ERROR        0x3c0b
//Cause: Failed to clear COM port
//Action: Check windows errorcode in subcode field
//Subcode:WINH.H

#define _7TACOM_UNKNOWN_OPCODE        0x3c0c
//Cause: 
//Action:
//Subcode:WINH.H

#define _7TACOM_NOSTXSOH       0x3c0d
//Cause: 
//Action: