Conversión usb-rs232

He adquirido recientemente un conversor usb-rs232 para mi ordenador portatil (Prolific usb-to-comm). He instalado el programa Niser310 que he descargado de la página de National Instruments. De esta forma, he conseguido mandar datos por mi nuevo puerto serie. Estoy controlandormediante este puerto el Generador de funciones HP-33120A
El problema que tengo es que al enviar grandes cantidades de datos se produce el desbordamiento del buffer de recepción del generador, aunque tenga activo el protocolo de comunicacón hardware DTR/DSR (que es el que admite el intrumento). Este fallo es curioso porque cuando ejecuto el mismo código en mi ordenador de sobremesa este error no se produce, pudiendo enviar gran cantidad de datos sin problema.
Caracteristicas de la comunicación serie; velocidad 9600 baudios, 1 bit de inicio, 2 bits de parada, 8 bits de datos (no paridad), COM1, tamaño del buffer 1Kbyte.
Sistema Operativo Windows XP, LabVIEW 7.0.
Alguien me puede ayudar... Muxas Gracias.-
Mensaje editado por fran_m
Adjuntos:
Simulación de perturbaciones en la red.vi ‏412 KB
Subinstrumentos.zip ‏81 KB

Hola Fran el problema es posible que sea por los limites de tu adaptador serial, o la version de drivers que estas utilizando. Prueba Descargar una version mas actualizada de los drivers de tu adaptador, esto puede corregir el problema.
Saludos
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

