Kamran Posted February 4, 2018 Share Posted February 4, 2018 64 Bit LabView 2017 DLLs are not available anywhere. 32 bit DLLs all generate errors. Is there a solution for this? Best Regards... Kamran Link to comment Share on other sites More sharing options...
JColvin Posted February 5, 2018 Share Posted February 5, 2018 Hi @Kamran, I'm not certain what you are referring to; Digilent sells the LabVIEW Home Edition for LabVIEW 2014, but we don't have any advice for LabVIEW 2017. NI's LabVIEW forum may be a better place to ask your question to receive more accurate help on this. Thanks, JColvin Link to comment Share on other sites More sharing options...
Kamran Posted February 5, 2018 Author Share Posted February 5, 2018 Many thanks JColvin, I want to use an array (about 8) Digilent Analog Discovery modules controlled by LabView 2017 64 bit. The current LV drivers downloaded through VI Package Manager come with DLLs that work only on 32 bit LabView. There is no utility to convert 32 bit DLLs to 64 bit DLL, so I am stuck. What is needed is taht someone with access to the DLL source-code recompiles them for 64 bit LabView and publishes them. Then all versions of LV could control the units. Best Regards.... Kamran Link to comment Share on other sites More sharing options...
attila Posted February 6, 2018 Share Posted February 6, 2018 Hi @Kamran The WaveForms runtime installs both, 32 and 64 dwf versions for 64 bit Windows. https://forum.digilentinc.com/topic/1682-error-running-example-python-script-for-analog-discovery/?do=findComment&comment=5624 https://forum.digilentinc.com/topic/8798-labvew-executable-and-ad2/?do=findComment&comment=26534 Link to comment Share on other sites More sharing options...
StuE Posted October 15, 2018 Share Posted October 15, 2018 I had this same issue with XP and 64-bit Labview 2017. I have waveforms installed and the installed both the waveforms and AD2 packages via the package manager. Weirdly, if I try to run anything from AD2 it doesn't work, but if I just open a vi from waveforms and THEN open an AD2 vi, it works fine. I'm concerned if I write a vi using AD2 packages it will randomly throw errors because of this behaviour. Has anyone else seen this? It didn't happen with 32-bit Labview 2017, so I assume it's related to the 32-bit vs 64-bit issue Kamran is seeing. Kamran, can you try to see if you get this too, please? Link to comment Share on other sites More sharing options...
Question
Kamran
64 Bit LabView 2017 DLLs are not available anywhere. 32 bit DLLs all generate errors. Is there a solution for this?
Best Regards... Kamran
Link to comment
Share on other sites
4 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.