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

  1. anonymous_user_YzfR31S6d3
  2. PLCnext Technology & PLCnext Controls
  3. Friday, 18 October 2019

Dear All,

I was working with my SD card on AXCF2152, with my DEMO CASE with Safety Bridge.

I used FW 2019.3 because before the hotfix for 2019.0.x & 209.6.x it was the only stable with Safty Bridge.

Dear All,

I was working with my SD card on AXCF2152, with my DEMO CASE with Safety Bridge.

I used FW 2019.3 because before the hotfix for 2019.0.x & 209.6.x it was the only stable with Safety Bridge.

I would like now to upgrade to 2019.9 :

I've upgraded the FW on AXCF2152
I've installed PLCnext Engineer 2019.9.
I've opened old 2019.3 project with last 2019.9 replaced & recompiled new template
After reboot it remaing with D LED ON and it was't reachable also via HTTP, only via WinSCP/Putty.

I'can't download upgraded project because I'can't estabilsh a communication with Engineer.

NodeRED app is reachable again, but without data.

I'm doing several tests but without any result, I don't want delete my SD card with all programs on it.

Waiting for your kindly support

Fabrizio

 

Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hi Fabrizio,

The symptoms indicate that the PLCnext runtime is not starting correctly.

Can you please log on to the controller using PuTTY, and then execute the following command:

sudo /etc/init.d/plcnext restart && tail -f /opt/plcnext/logs/Output.log

