LabVIEW FPGA Idea Exchange

About LabVIEW FPGA Idea Exchange

Have a LabVIEW FPGA Idea?

  1. Does your idea apply to LabVIEW in general? Get the best feedback by posting it on the original LabVIEW Idea Exchange.
  2. Browse by label or search in the LabVIEW FPGA Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  3. If your idea has not been submitted click New Idea to submit a product idea to the LabVIEW FPGA Idea Exchange. Be sure to submit a separate post for each idea.
  4. Watch as the community gives your idea kudos and adds their input.
  5. As NI R&D considers the idea, they will change the idea status.
  6. Give kudos to other ideas that you would like to see in a future version of LabVIEW FPGA!
cancel
Showing results for 
Search instead for 
Did you mean: 
EricLM

For loops inside SCTL should support Number to Boolean Array and Boolean Array to Number

Status: New

Number to Boolean Array and Boolean Array to Number along with array manipulation functions (index, replace, reverse) are commonly used methods in FPGA for doing bit manipulation on arrays of integers inside SCTLs. Not having access to these functions is prohibitive and results in having to write code like this:

image.png

This becomes very unwieldy when dealing with arrays of 20+ elements. If Number to Boolean Array and Boolean Array to Number are truly no-op elements, then they (along with basic array manipulation nodes) should be added to the list of supported nodes inside for loops inside SCTLs.

2 Comments
T-REX$
Active Participant

Hey Eric,

 

Good news, I believe what you're asking for here made it into LabVIEW 2020. I was able to compile the following diagram this morning:

 

ArrayFuncInForLoopInSCTL.png

 

Kind of a random test, but I wanted to get most of the nodes I believed to work in the build. Would you like to try it out for yourself or see anything else before I contact the forum owners to mark this idea as implemented?

Cheers!

TJ G
EricLM
Member

Thanks for that comment TJ. Unfortunately, it doesn't help me much. Many of my customers are gov't contractors and they move slowly to adopt new LV versions. The projects where this will help me likely won't move to LV 2020 for another 6-12 months. I only just recently installed LV 2020 on a development machine for work on a non-FPGA project.

 

I know the answer is likely no, but is there any way that this can be applied to older versions through a patch? Having to wait 1-2 LV versions (years) after an idea is submitted to see it enacted, then waiting another 1-2 years for my projects to catch up makes it hardly even worth my time to submit ideas.

 

Thanks

Eric