12-16-2022 08:20 AM
I understand that the old "in port.vi" and "out port.vi" haven't been supported for a while. When I run my old vi which uses "in port.vi" and "out port.vi" to access the Intel processor's memory mapped I/O, I get a -4850 error and the knowledge base suggest I use NI-VISA.
Error -4850 in LabVIEW Using Port Out or Port In - NI
I've searched for examples and descriptions on how to use NI-VISA to accomplish this unsuccessfully. Any guidance would be appreciated.
Solved! Go to Solution.
12-16-2022 10:35 AM
I guess it's more a Windows security issue than a LabVIEW issue…
Since Windows Vista "user priviledge" programs are not allowed to directly access specific memory areas, like it was allowed for InPort/OutPort on old WinXP systems. This is only allowed for driver software running in the "kernel context" after successful installation (using signed certificates).
So the question is: why do you need this feature on a modern Windows with a (hopefully) modern LabVIEW version?
12-16-2022 10:49 AM
Yes I'm running LV2020 on a Win10(32-bit) machine which has embedded digital I/O and analog to digital converters. We are transitioning away from this embedded technology but I'm hoping to maintain my LV application's compatibility between this old tech and the new. The boards are Versalogic EBX38.
12-16-2022 11:10 AM
unfortunately Versalogic only allows to download manuals after registration.
But hey: they offer Win10 compatible "VersaAPI"!
So I guess Versalogic already explored a way to provide IO access for their board even from Win10 user-priviledge programs. All you need to do is to follow their documentation and use their APIs…
12-16-2022 11:13 AM