Communicate via RS232

[Cory_K]

So if I plug in this device into the serial port in my computer, where can I find it.

I'm not sure what the computer will call it, or what COM port it will assign it to (if that's what the computer does)

I'm not terrible at communicating with the device once I have my LabVIEW program recognizing the device.

Setting up the device so it is recognized is the hardest part for me.

[Dennis_Knutson]

---

Cory K wrote:

So if I plug in this device into the serial port in my computer, where can I find it.

I'm not sure what the computer will call it, or what COM port it will assign it to (if that's what the computer does)

I'm not terrible at communicating with the device once I have my LabVIEW program recognizing the device.

Setting up the device so it is recognized is the hardest part for me.

---

You can find the device at the end of your serial cable.

MAX will not call your device anything. It doesn't even know that it is there. The only thing that MAX knows about serial is whether there is a com port or not and what the default settings for it are. The actual com port number is assigned by windows but it is something that you can change as long as the name does not conflict with another port. You are the one that assigns the device to a port when you select wwhich port to plug it into.

Can you explain exactly what you mean by LabVIEW recognizing the device? As I said, MAX and the VISA Resource Control only recognizes serial ports.

[Song_M]

Hey Cory!
Dennis is completely right.  Serial Protocal has no protocal for device identification; thus, unlike GPIB, you won't be able to see the device in MAX.  What this means for us is, as long as you are able to use Hyperterminal to communicate with the device as outlined previously, you will be able to use basic serial example VIs to communicate with the device as well.  Once you get to that point, you can then start working on developing a driver.  Hope this helps!

[Cory_K]

Well in case anyone was wondering, I finally got this thing working.
The problem ended up being I had a regular DB9 RS232 cable instead of a null-modem cable.
This made it so the Transmit and Recieve pins weren't connected.

Anyways, now at least I can communicate with the device.
Thanks for all of your help everyone.

- Cory

[Ray.R]

It is amazing how many times a serial communication problem is related to the cable. 🙂

[AnalogKid2DigitalMan]

That's why I always use wireless serial adapters!