Necessity of GPIB-RS232 Converter

Hello,
This may be a silly question but I just want to be sure.
Say I have a PC running Win7 and LabView and an instrument is connected to it with both a GPIB cable and and RS232 in its serial port. Will I be able to use VISA functions to send and receive serial data to the instrument or would it be better to use an NI GPIB-RS232 Converter? In what situations would said converter be useful?
Thanks!

Yes, you would use VISA with all three options. The fastest and more robust method is with GPIB. Personally, I see no point in the GPIB-RS232 converter. It's expensive and you are limited to the same RS232 baud rates that an inexpensive USB-RS232 converter gives you. I recommend FTDI based serial converters. You would probably need to modify any driver if you use the GPIB-RS232 as well.
The last time I saw and used the GPIB-RS232 converter was several years ago when I bought an instrument that the vendor said had a GPIB option. What it really had was the converter inside. Very disappointed by what I found.

Similar Messages

  • Using GPIB-RS232 converter with an embedded application

    Hi
    I am quite new to GPIB, so this might be a rookie question Using my own embedded application I need to communicate with a couple of Agilent power sources to send commands and queries. I got a GPIB-RS232 converter from NI but I can't figure out from the online help wether I can directly write to the serial port attached to the NI GPIB-RS232 ans SCPI command. I would be grateful if you can help me out to find the documentation on how to communicate to several Agilent GPIB instruments connected to the NI GPIB-RS232 converter configured to work in mode S.
    By the way, for testing I am developing the modules for my application on a desktop computer under linux using gcc c++ compiler.
    Thank you!

    This might be useful: NI GPIB-RS232 Examples
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions

  • GPIB-Serial Converter Wizardに関して

    お世話になっております。
    下記URL質問（題名：CONVERTER SOFTWAREと通信できない）と同じ状況（エラー発生）です。
    違いは、OSが2000のSP4、ＰＣからはGPIBケーブルで本体に接続しています。(Software:Version1.0  501410A-01)
    ＰＣ側GPIBボードは○ontec社製で、GPIB通信は他社デジタルマルチメータにて動作を確認しています。
    また、Locatingが正常になってから行う作業だとは思いますが、GPIBボード側のパラメータを変えてみたり、
    外部機器(RS232)側も本体に接続したり外したりしながら試しております。
    何かお気づきの点がありましたら宜しくお願いします。
    http://forums.ni.com/t5/NI%E8%A3%BD%E5%93%81%E3%83%87%E3%82%A3%E3%82%B9%E3%82%AB%E3%83%83%E3%82%B7%E...

    池田様
    ご返信ありがとうございます。
    前回引用したＵＲＬ先の質問とは、ハードウェアが違っていました。申し訳ありません。
    http://sine.ni.com/nips/cds/view/p/lang/ja/nid/203552
    使用しているハードウェアは上記ＵＲＬ先の物で、本体の裏側に
    「MODEL:GPIB-RS232　 PART NO:191971C-01L　 SERIAL NO:14BD91D」
    と記載されています。
    また、先ほどＰＣと上記ハードウェアを「シリアルケーブル」で接続してソフトウェア
    (GPIB-Serial Converter Wizard)を起動したところエラーは発生せず、
    制御側にデジボル（ＧＰＩＢ）を接続したところ、通信が可能でした。
    ですが、やはりPCと上記ハードウェアを「GPIBケーブル」で接続すると、エラーが発生します。
    使用しているGPIBボードは下記ＵＲＬ先の「GPIB(PCI)F」です。
    http://www2.contec.co.jp/prod_data/gpibpcifl/c01.pdf#search='GPIB(PCI)F' 
    宜しくお願いします。

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

  • GPIB-RS232

    Bonjour,
    J'utilise actuellement un GPIB-RS232 pour la communication entre un banc de test (GPIB) et une étuve (RS232).
    Anciennement l'étuve était directement en GPIB mais la nouvelle fonctionnant en RS232 nous utilisons ce module. On l'a configuré en mode D et il y a bien des échanges entre les deux. Mais c'est trop lent pour les tests qui ont déjà été développé sur ce banc. La lecture coté banc coupe la communication avant la fin et on ne lit que le début de la réponse.
    Existe-t-il une méthode pour optimiser le temps de traitement et renvoyer plus vite en GPIB le message RS232 ?
    Merci de votre aide.

    Bonjour Titel,
    Avez-vous solutionner votre problème?
    Si tel n'est pas le cas, pouvez-vous nous communiquer une référence du "GPIB-RS232" utilisé?
    Votre banc de test est certainement composé d'un ordinateur. Si tel est le cas, vous n'avez pas direcement accès à un COM pour réaliser la communication RS232 directment sans passer par le bus GPIB?
    Cordialement,
    Rémi D.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> Les rencontres techniques de NI - Mesures et acquisition de données : de la théorie à la mise en ...

  • GPIB-RS232 lock up in c-mode

    I have a simple driver talking to a GPIB device in c-mode.
    This is working.
    I am testing what happens in fault conditions.
    If I power down the GPIB device and send a character on the RS232 I get the the following LED pattern:
    RDY - Red
    LSTN Green
    ATN Yellow
    FULL Yellow
    BUSY Yellow
    The only way out of this condition is to cycle the power on the GPIB-RS232
    How do I make my application more robust?

    I ran into the same problem.
    C-mode is not robust.
    You have to change it to S-mode and program in S-mode to prevent it from locking up.
    Its a pain since S-mode is more complicated and has it's own special syntax but its the only way I've found around it and it doesn't lock-up.

  • Which RS232 converter recommended for cisco console

    hi,
    which RS232 converter cable is the recomanded for cisco console?
    i used many converters and getting blue screen error for my windows 7 Enterprise
    sometimes port not working as well!
    Any assistance would be most appreciated.  Thanks.

    There are several good options. Personally I use a USB-Serial converter from TRENDnet purchased at amazon.com for US$9.99:
         http://www.amazon.com/TRENDnet-RS-232-Serial-Converter-TU-S9/dp/B0007T27H8
    I use it on conjunction with the standard Cisco RJ-45-DB-9 serial console cables that come with every router and switch. Since I'm regularly unpacking new ones, they're easily replaced when the little tab on he RJ-45 breaks off (the most common failure). The same USB-DB-9 serial adapter has held up under regular use for about 5 years.
    Other threads have also reported good luck with other vendors:
         https://learningnetwork.cisco.com/thread/46991
         https://supportforums.cisco.com/thread/2009070

  • MAX can't see my Agilent 82357A GPIB/USB converter

    I have a LV 8.5 program that talks to an Agilent 34970A through the subject converter and generally works well except I often lose comm. Also when I first start my LV program it can't establish comm until I run the Agilent Connection Wizard, then LV and MAX comm ok with it. I've tried a different converter with same results. I'm using the Agilent Initialize vi, which is where the error occurs. The error I get is "Error 1073870264 occurred at VISA Clear in HP34970A Initialize.vi.....(Hex 0xBFFF00600) The interface associated with this session is not currently the controller in charge. "
    I've been on the phone with Agilent tech help and we've tried lots of things, and finally he suggests updating the Agilent I/O s/w, as well as NI-MAX. My MAX rev is 4.4of1. My first question is where/how do I download an update for MAX? and second question is, what's my problem?  I can always get my LV program and MAX to recognize the converter ONLY after I run the Agilent Connection Wizard OR unplug/replug the USB cable, and that's getting to be a real pain.

    Hi,
    Had the same problem a while ago. Here's what I did with Agilent 82357B..
    1. Download and Install Agilent IO libraries suite 15 --> http://www.home.agilent.com/agilent/product.jspx?cc=US&lc=eng&ckey=1249127&nid=-536900532.731306.00&...
    2. Set Agilent VISA to secondary
    3. Enable VISA Tulip (as you have done already)
    4. Hope it works

  • Labview 9 with GPIB-RS232 for controlling shutter at fixed interval of time

    Hello,
    I want to control my shutter using LabView. I have got a program for it from which I can see that shutter is being controlled. But I don't know how should i incorporate this conditional opening and closing of shutter. For example, I would like shutter to be close for  first "t1' sec and open for next "t2" sec and again close for "t1" and this repeated over unless stopped.
    I am attaching the file also, Can somebody explain me how I can do it?
    Thanks and regards.
    Solved!
    Go to Solution.

    I'm thinking this would be a good application for a State Machine.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions

  • FieldPoint and Enet-RS232 converter

    Hi all,ces
    How can I drive ENET-232/2 from the application, embedded into the FP-2010? I'd also like to know where to get more detailed description about ENET-232 devi

    Hi,
    I do not believe that you will be able to communicate to an ENET-232 device from an embedded application in a FP-2010. The ENET-232 device requires that you use NI-VISA in LabVIEW to communicate to the device. However, the FP-2010 currently does not support NI-VISA. Here are a few links to more information regarding the ENET devices:
    ENET-232 Series and ENET-485 Series User Manual for Windows 2000/NT 4.0 and Linux x86/Solaris 2.x
    Using the ENET-232 and ENET-485 Series on Windows 9x
    Hope this helps,
    Mike

  • Clearing RS232-GPIB Prior to sending commands to Agilent N3300A

    I have been trying to communicate with an Agilent N3300A DC Load Bank via a CRIO 9012 Com port and NI GPIB-RS232 converter. 
    The communications is somewhat buggy and the instrument does always do as instructed.   I have tried adding time outs (which should not be required but that does not help.
    How do I flush the RS232 converter ahead of every command in the hope this will help clean up the communications between the CRIO and GPIB instrument?
    Thanks
    Tim C.
    1:30 Seconds ARRRGHHH!!!! I want my popcorn NOW! Isn't there anything faster than a microwave!

    What is the purpose of this command scheme?
    Do you want to have a sweep range?
    In that case you can most likely prepare the instrument to react on analog triggers to go to the next frequency.
    Look into the GPIB examples of your instrument and into the GPIB command set of your instrument you might find something interesting.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • CRIO 9014 crash exception 0x00000700

    Hello,
    I am having a rather frustrating time trying to diagnose a repeated crash on my cRIO 9014 controller.  I have a big control system, centered at the RIO, which is talking to some C-series modules, several "intelligent" boxes over GPIB via the GPIB-RS232 converter, and an OPC server through the shared variable engine bound to an OPC client on my computer.  It will work without complaints for usually anywhere from 2 - 10 minutes and then crash with no explanation.  After the second crash I get the status LED blinking 4 times and the controller must be rebooted before I can try to re-connect.   I've monitored the cpu and memory up until the crash point with no issues.
    I've tried disabling random parts of the block diagram to no avail, unless I remove all of the functional elements completely.  I really have no idea what to even try next, so I very much hope someone out there has a guess.  I've attached a representative error log - they all look pretty similar, with the same exception code 0x700 and some function in niserial.out, though the function is not always the same.  I've also attached the master vi.  It will of course be broken without all of the sub-vis, but hopefully it is enough to get the gist of what is going on.  I can send the entire project if necessary, but it is huge so I leave it off for now.
    Thanks in advance, 
    ~Ben Loer
    Attachments:
    lvrt_err_log.txt ‏77 KB
    slowcontrol.vi ‏142 KB

    Hi Flash,
    Thanks for your reply.
    The crash you are seeing will require you to narrow down the specidific system that is causing the crash. The crash log does not point to one specific component. Can you provide the niserial.out error log? 
    How do I get this log?
    I think you should first eliminate the communication to the c-series module, then the communication with the OPC server.
    I've tried removing these components from the primary loop using a diagram disable structure, but the crash doesn't go away unless I remove all of the functional parts at once.  A new behavior I just discovered today is that the crash also goes away if I remove the separate loop which logs the data.  Is there some issue with having two timed loops in parallel?
    Also can you provide the versions of LabVIEW, RIO driver, and OPC Server?
    LabVIEW, FPGA, and RT modules are all 2009 (9.0.0.
    RIO 3.2.0 with scan engine support
    The OPC Server is a CAEN HV OPC Server for a SY1527LC power supply. It says it is version 3.0, but I'm not sure how to check the version of the OPC Server protocol itself.
    Thanks,
    ~Ben

  • Error 550 while using windows terminal mode

      I am using the GPIB-RS232 converter
      I am NOT using LabView.  I am attempting to use it with an RS232 interface via a standard terminal program.
      I am testing the setup with an HP(Agilent) 34401A meter
      If I enter the following via the terminal:
    Wrt 22
    *cls
    Wrt 22
    *rst
    Wrt 22
    Conf:volt:dc 100, 0.003
      Everything is fine and the meter goes in the proper mode.
      If I enter:
    Wrt 22
    Meas?
      Or
    Wrt 22
    Read?
      The meter reports Error code 550:
    From the HP manual:
    "The multimeter received a READ? or MEASure? command while in the local mode. During RS-232 operation, you should always execute the SYSTem:REMote command before sending other commands over the interface."
    SYSTem:REMote is an RS232 command and is not available when utilizing the GPIB interface.
    From the HP site
    This RS-232 error 550 can be generated when using a non-Agilent controller to program the DVM over the GP-IB. The error usually occurs when performing a query (MEAS: ? or READ?). We have seen the problem occur with a National Instruments and a Metro-byte(sp?) 488 card.
    This error occurs when the non-Agilent controllers sends commands to instruments, without pulling the REMOTE line on the GP-IB interface. The IEEE 488.2 specification requires the instrument to be in remote mode, when performing a query. The fixes is to set a bit on the card to force the REMOTE line true.
    Something is wrong with how your GP-IB card is setup, please contact the manufacturer of your GP-IB card on how assert the REMOTE line.
    Solutions or suggestions appreciated.
    Phil

    Phil,
    There is a special remote enable command for using the serial to gpib converter. You need to send "sre" command to enable the Remote Enable line. Here is the info from the GPIB-serial converter help file:
    sre
    Set (or Clear) Remote Enable
    Type
    Low-level bus management function
    Syntax
    sre
    [bool]<CR>
    Purpose
    Use sre to turn the Remote Enable
    signal on and off. In some cases, the first I/O or high-level bus management
    function you call sets remote enable automatically.
    Remarks
    If the argument bool is 1, the GPIB-RS232/485/422 asserts the Remote Enable
    (REN*) signal. If the argument bool is 0, the GPIB-RS232/485/422 unasserts REN*.
    Many GPIB devices have a remote program mode and a local program
    mode. It is usually necessary to place devices in remote mode before programming
    them from the GPIB. A device enters the remote mode when the REN* line is
    asserted and the device receives its listen address.
    Use cmd to send a device its listen
    address after using sre. Use loc to return the device to local program mode.
    If you call sre with an argument and
    the GPIB-RS232/485/422 is not System Controller, the ESAC error is recorded.
    If you call sre without an argument,
    the GPIB-RS232/485/422 returns its current remote status: 1 = remote, 0 = local.
    -Marshall R
    National Instruments
    Applications Engineer
    One stop for all your NI-VISA Support
    GPIB Support has a new homepage

  • Manual for GBIP-232CT.64K RS232 to GPIB converter

    I'm trying to locate a product manual for an "older" style GPIB to RS232 converter box. The part number on the box is GPIB-232CT.64K (180450-01 Rev B2).

    Hi,
    All of our old product manuals should be available online at http://www.ni.com/manuals.
    Hope this helps out!
    Best Regards,
    Aaron K.
    Application Engineer
    National Instruments

  • Bytes problem over RS232

    Hello!
    I'm trying to send data between to computer using RS232.
    The problem I encounter is the following:
    when I send data from 0 to 127 they are well received.
    from 128 to 160 they are bad received (actually 130 is received as 8218, 131 as 405, 135 as 8225).
    from 160 to 255 they are well received.
    I know that bytes in Java are from -128 to +127 and I could understand that number greater than 127 have problems to be transmitted, but because of those 160 to 255 numbers that are well received, I don't get it.
    I tried to find a pattern with the association of number sent and received between 128 and 160 but I didn't find anything relevant...
    I'm using a simple RS232 cable via an USB to RS232 converter on my computer (I don't have any serial port) while the other computer is directly using its RS232 port.
    The port is configured to send data to 9,6kbps, no parity bits, 1 stop bit and 8 data bits.
    Has anyone any idea of where my problem could come from?
    I get really confused with that...
    By the way, if some admins wants to put my post somewhere else because here is not the appropriate place, I totally understand it but could he (or she?) just mail to tell me where it has been put, because last time I posted I didn't find it anymore... lol
    Thanks ;)

    Please help me!
    finally I cannot even write a conversion algorithm because different values return the same value (sounds odd but here it is:)
    Send Receive
    127 127
    128     8364
    129     65533
    130     8218
    131     402
    132     8222
    133     8230
    134     8224
    135     8225
    136     710
    137     8240
    138     352
    139     8249
    140     338
    141     65533
    142     381
    143     65533
    144     65533
    145     8216
    146     8217
    147     8220
    148     8221
    149     8226
    150     8211
    151     8212
    152     732
    153     8482
    154     353
    155     8250
    156     339
    157     65533
    158     382
    159     376
    160 160
    As you can see for example 143 and 144 both return 65533...
    What can I do?

Maybe you are looking for