Labview Serial Port Hyperterminal Software

Labview Serial Port Hyperterminal Software Rating: 3,9/5 2403 reviews

'How does the Virtual Instrument work from the software perspective? Standard, thus enabling control from a computer that is equipped with a serial port. For transmission from LabVIEW to a Windows Hyperterminal, using the following files. Next, you can use “HyperTerminal” to communicate with the AGILIS-UC2 (for. With the AGILIS-UC2 labVIEW driver, the communication is used like a Serial.

How is Prologix GPIB-USB controller different from other vendors' products?

While Prologix GPIB-USB controller provides many of the same features as GPIB-USB controllers from other vendors, it is much easier to use. Prologix GPIB-USB controller provides a virtual serial interface to communicate with instruments, while handling all GPIB protocol details for you. As a result, you can communicate easily with instruments using any terminal program instead of having to write custom programs using the vendor supplied library. Please see the Manual for a complete list of features.

Is Prologix GPIB-USB controller compatible with National Instruments LabVIEW, Agilent VEE, and other test frameworks?

Yes. Prologix GPIB-USB controller provides a virtual serial interface to communicate with instruments, while handling all GPIB protocol details for you. Any test framework, or programming environment, that provides access to serial ports is compatible with Prologix GPIB-USB controller. For example, you may use NI LabVIEW Serial VIs or NI VISA VIs. Also, FTDI has sample LabVIEW VIs for communicating with the controller using D2XX drivers.

Will my custom LabVIEW or VEE programs work unmodified with Prologix GPIB-USB controller?

Probably not. Prologix GPIB-USB controller provides a virtual serial interface to communicate with instruments, while handling all GPIB protocol details for you. Programs that expect a different interface (such as NI 488.2 interface) have to be modified to use the serial interface to be compatible with Prologix GPIB-USB controller.

How do I use Prologix GPIB-USB controller with LabVIEW?

Prologix GPIB-USB controller provides a virtual serial interface to communicate with instruments. Therefore you may use LabVIEW Serial VIs or NI VISA VIs to talk to the Prologix controller and instruments. Please see the LabVIEW sample program in the Resources section and link to Matthias Schroeter web page on using Prologix controller with LabVIEW on Linux.

How do I use Prologix GPIB-USB controller with MATLAB, or using C++, C#, or Visual Basic?

Please see sample programs in the Resources section.

Is Prologix GPIB-USB controller a drop-in replacement for controllers from other vendors?

No. Prologix GPIB-USB controller provides a virtualserial interface to communicate with instruments, while handling allGPIB protocol details for you. Programs that expect a different interface (such as NI 488.2 interface) haveto be modified to use the serial interface to be compatible withPrologix GPIB-USB controller.

Can Prologix GPIB-USB controller control multiple instruments?

Yes. You specify the GPIB address of the instrument to control using the '++addr' command. All subsequent instrument commands are sent to the specified address. When you want to control a different instrument, issue another '++addr' command with the new address.

How do I download screen plots from instruments?

There are two ways of downloading screen plots — device initiated plots and host requested plots:

Device Initiated Plot

Set the instrument to TALK ONLY mode
Set Prologix GPIB-USB controller to DEVICE Mode (++mode 0)
Specify the address where the instrument expects the plotter to be (++addr <GPIB address>)
Connect the controller to the instrument and to the USB port on the PC
Open the virtual COM port using a terminal program like HyperTerminal, or using plotter software
Initiate screen plot download from device front panel

Host Requested Plot

Set the instrument to TALK/LISTEN (or ADDRESSABLE) mode
Set Prologix GPIB-USB controller to CONTROLLER Mode (++mode 1)
Specify the GPIB address of the instrument (++addr <GPIB address>)
Connect the controller to the instrument and to the USB port on the PC
Open the virtual COM port using a terminal program like Windows HyperTerminal, or plotter software
Using the terminal program, or plotter software, issue the instrument command to download screen plot (e.g. PLOT;)

How do I print screen plots from instruments?

To graphically render plots you need a plotter emulation application such as:

7470.exe — an excellent open source application.
PrintCapture — a full-featured commercial application. 30-day free trial version available.
Plottergeist — another full-featured commercial application.

Are drivers available for my OS?

Drivers are available for the following OS from FTDI website:

Windows Vista x64
Windows Vista
Windows XP x64
Windows XP
Windows Server 2003
Windows 2000
Windows ME
Windows 98
Linux
Mac OS X
Mac OS 9
Mac OS 8
Windows CE.NET (Version 4.2 and greater)

How do I install drivers?

Please refer to FTDI installation guides.

What accessories are needed to use Prologix GPIB-USB controller?

