01-25-2006 10:32 AM
01-26-2006 02:36 PM
Hi AMR-
This problem is most likely seen in versions of VI Logger 2.0 when LabVIEW 8.0 (or any device driver that installs MAX 4.0) is installed. To correct the problem you will need VI Logger 2.0.1. This is the "VI Logger Lite" download, so you will need to install the Lite version and then activate with your serial number. Please give this a try and let me know if you run into any other problems.
Hopefully this helps-
01-26-2006 09:49 PM
Thank you Tom!!
I did it exactly as you recomended and the new version works perfectly..!
Thank you very much for your help.
Alexander
01-27-2006 08:20 AM
Hi Alexander-
I'm glad to hear you're up and running- let us know if you run into any other problems. Thanks!![]()
02-17-2006 05:06 PM
02-18-2006 12:04 AM
Howard:
Sincerely, I can understand your exact frustration...
This is not an optimistic message, and I am sorry for that, but my experience with VI Logger has been the exact opposite of what I initially expected from National Instruments... And expensive, by the way...!
However, I don't consider the hardware (6009) is bad... I am trying to figure out what is the prtocol it uses in order to drive it from an application developed by me and based in a microcontroller with USB interface...
I wish you better results
Alex
02-20-2006 01:59 PM
Hi Howard-
It sounds like you are running into an inexplicable problem with creating tasks in VI Logger. Are you able to create NI-DAQmx Tasks under Data Neighborhood? This can be done by right-clicking (in MAX) and choosing Create New>>NI-DAQmx Task. Would it be possible to test on another computer and see if you can replicate the problem there?
If you see a crash screen again, please do generate an error report and send it to NI as this will make it much easier to diagnose the problem.
08-01-2006 09:45 AM
08-17-2007 01:22 PM
I am trying to use a USB-6009 and a cRIO-9211 via USB. Both worked in the past with VI-Logger on this computer. But when I hooked everything back up, I started getting the Error 4501 exactly as reported at the beginning of this thread. I had installed a USB-8451 (I2C interface) recently, and figured it must have put new stuff on the computer that broke VI-Logger. So I downloaded 2.0.1 as suggested and installed it.
Now I cannot do anything. My NI-DAQmx tasks in MAX now all have big red X's and when I try to test a task that worked 1 hour ago, I get "Error -89130 occurred at DAQ Assistant". At least before, it found the USB devices and could run the task test mode. This is driving me nuts. By now I could have recorded the test results on paper and been finished. Can anyone suggest what might be wrong?
James