07-17-2006 10:15 AM
07-17-2006 10:26 AM
Do any of these
help?
If not, tell us a bit more about your setup.
David
07-18-2006 08:14 AM
Hi,
what version of LabVIEW are you using?
What version of NI-VISA are you using?
Sometimes just upgrading the VISA can fix issues like this very generic one. You can get the latest version from here (licenseing permitting) :
http://digital.ni.com/softlib.nsf/websearch/78C0C40D1DDE95F8862571550050B9B1
We've also seen on the discussion forums where the instrument that's being talked to can be the cause of the problem - would it be possible to try a write, then a read, but with pins 2 and 3 (transmit and receive on an RS232 port) linked together rather than connected to your device? You should read back exactly what you transmitted then, and it removes the instrument as the cause of the problem.
Thanks
Sacha Emery
National Instruments (UK)
07-18-2006 08:35 AM
07-19-2006 03:53 AM
Hi,
you say "retrieve" the instrument - what do you mean - unplug it?
The PT104 from Pico-tech has got LabVIEW drivers and this may be an easier way of interfacing to it than going to the low level calls. Since the actual error only seems to appear when the device is plugged in, is the com port settings matching the settings required by the pt104 data logger?
http://www.picotech.com/drivers.html
Does the PICOlog software work OK?
http://www.picotech.com/software/beta/package/PicoFull_r5_14_4.exe
According to another discussion forum, you already have this, so do they work?? (you may need to re-install this to get the software for LV 8.0 support)/
Thanks
Sacha Emery
National Instruments (UK)
07-19-2006 08:52 AM
07-20-2006 03:22 AM
07-20-2006 04:29 AM
Hi,
what are the serial port settings you're using - do they match what the PT104 requires?
It may be that the drivers change the default serial port settings to match what they require. It's even possible that the settings change on the fly - something would have been programmed into the driver if this were the case - it's rare that manufacturers do this, however there's atleast one case of this on the discussion forums that I've seen.
If you can find those settings, then you can start dealing with the information coming back. If not, then you can't really establish correct communication.
Personally, the reason for "want to go lower level" isn't that good a reason. Needing to go lower level for speed / memory performance related issues would be, however if the driver works, then I'd recommend you just use it. If it doesn't have the features you need, then a better option would be to use the programmers reference manual for details on how to approach the communication which you're only going to get from the manufacturer of the hardware.
Thanks
Sacha Emery
National Instruments (UK)
07-20-2006 04:30 AM - edited 07-20-2006 04:30 AM
Message Edited by David Crawford on 07-20-2006 10:31 AM
07-20-2006 05:37 AM