At a minimum you need an USB A-B cable, with an USB-A connector at one end, and an USB-B connector at the other end. You may also need a GPIB cable.

Do I need a power supply?

No, Prologix GPIB-USB controller is powered from the USB bus.

Do I need a GPIB cable?

You may plug the Prologix GPIB-USB controller directly onto the GPIB connector on the instrument. The controller has a male GPIB connector and most instruments have a female GPIB connector. However, if it is not convenient to do so, you may use a GPIB cable.

How do I configure my Prologix GPIB-USB controller?

There are two easy ways to configure your Prologix GPIB-USB controller:

Use the excellent open source PROLOGIX.EXE utility written by John Miles.
Use any terminal program such as HyperTerminal or Tera Term Pro and enter commands manually. For example, to enable CONTROLLER mode enter ++mode 1

How do I use HyperTerminal with Prologix GPIB-USB controller?

Connect USB cable. Start HyperTerminal.

In 'File' 'Properties' dialog, select the virtual COM port created by USB driver.

Click 'OK', then select 'Settings' tab and click 'ASCII setup..'. In the dialog, check 'Send line ends with line feeds' and 'Echo typed characters locally'. Click 'OK' twice.

You are now ready to communicate with the controller. Enter ++ver command in the HyperTerminal window to verify communication with the controller.

How do I use Tera Term Pro with Prologix GPIB-USB controller?

Connect USB cable. Start Tera Term Pro.

In 'Setup' 'Serial Port..' dialog, set values as follows:

Port: Select virtual COM port created by USB driver

Click OK. In the 'Setup' 'Terminal' dialog, set 'Transmit' to 'CR+LF', and check 'Local echo'. Click OK.

You are now ready to communicate with the controller. Enter ++ver command in the Tera Term Pro window to verify communication with the controller.

How do I use 7470.exe with Prologix GPIB-USB controller?

Please see 7470.exe User Guide.

How do I use PrintCapture with Prologix GPIB-USB controller?

Please see application note in the Resources section. Also see PrintCapture website for more details.

How do I use Plottergeist with Prologix GPIB-USB controller?

Configure the controller as a DEVICE. Connect USB cable.

Start Plottergeist. Open 'Configuration' 'GPIB/RS-232..' dialog. Select 'Connect using Serial Port', and click 'Setup'. Set values as follows:

Port: Select virtual COM port created by USB driver

Click OK twice. Click the 'On Line' button on the tool bar. Plottergeist is now ready to receive data.

Which commands do I use to control my instrument?

Refer to the programming manual of your instrument for commands accepted by your instrument.

How do I create programs to control instruments, and acquire data, using Prologix GPIB-USB controller?

Any programming language and environment that provides access to virtual serial ports can be used to develop programs to control instruments using the Prologix GPIB-USB controller.

Also, checkout Ulrich Bangert's EZGPIB, an easy to use data acquisition tool for use with Prologix GPIB-USB controller.

Are code samples available?

Yes. See here.

Why am I not getting any response from instruments?

This could be due to any of the following reasons:

Serial port was not configured correctly
Instrument address was not set correctly in the GPIB-USB controller
Instrument was not configured for output
The command was not recognized by the instrument

Why is the instrument reporting 'QUERY UNTERMINATED' or '-420' error when using Prologix GPIB-USB controller?

After sending any command to an instrument, Prologix GPIB-USB controller will address it to talk to read the instrument's response. If the command does not generate a response (often called non-query commands), some instruments generate the above error when addressed to talk. In effect the instrument is saying, you have asked me to talk when I have nothing to say. The error is often benign and may be ignored.

However, if you want to avoid the error you have two options:

Use the ++auto 0 command to turn off the read-after-write feature before issuing a non-query command. Later use the ++auto 1 command to turn the feature on to read instrument response when issuing query commands. For example:

++auto 0	—	Turn off read-after-write
SET VOLT 1.0	—	Non-query command
*idn?	—	Query command
++auto 1	—	Turn on read-after-write
'HP54201A'	—	Response from instrument

Or, use the ++read command to read the instrument response. For example:

++auto 0	—	Turn off read-after-write
SET VOLT 1.0	—	Non-query command
*idn?	—	Query command
++read eoi	—	Qead until EOI asserted by instrument
'HP54201A'	—	Response from instrument

What if I have a question that is not answered here?

Please send email with your question to support@prologix.biz. Describe in detail your problem, your setup, and any troubleshooting you have done.

Where is the user manual?

Contact us

Live Chat with Tek representatives. Available 6:00 AM - 4:30 PM PST.

Question :

I am trying to use RS232 communication to my scope and it is not working. What can I do to fix it?

Answer :

The following is a trouble shooting guide which goes through the possible issues and how to fix them.

