Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

how to configure usb-rs232 under linux!

Hi

I am using NI USB-RS232/4 and NI VISA in Suse. NI VISA has been installed succesfully. According a post in NI knowledgebase, serial ports should be added as static sources using visaconf program. When I added COM1(ASRL1::INSTR), it's ok. When I added COM2(ASRL2:INSTR), state of device was in  "UNCERTAIN" state and an error message displaied in NI SPY (see following figures). What's wrong?

Thanks


COM1
 

COM2
 

Message Edited by goldfox_79 on 05-07-2007 07:09 PM

Message Edited by goldfox_79 on 05-07-2007 07:10 PM

0 Kudos
Message 1 of 14
(7,742 Views)
I tried usb-232 convertere in windows. Everything is ok.

I found that when the converter is plugged in windows, READY LED will be on. But in linux, the light is never on.

I am using Suse 9.3 and I have installed NI-VISA.

Help me!

thanks
0 Kudos
Message 2 of 14
(7,698 Views)

Hi goldfox_79,

That's good news that the hardware appears to be working properly since it works with a Windows machine.  What version of the NI-VISA driver are you using on the Suse 9.3 computer?

Also, I didn't see what error is shown in NI-SPY (and the image attachments were too blurry for me to really read..).  From your first post it sounded like the first com port was added successfully - if you just add this first port, can you use it successfully?  Thanks!


Regards,
Anna M.
National Instruments
0 Kudos
Message 3 of 14
(7,683 Views)
Hi, Anna

Thanks your reply.

I am using Suse 9.3 and NI-VISA 4.1.0. When I tried to open ASRY2::INSTR in NIvisaic, an error message is displayed and status code is 0xBFFF011 (please click figures and zoom them in).

I tried the converted in Windows. It works. I can send command from Windows to another instrument using NIvisaic. But when I switch to linux and run NIvisaic again, it doesn't work. There is no data output from PORT1, PORT2, PORT3 or PORT4. I tried to bind the port with "/dev/ttyS#" "/dev/ttyUSB#", and it seems that only ttyS0 is allowed (in visaconf, when I select ttyS0, status of device is READY; for other choise, status of device is UNCERTAIN).

In Windows, when I plug in the connecter, the READY LED will be on. When I open a port in NIvisaic, corresponding PORT# LED will be on. But in linux, all LEDs are always off. Is it correct?

In linux, I only installed NI-VISA software. Is any additional driver needed?

Thanks
Mo
0 Kudos
Message 4 of 14
(7,678 Views)
I think I don't install the coverter correctly. When I unplug the converter, I can still find ASRL1::INSTR in visaconf. The port must be a port on motherboard.


Did anybody use USB-RS232 converter under linux? It will be very helpful to me if you can give me a giude of how to install and configure it.

thx
0 Kudos
Message 5 of 14
(7,627 Views)
Hi, Anna

Thank your reply. I uninstall NI-VISA 4.1 and installed 3.5, which is for SUSE 9.3. But after I add ports as static sources using visaconf. The state of device is always "UNCERTAIN" and I can not find any static source in NIvisaic.

How to configure serial ports in linux?
0 Kudos
Message 6 of 14
(7,588 Views)
No one has used usb-rs232 on SUSE 9.3?
0 Kudos
Message 7 of 14
(7,570 Views)
The device is not working because there are no Linux drivers for NI's USB serial products.  They are only supported in Windows. You can verify this in the product Data Sheet (although this is somewhat outdated as Vista is not listed).

-tuba
0 Kudos
Message 8 of 14
(7,512 Views)
Thanks your reply, Tuba

But I found an article about how to configure USB-232/4 in Linux in NI knowledgebase, here
0 Kudos
Message 9 of 14
(7,499 Views)
Hello goldfox_79,

The wording in this knowledgebase is actually not correct, as it is not referring to NI USB-232 interfaces. NI USB-Serial interfaces require specialized drivers which are currently only available for Windows.

I believe the intent of the knowledgebase was to explain how to use VISA with 3rd party USB-Serial adapters in Linux.  The instructions in the knowledgebase appear to be correct if you already have an appropriate Linux driver installed for your hardware.

I apologize for the confusion, and will see the the knowledgebase gets updated appropriately.

Jason S.
NI-Serial Software


0 Kudos
Message 10 of 14
(7,483 Views)