Here's a newbie mistake:
When wiring to a sequence structure with multiple frames in order to create data dependency, be careful which frame you wire to.....
Following code shows a construct which lead to a deadlock in my code because the first frame of the sequence does NOT wait for the dequeue primitive...... This is actually something I never knew. If I place an "Acquire semaphore" in here.... 😞
Duly kudo'd. After programming LV for so long and dealing with forcing data dependency between structures, I never thought of even looking up the help on this because it was so obvious to me that it would work as I *thought" it should.
So another day, another thing learned.
When working with FPGA nodes on a RT system where the FPGA card is installed locally (no network access required) make sure you wire a local Alias for the "Open FPGA Reference" primitive otherwise you'll see large differences in performance as the network stack will be involved for no reason.
I was testing DMA speeds when I cama cross this. Testing speed of a U32 DMA to a local FPGA card was nearly 4 times (!!!) slower with the first option than the second. For a single element insert, the first one took a whopping 26 microseconds whereas the second took 7.1 microseconds.
Apparently the Reference used for FPGA nodes is not checked to see if it is really a local reference when opened.
On a related note:
I'm pretty sure I looked through the help.... I did not find a suitable explaination for this Right Click option ....
It seems like minutia that will bite visciously if angered.
Has anyone trained this dog to do tricks?
There are threads upon threads of what to do when an application build fails due to "error 8." Not a single solution I found on here worked for me, none of the knowledge base articles etc. Found this post here, and a simple control+shift+run arrow fixed all my problems. I understand this is not functionality related, but it seemed reasonable to post here. Hopefully it saves someone from the hours that I spent trying to figure this out...
Why did my config keep trying to load even when an empty path was wired up to the input? Oh, because file or folder exists returns TRUE on an empty path. Is there some computing reason for this?