06-17-2020 09:24 AM
I don't fully understand what triggers this condition. But I've seen times when the Compound Arithmetic node with one input, and the error data type showing a broken wire, but the VI can be ran.
The VI does actually run, but the wire shows it is broken. Attached is the code saved in LabVIEW 2020 that reproduces the error.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
06-17-2020 09:35 AM
Single input Compound Arithmetic seems crazy to me (but I see why you did it). I'm not surprised that it's buggy.
I would just replace it with an unbundler.
06-17-2020 09:47 AM
I often use single input Compound Arithmetic to perform inversion - either numeric (1/x) or boolean NOT. It's more compact than the native functions so it fits between wires when I place it inline between subvi's that use all 4 standard outputs and inputs (a.k.a. gazottas and gazintas).
No insight on the visual bug, I've never had it happen.
-Kevin P
06-17-2020 10:27 AM
Yeah I hope the demo VIs shows why you might want a feature like this, even though it seems an odd choice at first. There are probably a dozen other ways to accomplish something similar, but this seemed logical to me. Yes the unbundle would work just fine, but it is a bit smaller on the BD and I couldn't see a reason why it shouldn't work.
Also it probably shouldn't surprise anyone, but the old band-aid of Always Copy fixes this graphical issue.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
06-17-2020 12:52 PM
@Hooovahh wrote:
Also it probably shouldn't surprise anyone, but the old band-aid of Always Copy fixes this graphical issue.
For we Newbie's, can you please explain what "Always Copy" means? I don't think I've (probably because I'm not quite as inventive) the problem you're describing, but I also occasionally "squeeze" functions in between wires, so might want to avail myself of these nifty ideas, but don't know where to find the band-aids ...
Bob Schor
06-17-2020 05:56 PM
@Bob_Schor wrote:
@Hooovahh wrote:
Also it probably shouldn't surprise anyone, but the old band-aid of Always Copy fixes this graphical issue.
For we Newbie's, can you please explain what "Always Copy" means? I don't think I've (probably because I'm not quite as inventive) the problem you're describing, but I also occasionally "squeeze" functions in between wires, so might want to avail myself of these nifty ideas, but don't know where to find the band-aids ...
Bob Schor
Check the Application Control >> Memory Control Palette
Always Copy will make a data copy of what is contained on the wire.
mcduff
06-18-2020 08:45 AM
Yeah I was keeping a list of times the Always Copy fixed a weird bug, or edge case. But after a while I realized keeping a list of the primary feature of a function seemed silly.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
06-25-2020 07:30 AM
Can someone from NI confirm this bug? Assign a CAR?
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
06-29-2021 01:49 PM
I've created Bug 1518595 to track this issue.