Showing results for 
Search instead for 
Did you mean: 

Parallel Access DVR Bug - LV2017


Admittedly I'm tired so I could be missing something VERY obvious. If so, hope someone could at least confirm they are seeing the same behavior and explain it. I'm in disbelief that this is a bug because there's nothing subtle about it. Someone just needs to explain to me why this is normal and expected behavior and then I'll promise to get a good night's rest and start tomorrow a fresh day.


I'm using LV2017 f2 32-bit on Windows 10 64 bit.

0 Kudos
Message 1 of 5

I'm using LV 2014 so I can't configure for read only access, but it looks to be a bug.

CLA // LabVIEW 2016 // BALUG // Unofficial Forum Rules and Guidelines
0 Kudos
Message 2 of 5

Confirmed on my 2017, it seems the "Read only" still writes and thus empties the data.


G# - Award winning reference based OOP for LV, for free! ADDQ VIPM Now on GitHub
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
0 Kudos
Message 3 of 5

After confirming this in my LabVIEW 2017 as well, I did some searching and found that R&D is aware of this issue. Unfortunately there's not a listed workaround right now. The CAR number is 663379, so keep an eye out for future patches/releases for a potential fix.

Claire M.
Applications Engineering
National Instruments
Certified LabVIEW Developer
Message 4 of 5

As discussed in the LAVA crosspost thread, a well placed Always Copy seems to fix this until there is an official fix.

Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
Interesting in learning all you can about automotive CAN bus communication? Checkout my 12 part CAN Blog series.
Checkout and help contribute to the community driven LabVIEW Wiki.

Message 5 of 5