CLP FX3GE Mitsubishi x SCADA

#1

Boa tarde pessoal!

Estou tentando fazer minha aplicação SCADA comunicar com uma CPU série FX modelo FX3GE-24M, mas não estou conseguindo. O endereçamento segue como as demais séries FX que já trabalhei, porém, sem sucesso.

Já baixei o driver atualizado, mas mesmo assim nada. Esto usando comunicacao Ethernet porta padrão do SCADA (44818).

Segue o LOG…

07/10/2014 16:54:54.824 (07A8) [DRIVER] Driver name: Elipse Driver Mitsubishi MelsecFX v2.05 Build 2
07/10/2014 16:54:54.824 (07A8) [DRIVER] IOKIT.DLL version 1.15 of Aug 24 2009 16:43:53 (Win32)
07/10/2014 16:54:54.824 (07A8) [DRIVER] IOKitLib version 1.15 of Aug 24 2009 16:43:50 (Win32)
07/10/2014 16:54:54.824 (07A8) [DRIVER] drvStartComm(0,0,0,0)
07/10/2014 16:54:54.824 (07A8) [DRIVER] Current configuration (68 parameters):
07/10/2014 16:54:54.824 (07A8) [DRIVER] - IO.Ethernet.BackupIP = ‘’
07/10/2014 16:54:54.824 (07A8) [DRIVER] - IO.Ethernet.ListenIP = ‘192.168.1.40’
07/10/2014 16:54:54.824 (07A8) [DRIVER] - IO.Ethernet.ListenPort = 44818
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Ethernet.MainIP = ‘192.168.1.250’
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Ethernet.MainPort = 44818
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Ethernet.PingEnable = 1
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Ethernet.PingTimeoutMs = 4000
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Ethernet.PingTries = 1
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Ethernet.Transport = ‘UDP’
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.GiveUpTries = 1
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Log.Enable = 1
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Log.Filename = ‘D:\Melsec.log’
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.RAS.ATCommand = ‘’
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.RecoverEnable = 1
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.RecoverPeriodSec = 20
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Serial.Baudrate = 19200
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Serial.DataBits = 8
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Serial.Port = 1
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.TAPI.PhoneNumber = ‘’
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.TimeoutMs = 1000
07/10/2014 16:54:54.825 (07A8) [DRIVER] - IO.Type = ‘Ethernet’
07/10/2014 16:54:54.825 (07A8) [DRIVER] - ModiconModbus.ConfigFile = '[Functions]
Function: 1
Read: 3
Write: 16
Type: 6
Size: 2
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
Function: 2
Read: 1
Write: 5
Type: 0
Size: 0
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
Function: 3
Read: 2
Write: 15
Type: 0
Size: 0
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
Function: 4
Read: 4
Write: 0
Type: 6
Size: 2
FrameOrder: 0
ByteOrder: 0
WordOrder: 0
DWordOrder: 0
[End]
’
07/10/2014 16:54:54.825 (07A8) [DRIVER] - ModiconModbus.DefaultSlaveAddress = 1
07/10/2014 16:54:54.825 (07A8) [DRIVER] - ModiconModbus.ModbusMode = 2
07/10/2014 16:54:54.825 (07A8) [DRIVER] - ModiconModbus.UseDefaultSlaveAddress = 1
07/10/2014 16:54:54.825 (07A8) [DRIVER] - UniTelway.DefaultSlaveAddress = 254
07/10/2014 16:54:54.826 (07A8) [DRIVER] - UniTelway.Timeout = 1000
07/10/2014 16:54:54.826 (07A8) [DRIVER] - 41 parameters with value = 0 were omitted
07/10/2014 16:54:54.826 (15B8) [IOKIT] INITIALIZING…
07/10/2014 16:54:54.827 (15B8) [SOCKET] Winsock initialized: version=2.2, highVersion=2.2
07/10/2014 16:54:54.827 (15B8) [IOKIT] INITIALIZED!
07/10/2014 16:54:54.827 (15B8) [IOKIT] Request handler enabled
07/10/2014 16:54:54.827 (15B8) [IOKIT] CONNECTING…
07/10/2014 16:54:54.829 (15B8) [SOCKET] PING ‘192.168.1.250’ (IP 192.168.1.250) SUCCEEDED (1 msec)
07/10/2014 16:54:54.830 (15B8) [SOCKET] connecting socket to ‘192.168.1.250’ on port 44818…
07/10/2014 16:54:54.832 (15B8) [SOCKET] socket connected to ‘192.168.1.250’ on port 44818 (local port 55884)!
07/10/2014 16:54:54.832 (15B8) [IOKIT] CONNECTED!
07/10/2014 16:54:54.838 (07A8) [DRIVER] Tag(17.100.0.0).Validate = SUCCESS (type=10;flags=0)
07/10/2014 16:54:54.838 (15B8) TX: 05
07/10/2014 16:54:55.840 (15B8) RX: TIMEOUT
07/10/2014 16:54:55.841 (07A8) [DRIVER] <== (1.003) Tag(17.100.0.0).ReadValue = ERROR (hr=80004005)
07/10/2014 16:54:55.851 (07A8) [DRIVER] drvStopComm(0,0,0,0)
07/10/2014 16:54:55.852 (07A8) [IOKIT] Stopping physical layer thread…
07/10/2014 16:54:55.852 (07A8) [IOKIT] Waiting for termination of physical layer thread…
07/10/2014 16:54:55.852 (15B8) [SOCKET] socket closed
07/10/2014 16:54:55.852 (15B8) [IOKIT] TERMINATING…
07/10/2014 16:54:55.852 (15B8) [IOKIT] TERMINATED! (1 bytes sent, 0 bytes received)
07/10/2014 16:54:55.852 (15B8) [IOKIT] Request handler disabled
07/10/2014 16:54:55.853 (07A8) [IOKIT] Physical layer thread stopped!

Alguém já trabalhou com essa série e poderia me auxiliar?
Desde já agradeço a atenção de todos.

#2

Fernando,

Atualmente o driver Melsec-FX não suporta comunicação através da interface Ethernet. O protocolo implementado no driver funciona apenas para comunicação serial. Nesse caso, a única alternativa disponível no momento seria o Driver Mitsubishi MX, que depende da instalação e configuração prévia de um componente da Mitsubishi chamado “MX Component”.

#3

Boa tarde.

Alguma novidade sobre esse assunto? Estou tendo o mesmo problema com o Melsec-FX, não comunica via Ethernet.

#4

Nenhuma novidade Alessandro. O driver Melsec-FX só funciona via serial.