Greetings everyone, I'm a beginner in the world of PLCs and I want to share a detailed post about my current project. I am integrating Ignition, a software by Inductive Automation, with an existing system controlled by a Siemens S7-1200 PLC. The system consists of the S7-1200 PLC, a Siemens IO device, and two Siemens HMI panels (KTP1200 Basic). The setup was done by a third-party company and we do not have access to the original project file. However, there is no password protection on the PLC, and we have a TIA .15 project backup that I am reviewing. At this stage, I need to establish communication between Ignition and the PLC by connecting a local workstation. I also need to upload the live program on the PLC to a new project in TIA Portal, enable the PUT/GET with remote partner configuration option, and then redownload the project to the PLC. I have a few concerns regarding the process. When connecting the local workstation, I plan to temporarily disconnect the ethernet cable between the PLC and one of the HMI panels to introduce a network switch. Will this cause any long-term issues in the HMI or PLC? Additionally, can I use a basic dumb switch and cat5/6 cables for this setup? The original project was created using TIA v15, which is no longer available. I have licensing for v17 and a trial version of v15.1. Can I upload the program using these TIA versions? Enabling PUT/GET is essential for Ignition to communicate with the PLC. If I change this configuration option and redownload it to the PLC without altering the program, will it overwrite/reset any live tag values or PLC memory? I want to ensure that I do not break the system or cause any issues. Any advice on these matters would be greatly appreciated. Thank you in advance for your help!
1. Disconnecting the HMI while the system is inactive will not affect any functions. Once reconnected, the system will operate normally. 2. It is not possible to upload a lower version PLC using a higher version of TIA software. You will need TIA15 for this process. After uploading, you can upgrade the program to version 15.1 and download it. 3. Enabling put get access to the PLC will not impact the program in any way.
DeltaOP inquired about the process of connecting a local workstation, mentioning the need to disconnect the Ethernet cable between the PLC and an HMI panel to install a network switch for an extra output to the workstation. The concern raised was whether disconnecting the HMI momentarily to introduce these new components could potentially lead to long-term issues in either the HMI or PLC systems. One potential issue could arise if the IO Controller configuration utilizes a Profinet system with a specific topology requirement, where cabling must match the topology precisely. Introducing a switch in between devices could disrupt this setup. However, it is unlikely that the system is configured with such topology, but it is advisable to confirm before making any changes. Additionally, for this setup, a basic dumb switch and screened Profinet cables are recommended for connectivity outside the cabinet. In terms of software compatibility, the original project was developed using TIA v15, which is now obsolete. However, with licensing for v17 and access to trial v15.1, it is possible to upload the program using these versions concurrently. It is important to note that uploading a program from V15.1 to V17 may require recompilation and a fresh download. Regarding communication with the PLC, enabling PUT/GET is necessary for Ignition to interact with the PLC. Changing this option in the upload and then re-downloading it without modifications should not overwrite or reset live tag values or PLC memory. However, transitioning from V15.1 to V17 may reset actual values to their initial state, requiring a mindful approach to managing this migration effectively.
When connecting to the local workstation, it may be necessary to temporarily disconnect the ethernet cable between the PLC and one of the HMI panels in order to introduce a network switch for an additional output. Will this temporary disconnection of the HMI cause any long-term issues for the HMI or PLC? Would using a basic dumb switch and cat5/6 cables suffice for this setup? The original project was developed using TIA v15, which is no longer available. However, I have licensing for v17 and access to the trial v15.1. Can I upload the program using these TIA versions? Visit this link to determine which version of Portal is compatible for programming uploads. Usually, only the exact version works, which can be frustrating. Contact tech support if you need the v15 installer. Note that if it's a 1200F (safety PLC), it does not support uploads for the safety program, meaning you can't upload the full station if safety is active in a 1200. For communication between Ignition and the PLC, PUT/GET must be enabled. If I modify this option in the upload and then redownload it to the PLC without changing the program, will this reset any live tag values or PLC memory? Any hardware changes on the PLC will cause it to go to STOP for the download, resulting in non-retentive data being reset. Consider using the Snapshot function suggested by Jesper as a solution, although it may not cover all scenarios.
JesperMP explained that when configuring the IO Controller, there is a potential risk if the Profinet system is set up with a specific topology. This requires precise cabling from one specific port on a device to another specific port on another device, without adding a switch in between. While it is unlikely to be configured with a topology, it is recommended to confirm before proceeding. In terms of the project's topology backup, there are no links between devices, indicating that it should not be an issue. As for migrating from V15.1 to V17, it will reset all actual values to their initial values. Using the snapshot function in V15.1 can help by copying the snapshot to the initial values, but keep in mind that there may be changes in actual values during the migration process. If a download from the controller is successful, there may not be a need to migrate between versions, as making hardware changes in an offline version and re-downloading could suffice. The snapshot feature could be beneficial if needed. Since the system is for a brewery that operates mainly on batch work, it would be ideal to implement these changes during off-peak hours to avoid disrupting any processes. This could also be a good time to utilize the snapshot feature when tag values are stable.
According to mk42, disconnecting the HMI may be fine, although it could potentially disrupt processes like data logging. It's uncertain if the Basic panels support this feature. However, since there is no data collection for the process, it shouldn't be an issue. There's no need to stop the PLC before disconnecting the HMI; it can be done while the system is running. When it comes to uploading from another version of Portal, it's crucial to use the exact version to avoid compatibility issues. If you encounter any challenges, contacting tech support for the v15 installer may be helpful. Siemens is known for being specific about TIA version requirements for uploads. Regarding PLC changes, a hardware modification will cause the PLC to stop for the download process, resulting in the reset of non-retentive data to start values. The Snapshot function is recommended, but may not cover all scenarios. It's important to be cautious, especially if the program is from a third-party Chinese company. In the case of a 1200F safety PLC, uploads for the safety program are not supported, which means the full station cannot be uploaded if safety is active. It's essential to confirm the controller model and project file to avoid any issues. If a re-initialization occurs, it should be indicated on the warning screen before downloading. Testing with PLCSIM and TIA projects with tags but no program has shown that changing the PUT/GET option between offline and online versions does not overwrite tag values when redownloading to the PLC. It's advisable to ensure that the software versions for offline and online are the same to prevent any software overwrites.
Hello! Interesting project you're working on there. On the topic of disconnecting the ethernet cable between the PLC and one of the HMI panels, as long as you're just making a temporary disconnection for install, there shouldn't be any long-term adverse effects on the HMI or the PLC. Make sure to document your setup before and after so you can revert if necessary. For your network setup, a basic unmanaged or 'dumb' ethernet switch should suffice along with cat5/6 cables for making a connection. Regarding using TIA v17 or v15.1 for the upload, generally, the TIA Portal is backward-compatible, meaning you should be able to upload using later versions. That being said, it might be safer to use v15.1 if it was originally created in v15 to avoid any compatibility issues. Concerning the enabling PUT/GET configuration, yes, it might overwrite or reset some live tag values or PLC memory. What I recommend is doing a full backup before commencing the process to ensure you can recover in case of any issues. Of course, validate the changes in a controlled, safe manner before deploying it to the live system. Good luck!
Hey there! It sounds like you're diving into an interesting project! To address your concerns, temporarily disconnecting the Ethernet cable while you introduce a switch shouldn't cause any long-term issues; just make sure to reconnect everything afterward to maintain communication. A basic dumb switch with Cat5/6 cables should work perfectly for your setup too. As for the TIA versions, you should be able to upload the program with v17 or even the trial version of v15.1, but always ensure you have backups before making any changes. When enabling PUT/GET and redownloading to the PLC, the configuration should not overwrite any existing live tag values or the PLC memory as long as you don't change the actual program logic itself. Still, it’s a good idea to test on a non-critical system if possible. Good luck, and make sure to keep us posted on your progress!
Hey there! It sounds like you've got a solid project lined up. As for your concerns, temporarily disconnecting the Ethernet cable while you introduce a switch shouldn’t cause any long-term issues; just ensure that you reconnect everything correctly afterward. A basic switch should work fine for your setup, but make sure it’s a good quality one to avoid any potential network hiccups. Regarding the TIA Portal versions, you should be able to upload the project using v17 or the trial version of v15.1, since they generally support backward compatibility, but I'd advise double-checking the specific features used in your existing project. When it comes to the PUT/GET configuration, changing it and re-downloading the project shouldn’t reset your live tag values, but it’s always wise to take a backup first just in case. Best of luck with your integration!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - Yes, using a basic dumb switch and cat5/6 cables for this setup should work fine. It should not cause any long-term issues in the HMI or PLC.
Answer: - Yes, you should be able to upload the program using TIA Portal versions v17 or v15.1, even though the original project was created using TIA v15.
Answer: - Changing the PUT/GET configuration option and redownloading it to the PLC should not overwrite or reset any live tag values or PLC memory as long as you do not alter the program. It should not break the system or cause any issues.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.