(if admin can't execute sudo, please switch user to root - using the su command - before executing this command).

You should then see all the log messages appear in the terminal as the plc starts up.

If you do not see what is causing the problem with the PLCnext runtime, please post the messages here, and we will try to help.

Martin.

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

anonymous_user_YzfR31S6d3 Accepted Answer Pending Moderation
0
Votes
Undo

Hello, Here the log :

Stopping service plcnext
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Warning: Application with pid does not terminate within 20 seconds.
plcnext stopped
Starting service plcnext
Set plcnext exports
plcnext started (bus system is axioline)
at: Arp::System::Acf::Internal::Sm::Config::AcfConfigurationLoader::Load(Arp::BasicString > const&, Arp::BasicString > const&, Arp::System::Acf::Internal::Sm::Config::AcfCon figuration&)
at: Arp::System::Acf::Internal::Sm::SystemManager::LoadConfig()
at: Arp::System::Acf::Internal::Sm::SystemManager::SetupSystemSettings()
at: Arp::System::Acf::Internal::Sm::SystemManager::SetupSystem()
at: Arp::System::Acf::Internal::MainApplicationBase::SetupInternal()
at: Arp::System::Acf::Internal::ApplicationBase::Setup(Arp::System::Commons::Diagnostics::Logging::LogLevel, char const*)
at: Arp::System::Acf::Internal::ApplicationBase::Main(int, char**, Arp::System::Commons::Diagnostics::Logging ::LogLevel)
at: Arp.System.Application(+0x191ee) [0x47d1ee]
at: /lib/libc.so.6(__libc_start_main+0x97) [0xb6a234a4]

18.10.19 16:52:40.868 Arp.System.Acf.Internal.ApplicationBase INFO - ArpVersion: 2019.9 (19.9.0. 23151 )
18.10.19 16:52:40.878 CommonRemoting INFO - [IpcRemotingBroker]: Starti ng IPC Remoting Broker
18.10.19 16:52:40.879 CommonRemoting INFO - Starting remoting server (v ersion=4)
18.10.19 16:52:40.879 CommonRemoting INFO - Start listening on TCP port 41120
18.10.19 16:52:40.879 CommonRemoting INFO - Start listening on TCP port 41121
18.10.19 16:52:40.932 Arp.System.Acf.Internal.ApplicationBase FATAL - Fatal error occurs in appli cation 'MainProcess':
18.10.19 16:52:40.932 Arp.System.Acf.Internal.ApplicationBase FATAL - Exception occurs: Exception of type 'Arp::System::Commons::KeyNotFoundException' was thrown
Key not found: key = 'ARP_SYSTEM_WATCHDOG_SUPPORT'
at: Arp::System::Acf::Internal::Sm::Config::Components::ReadXml(Arp::System::Commons::Xml::XmlReader&, Arp::S ystem::Commons::Xml::XmlSerializationContext&)
at: Arp::System::Acf::Internal::Sm::Config::AcfConfiguration::ReadXml(Arp::System::Commons::Xml::XmlReader&, Arp::System::Commons::Xml::XmlSerializationContext&)
at: Arp::System::Commons::Xml::XmlConfigDocument::ReadDocument(Arp::System::Commons::Xml::XmlReader&)
at: Arp::System::Commons::Xml::XmlConfigDocument::Load(Arp::BasicString > const&)
at: Arp::System::Commons::Xml::MultiXmlConfigDocument::ReadDocument(Arp::System::Commons::Xml::XmlReader&)
at: Arp::System::Commons::Xml::XmlConfigDocument::Load(Arp::BasicString > const&)
at: Arp::System::Acf::Internal::Sm::Config::AcfConfigurationLoader::Load(Arp::BasicString > const&, Arp::BasicString > const&, Arp::System::Acf::Internal::Sm::Config::AcfCon figuration&)
at: Arp::System::Acf::Internal::Sm::SystemManager::LoadConfig()
at: Arp::System::Acf::Internal::Sm::SystemManager::SetupSystemSettings()
at: Arp::System::Acf::Internal::Sm::SystemManager::SetupSystem()
at: Arp::System::Acf::Internal::MainApplicationBase::SetupInternal()
at: Arp::System::Acf::Internal::ApplicationBase::Setup(Arp::System::Commons::Diagnostics::Logging::LogLevel, char const*)
at: Arp::System::Acf::Internal::ApplicationBase::Main(int, char**, Arp::System::Commons::Diagnostics::Logging ::LogLevel)
at: Arp.System.Application(+0x191ee) [0x4c31ee]
at: /lib/libc.so.6(__libc_start_main+0x97) [0xb69d74a4]

Also WBM is not reachable :

https://172.16.5.100/wbm/

502 Bad Gateway


nginx/1.15.2

- Login

Greetings

Fabrizio

Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hi Fabrizio,

Yes, this is a known issue in systems where the file /etc/plcnext/Device.acf.config has been edited.

Long story short, because of the past edit, the old (edited) version of this file is still being used even after the firmware upgrade, and it is now missing some variables that are required by the latest version.

There are two possible solutions:

  1. Manually add the missing lines to the Device.acf.config file - but while this may solve the problem in the short term, it just kicks the can down the road until a future firmware update causes a similar problem.
  2. Do a Type 1 reset, which will delete the edited version of Device.acf.config from the overlay file system, and will solve the problem for this and all future firmware upgrades (as long as you don't edit that file again).

I am not 100% sure, but I think that the Type 1 reset will only delete the system files in the overlay file system (like Device.config.acf), and will not delete the additional files that you have added (like node red). So, I think that the Type 1 reset - which is the simplest solution - will be OK. But if you decide to do this, please be prepared to lose some or all of your customisations.

Moral of the story (which I also learned the hard way): Never edit any of the system files that are installed with the firmware.

Hope this helps.

Martin.

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

anonymous_user_YzfR31S6d3 Accepted Answer Pending Moderation
0
Votes
Undo

Dear Martin,

thanks for your answers, but I never edit that file /etc/plcnext/Device.acf.config.

I'used the FW 2019.3 and I wanted only to upgrade the device to the last fw version, I assume that something goes wrong during ugrade. I guess that upgranding FW to the last version we don't find any issue.

I started that project at the beginning ..from FW120/2019.0...and step by step I update the FW, could it be the problem ?

What are the the file that I had to add on /etc/plcnext/Device.acf.config. ?

..I could try to Type 1 Reset but I'm quite sure it erase also my standard applications.

Greetings

Fabrizio

Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Ah right, there was a problem with an earlier version of 2019.x firmware, which caused a similar problem, so if you upgraded step-by-step this is probably what you are seeing (in future you can just upgrade directly to the latest FW, which will avoid this problem).

For that upgrade problem, the solution is also to do a Type 1 reset.

If you really cannot do a Type 1 reset ... then I guess the only option is to edit the Device.acf.config file yourself (but again, this may case problems with future firmware upgrades).

I have attached the version of the Device.acf.config file that is installed with FW 2019.9 - you can see the environment variable you saw in the error message in the Output log, near the end of the file.

Martin.

Attachments (1)

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Better idea: You could try deleting this file (as root user):

/media/rfs/rw/upperdir/etc/plcnext/Device.acf.config

... which will delete the old version of the file, and use the version that was installed with the latest firmware.

 

 

 

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.