Deployment error while running UDP Custom Device alongside with Ballard Arinc 429 CD

[CoderMad]

Hi Team,
In my use case, I'm using UDP Custom Device in integration with Ballard Arinc 429 CD. In this scenario, I'm getting an error during deployment (mentioned below). This error is not popping if I deploy UDP CD alone. Can you guys pls share your comments on this error and any possible workaround would help. I'm also sharing the Veristand project files incase of recreating the issue

UDP_Arinc429_Integration_Testing.zip

[ryanvallieres]

Hey @CoderMad

My apologies for not seeing this issue sooner! At some point my email filters appear to have gotten overzealous and eaten this update - that said, I spoke with a colleague today and I think we know what the issue is. For one, a relevant issue where I addressed this previously:

#21

To summarize, it's extremely likely that the UDP Custom Device and the Ballard ARINC CD both rely on different versions of the same back-end libraries. Since Veristand uses libraries to deploy code (and therefore doesn't conveniently namespace things in a way that prevents these collisions), we run into cases where either codebase could. It just so happens that the ARINC CD is loading in "first" here.

Your best bet here is to pull down the project source code and recompile the custom device engine with a custom pre-fix or post-fix enabled on every VI. You can do this in the project build specification settings - there should be some LabVIEW help docs on the subject or a forum post floating around that addresses it. Let me know if this fixes your problem.