Hi, I am having trouble building a DCAF program that can be deployed on a cRIO and autostart when turned on.
Some background first, I've started trying and implementing the DCAF framework on some CompactRIOs after seeing some features I liked, such as reusable static modules. I installed the DCAF Core package and some additional modules a few months ago, around August 2018. I've made a working program that can run fine on the CompactRIO when started on my development computer. However, building and deploying the code to autostart on the cRIO was a challenge. I tried building an application (.rtexe) first that can be set to autostart, but it didn't work. I then tried building a Source Distribution and edited to lvrt.conf file to autostart the main startup vi, "cRIO Main.vi", and that worked.
A few days ago I installed some updates for a few DCAF packages in the VI package manager. The program still worked when running from my development computer, but when I build and deploy a Source Distribution, the program won't startup anymore. I can't monitor the VIs on the VI server, and I can't connect to the cRIO on my Project Window unless I edit out the autostart line from the lvrt.conf file. The cRIO CPU also acts funny, alternating between 100% to 0%. on both cores.
Luckily I have an older Source Distribution that I can deploy to make the program work. When comparing the old vs new source distribution, I noticed the new one had more files and folders, mostly regrading the PL Framework Configuration tool.
I have no issues when building an executable for the DCAF UI, which runs on a separate Windows computer and communicates with the cRIO via Ethernet. It worked before and after the DCAF update.
The packages I updated are:
DCAF PID Module
DCAF Project Templates
DCAF Scan Engine Module
DCAF Tag Editor
DCAF UI Reference Module
Should I revert to a previous version of the packages to fix my problem? Does anyone else have an issue when building and deploying a DCAF application/source distribution to their cRIO?
Linus
