Sonstiges Versions of TIA

Glenn Patton

Level-2
Beiträge
7
Reaktionspunkte
0
Zuviel Werbung?
-> Hier kostenlos registrieren
Hi All,
New guy to the site (new(ish) guy to PLC's. I am a Brit and my German is poor at best, so I will be posting asking in English (via Google translate) will this cause an issue? Trying not to offend anyone!
Quick question the PLC/HMI is not the latest version, if the program is open in the version of TIA Portal 18 and I was created in 16 will it compile or am I heading down a path of fixing issues.

Glenn
 
If you open a project that was last used with V16 and you open it with V18, the project will be upgraded and you as long as it compiles without errors and warnings you should be goot go. Also check before hand if the CPU and HMI you use are still in the hardware catalog of V18

But since its your project and your machine, you'd have to evaluate if it safe to download the re-compiled project.+

Also if you upgrade the project to V18 you could also think about upgrading the firmware and Panel Image to it's latest versions. And if you're doing that don't for get to change the firmware of the CPU in the hardware configuration of your project.
 
What do you mean with ownership? Being responsible?
If you're unsure how to proceed, or to proceed anyway, talk to your expierenced colleagues, higher-ups and people who are in charge of the machine. If it's a machine which is currently immanent with production, you need to check in anyway with the people in charge of it and the maintenance to get some planned downtime.
 
Also if you upgrade the project to V18 you could also think about upgrading the firmware and Panel Image to it's latest versions. And if you're doing that don't for get to change the firmware of the CPU in the hardware configuration of your project.
Does he really need to update the FW?

I would go the way to open the project in V18, compile it and see if it works. If yes, I would assume that I could load it to the PLC without any changes!? Or am I wrong? I would update the FW only if TIA asks me to do it or if I had trouble with it and need to try a newer one.

What do you mean with ownership? Being responsible?
I guess he means that he is not the author of the software. He responds to
But since its your project and your machine, you'd have to evaluate if it safe to download the re-compiled project.+

Of course: Downloading and testing the new compiled program needs some time in which the machine might not be available.
In case you get trouble, you could revert to the old version V16, at least as long as the FW is not updated. Make sure the offline version is same than the online version, safe the current DB values if necessary and make sure your V16 environment is able to upload the old software version to the devices in case of failure.
 
Zuviel Werbung?
-> Hier kostenlos registrieren
What do you mean by ownership? Being responsible?
If you're unsure how to proceed, or to proceed anyway, talk to your experienced colleagues, higher-ups and people who are in charge of the machine. If it's a machine which is currently immanent with production, you need to check in anyway with the people in charge of it and the maintenance to get some planned downtime.
Being blamed! It's not my Fault!
 
Does he really need to update the FW?
I didnt say or mean that it is mandatory, but it's something to take into consideration after a successful upgrade and implementation of the V18 project.

If you're not the owner of the original program @Glenn Patton, who is it then?
If the person is working at your company => get in touch with them

If the machine is bought, there is to take into consideration that there is an active warranty for that machine provided by the supplier of it. Your company could lose that warranty, if the machine is getting altered in any way. (that includes the program).

Being blamed! It's not my Fault!
No one is at any fault currently, or did I miss something?
If your motivation is to upgrade the machines project and you have the green light from your higher ups, then just make sure to take enough precautious actions to minimize any risk of faulting. And if you're still unexpierenced/feel unexpierenced, talk to the personnel with more expierence in that field and do it together.

There is nothing wrong with wanting to do operations you're unfamiliar with, or trying to gain expierence. There is nothing wrong with making mistakes and errors in that part of the process, as long as you have the support from your colleagues and as long as everyony is on the same page.

Making mistakes is part of any process. Expierence doesn't come from doing everything correct at the first try.
 
"If the person is working at your company => get in touch with them" they left under a cloud! so wont be of much help. The best of finding out how to do something, is finding out how to do it wrong!
 
Zuviel Werbung?
-> Hier kostenlos registrieren
We've given you some options how you could proceed, it's up to you to take those into consideration, or not.

  • Make a back up of the original project which is currently live on the plc.
  • Make a online back up of the current plc program, in case you need some settings values for the machine to run as intended.
  • Upgrade the project to V18
  • Compile both plc and hmi (compile the whole project, not just changes) and check if you get any errors and warnings
  • Make sure you are able to download the old V16 project again, if the upgrade fails
  • Arrange some downtime with production and maintenance in the loop - they should know what you want to do and why and if other personnel is needed to get the machine running again
  • Download the plc and hmi program
  • Check if everything works as before/inteded
  • Stay at the machine for 10-15min as production ramps up to be in direct support for it.
  • Monitor the production of the machine throughout the rest of the day a bit, just stay in touch with the production staff (operators, supervisors etc.)

Have some fun while doing it! ;)
 
Zuletzt bearbeitet:
Any change to any code affects something. Doesnt matter which enviorment.
But why do you think that upgrading the project would make any changes code-wise?
 
Zuviel Werbung?
-> Hier kostenlos registrieren
If You upgrade the project from TIA V16 to TIAV 18, nothing is normally changed in the software code, and Your TIA V16 project remains in its original form and is not changed.
However, if You use V18 on the CPU with the V16 project, there could be problems, which is why we recommend upgrading the FW. However, this can also lead to problems, which can also result in the production system coming to a standstill. Whether You want to / can take this risk is entirely up to You (or Your supervisor).
Why not use TIV16? If You don't have a license for it, You could work with the trial license.
 
What I was afraid of was Altering the code on 18 and not being able to run on the PLC as it was a 16. Memories of Visual Studio 2008, if you edited a project with Enterprise you couldn't open it and edit it in Professional, despite not using any tools from the Enterprise edition.
 
You can install V16 simultaneously to V18. As long as you dont upgrade the firmware to a version that is only applicable to V18 you have access to both projects
 
Zurück
Oben