AdvancedHMI Software

General Category => Support Questions => Topic started by: trung.bui on February 25, 2019, 10:53:55 PM

Title: EthernetIPforCLX driver: Communication Fault code
Post by: trung.bui on February 25, 2019, 10:53:55 PM

Hi,
When i read data from PLC, some time it cannot read and throw the exception (cannot communicate w PLC) but it's not frequent, only 1 or 2% the number of command (all are same command)
the error code is -22, 106, 34, 0.
How can i diagnose  the problem. Is this really because of the network?
Thank you so much!

Code: [Select]

2019-02-25 21:10:04;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:10:04;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 21:11:56;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:12:06;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:31:18;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:36:08;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:36:29;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:36:33;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:37:57;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:38:13;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 21:40:38;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:41:04;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:44:28;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 21:44:28;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:48:33;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 21:48:35;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:53:11;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 21:53:13;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:53:22;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 21:53:22;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:56:48;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:56:48;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 21:56:52;Id:-22;Desc:No Response from PLC(22)
2019-02-25 21:58:35;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:00:08;Id:106;Desc:
2019-02-25 22:00:09;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:00:13;Id:-22;Desc:No response from Forward Open
2019-02-25 22:00:42;Id:106;Desc:
2019-02-25 22:00:44;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:00:48;Id:-22;Desc:No response from Forward Open
2019-02-25 22:04:52;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:05:06;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 22:05:09;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:07:37;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:07:57;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:08:06;Id:-22;Desc:No response from Forward Open
2019-02-25 22:10:19;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:14:49;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:15:12;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:15:58;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:15:58;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 22:16:00;Id:-34;Desc:Could not connect to 172.30.5.32, port 44818. Timed out
2019-02-25 22:16:02;Id:-22;Desc:No response from Forward Open
2019-02-25 22:18:43;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 22:18:43;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:19:09;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 22:19:09;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:19:32;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:21:27;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:24:08;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 22:29:50;Id:106;Desc:
2019-02-25 22:29:52;Id:-22;Desc:No Response from PLC(22)
2019-02-25 22:29:56;Id:-22;Desc:No response from Forward Open
2019-02-25 23:01:24;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:05:57;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:07:20;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:14:44;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:19:48;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:20:02;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 23:20:02;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:21:31;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 23:23:55;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:23:55;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 23:26:26;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 23:27:41;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 23:30:06;Id:106;Desc:
2019-02-25 23:30:08;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:30:12;Id:-22;Desc:No response from Forward Open
2019-02-25 23:32:56;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:34:45;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:34:53;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 23:34:53;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:35:58;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:38:12;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:38:24;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:38:28;Id:-22;Desc:No response from Forward Open
2019-02-25 23:39:41;Id:106;Desc:
2019-02-25 23:42:03;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 23:42:03;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:42:10;Id:0;Desc:EIPTransport.SendData-No Response
2019-02-25 23:42:13;Id:-22;Desc:No Response from PLC(22)
2019-02-25 23:46:17;Id:0;Desc:EIPTransport.SendData-No Response


Title: Re: EthernetIPforCLX driver: Communication Fault code
Post by: Archie on February 25, 2019, 11:06:14 PM

It means the packet was sent, but no reply was returned. Was is your PollRateOverride?

Title: Re: EthernetIPforCLX driver: Communication Fault code
Post by: trung.bui on February 25, 2019, 11:12:41 PM

hi, poll rate is 2 secs.
Think that is still ok to read? how can i detect it s because of network or because PLC refuse?
Thanks

Title: Re: EthernetIPforCLX driver: Communication Fault code
Post by: Archie on February 25, 2019, 11:26:44 PM

Quote from: trung.bui on February 25, 2019, 11:12:41 PM

hi, poll rate is 2 secs.
Think that is still ok to read? how can i detect it s because of network or because PLC refuse?
Thanks

PollRateOverride=2000 ?

Title: Re: EthernetIPforCLX driver: Communication Fault code
Post by: Archie on February 26, 2019, 12:15:10 AM

From your other posts you had PollRateOverride = 0 which is extremely taxing on the network and processor. At that setting it can be expected for the processor to not be able to respond to every packet.

Title: Re: EthernetIPforCLX driver: Communication Fault code
Post by: trung.bui on February 26, 2019, 12:21:17 AM

No sir, i changed PollRateOverride to 2000 ms already to test with L73 controller. PollRateOverride = 0 is for pressure test with SoftLogix controller only.
Could you please help give the idea to find the problem with those error code?
Thank you so much

Title: Re: EthernetIPforCLX driver: Communication Fault code
Post by: Phrog30 on February 26, 2019, 12:29:45 AM

Do you happen to have managed switches to look at logs to see if you are getting any error codes? What Ethernet card, EN2T/R? What else is on the network? Does it happen on all forms/windows? All controls?