PLCnext on LinkedInPLCnext on Instagram  PLCnext on YouTube Github PLCnext CommunityStore PLCnext Community

  1. carflomi
  2. PLCnext Engineer
  3. Tuesday, 13 October 2020

Working with PLCNEXT ENGINEER and had an unexpected shutdown, then I show the information that gives the program the error

 

PLCnext Engineer, Version 2020.6.2 (Build 4.5.239.0)

 

Unexpected Exception

======================================================================

Channel already closed.

 

Exception chain:

----------------------------------------------------------------------

AdeFatalCommunicationException

 

======================================================================

 

Details

----------------------------------------------------------------------

 

AdeFatalCommunicationException

==============================

Message:

------------------------------

Channel already closed.

 

Stack trace:

------------------------------

 

Server stack trace:

   at c30.Invoke(IMethodCallMessage A_0)

 

Exception rethrown at [0]:

   at c3e.Execute()

   at c6e.a(ICallStackFrame A_0)

   at c6j.get_IecInstancePath()

   at Ade.Internal.Plc.PlcCommunicationContextWrapper.a(ICallStackFrame A_0)

   at Ade.Internal.Plc.PlcCommunicationContextWrapper.<>c.a(ValueTuple`2 A_0)

   at System.Collections.Generic.List`1.ForEach(Action`1 action)

   at Ade.Internal.Plc.PlcCommunicationContextWrapper.a(ICallStackInfo A_0, Boolean A_1)

   at Ade.Internal.Plc.PlcCommunicationContextWrapper.c()

   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

   at System.Windows.Threading.DispatcherOperation.InvokeImpl()

   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)

   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Windows.Threading.DispatcherOperation.Invoke()

   at System.Windows.Threading.Dispatcher.ProcessQueue()

   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)

   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

   at System.Windows.Application.RunDispatcher(Object ignore)

   at System.Windows.Application.RunInternal(Window window)

   at Ade.Application.ApplicationStarter.Run()

   at (String[] )

   at PCWorxNext.Startup.Main(String[] args)

In addition to this, when I am connected to the PLC debugging, it systematically disconnects in a timely manner from the PLC (note, the connection between PC and PLC is direct via network cable).

error 1

I also notice the following error when I connect to the PLC HMI

error 2

 

Please, any way to improve PLCNEXT ENGINEER's behavior?

Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Sorry for the delay.

This exception will be fixed in the next release of PLCnext Engineer, version 2021.0.

~ Martin.

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.