Getting Started

If you’re having communications problems between your PC and Oscilloscope this document provides the steps to help you get the communications running successfully. One of the most common complaints is “I’m getting an error message from the WaveStar program’s Instrument Manager Service that states “Device Running” and “Attached Hardware not Responding”. We will review the steps necessary to verify the hardware and software components and ultimately to get WaveStar running. You may also be having issues communicating with OpenChoice. If you encounter problems at any of the steps below, contact technical support with information on the kind of error that is occurring, and the step in the guide that it is occurring.

1.0 Verifying the Hardware

We will begin by verifying that your cable, the PC COM port, and the oscilloscope COM port are working correctly.

Is your cable a Null-Modem style RS-232 cable? If you are not sure, read the section RS-232 Cable Issues. If yes then go to next step.
Have the communications parameters been set properly on your oscilloscope? If you’re not sure see the sectionCommunications Parameters. You may also need to refer to the operator/users manual for your oscilloscope to determine how to set these parameters. If the parameters are set correctly go to next step.
Are the COM ports on the oscilloscope and PC functioning properly? See the sections Test the oscilloscope RS-232 portand Test your PC RS-232 port

1.1 RS-232 Cable Issues

One of the most common problems with RS-232 communication is choosing the wrong RS-232 cable. There is no such thing as a standard RS-232 cable, so you may need to use an ohmmeter to verify that your cable is wired correctly. Many cables don’t have all of the pins connected. The first thing you need to know is whether the PC and oscilloscope are DTE (Data Terminal Equipment) or DCE (Data Communications Equipment) devices. This information is in the documentation provided with your oscilloscope and with your PC. Most modern Tektronix oscilloscopes are DTE devices.

If you are connecting two devices of the same type, like a modern Tektronix oscilloscope and a modern PC, you need a null modem cable. This is a cable whose lines are crossed such that the inputs of one device are connected to the outputs of the other.

Confirm that your cable is a null-modem cable as follows.

Short pins 1&8 at each end of the cable.

This cable is available from Tektronix under the part number 012-1379-00.

If you are connecting a DTE device to a DCE device you will need a straight-through cable. This is a cable that has the same pin assignments on both ends of the cable.

CAUTION: Do not connect the output lines of two same-type devices to each other. Doing so may damage one or both of the devices.

For hard flagging to work, the RTS (Request To Send) and CTS (Clear To Send) lines must be connected. Use an ohmmeter to verify that they are actually connected since not all cables connect these lines. The RTS line is sometimes referred to as RFR.

WaveStar does not use the DCD (Data Carrier Detect) so it does not matter whether or not it is connected. The DCD line is sometimes referred to as RLSD.

1.2 Communications Parameters

Make sure the communication parameters are set correctly on the oscilloscope and the PC program.

Baud rates should be the same on both the oscilloscope and the PC. Parity should be None, Data Bits should be 8, and Stop Bits should be 1. Do not use baud rates above 9600.

Soft flagging should never be used for waveform and hardcopy transfers. This is because waveform data and hardcopy output contain binary characters, which can easily include the XON and XOFF characters, used to implement soft flagging. Soft flagging should only be used for transferring stored setups since stored setup information generally consists of printable ASCII text.

Although it generally should not matter if the EOL characters are the same, it is typically recommend that you set the EOL to CRLF to be sure there are no problems.

Hint: In the RS232 setup menu of the scope select Default RS232 button if available. This will result in a good starting point.

1.3 Test the oscilloscope RS-232 port:

The following steps will allow you to verify the performance of the RS-232 port on your scope.

Short pins 7 & 8 on the end of the 9 pin cable that would connect to your PC.
Connect the scope probe to the channel 1 BNC connector on your scope.
Connect the probe tip to pin 2 and the ground clip to pin 5.
Set the hardcopy port on the scope to RS-232.
Set the scope volts/div to 5 Volts.
Set the scope time/div to 500us.
Press the hardcopy or print button on the scope.
You should see a stream of square wave pulses as the hardcopy data is sent out the RS-232 port.

If the test of your oscilloscope port is successful then go to the next step to confirm the function of your PC's RS-232 port. If your oscilloscope fails to output data you should contact Tektronix service to arrange for repair of the product.

1.4 Test your PC RS-232 port:

Using a terminal program such as Windows Terminal, HyperTerminal, Crosstalk, etc. you can test the RS-232 port on your PC. At this step you will setup a terminal program to receive data from the selected COM port and display on your PC screen. The data will be the hardcopy output that we verified in the previous step was transmitting out of the scope.

At the time of writing this file we used Windows HyperTerminal 1999 on a Windows 2000 PC. Specific steps for using HyperTerminal are listed next. To learn how to use your specific terminal software, refer to the documentation for the product or contact the software vendor.

