Conversion issues from Engineer 2020.6.2 to Engineer 2021.LTS / 2021.02
I have been running in to some interesting if annoying issues over the last two days when converting an existing project from Engineer 2020.6.2 to Engineer 2021.02.
To start I did update the firmware (FW) on the controller (AXC F 2152) and checked in the web base management (WBM) the FW was correctly updated. I added the users needed and assigned the roles.
In engineer I replaced the controller with the one that has the FW 2021.LTS. Personally, I always do a re-build after before loading the program to the controller.
When I did load the program, the controller presented me the following issues:
RUN LED - blinking; Fail LED - ON; Diag LED - blinking red; no local bus components and no ProfiNet communication. A quick look in to the WBM shoes the same.
Well, I haven't seen that one before. So I requested help from Phoenix Contact.
Our local supporter was onside yesterday morning to assist me. But he also hasn't seen this before. So, we needed to contact the HQ for help
Together with Frank Walde from Phoenix Contact we had yesterday a look at it. In the outputlog we could see that the local bus component config had issues.
The why is still a question - the application has been running before.
Franks quick fix was to remove the AxioLine modules from the local bus (in Engineer) and load the program - that did work! I could load the program in the controller and the controller did go in RUN mode.
After that, I added the AxioLine modules again, connected my process data and loaded the program to the controller. Again, it did work.
So, in case you see a case like this, try those steps. Helped in my situation.
Frank is also still looking in to the issues to see if there is something that can be done in the Engineer to prevent this.
I would have liked to have some kind of information in the Notifications from the controller, that could give us a better idea on the issues. Frankly, the Notifications are a bit on the down when it comes to the information needed to diagnose issues. But that will hopefully change over time, so that we get better information's to diagnose problem in our applications. The outputlog does help here, but it should not be necessary to go that far to identify a problem.
But in any case I'm thankful for the support, no matter how annoying the issues has been.
Peter Paul
Comments
I had the same problems bit IO but i just started with PLCnext and thought is was my problem..
The Coffee demo program worked well in my case so I used this project as base and cleared all code 'till i got an empty project.
Then i started again with my code. I choise this because i did not have serious code yet and i was playing.
Thanks for sharing so we are aware of this problem,
Marco van Os,
GeoComfort
Hi Marco,
there is no reason why you should fight the same issues as me. I am more then happy to share my findings with the forum, so that we all can benefit from it.
We will see some issues along the way with PLCNext - there is sadly no way around it. We have a complete new eco system here and there will be some issues.
The control systems are getting more and more complex, we want to have more functionalities and possibilities in our controls, well sometimes that isn't working at the first try.
Also is there the possibility some parts of the software / firmware will collide when adding new function. This is as the story will go.
What we can do here: report the issues, so that all in the forum can see what the issues is. If there is a solution - good! If not, the folks from Phoenix are there too to have a look.
But please: Always post solutions to the issues. It isn't helpful to see that an issue has been solved via email or so. Others may have the same problem
Peter Paul