11-10-2009 01:47 PM
I am trying to program a SeaDAC Lite model 8126. I had it working but had some changes. I am having some trouble with the variables. The number and what representation they should have. Here is a link for the Sealevel API http://www.sealevel.com/software/seamax/seadaclite_8126.html. when I try to import the DLL I configure them like i think they should be but i get errors from the device saying that it could not read VID or PID. I used NI visa wizard to create a visa that NI can use, and i am able to see it in NI MAX.. I did get it towork fine but was unable to save it so I lost the data. So I am trying to redo my mistakes see if i can get it working again.. Another thing when I get the open working I get an invalid handle. SO PLEASE HELP ME.. I am a new user to Labview ... currently using version 8.6 ..
One thing is that the SM_HANDLE= void*
thanks
11-12-2009 06:50 PM
Hello Ingenibro,
This sounds like you are trying to interface with a .dll which is more of a LabVIEW issue than a hardware issue. I am not sure that this forum is the best location to get the help you need. I am guessing that 1. The LabVIEW forum might find you more help and 2. that the error you are seeing is because you a passing a bad parameter to your .dll. Please make sure that you know what you actually need to pass and that you are passing data in the proper data type.
Also, just so you know, NI-VISA is a driver that is used to interface with hardware, not dll's (software).
11-18-2009 11:28 AM
thanks for the heads up. I have contacted NI and the vendor SeaLevel. Seems that it is something with labview I have been having some issues with the visa where some times the computer device manager does not like the NI visa, making me have to reboot the computer, or reinstall the NI visa driver. I have checked also with the vendor, about the parameter and seems that they are fine the way that i have them. I had this program working previously and now seems that something is not working between the program and the hardware. I am thinking that there is some type of communications failure. I have also installed Snooper.exe, to monitor the interaction between the USB device and the program seeming since NI spy does no support RAW USB interaction. the only change that i have had was a change in labview from 8.6 to 2009. I dont have the option to purchase another USB device at the moment. So i was wondering if anyone has seen some similar way of programing it. I had gotten a sample VI from Sealevel and its pretty straight forward. that is why i have considered using the .dll file for programming.. if you want to take a look its attached to the forum. I have attached also a flow of what i want to do and also has the methos that the parameters are put in missing imported .dll vi's which was one thing that got messed up on the change of software.
11-19-2009 07:12 PM - edited 11-19-2009 07:12 PM
Hello Ingenibro,
I will recommend again to post this in the LabVIEW forum if you do not get much success here. If this worked in one version of LabVIEW, but is no longer working, there are users and other employs here that would know a lot more of the intimate details of LabVIEW and can help you work through what might be happening. As it is, you have a number of cascaded Call Library Nodes all calling to the same dll in the "SeaMAX" vi, and I am not completely sure, but I think you should be able to combine all of that into just one call library node by passing parameters in the Call Library Node. Anyone else have thoughts on this?
11-23-2009 09:56 AM
11-24-2009 02:08 PM
Ok Sorry for the Delay Finally together with Sealevel, I finally have a complete program. There were several things that were wrong.
1. With the new version of NI MAX installed all my driver information was deleted. Which anyways resulted in me not needing it for this driver.
2. My fprogram was working correctly, but since I was using the wrong driver the software could not read or see the hardware.
3. Error check on the software created a conflict with the hard/software flow. So was removed and relied on .dll error checking.
4. Usb device flow must be correct. Timing is no issue unless there are time constraints, then add delays other wise try it will function at the speed that your computer lets you work.
5. Finally if you encounter an error whether it be hardware or software then you must. Then you must remember to unplug and replug device in, seeming that it will stall your program, if not shut it down.
Thanks for the assistance from the ppl at NI and Sealevel. I have all of you to thank for helping me complete my program with the time constraints.
I will be adding all the required software with images to the forum in order to help anyone that might be lost for future reference.
11-30-2009 11:14 AM