Similar Messages

  • DAQCard6024e & USB-RS232 Conflicts?

    Has anyone had problems using both a DAQCard-6024E in a notebook computer
    that also uses a generic USB to RS232 converter? We've had several
    instances in different computers and different USB-RS232 converters where
    not long after installing and using the USB-RS232 converter the computer
    locks up and will not reboot, even after removing power and the battery!
    It does not seem likely that these two devices would conflict but we cannot
    find anything else common that would cause the problems we are seeing. If
    there is a conflict and buying an NI USB-RS232 converter would solve the
    problem then I'd be willing to spend the $150 for the NI converter but I'd
    like to know that this will fix the problem first.

    Duplicate question. See post at http://forums.ni.com/ni/board/message?board.id=250&message.id=11456#M11456

  • CRIO 9067 to recongnize SiLabs USB RS232

    Hello,
    I have a cRIO 9067 and would like to interface to an instrument that has a SiLabs USB-RS232 converter.  I can comminicate with this instrument easily on a Windows PC.  I am able to see the device in MAX when its connection the cRIO.  IT shows up under "Devices and Interfaces" as "USB0::0x1FB9::0x0100::121A00A::RAW"  with the Model number and the device description.
    I've followed the description at this link, but I don't get a ttyUSB# devices.
    https://decibel.ni.com/content/docs/DOC-34827
    Is there any chance to get this working on the cRIO as a serial port?
    Thanks.
    Solved!
    Go to Solution.

    After some digging, talking with NI Folks, google, and Talking with Folks at lakeshore.com (device vendor) here's what I've piece together on how to get this to work:
    In Linux, usb devices are enumerated automatically, and, by default, will show up as a USB RAW device
    Once the USB device has been enumerated, it can then, subsequently be linked to a driver
    Linux determines if and when to link each USB device based on the Device's on Vendor ID (VID) and Model ID (MID). These are typically 3-4 digit hex strings.
    For the case of the Lakeshore 121 current source, VID=1FB9 MID=100.       I could see these in MAX for the USB Raw Device.
    There are two levels of drivers for USB-Serial Devices. The first driver: usbserial.ko is a generic driver that handles all USB-Serial devices. This must be loaded for all USB-Serial converters.
    The second driver is specific to the chipset of the USB-Serial device.       For the cRIO, there are three options that are pre-installed (FTD, SiLabs, and some other)
    The drivers reside at       /lib/modules/3.2.35-rt52-2.0.0f0/kernel/drivers/usb/serial/ (where the kernel version directory may vary)
    The Lakeshore 121 use the SI labs CP210x chipset, so we chose this one.
    The device drives first need to be loaded by Linux. Linux can automatically do this by adding zero length files to the module.autoload.d directory. To do this execute the following:
    cd /etc/modules.autoload.d
    touch usbserial
    touch cp210x
    reboot cRIO
    execute dmseg | grep usbserial to confirm that the usbserial driver is loaded
    execute dmesg | grep cp201x to confirm that the cp210x driver is loaded
    The next step is to associate our USB device with the cp210x device driver. Remember that linux associates the device with a driver based on VID and MID. Whomever installed the cRIO linux base, I'm sure, knew nothing about the Lakeshore 121 VID and MID.
    Lakeshore recommended getting the source code for cp210x, adding the VID and MID to the list of recognized devices, recompiling the cp210x.ko file and installing to the cRIO. This would work, but is beyond my current Linux capability.
    Linux gives the ability to dynamically add MID, VID so that a device can be recongized on the fly
    When the CP210x driver is loaded, an whole directory struchture is created. Ther is a file in that directory structure called new_id where we can dynamically added VID,MID's.
    Create a startup script to execute the following command. Be mindful of cr/lf line termination issues between operating systems. It's usually easier just to create the script on the cRIO with the VI editor to avoid any issues.
    echo 1FB9 100 >/sys/bus/usb-serial/drivers/cp210x/new_id
    Startup script info: https://decibel.ni.com/content/docs/DOC-38960
    Now on reboot (or execution of the script), you will get a /dev/ttyUSB[0-9] device
    Unfortunately, the default creation of the ttyUSB[0-9] device does not allow write permission, so we need to create a UDEV rule to automatically give write permission
    Add the following lines of code to udef.conf in the folder /etc/udev
    #typical devices
    ttyUSB[0-9]* root:tty 666
    Create a file named 99-ttyUSB.rules in the folder /etc/udev/rules.d
    Add this line of code to that file:
    KERNEL=="ttyUSB[0-9]*", OWNER="admin", MODE="0666"
    Reboot the cRIO. This should be it! It worked for me.

  • How to install USB-RS232 connector

    I want communicate zebra printer with USB-RS232 cable, somebody say, if i install the USB-RS232 connectly, it will appear virtual serial port in MAX, is it right? do i need to download NI-Serial driver?

    :-) congradulations

  • Adaptateur usb rs232

    Bonjour,
    J'utilise des adaptateurs usb->rs232 double ou quadruple (prolific)
    mais il m'arrive d'avoir des coupures dans la communication qui ne se produisent pas avec le port integré de la carte mere
    Est ce que cela peut etre du au ports usb de mon pc ou plutôt aux adaptateurs , j'ai essayé sur un autre pc avec des adaptateurs
    de la même marque et même probleme
    Avez vous deja constaté de genre de soucis, auriez vous des adaptateurs à recommander hormis les adaptateurs NI ?
    Cdt
    Tinnitus
    CLAD / Labview 2011, Win Xp
    Mission d'une semaine- à plusieurs mois laissez moi un MP...
    RP et Midi-pyrénées .Km+++ si possibilité de télétravail
    Kudos always accepted / Les petits clicks jaunes sont toujours appréciés
    Don't forget to valid a good answer / pensez à valider une réponse correcte

    Salut tinnitus,
    perso j'ai pas eu ce genre de soucis, mais j'ai constaté des tempo différentes dans la com en communication avec un même équippement : Par exemple un adapatateur A, je devais attendre 10ms avant d'avoir la réponse de mon esclave, et avec un adaptateur B, je devais attendre 50ms avant d'avoir la réponse. 
    J'ai déjà utilisé un convertisseur prolific, et je n'ai jamais eu de coupures de com...
    Bon courage a toi,
    V-F

  • Accesso a porta seriale con labview, scientific linux e interfaccia usb-rs232

    Ho un pc con SLC5, con interfaccia USB-RS232 e sto cercando di parlare con fieldpoint. Visaconf vede correttamente 4 interfacce (/dev/ttyUSB0, 1, 2, 3), mappate su ASRL1::INSTR .. ASRL4::INSTR.
    Se provo ad usare "Advanced Serial Write and Read.vi", va sempre in timeout.
    Se provo ad aprire "Optomux Send General Command.vi", lo trovo "rotto" (il parametro "VISA resource name" è connesso al "Port number" di "FPOptoHandler.vi".
    Mi manca qualcosa ? Oppure cosa c'e' di sbagliato ?

    Salve,
    provi a verificare la compatibilità con i driver al seguente link:
    What Linux Distributions Do National Instruments Drivers and Software Support?
    http://digital.ni.com/public.nsf/allkb/4857A755082E9E228625778900709661?OpenDocument
    e se il seguente esempio le risulti non corrotto:
    Programmatically Identify VISA Resource of cFP-1808
    https://decibel.ni.com/content/docs/DOC-23375
    Buon lavoro e buona giornata.
    A.P.

  • USB RS232/4 Driver for Windows CE

    I'm using USB RS232/4 device well with my laptop. I wonder whether i can use the device directly connected with Windows CE system instead of Windows XP system.
    I have LabView PDA Module and a single board computer operated by Windows CE.NET 4.2.
    Is there any driver of the device for Windows CE system?

    Windows CE is very different from Windows XP and currently the NI-Serial drivers is not supported on Windows CE. If you feel that this would be a valuable feature please file a product suggestion by going to Contact NI and click on the feedback link.
    -Josh

  • Using fieldpoint with scientific linux and USB-RS232 interface

    I am using a desktop PC with SLC5 and an USB-RS232 interface. I need to program a fieldpoint FP1000 module within labView. Visaconf is correctly seeing the interfaces (4 ports: /dev/ttyUSB0 .. 3, mapped as ASRLx::INSTR, with x = 1..4), but when I try to use "Advanced Serial Write and Read.vi", I always get timeout. If I try "Optomux Send General Command.vi", it looks broken (the parameter "VISA resource name" is connected to the "port number" input of "FPOptoHandler.vi" and the type is not matched).
    What am I doing wrong ? Am I missing some piece ?
    Thanks a lot in advance,
    Roberto Ferrari

    The people over in the GarageBand forums are amazing at diagnosing and fixing these sorts of things. I recommend that you give it a try posting the question over there:
    http://discussions.apple.com/forum.jspa?forumID=1308
    Good luck!

  • Mac Mini - USB/RS232 Cable - help to command display

    Could anyone help out with advice in a project where we would like to put a monitor in different modes from a Mac Mini.
    The interface for the commands to the display is a RS232 serial port. As Mac Mini has no RS232 port but there are USB to RS232 cables on the market our question is if one could use apple script or shell script to make the job?
    Would really appreciate any advice!

    this has absolutely nothing to do with scripting. you need a USB to serial adapter.

  • VISA error BFFF003E USB-RS232

    Hello, I try to communicate to a HP34401A DMM via RS232. I use a WhiteHeat USB-to-RS232 converter with 4 RS232 connectors. They are known as COM7 to COM10 (in NI-MAX ASRL4 to ASRL7). When I send a Basic I/O "*IDN?\n" I get the right answer but the error 0xBFFF003E occurs immediately. The LabView VISA write.VI also returns this error code. When I use a single USB-to-RS232 converter, everything works fine. Can anybody help me about this error code?

    Don't remember the exact error, but I've seen some USB-232 converters return errors when you try to configure certain serial settings. Try checking to see if the VISA Configure Serial is returning an error. Another, perhaps not ideal, solution is just to ignore the error. If the communication is really working properly, there may just be something out of specification which is confusing VISA, you could always just ignore the error (call clear error only if the error code is equal to that error).
    Regards,
    Ryan K.

  • Rs232 communications with usb rs232

    This is my problem. I am trying to log communication over rs232.
    I use an standalone laptop with runtime and a built application, installed on this is an usb to 4 rs232.
    I use the serial port read.vi.
    The only thing i get out is when i set the string indicator to /code. and then i get alot of number, letters and symbols.
    its not hex becuse hex isnt using %+ and )
    anyone got a solution to this or a even a guess.. i am running out of things to try.
    /Mattias

    What are you trying to log from?   Is it possible that the device that you are listening to is speaking binary and you may need to convert the format?
    Paul <--Always Learning!!!
    sense and simplicity.
    Browse my sample VIs?

  • USB to RS232 converter

    I would like to run a terminal emulator (eg. minicom) on my Arch box to look into my Netgear DM111P router.
    I have the 3.3v TTL to RS232 converter already, but my IBM Thinkpad T40 does not have any (DB9) serial ports.
    I was wondering if I could use the USB port instead with a RS232 to USB converter cable like this one:
    http://www.amazon.co.uk/USB-RS232-Conve … B00077DJIQ
    Can anyone tell me if this will work or what my other options are?

    If I read you correctly, you're saying that the physical connection to the microcontroller is (DB9) serial, while the physical connection to your Arch box is USB and that you're running minicom on your Arch box to read the output from (and send input to) the microcontroller.  Have I got that right?  I'm new to this stuff, as you can tell, and I find it pretty confusing so I just wanted to clarify.
    Could you suggest some serial-USB hardware to me as I've got to buy mine and I'd like to get something I know will work?

  • WIth LabVIEW how do I control an instrument with a RS232 output, using a RS232 to USB converter cable.

    WIth LabVIEW how do I control an instrument with a RS232 output, using a RS232 to USB converter cable since I dont have rs232 ports. I have two instruments that I want to control in this manner. One is an Imada ZPS force gage with RS232 output. The other is a Panasonic HL-G103-S-J laser micrometer sensor which is RS422. I've done considerable LabVIEW programming using GPIB but I have no experience with devices like these. Any tutorial or examples would be greatly appreciated.
    Thanks.
    Solved!
    Go to Solution.

    I understand that you want to control a device which having RS 232 port as output. If so, you can use an USB-RS232 cable from PC to device and you can control or monitor the device.
    See this link http://zone.ni.com/devzone/cda/epd/p/id/2669
    Also, first check the device in hyperterminal and then continue to program in labVIEW. You can find the serial VI's in Instrument I/O.

  • Controllin​g the Thermotron 7800 going USB to RS232.

         I'm very new to LabVIEW so I apologize if this is a quick fix I haven't stumbled across.  My goal is to control my Thermotron 7800 which has an RS232 interface with a machine that only has USB.  I'm using the  manufacturer's LabVIEW drivers with LabVIEW 8.2.1.  I've mass compiled them per instructions so they'll work with my 8.2 as they were written for LabVIEW 7.1.  I've connected and used a 3rd party USB / RS232 converter with other hardware to this machine so I know that's not the issue and I can get the LabVIEW driver to recognize what port I'm connected to but I know no data is transferring across the cable as the indicator LED is not flashing and all I can get is a time out error.
         Anyone tried this before?

    Hi,
    I have a few questions/suggestions regarding your system. 
    1.     When installing the USB to rs232 convertor did you create a driver using the Driver Development Wizard?  The following link will help you create an inf file to ensure proper communication with the instrument. 
    http://zone.ni.com/devzone/cda/tut/p/id/4478
    2.     Use the following link to try a loopback test to verify the usb-rs232 hardware is operating correctly.
    http://digital.ni.com/public.nsf/allkb/E22DA85E978​18DE78625678C0069BFC9?OpenDocument
    3.     Verify with the Thermotron manual that all the serial settings (BAUD rate, Parity, Start and Termination characters) are correct, like falkpl suggested. 
    4.     Try communicating to the instrument using a VISA test panel in Measurement and Automation Explorer.  The VISA test panel can be accessed by right clicking on COM1 from Devices and Interfaces>>Serial & Parallel.  The test panel allows the user to test basic serial write/reads without writing any code.
    Regards, 
    Andy L.
    Applications Engineer
    National Instruments

  • Can i communicate by the USB port, if my application is set up to communicate with the serial RS232 port???

    Hi to all labview users... Please help me with my deadly problem. Last Deadline is on monday next week!.
    I got a complete program now, written and tested OK. It communicates with a slave to control a motor. I've set up the program to communicate with the slave by the VISA RS232 Serial Port commuication.  and all works fine...
    Now the problem is.. that The communication should have been by the USB port instead. So what I have done now, is that i used a USB to RS232 converter.  So that the USB Plug is plugged to the PC, and the RS232 end to my SLAVE,
    When I send a command to my SLAVE,  the SLAVE seems to understand it and it executes the command. But I must read some data at the port after sending my command to the SLAVE, coz, this command ask the SLAVE to start streaming data to me.
    All communication to me from the Slave  crashes so that i get ( sometimes if I get data ) wrong unknown data i cant understand.
    So the big question is: Can i use USB communication although my Application is set up with serial communication if I use a USB to RS232 converter???  ( the Driver for the USB - SERIAL conv. is installed well.)
    Baudrate :115200.. parity : none,  Data bits: 8, stop bit : 1.
    Please help me.....
    Hassan Zamzam
    Pictures attached
    HFZ
    Attachments:
    Connection diagramJPG.JPG ‏33 KB
    Serial ReadJPG.JPG ‏107 KB
    Serial ConfigJPG.JPG ‏104 KB

    Hi ZamZam,
    Thanks for your detalied description of the problem. However I think the problem is how your USB-RS232 converter is converting the incoming serial command to the USB port. All Labview can see is a "normal" serial port. Do you have some information on the converter? You might also want to contact them to see if they are aware of this issue.
    Thanks! 
    Dennis Morini
    Field Sales Engineer
    National Instruments Denmark
    http://www.ni.com/ask

Maybe you are looking for