2.0 Steps for running HyperTerminal

To run the program click on the Windows Start button, select Programs > Accessories > Communications > HyperTerminal.
The HyperTerminal program launches with a spinning globe logo. A popup dialog screen appears asking for the name and icon. This is used if you plan to save a communications session. Since you won’t need to save the session just type anything in the name field and don’t worry about the icon. Click on the OK button.
A popup dialog box titled “Connect To” appears. At the bottom of the box is a field titled “Connect using:”. Click on the arrow to the right side of the field and choose your COM port. (On most laptop PC’s there is only one COM port and it is typically numbered COM1. Click on the OK button.
A popup dialog box titled COM<x> Properties appears. The value for <x> will match the COM port number you selected in step 3.
Click the arrow at the right side of the Bits per second field and change the rate to 9600. The rest of the properties, 8, None, 1 and Hardware should already be set. Click on the OK button.
At this point the HyperTerminal window will either clear leaving a blinking cursor in the upper left corner or an error message dialog box may appear. The message may read: “Unable to open COM<x>. Please check your port settings”
If the screen clears go to step 9. If you see the error message then you will need to determine why your com port won’t open.
If you got the error message, this is typically due to some other application such as the HotSync program installed for a Palm Pilot or other PDA. You can check the Windows Task Manager Processes list to see if “hotsync.exe” is running. If it is, end the process and go back to step 1. If you’re not sure about applications using your COM port you may be able to get assistance from your company computer support staff or from your PC vendor technical support in determining what application is preventing access to the COM port. Keep in mind that as long as the COM port is not available to HyperTerminal it will also not be available to WaveStar or OpenChoice. If the WaveStar Instrument Manager was started previously, it may still be using the COM port. The Instrument Manager Service continues to run as a background task even after the Instrument Manager control panel has been closed. To check on this, reopen the Instrument Manager, open the “Control” menu and select “Shutdown Service”. Return to Step 1 of this section.
(NOTE: In this next step you will not see the characters echo on the Hyperterminal screen. This can be changed by going into Hyperterminal menu File > Properties > Settings > ASCII Settings and check the box labled Echo typed characters locally)

Type the characters *IDN?, hit the Enter key. The oscilloscope should respond with its identification string. This string will look similar to this:

TEKTRONIX,TDS 2024,0,CF:91.1CT FV:v4.12 TDS2CM:CMV:v1.04

This concludes the troubleshooting guidelines. If you have successfully completed the steps above, you have full communication with your oscilloscope through the RS-232 port. You should now be able to restart WaveStar and establish a connection. The following steps provide a quick getting started with WaveStar guide. Please refer to the WaveStar Users Manual for complete instructions on that products use.

3.0 If you’re using the Tektronix WaveStar program:

The first step in running the WaveStar program is to establish the connection to the oscilloscope using the Instrument Manager.

Start Instrument Manger from the WaveStar folder
Select the Edit menu then Add Instrument.
From the pull-down list, choose your instrument type
A list of available ports will appear.
Select the proper COM port. (COM1 = ASRL1 and COM2 = ASRL2)

4.0 Check the Instrument Manger Status

The status should read:

SW Status HW Status

Running Responding

If you get a status that reads:

SW Status HW Status

Running Not Responding

There may be an error in the installation of WaveStar. Try uninstalling and reinstalling WaveStar. If TekVISA does not show an RS232 port, i.e. ASRL1::INSTR, check that the search for serial is enabled. Verify that TekVISA has been installed and was not overwritten by another vendors VISA. You can do this by searching for the file visa32.dll and right click on it to see its properties.

This FAQ Applies to:

Product Series:

Product:

A mod called Simple Realism sounds about right. It doesn't reshape the entire game, it just juices some of the behind-the-scenes math relating to weapons, damage, health, and loot. Can someone help with Simple Realism on Fallout 3? I've tried installed FOVE in the main folder, putting the modular parts in the data (don't have DLC), tried loading it with nexsus, but I don't think it's working. Simple Realism is a gameplay enhancement mod in development for over 6 years which has been painstakingly tuned and playtested to provide a more challenging and rewarding Fallout 3 experience There are no new items or new mechanics added so you can jump right into a new playthrough without having to learn about all the changes like you do with other mods such as FWE. Fallout 3 goty mods. Videogameasset My games. When logged in, you can choose up to 12 games that will be displayed as favourites in this menu. Simple Realism 3.3 - Update Only. Date uploaded. 05 Apr 2015, 2:02AM. Unique DLs - Total DLs - Version. Only includes the updated ESP's.

FAQ ID 56651

View all FAQs »