Fault Insertion Units Add-On Feedback Forum

[RyanZoeller]

Hi Andrew,

I'm not very familiar with the details of the custom controls this archived custom device provides, but it appears they are just settings the channel values to the underlying typedef values.

You should be able to recreate this functionality in the VeriStand 2020 screens using a ring control, although I don't believe this custom device provides the data needed to populate these fields automatically. You would need to manually configure them.

That said, we are encouraging new applications to use the Routing and Faulting custom device, which recently gained support for NI-SWITCH hardware through the NI-SWITCH custom device. These custom devices are officially supported, and the R&D team actively monitors the repository on GitHub for issues. If your application does not need high-speed switching, these custom devices are likely a better choice than the Fault Insertion Units Add-On.

Best,

Ryan Zoeller

[~Andrew~]

Hi Ryan,

Thank you very much for your guidance!

I've switched to pursuing the use of the Routing and Faulting Custom Device to control my FIU, but am struggling to map the Source and Destination when creating a Routing Channel.

I ran the Configure Routing and Faulting Custom Device.vi from the <Git Hub repo>\Source\Scripting Examples and it generated a System Definition file (Scripted Routing and Faulting.nivssdf) which I was able to load into VeriStand 2020 and study. However, this example System Definition file seems to be mapping Routing Channels within an SLSC Chassis. In my case, I'm using a PXI chassis with a PXI-2510 and PXI-2512 card. Specifically, my issue is that when I create a new State and attempt to use the Configure Connection window to add a new connection, the Module, Source, and Destination lists are empty.

Thoughts or suggestions on how to assign the PXI-2510 card that I can see under Targets-> Controller->Hardware->Chassis->DAQ to the Routing and Faulting Custom Device?

Thanks!

-Andrew