This site uses cookies for functional purposes. To continue please read and agree to our Data Privacy.

By closing this message, you consent to our use of cookies on this device.

PLCnext on Instagram  PLCnext on YouTube Github PLCnext CommunityStore PLCnext Community

  1. d.vanschoorisse@uboatworx.com
  2. PLCnext Engineer
  3. Friday, 01 March 2019

Hi,

Posting here in the forums so it can be used for future reference for somebody else experiencing the same problem :-) 

When I try to import a second library that's depending on a library that's already imported as a dependency an error is raised.

  1. Start an empty project
  2. Import the PN_Dev_Diag_2 library. This library depends on the AsynCom_5 library. Importing this library should cause no problems. 
  3. Import the CANbus_5 library. This library also depends on the AsynCom_5 library. Importing this library raises an error: "The library could not be added because a solution with the same id is already open".

What I have tried:

  • Reverse the order of importing the libraries
  • Delete the dependency from the directory from the second library before importing it (in the example above this would mean deleting the file "C:\Users\Public\Documents\Phoenix Contact Libraries\PLCnext Engineer\CANbus_5\AsynCom_5.pcwlx" before executing step #3)
  • Copying the dependencies to make sure they are the exact same version

None of these steps help to solve the error. 

In the help file I read the following: 

Always use the current AsynCom library available on the Phoenix Contact website. Integrate both theAlways use the current AsynCom library available on the Phoenix Contact website. Integrate both thePN_Dev_Diag and the AsynCom library into your project. Make sure that the current AsynCom library is alsointegrated into the PN_Dev_Diag library. If the PN_Dev_Diag library cannot be transferred, even though the currentAsynCom library is integrated, check the path of the integrated library and change it if the path does not match thestorage location of the current library.

As far as I can see the stand-alone version available for download on the PLCnext Store is the same (5.0) version.

The version of the IDE used is PLCnext Engineer 2019.0 LTS build 3.13.543.0

 

Attachments (1)
Accepted Answer
d.vanschoorisse@uboatworx.com Accepted Answer Pending Moderation
0
Votes
Undo

Thanks for sharing your solution! Just copying the PCWLX files (CANbus_5.pcwlx and PN_Dev_Diag_2.pcwlx) into libraries folder in the Program Files libraries folder (C:\Program Files\PHOENIX CONTACT\PLCnext Engineer 2019.0 LTS\Libraries) does the trick for me.

 This solves this issue for now, but I think this should be considered as a bug in PLCnext Engineer.

 

  1. more than a month ago
  2. PLCnext Engineer
  3. # Permalink
thekrel Accepted Answer Pending Moderation
0
Votes
Undo

I ran into the same problem. The solution I found was to copy and move the *.pcwlx files. When the libraries are downloaded and installed in named folders placed in the /ProgramFiles/PhoenixContact/PLCnextEngineer2019.0LTS/Libraries folder. I then took the *.pcwlx file from each of these named folders, and copied it out to the main Libraries folder. Once I did this, I was able to add the libraries that had common dependencies. For example I was trying to add the CAN Bus, IO Link and PN Dev Diag libraries. I have attached a screen shot showing my folder structure.

Attachments (1)
  1. more than a month ago
  2. PLCnext Engineer
  3. # 1
  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.