Distributed Control & Automation Framework (DCAF)

Reply
This is an open group. Sign in and click the "Join Group" button to become a group member and start posting.
Highlighted

Class not found error 538500 overwrites pcfg not found error 7. Bug & Solution.

Hi

 

Load target hierarchy is not passing though errors - so if pcfg file is not found (Error 7) it gets overwritten by class not found error 538500. 

Just needs an error case around it's code so the root cause error (pcfg file not found) is passed through. See attached pictures - root cause is that if pcfg file is not found, instance data is not loaded and is an empty array, so for loop in strings to memory.vi does not execute and returns and empty array to merge errors.

 

P.S. Wasn't sure of correct place to post this in Git Hub.

 

Cheers

Nick

0 Kudos
Message 1 of 4
(311 Views)
3 REPLIES 3

Re: Class not found error 538500 overwrites pcfg not found error 7. Bug & Solution.

For pretty clear bugs like this you can open an issue under the correct repository. For this issue it's actually a fix in the Configuration Editor Framework and not DCAF itself. Regardless this issue was actually tracked and closed under the following GitHub issue:

 

https://github.com/NISystemsEngineering/CEF/issues/105

 

Matt J
National Instruments | CLA
Message 2 of 4
(292 Views)

Re: Class not found error 538500 overwrites pcfg not found error 7. Bug & Solution.

Thanks Matt, my secondary issue was knowing / finding the correct repository to see if it had been fixed and to post it. 

Perhaps a link to host repository should be in VI documentation.

its got all the licence info there... 

In VPIM it just says Repository Name: NI LabVIEW Tools Network

which isn't that helpful. 

 

0 Kudos
Message 3 of 4
(283 Views)

Re: Class not found error 538500 overwrites pcfg not found error 7. Bug & Solution.


@NickNZ wrote:

 

In VPIM it just says Repository Name: NI LabVIEW Tools Network

which isn't that helpful. 


Ya, that repository is where VIPM is downloading the package from and not anything we can change (it's basically the default feed).

 

Talked to others though and we can start adding links to the GitHub repos in the VI Package description if that is helpful at all. The current idea is to end all of the descriptions with something like "Contribute to this open source package at <GitHub Link>"

Matt J
National Instruments | CLA
Message 4 of 4
(279 Views)
Reply
This is an open group. Sign in and click the "Join Group" button to become a group member and start posting.