Actor Framework Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Actor Framework PPL issues in LV2020

Solved!
Go to solution

I am starting a new Actor Framework project in LV2020 using plugins, and I built the Actor Framework library into a PPL following the steps outlined here and using the "Actor Framework as a Debug PPL" example project. Now whenever I try to create a message I get the following error message:

 

"This target depends on multiple actor framework libraries. Only one library is allowed. You must remove the extra dependencies before proceeding."

 

There are no additional actor framework libraries listed in the dependencies, and if I change the inheritance to the .lvlib version then I have no problems. I've included an example project which gives me the error as well as the project I used to build the Actor Framework PPL.

 

One other thing to note. I also encountered this bug and implemented the workaround listed in the solution. I don't think this is the problem because reverting the scripting VI didn't change anything but figured it is worth mentioning.

Download All
0 Kudos
Message 1 of 8
(4,099 Views)
Solution
Accepted by topic author Cy.Rybicki

I had the same issue in LV2017 and ended up figuring this out via a support request with NI. Your PPL needs to be named Actor Framework.lvlibp. If you don't have the space, all the internal macros (rescript message, etc.) get confused and give you that incorrect error about there being 2 libraries.

Message 2 of 8
(4,095 Views)

Yup, that was it. The example project that comes with LabVIEW does not have any spaces in the PPL name. I wonder what the reason is for omitting the space given that it breaks things?

 

Thanks for the help.

0 Kudos
Message 3 of 8
(4,083 Views)

I filed a bug to get that looked at. In the future, if you see problems like that in a KB or other example on ni.com, you may click the "Site Feedback" link at the bottom to request fixes for that page.

0 Kudos
Message 4 of 8
(4,051 Views)

The problem wasn't actually with anything on ni.com, the KB steps are correct, it was with the "Actor Framework as Debug PPL" project that ships with LabVIEW. The project has a pre-configured build spec with the incorrect PPL name which I used as a starting point rather than creating a project and build spec from scratch as I've done in the past. It looks like it is named the same going back at least to 2018.

0 Kudos
Message 5 of 8
(4,036 Views)

Oh! I see. I'll adjust the bug report then... we should be able to adjust that shipping example.

0 Kudos
Message 6 of 8
(4,030 Views)

Hi this bug is still in LabVIEW 2021.

But another question: I want to integrate the Actor Framework in another ppl.

If I do this I get the same failure when I select Actor Framework \ Create Message from the context menu.

Is it not possible to do this? 

Failure_AF_in_ppl.PNG

0 Kudos
Message 7 of 8
(2,615 Views)

If the source version of AF is in memory at the same time as the PPL (say after you've done a "Replace with..."), you may see that message. Try closing and reopening your project.

 

If the problem still exists, you may still have linkages to the source version of AF somewhere. 

CLA CLED AF Guild
0 Kudos
Message 8 of 8
(2,611 Views)