Hello, I am using a 2152 with this firmware: 2021.0.0 LTS (21.0.0.35466) I use C# blocks, and also use the Linux Shell. Lately the PLC started to throw these errors (and it stops!), but I can’t connect them to any event or block execution. How can I decode what it means? To get a idea of where to look. Thanks, Alex 30.09.21 16:31:43.063 Arp.Plc.Esm.Internal.Tasks.TaskBase ERROR - Exception in task ‚Cyclic2s‘ occured: Exception of type ‚Arp::System::Commons::Plc::PlcException‘ was thrown Execption ‚1‘ occured. at System.String.Create : 146 at System.Iec61131Lib.IecStringEx.ToString : 64 at PLCnextBase.Internals.SymbolAccess.ResolveAbsolutePath : 190 at PLCnextBase.Internals.SymbolAccess…ctor : 152 at PLCnextBase.Internals.SymbolAccess.op_Implicit : 94 at PLCnextBase.SystemFunctions.PBCL_SysLinuxShell_1.Reset : 94 at PLCnextBase.Internals.Iec61131.AbstractServicePou.__Process : 162 at ProConOS_eCLR.Mcv_Creation.__Process : 822 at Arp::Plc::Eclr::Internal::Esm::EclrExceptionHandling::ConvertExcpetionCodeIntoException(int, CPcosDomain*) at Arp::Plc::Eclr::Internal::Esm::IecProgram::Execute() at Arp::Plc::Esm::Internal::Tasks::TaskBase::ExecutePrograms() at Arp::Plc::Esm::Internal::Tasks::TaskBase::ExecuteTask() at Arp::Plc::Esm::Internal::Tasks::TaskBase::Execute() at Arp::Plc::Esm::Internal::Tasks::CyclicTask::SpecializedRun() at Arp::Plc::Esm::Internal::Tasks::TaskBase::ThreadRun(void*) at Arp::System::Commons::Threading:
:RunThread(Arp::System::Commons::Threading::ThreadBinaryCompatibilityExtensions*) at Arp::System::Commons::Threading::RunInternal(void*) at Arp::System::Ve::Internal::Linux::ThreadService::RunInternal(void*) 30.09.21 16:31:43.645 Arp.Plc.Esm.Internal.Tasks.TaskBase ERROR - Exception in task ‚Cyclic1s‘ occured: Exception of type ‚Arp::System::Commons::Plc::PlcException‘ was thrown Execption ‚1‘ occured. at System.String.Create : 146 at System.Iec61131Lib.IecStringEx.ToString : 64 at PLCnextBase.Internals.SymbolAccess.ResolveAbsolutePath : 190 at PLCnextBase.Internals.SymbolAccess…ctor : 152 at PLCnextBase.Internals.SymbolAccess.op_Implicit : 94 at PLCnextBase.SystemFunctions.PBCL_SysLinuxShell_1.Reset : 94 at PLCnextBase.Internals.Iec61131.AbstractServicePou.__Process : 162 at ProConOS_eCLR.Mcv_Creation.__Process : 822 at Arp::Plc::Eclr::Internal::Esm::EclrExceptionHandling::ConvertExcpetionCodeIntoException(int, CPcosDomain*) at Arp::Plc::Eclr::Internal::Esm::IecProgram::Execute() at Arp::Plc::Esm::Internal::Tasks::TaskBase::ExecutePrograms() at Arp::Plc::Esm::Internal::Tasks::TaskBase::ExecuteTask() at Arp::Plc::Esm::Internal::Tasks::TaskBase::Execute() at Arp::Plc::Esm::Internal::Tasks::CyclicTask::SpecializedRun() at Arp::Plc::Esm::Internal::Tasks::TaskBase::ThreadRun(void*) at Arp::System::Commons::Threading::RunThread(Arp::System::Commons::Threading::ThreadBinaryCompatibilityExtensions*) at Arp::System::Commons::Threading::RunInternal(void*) at Arp::System::Ve::Internal::Linux::ThreadService::RunInternal(void*)
Hi Alex, It can be a little tricky to track down errors based on information in the Output.log file, but - like we can see here - the complete stack trace is now included in the log file (where possible) after a crash, which could help. A useful piece of information is this: [quote]at PLCnextBase.SystemFunctions.PBCL_SysLinuxShell_1.Reset : 94[/quote]… which indicates that the problem occurs in a PBCL_SysLinuxShell function block instance. This might be a problem with the function block itself, or it might be a problem with the way the function block is being used in the application, or (less likely) this could be a side-effect of a problem that is unrelated to this function block. Without seeing your code it is difficult to say anything else about the potential causes of this problem. I know that you are in contact with my colleagues in your local Phoenix Contact office, so perhaps you can ask them to look at your code and offer some suggestions. It may also be necessary to involve the developers of the PLCnext Base library if further investigation is needed. In any case, since (at this stage) this is likely to be an application-specific issue, if you want we can deal with this directly via email.
Thank you Martin, This is a new PLC that we are testing on and I reviewed the installation of the .NET Core runtime for C# and I had missed changing the permissives of the file dotnet.sh with the command: „chmod +x /etc/profile.d/dotnet.sh“ I am not sure if this was causing the error, but it is running now. Will keep an eye during the weekend.