10-28-2003 07:57 AM
10-29-2003 05:42 PM
07-13-2009 02:18 AM
07-13-2009 10:09 AM
This thread is quite old, so you may want to start a new thread.
There are still no drivers for that on IDNet, so if the manufacturer does not provide drivers then you will either have to hire somebody to write drivers for you or you will need to write them yourself. If you have to write them yourself then you should start by making sure you can even talk to the instrument. Start by using something like HyperTerminal (if you're on Windows). This will make sure that you can communicate with the instrument. Then in LabVIEW use the Basic Serial Write and Read example to try to do the same thing.
If you have not already done so, it is recommended that you go through the tutorial(s) and look over the material in the NI Developer Zone's Learning Center which provides links to other materials and other tutorials. You can also take the online courses for free.
07-13-2009 10:52 AM
Here's the manual for the RS232 option- includes wiring and command codes and response formats:
http://www.gesensing.com/downloads/manuals/K086B-Is1.pdf
-AK2DM
07-13-2009 09:08 PM
Thanks i have manual for the RS232 option ,
I try it HyperTerminal about K086B-Is1.pdf all control code still no response, link parameters
Address:16 ;
Terminator:<CR> ;
Mode:Direct ;
Baud Rate:9600 ;
Parity:none ;
Output Format:Computer ;
Printer "N" value:1 ;
End Device:No
07-13-2009 10:17 PM
Are you sure you are using the right kind of cable? The wiring diagram on page 7 makes it look like you should be using a null modem cable.
In hyperterminal, are you sure which character is being sent? Page 16 says that sending a carriage return will return the latest reading. However, depending on the settings in Hyperterminal, it is possible it is sending a line feed, or a line feed, carriage return combination when you hit the enter key.
07-14-2009 01:43 AM
07-14-2009 08:26 AM
The manual is rather poor in that page 7 really doesn't state whether those pinouts are DB25 or DB9. But I saw that the pin outs are the same between both devices. (Pin 2 is transmit on both and Pin 3 is receive on both). And that they have pin 2 wired to pin 3 each way. Likewise for pins 4 and 5. That is a null modem cable. Thus a straight through cable will not work.
Handshaking is a method for the two devices to tell each other when they can send data and when they can't send data. So if the receiving device's serial buffer fills up, it will either send a byte (XOFF) or set the CTS line to tell the other device to stop sending data. When it has room again, it will either send another byte (XON) or set the CTS line to tell the other device to start sending again. If it uses bytes, that is software handshaking. If it uses the CTS line, that is hardware handshaking. Make sure which way your instrument is set, you do it the same way on the PC side.
07-15-2009 11:35 AM
We have a Druck pressure controller and we had to write our own drivers. Sorry I can't send it to you, it is proprietary. You can write your own using the serial commands listed in the manual. Use VISA instead of Serial functions in Labview. You should get it to work with Hyperterminal first to verify a good connection. The serial port uses standard wiring, so a 25-pin to 9-pin adapter should be OK. Don't use any handshaking at all, set to none. There normally isn't enough communication to overflow a buffer in this instance. Usually you just send a command and read a response. Make sure the baud rate, stop bits, parity, etc are all set correctly.
When using Hyperterminal, do you see any response at all, even garbage characters? If not, your wiring may be faulty. If you see some response, then your settings (baud, parity) are incorrect.