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.

Similar Messages

  • Maxon EPOS P + WinXP + Labview2013 = error reading USB data 0x23000002

    Hi, 
    I have a DC servo with 3-channel encoder and Maxon Epos P 24/5 controller, connected via RS232 to a Windows XP machine with Labview 2013.
    Epos Studio 2.0 works fine, PIDs are tuned and all functions work 100%. When I try any of the Maxon example VI's, however, it gives me this "error reading USB data. (0x23000002)"
    I can communicate with EPOS in Labview using NI VISA. I have recorded the sequence that Epos Studio sends when scanning COM interfaces (something with hex 07 00 00 00 ). I have sent this sequence via "write to COM port" VI, and received a response from EPOS P.
    If I put my COM Tx and Rx lines on the oscilloscope and run the example VI, I see that at the execution of "VCS Set Operation Mode" VI the computer sends one byte to EPOS, but EPOS does not respond with anything. I guess the read times out and triggers the error. Other EPOS VI's which query the controller for information produce the same error, as EPOS does not talk back to them either...
    I urgently need assistance on this matter. Thank you in advance for your prompt response!

    I need to apologize for confusion. I wrote "error reading USB", while of course I mean "error reading RS232" everywhere in the text. Sorry for that, but the question remains - why do the Maxon LabView VIs give this error when communicating via COM port to EPOS P?

  • Visa error unless logged in as admin

    I'm installing a LV program on several computers running Win7. It uses VISA to communicate with three separate instruments. If I'm logged in as admin everything runs perfectly but when anyone without admin rights logs in I keep getting VISA error "resources not found". This seems to be the two serial ports on a card, COM1 which is the on board port is working. I installed this on an identical computer yesterday and did not have this problem.
    Solved!
    Go to Solution.

    When you are logged in as the other user, what do the serial ports show up as in Device Manager?  What do they look like in MAX?
    I wonder if there is a setting, possibly some sort of Windows Group Policy that is locking out serial ports for non-admins.
    Is this a real serial port (with DB9 connector) or is this a USB-RS-232 converter which gives a virtual com port?  Perhaps if group policy is to disable USB ports for non-admins, it is blocking the converter from working.  Just speculating.

  • Sbrio9636 VISA Error -1073807202

    Hello
    I have a sbRIO9636 and the test instruments. I just want to connect sbRIO and Test instruments(with RS232).
    I am trying to connect RS232 (9 pin) via serial ports..I also have Measurement & Automation Explorer (ver 5.1) to monitor and configure Serial/parallel connections.
    The problem is that when I query, it looks like my device is not properly recognized. I only get time-out errors.  VISA Error -1073807202. But when I connect the Test instruments directly to PC, NI Max shows COM 1 and can get the data from the test instrumnets. That means, I can get the data from PC , but I can't do the same with sbRIO9636.
    How can I ensure that my device is properly recognized? Is my COM1 port activated at all? I can't see COM Port in NI Max for sbRIO9636.
    thank you!
    Solved!
    Go to Solution.

    Hey Kellydog
    This is a kB what the VISA Error -1073807202 is.
    http://digital.ni.com/public.nsf/allkb/10C6C0FBB8E7BD4486257850006CE8FF?OpenDocument
    maybe this will fix your problem.
    best regards,

  • 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

  • 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.

  • 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!

  • Intermittent VISA errors -10073807194 'connection for given session has been lost'

    I am using a USB/Serial converter with FTDI chipset (VCP configured) to communicate with a serial device. There is an intermittent problem where the connection disappears, and the VISA error '10073807194' is generated. I have read carefully through the other threads related to this error, but still do not have a solution. Some background information on my set-up:
    1) NI VISA 5.1.2
    2) LV 2010
    3) Windows 7 - 64 bit
    Could windows be dropping the connection for the FTDI device when communication errors occur? Has anyone had this experience? We were previously using a prolific converter, and were encountering other communication errors where the read would timeout or only partial responses would be returned, but the VISA connection was not lost. I know the prolific converters can be problematic on 64 bit windows, so I was hoping the new converter would solve the problems.
    I will post the code tomorrow, but I open the VISA session and configure the port on start up and close it when the application exits. I am using the bytes at port with the VISA read. However, the code I have has been running fine on two test machines in our office for several months. The above issues have been occuring at a customer's site overseas. We have not been able to reproduce the above problems here. There may be environmental factors at play (improper grounding, noise, etc.)
    I should also mention that the original setup has this USB converter running through a hub, but the hub on their setup had to be removed due to reoccurring communication problems with this serial device, as well as other connected devices. We are going to get them to try installing a serial port on one of their PCs, and see if it eliminates the issue.
    In the mean time any experience/help troubleshooting would really be appreciated.  Thank you!!!
    Zalusky

    Well, I saw your Kudos to this post
    Using "Bytes at port" on the FTDI driver can be very problematic and is the likely culprit for the behavior change.  If there is any way to use a term char with the serial protocol change this.
    The FTDI driver does have control of the buffer size and latency timer.  Read through the documentation in this link.  At the very least your polling rate for "Bytes at port" should be greater than the latency timer setting if the expected transfer is less than the buffer size. (shorten the timer )
    Jeff

  • When I plug in my iPhone to a USB port on the back of my computer I get the error "MTP USB Device driver was not successfully installed"   and of course there is no device that shows up either.  It would be great to download my photos!  I'm using Windows

    When I plug in my iPhone to a USB port on the back of my computer I get the error "MTP USB Device driver was not successfully installed"   and of course there is no device that shows up either.  It would be great to download my photos!  I'm using Windows

    Go through this support doc:
    OS: Device not recognised in iTunes
    Windows: http://support.apple.com/kb/TS1538

  • When trying to test my serial port instrument I receive Visa error 1073807346​, which means that they is not enough informatio​n for Visa to access or resource does not exist.

    The error I am getting is on Visa open.

    I found couple of knowledge base (KB) entries that talk about Visa error 1073807346. The best way to find knowledge bases (KB) is to goto ni.com >> Support >> Advanced Search (option 3) >> type in the keywords in the box "1073807346", you will get them.
    Also refer, http://www.ni.com/support/labview/visa/default.htm​. Hope this helps.

  • 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.

  • I getting error when connecting my new iPod in my car. Getting error that usb is not recognized.

    I getting error when connecting my new iPod in my car. Getting error that usb is not recognized.

    Not all car systems are compatible with the iPod touch.  Does the documentation/website for the car system say it is compatible with an iPod with iOS 5?

  • TestStand 3.1 Run Selected Steps generates Visa error -1073807346?

    When using Run Selected Step in TestStand 3.1 to interactively execute previous steps in a sequence a Visa error (-1073807346 The given session or object reference is invalid.) is generated even though the selected step has previously executed with no errors.
    Some history:
    The sequence in question was developed with TestStand 2.0 and LabView 6.1 and does not exhibit the above mentioned issue. The error began after migration to TestStand 3.1 and LabView 7.1. The sequence executes without errors in all other conditions. 

    Hi,
    When your sequence halts, does that mean it's closed the visa sessions and if so when running the selected steps are you running the setup with the open visa sessions or are you just reusing the sessions stored in the Station Globals (I assuming when you said globals you were referring to Station Globals).
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • I can't install VISA driver and USB GPIB driver on my PC with VISTA... help me...

    I have LabVIEW7 and VISTA, it's ok, but I can't install VISA driver and USB GPIB driver on my pc... it's necessary to connect my pc with instruments? Or LabVIEW7 have this files??? Thanks,
    Vanny.
    Thanks,
    Vanny
    Sweet, Beautiful and Young Female Physicist (SBYFP)
    (I speak a not very good english, so If U are Italian LabVIEW expert speak in Italian, if U speak in Eglish... please speak easy )
    My e-mail for personal contact: [email protected]_NO_SPAM_PLEASE
    Solved!
    Go to Solution.

    You need Administrator privelages to install drivers on Vista
    David
    www.controlsoftwaresolutions.com

Maybe you are looking for