No response from Forward Open

[JasonXiao]

Our program has stopped running by a error message often.
Could you please help us to know what is the reason cause this error happen?

Error message:


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
MfgControl.AdvancedHMI.Drivers.Common.PLCDriverException: No response from Forward Open
   at AdvancedHMIDrivers.EthernetIPforCLXCom.BeginRead(String startAddress, Int32 numberOfElements)
   at AdvancedHMIDrivers.EthernetIPforCLXCom.Read(String startAddress, Int32 numberOfElements)
   at AdvancedHMIDrivers.EthernetIPforCLXCom.Read(String startAddress)
   at WindowsFormsApplication1.PHMonitor.timer1_Tick_1(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1076.0 built by: NETFXREL3STAGE
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
WindowsFormsApplication1
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/PLCLogin/AppData/Local/Apps/2.0/2RL8E54T.M0B/OHQQGXK3.G1Z/wind..tion_0000000000000000_0001.0000_e57228dd4f8b1746/WindowsFormsApplication1.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1075.0 built by: NETFXREL3STAGE
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1068.2 built by: NETFXREL3STAGE
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
MySql.Data
    Assembly Version: 6.9.6.0
    Win32 Version: 6.9.6.0
    CodeBase: file:///C:/Users/PLCLogin/AppData/Local/Apps/2.0/2RL8E54T.M0B/OHQQGXK3.G1Z/wind..tion_0000000000000000_0001.0000_e57228dd4f8b1746/MySql.Data.DLL
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Transactions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
AdvancedHMIDrivers
    Assembly Version: 3.9.8.4
    Win32 Version: 3.9.8.4
    CodeBase: file:///C:/Users/PLCLogin/AppData/Local/Apps/2.0/2RL8E54T.M0B/OHQQGXK3.G1Z/wind..tion_0000000000000000_0001.0000_e57228dd4f8b1746/AdvancedHMIDrivers.DLL
----------------------------------------
MfgControl.AdvancedHMI.Drivers
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/PLCLogin/AppData/Local/Apps/2.0/2RL8E54T.M0B/OHQQGXK3.G1Z/wind..tion_0000000000000000_0001.0000_e57228dd4f8b1746/MfgControl.AdvancedHMI.Drivers.DLL
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.6.1055.0 built by: NETFXREL2
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1067.0 built by: NETFXREL3STAGE
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.EnterpriseServices
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Archie]

Disable Just In Time debugging. See the web page on how to do it:

https://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx

If you are getting frequent No Response from Forward Open, then you are losing connection to your PLC or network.

[thebestg2002]

I'm resurrecting this topic as I'm experiencing the same issue. I have a 17" AHMI touchscreen PC and a L30ER CompactLogix PLC I'm using for debugging. I went to the link Archie shared above to disable JIT debugging, but my PC did not have any of the registry entries described in the article. I simply get a popup that says "No response from forward open" or "No Response from PLC(22)". I also occasionally see labels displaying an error indicating communication with the PLC is lost at least temporarily. It is not specific to one form. I know that I'm losing communication with the PLC, but I can't figure out why. I have been developing this application using my laptop to run it up until the last few days. When I run the application from my laptop, I do not get these popup messages. My laptop has much greater processing capabilities than the touchscreen with an 11th gen i7 processor with 32Gb of RAM.

Any advice on where to start from anyone else who experienced this would be greatly appreciated. If there's any other information needed, let me know.

[Archie]

Any advice on where to start from anyone else who experienced this would be greatly appreciated. If there's any other information needed, let me know.

What is your PollRateOverride setting for your drivers? You can try to set it to 1000 to see if slower communications has any effect.

[thebestg2002]

They are all set to the default of 500ms. I'll change to 1000ms as you suggested and see what happens.

I did find one issue that I thought might have fixed it. I made a change to the PLC a few weeks ago which eliminated some tags within a UDT, and I failed to remove one of those tags from a datasubscriber. After fixing that error, the rate of those popups decreased noticeably.

[thebestg2002]

For future reference, my issue had nothing to do with the application whatsoever. I removed the HMI ethernet cable from the ethernet switch and plugged it into the PLC directly. Not sure why this had to be done.