Hello,

I have been attempting to create a pack and go file for a remote site. They do not have TIA Portal. Recently they upgraded from the KTP400 Basic Color PN (6AV6647-0AK11-3AX0) to the KTP Basic (6AV2123-2DB03-0AX0).

I have their HMI software in TIA Portal Version 13 SP 1 Update 2. I went to properties of the HMI and selected Change Device/Version. I navigated and selected:

HMI > SIMATIC Basic Panel> 4" Display > KTP400 Basic > 6AV2 123-2DB03-0AX0

The new device shows up as "KTP400 Basic PN" instead of "KTP400 Basic". Since the article numbers match and the data sheet for the HMI reccomends TIA v13 I assumed this might work. I created a pack and go and asked the remote site to try it. They told me it did not work; they received an error saying "loading target failed".

Has anyone else experienced this? How can I select the correct article number and get a device with a slightly different name? Is this some kind of bug that selects the wrong device?

Hello Daniel,

even if they don't need TIA portal there are some requirements (see https://support.industry.siemens.com/cs/ww/en/view/109476153, section Pack & Go):

Remote Access to SIMATIC HMI Comfort Panels

Requirements

To transfer the “Pack&Go” file to the operator panel, the following conditions must be fulfilled:

• On the PC, from which the “Pack&Go” file shall be transferred, the following software must be installed:
  • SIMATIC ProSave can either be installed via the WinCC (TIA Portal) product DVD, or downloaded in \3\. 
  • Microsoft Visual C++ 2010 Redistributable Package (x86) can be downloaded in \4\. 
  • Microsoft .Net Framework 4.5 can be downloaded in \5\. 
• The PC, from which the “Pack&Go” file shall be transferred, must be connected to the operator panel via a network. Transfer via routing is not possible.

Regards,

Frink

Hello Frink,

Thank you very much for the advice. I checked with the field and it seems like they have the correct software. They have successfully installed Pack & Go files on other systems. It is just this one that is giving them trouble.

They have reiterated that they believe the problem is that the file is for the KTP400 Basic PN instead of KTP400 Basic.

I will keep trying to figure out why I keep getting the "PN" version of the pack & go.

Daniel