Distributed Control & Automation Framework (DCAF)

cancel
Showing results for 
Search instead for 
Did you mean: 

migrating from older version?

Hi,

I have a project developed in an older version of DCAF from back when it was called Tag Bus.

 

I did not develop this, but I am going to be maintaining it. I have two challenges, one immediate and one long term.

 

The immediate challenge is how to modify the config file. If I try to open it with a more recent version of DCAF, I get an error. Specifically Error 1527 occurred at Unflatten from XML... I presume a class or cluster has changed causing the unflatten to fail.

 

Are the previous versions available for me to install?

 

The long term challenge is migrating this project to a more recent version of DCAF. Has anyone tried this? Is there a guide to this somewhere?

0 Kudos
Message 1 of 6
(4,495 Views)

In regards to installing previous versions, it looks like you may be able to pull the old TBDF from the following archived post. You may also be able to comb through older commits on the DCAF github for specific module versions.

 

https://forums.ni.com/t5/Archive-TKB/Downloading-the-Tag-Bus-Data-Framework/ta-p/3545020

Matt J | National Instruments | CLA
0 Kudos
Message 2 of 6
(4,488 Views)

Hi Jacobson,

 

When I follow that link I get an access denied web page.

 

I will check github and see how far back it goes.

0 Kudos
Message 3 of 6
(4,486 Views)

Here is a github release which I think is the same thing.

 

https://github.com/LabVIEW-DCAF/LabVIEW-DCAF.github.io/releases/tag/2.0

 

it may at least give you a starting point.

Matt J | National Instruments | CLA
Message 4 of 6
(4,483 Views)

That link allowed me to open the config file. Now at least I can recreate the config in a later version.

 

Any thoughts on migrating modules?

0 Kudos
Message 5 of 6
(4,475 Views)

H cgibson, You can migrate old modules to DCAF but that will force you to do some relinking of the classes. Many names are the same but with DCAF instead of TBDF in the name.

In general, an easier option would be to create a new module with the new templates, and update the content inside of the overrides with the ones in the old module. For example, the input of one module will be very similar between the 2 versions, and it will be easier to move code from one to the other rather than going through all the relinking. 

Best Regards

 

Benjamin C
Principal Systems Engineer // CLA // CLED
0 Kudos
Message 6 of 6
(4,426 Views)