7/23/2019 1:45 PM | |
Joined: 3/5/2014 Last visit: 8/5/2022 Posts: 5521 Rating: (1051)
|
hi maccari79, Did you compile the V15-project? any errors or messages while compiling? regards, |
FCK WAR! |
|
7/23/2019 2:04 PM | |
Joined: 7/9/2015 Last visit: 5/29/2024 Posts: 3850 Rating: (564)
|
Hi maccari79, if V15.0 project will be compiled (Hardware and Software complete) without errors, do a Service Request at Siemens and Send ZAP15 File to check it. Regards, Towome |
|
|
7/23/2019 2:06 PM | |
Joined: 8/18/2011 Last visit: 11/14/2023 Posts: 14 Rating: (0) |
No errors, only warnings... |
7/23/2019 8:56 PM | |
Joined: 7/7/2010 Last visit: 6/3/2024 Posts: 14762 Rating: (2377)
|
Add English or German to your supported languages in V15. Compile HMI and try again.
|
science guy |
|
7/24/2019 12:52 PM | |
Joined: 8/18/2011 Last visit: 11/14/2023 Posts: 14 Rating: (0) |
I already had the project in English, I ended up adding German, but I still have the same problem. Thanks for the try |
Last edited by: maccari79 at: 07/24/2019 13:23:31 |
|
7/24/2019 8:31 PM | |
Joined: 7/7/2010 Last visit: 6/3/2024 Posts: 14762 Rating: (2377)
|
Does that also apply to your HMI? If it does, try splitting the HMI into a separate project and just converting the HMI by itself, then do the same with the PLC (and everything else except the HMI). Once they are converted, combine them back together.
|
science guy |
|
7/24/2019 8:38 PM | |
Joined: 8/18/2011 Last visit: 11/14/2023 Posts: 14 Rating: (0) |
The problem is that in this project I have 8 PLCs and 5 HMIs and everyone has communication with each other . But I will try to do what you advised me. thank you
|
7/24/2019 8:45 PM | |
Joined: 7/7/2010 Last visit: 6/3/2024 Posts: 14762 Rating: (2377)
|
Ok, one project with 5 HMIs. One project with 8 PLCs. Make the HMI project compile completely, and the same for the PLC project. You may have to move some logic to another block temporarily and not call it (leave a placeholder for it) to get the PLC project to compile. For the HMI project, you can create 8 new PLCs and copy the DBs / tag tables as needed to get them to compile. Don't copy the PLCs to the HMI project. That puts you back where you started.
|
science guy |
|
7/25/2019 2:53 PM | |
Joined: 8/18/2011 Last visit: 11/14/2023 Posts: 14 Rating: (0) |
I didn't get it, I took all the HMIs, but the problem persists ...
|
7/25/2019 3:11 PM | |
Joined: 7/7/2010 Last visit: 6/3/2024 Posts: 14762 Rating: (2377)
|
Ok now that you tried the easy solution, which I will state again in case I was not clear before: "Easy solution" (suggested to me by Siemens Support when I had a similar problem): 1. Split project into PLC only and HMI only. 2. Compile hardware / rebuild all for PLC-only project. Change it until it compiles without error, documenting what you had to do or undo. 3. Compile software / rebuild all for PLC-only project. Change it until it compiles without error, documenting what you had to do or undo. 4. Compile / rebuild all for HMI-only project. Change it until it compiles without error, documenting anything changed to make it work. 5. Upgrade HMI-only project. If it works, great. 6. Upgrade PLC-only project. If it works, combine it with the HMI-only project and reconnect tags and re-do anything that was un-done to make them compile before upgrading. I know it does not sound so easy when you state it like that. What they said was much simpler. Split the HMI and PLC into separate projects, and get them both to cleanly compile. Then upgrade each smaller project, and reintegrate them after upgrading separately. What was the real solution in my case - and probably is for you as well? I sent my project to Siemens Support. They split it apart, found I had a problem in the HMI that kept it from compiling cleanly, so it would not upgrade the entire project. I think I had warnings in my HMI compile. Apparently warnings do not mean "cleanly" for my project. I ripped out the screen causing the problem into a separate HMI, and changed it so the warnings went away. I was then able to upgrade that HMI-only project and put it all back together. That said, Siemens Support compiled and upgraded the PLC-only portion of my project without difficulty. I however could not. I had to use the project components Siemens upgraded for me. You may run into a similar situation, especially if your current project has been upgraded from earlier versions, or even one small part of it came from an upgraded / earlier version. There are hidden configuration settings that do not upgrade and that we do not have access to. I simply assume Siemens Support knows all those problems and fixes and apply them before attempting upgrades when customers are not able to upgrade.
|
science guy |
|
7/25/2019 4:49 PM | |
Joined: 8/18/2011 Last visit: 11/14/2023 Posts: 14 Rating: (0) |
Thank you very much for your concern in helping me. It has been of great value. Before reading what you reported above I was already conducting tests, and I found out that the compilation problem lies in two PLCs that use the GPRS / SMS 6GK7 242-7KX31-0XE0 communication module. I already checked some possibilities, but I haven't got it yet. I have a few more ideas of isolating these PLCs and trying to migrate separately to V15.1, the other PLCs compiled without problem. Again thank you very much for your attention.
|
7/25/2019 5:05 PM | |
Joined: 7/7/2010 Last visit: 6/3/2024 Posts: 14762 Rating: (2377)
|
When you remove those modules from the 2 problem PLCs (and hard-coding anything required to make it compile cleanly), can you migrate the project? |
science guy |
|
7/25/2019 5:10 PM | |
Joined: 8/18/2011 Last visit: 11/14/2023 Posts: 14 Rating: (0) |
did a test, downloaded set32 (https://support.industry.siemens.com/cs/ww/de/view/58638283) on V15, I tried to open on V15.1 and had the same problem, I believe the problem really lies in converting the 6GK7 242-7KX31-0XE0 module and the other GPRS / SMS modules. I'll try to do what you told me ...
|
Last edited by: Jen_Moderator at: 07/26/2019 10:46:04Edited text for better reading and optimized link. |
|
7/30/2019 12:19 PM | |
Joined: 8/18/2011 Last visit: 11/14/2023 Posts: 14 Rating: (0) |
As I didn't see a solution until yesterday, I ended up using the TIA V15, I have to add another PLC and an HMI to it, and I'm short on time, I will try to upgrade later. Thanks for all the help I was given in previous posts. Maybe in a future upgrade solve this problem the upgrade becomes more simple |
8/29/2019 2:45 PM | |
Joined: 11/23/2016 Last visit: 6/3/2024 Posts: 9 Rating: (4) |
Hi Not sure if this is useful, but I might as well chip in with my experience in the matter. I seem to have the same issue, trying to convert a simple project from V15 Upd. 4 to V15.1 Upd. 2, the project compiles without error in V15 but fails in upgrading in V15.1 After reading this thread, I've been gradually removing components/blocks and libraries in the PLC to no avail. Now I'm at a state where the only thing left in the project is the raw PLC (And it still compiles just fine), I might as well just have pulled a new controller in from the catalogue (CPU 1214 DC/DC/Rly) but the upgrade still fails with the same error... Well, I think this is out of my hands now, luckily the project is small and easy to recreate from scratch in V15.1, but I'm pretty sure that others will have a much harder time upgrading their projects. |
8/29/2019 3:37 PM | |
Joined: 7/7/2010 Last visit: 6/3/2024 Posts: 14762 Rating: (2377)
|
Have you tried installing V15.1 update 3? What did Siemens Support say when you submitted your project to them via support request? (That was one of the suggested methods, and you said you tried them all) Have you read and then read again the suggested solutions? I think not by your post. You seem to have a problem with upgrading the main PLC in the V15 project. Try instead opening 2 copies of TIA Portal. In portal #1, open original project. In portal #2, recreate just the main PLC hardware configuration. Now try to upgrade that to v15.1 If that succeeds, you may be in luck. Let's assume it succeeds ... Now in portal #2 in V15, drag over all the hardware modules, and set the PN/PB subnet details the same. This should be a complete hardware configuration. Compile / rebuild all in v15. If it succeeds (which it should), upgrade to v15.1. Let's assume it succeeds ... Now drag from portal #1 to portal #2 over all the OBs/FBs/FCs/DBs, tags, UDTs, watch tables, and whatever non-default items are in the PLC portion of the project tree. Compile / rebuild all hardware & software in v15. Upgrade to V15.1 If this succeeds, smile and post your results.
|
science guy |
|
2/27/2020 3:37 PM | |
Joined: 3/2/2007 Last visit: 5/30/2024 Posts: 931 Rating: (5) |
Kindly, how did you finally solve this problem of upgrade? |
... thank you ... |
|
7/8/2020 4:28 PM | |
Joined: 5/19/2011 Last visit: 4/12/2024 Posts: 24 Rating: (1) |
In case others stumble upon this problem. We searched a while also... In my case, in the V15 project, there were still FB's being edited in the Project Library. I discarded the changes, did a rebuild and archived the project again. Then I had no issues anymore retrieving the project in V15.1. |
7/8/2020 4:48 PM | |
Joined: 3/2/2007 Last visit: 5/30/2024 Posts: 931 Rating: (5) |
It looks ok now, after installing the following softwares (cant guess which one solved it). TIA Portal V15.1 Upd4 Startdrive V15.1 Update 3 SCOUT TIA V5.3 SP1 |
... thank you ... |
|
Follow us on