Restrictions for Boolean data type in Custom FPGA

[RishiDivakar93]

Hi All,

I recently underwent a training for Custom Devices and Custom FPGA for Veristand. During which, while mapping the digital signals directly as Boolean values, the trainer told us to configure the input as numeric FXP(min 0, max 1) and after comparison if it's zero, the value will be passed to Veristand XML builder. When I asked him about it, he said the Boolean values have some restrictions which I didn't understand. Can anyone please explain why there's a restriction.

Regards,

Rishi

[PlatypusRex · Accepted solution]

VeriStand out of the box can only accept the doubles data type as is, and the FPGA XML custom device may just have restrictions in it's architecture as far as what data types it's configured to handle and convert over to VS. Instead, I recommend using this:

https://github.com/NIVeriStandAdd-Ons/FPGA-Custom-Device

It's way easier to use- no mucking about in the XML. Just build your FPGA code as usual, make your i/o front panel objects, add an interrupt, build a bitfile, and import into VS. I described the interrupt part a bit more here: https://forums.ni.com/t5/LabVIEW/NI-PXIe-7820R-fpgaconfig-and-lvbitx-file-are-missing/td-p/3876118

I used this add-on first and then tried the XML method once to see what it was like. I got partway through after an hour or so, then trashed it and put together a bitfile with this add-on in a few minutes.

JHP