PLCNextapp install fails: wrong target

PLCnext Store
1

Hello, I tried to create and install a plcnextapp cmdlinetool. plcnextapp create … works, but when I try to install it via plcnext install …app it says: “error2: app exampleid wrong target” I have an AXC F 2152, so the target looks correct. I guess I should not install it via cmdline but via the AppManager? But I cant find how to trigger the installation via the appmanager. How does that step work? Best, Sören

2

Hello Sören, Can you give me the contents of the app_info.json file that you packaged with the app? - Martin.

3

Sure: {

“plcnextapp”: {
“name”: “testX”,
“identifier”: “testXid”,
“version”: “1.0”,
“target”: “AXC F 2152”,
“minfirmware_version”: “19.3.0”,
“manufacturer”: “Resolto Informatik”
},
“cmdtools”:
[
{
“path” : “/bin/test”
}
]
}

4

I guess you are trying to use the command “plcnextapp install …” to install your app? Instead, can you please try installing the app from the PLCnext Store? Before doing this, you will need to include the correct value in the “identifier” field, which is the unique 14 digit number you get when you create the app in the Store. - Martin.

5

That’s correct. Is there no way to test it locally? Also I am now hanging when I want to install he asks me to add a device by name and deviceId. Where do I get the DeviceID from? Serial no and order no didnt work. - Sören

6

Currently, the only supported way to install or uninstall a PLCnext Store app is from the PLCnext Store. There are instruction on how to register a device in the PLCnext Store in this FAQ: https://www.plcnext-community.net/index.php?option=com_fss&view;=faq&tmpl;=component&window;=1&faqid;=111&Itemid;=272⟨=en … and in section 2.4 of this Quick Start guide: https://www.plcnext-community.net/index.php?option=com_wrapper&view;=wrapper&Itemid;=375⟨=en (you can see the device ID either on the housing of the device, or on the Proficloud page of the Web-Based Management site). (P.S. I have moved this thread to the PLCnext Store group)

7

Okey, found the device id (is it normal that there is a section “-dead-code-” inside the uuid string?). From the wbm: Proficloud Service State | The Proficloud is reachable and available.

—|—
Proficloud Connection State | Connecting
Device Registration State | Not Registered
Maybe the problem now is that the proficloud connection state is hanging at “connecting” ? The device is reachable via internet (but only over port 443 and by ping). Are there more ports which need to be opened?

8

Hello Sören,

I have now checked your UUID in the backend.
Your UUID is one of the first that was generated.
Your UUID was not known to the Proficloud.
I have announced the UUID of the Proficloud.
Your UUID is now available for the Proficloud service TSD and Store.
Additionally I reset the Regtoken again. Now your device should establish a connection.