Boa tarde. Estou enfrentando um problema com a comunicação entre o CLP e o Elipse. O Log do driver é este:
06/01/2020 13:40:02.724 (2C88) DRIVER Driver name: Driver Modicon Modbus v3.1.29 (IOKitLib v2.0.54)
06/01/2020 13:40:02.724 (2C88) DRIVER IOKitLib version 2.0.54 of Feb 22 2016 10:47:34
06/01/2020 13:40:02.724 (2C88) DEBUG CModbusHost CREATED
06/01/2020 13:40:02.724 (2C88) DRIVER Selected ASCII mode!
06/01/2020 13:40:02.724 (2C88) DRIVER User Types file compiled successfully!
06/01/2020 13:40:02.724 (2C88) DRIVER drvStartComm(0,0,0,0)
06/01/2020 13:40:02.724 (2C88) DRIVER Current configuration (76 parameters):
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Ethernet.BackupIP = ‘’
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Ethernet.BackupIP2 = ‘’
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Ethernet.BackupIP3 = ‘’
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Ethernet.ListenIP = ‘’
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Ethernet.MainIP = ‘’
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Ethernet.MainPort = 502
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Ethernet.PingTimeoutMs = 4000
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Ethernet.PingTries = 1
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Ethernet.Transport = ‘TCP’
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.GiveUpTries = 1
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Log.Enable = 1
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Log.Filename = ‘C:\eeLogs\Modbus_%DATE%.log’
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.RAS.ATCommand = ‘’
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.RecoverEnable = 1
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.RecoverPeriodSec = 20
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Serial.Baudrate = 9600
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Serial.DataBits = 7
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Serial.Parity = 2
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Serial.Port = 5
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Serial.SupressEcho = 1
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.TAPI.ModemID = 4294967295
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.TAPI.PhoneNumber = ‘’
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.TimeoutMs = 300
06/01/2020 13:40:02.724 (2C88) DRIVER - IO.Type = ‘Serial’
06/01/2020 13:40:02.724 (2C88) DRIVER - ModiconModbus.ConfigFile = '[Functions]
Function: 1
Read: 3
Write: 16
Type: word
Size: 2
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
Function: 2
Read: 3
Write: 16
Type: dword
Size: 4
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
Function: 3
Read: 3
Write: 16
Type: int16
Size: 2
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
Function: 4
Read: 3
Write: 16
Type: int32
Size: 4
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
Function: 5
Read: 3
Write: 16
Type: float
Size: 4
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
Function: 6
Read: 1
Write: 15
Type: bit
Size: 0
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
Function: 7
Read: 2
Write: 0
Type: bit
Size: 0
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
[End]
’
06/01/2020 13:40:02.724 (2C88) DRIVER - ModiconModbus.DefaultSlaveAddress = 1
06/01/2020 13:40:02.724 (2C88) DRIVER - ModiconModbus.EnableGenSOERegGrouping = 1
06/01/2020 13:40:02.725 (2C88) DRIVER - ModiconModbus.MaxPDUSize = 253
06/01/2020 13:40:02.725 (2C88) DRIVER - ModiconModbus.ModbusMode = 1
06/01/2020 13:40:02.725 (2C88) DRIVER - ModiconModbus.UserTypesConfigFile = '// USER DEFINED TYPES SAMPLE CONFIG FILE
// The samples below illustrate how to create user defined structs, using the driver built-in types (note the built-in
// types must be entered with the same keywords used in the Data combobox of the operations).
// The new user types can afterwards be used in the same way as the other built-in types in the Data combobox.
/* Sample types entirely commented by default
struct TYPE1 // TYPE 1 - declares struct with elements with no name, and no timestamp
{
int16;
word;
dword;
int32;
}
// TYPE2 declares named elements, and includes a timestamp of GenTime type. The named elements can then be
// loaded to the user application using E3 Tag Browser.
// NOTE: the timestamp value will not be returned on a block element, but rather returned on the timestamp property
// of the block type tag. The order in which the timestamp appears within the structure is related to the order
// in which this field appears within the data area of the received protocol frame (usually the first field).
struct TYPE2
{
timestamp = GenTime; // this time field will be returned in the block’s timestamp field
GenTime timeField; // this time field will be returned in the block’s first element
dword dwordField;
}
struct TYPE3 // this type has a timestamp of type UTC32 and some named elements
{
DefaultAddress = 0x101;
timestamp = UTC32;
float Va;
float Vb;
float Vc;
float Ia;
float Ib;
float Ic;
}
*/’
06/01/2020 13:40:02.725 (2C88) DRIVER - ModiconModbus.WaitSilenceOnError = 1
06/01/2020 13:40:02.725 (2C88) DRIVER - 45 parameters with value = 0 were omitted
06/01/2020 13:40:02.725 (0AE0) IOKIT INITIALIZING…
06/01/2020 13:40:02.725 (0AE0) IOKIT INITIALIZED!
06/01/2020 13:40:02.725 (0AE0) IOKIT Request handler enabled
06/01/2020 13:40:02.725 (0AE0) IOKIT CONNECTING…
06/01/2020 13:40:02.725 (0AE0) SERIAL Opening COM5:9600,7,EVEN,1 …
06/01/2020 13:40:02.725 (2020) TAG Tag(1.1.0.4096).Validate = SUCCESS (type=10;flags=9)
06/01/2020 13:40:02.730 (0AE0) SERIAL Port opened!
06/01/2020 13:40:02.730 (0AE0) IOKIT CONNECTED!
06/01/2020 13:40:02.736 (0AE0) IO TX: :010310000001EB[0D][0A]
06/01/2020 13:40:02.776 (0AE0) IO RX: ERROR receiving echo for byte 6 of 17 (received ‘30’ instead of ‘31’)
06/01/2020 13:40:02.776 (0AE0) SERIAL Restarting COM port due to transmission error (80004005) (try 1 of 3)
06/01/2020 13:40:02.878 (0AE0) SERIAL Port closed! (se repete…)
Qual poderia ser o problema?
