Error but no error when attempting to deploy to RT target

[cirrusio]

OK....I have currently run into a very irritating problem.  Often when I attempt to run an Actor Framework based project on an RT target (PXIe-8135), I run into the problem where a VI seems to throw an error and causes the launch to fail (i.e. I get an error message in the deployment progress window).  It seems that the same VI is not always indicated as the source, but whatever the source, if you hit run on the VI that has a broken run arrow, you inevitably get the error window to pop up with NO errors as shown in the image below.  Anyone have any thoughts or has run into this before?

Thanks, Matt

[cirrusio]

Update: Tried reformatting drive to see if this is the problem, but no dice.  Error seems tied to the Launch Nested Actors VI in the Actor Framework library.  The error message is Actor Framework.lvlib:Actor.lvclass:Launch Nested Actor.vi loaded with errors on the target and was closed. Ugh..

[lucaso3]

Hi mtat76,

Since reformatting drive didn’t solve the problem, I would recommend reading these links to see if we might be able to find valuable information, by checking the examples and some community information. On the context help it says that we must ensure that the Caller Actor in has already been launched, because if not, the Nested Actor VI will throw an error.

http://zone.ni.com/reference/en-XX/help/371361L-01/lvcomm/af_launch_nested_actor/

https://decibel.ni.com/content/thread/11299

https://decibel.ni.com/content/docs/DOC-24187

https://decibel.ni.com/content/message/44213

https://decibel.ni.com/content/docs/DOC-24051

I hope you might be able to find the proper information on that links. You can also try with the example on the community to see if that runs properly on your RT target, and if it does, the problem might be on the program. If you encounter any other issues, it might be a compatibility issue or we need to troubleshoot further.

Luis C.

National Instruments

[cirrusio]

Thanks, Luis.  I will look these over.  I think that I should have state that I have had this project compiled and running before, so I am not sure why it is not deploying properly now...

[cirrusio]

Another couple of things I should note here.  First, I am using LV 2014, so issues associated with earlier versions of the AF are unlikely to impact this current project.  Second, this is a very large project that until recently I have been doing nightly builds to verify that the project was 1) depoloyable, 2) buildable and 3) executable.  I took a short break from this portion of the project to work on some aspects unrelated to the execution of the current system (testing some other actor functionality that will be folded into the current application but has not yet been, working on web based displays etc).  It is not clear to me that the issue is directly related to any changes regarding the current application (but, in my experience, it is not unlikely that something in one of the project classes has become corrupted).  Finally, given the current errors thrown during deployment, I absolutely can not execute the current application in the LV environment, so I can not trace anything.  

That being said, I do have an error log from the chassis and I should probably post it as it likely contains a clue as to why things are not deploying (but, it is rather cryptic, so I am having trouble decoding it).  I will post this when I get a chance.

Cheers, Matt

[lucaso3]

Hi mtat76,

That would be great. Also, have you tried with a smaller example?

If you would like, this link might help as reference on certain aspects.

https://decibel.ni.com/content/message/84529

Luis C.

National Instruments

[cirrusio]

Thanks, Luis.  As I said before, I am familiar with that thread.  If you will notice, deployment, which is where this error occurs, receives little attention other than to say it takes a long time to deploy a AF based project.  One thing to keep in mind is that the cRIO is a different platform in terms of resources than the PXI, so what is observed on the cRIO may not be applicable to the PXI.

I will give a smaller implementation a go...

Matt

[cirrusio]

As it turns out, I am having some other issues that appear to be associated with the NI System Configuration 14.0.1 update so I am going to attempt to unwind these.  Unfortunately, this means that I will have to remove a lot of other stuff also.  I will let you all know how things turn out.

Cheers, Matt

[cirrusio]

Sooo....after uninstalling everything and then reinstalling, this error didn't seem to go away.  Oddly, I was not able to import a MAX configuration file from my development computer.  But, I was able to import from another computer....and viola!  Everything was up and running again.  Unfortunately, I can't point to one thing that helped me get back up and running, but I suspect it had something to do with redeploying the config from another computer to the target.

Wish I had more insight into this....Cheers, Matt