|
|
What is PrintCapture primarily used for?PrintCapture was designed to emulate a printer or plotter. It is normally used to replace the printer or plotter connected to your logic analyzer, spectrum analyzer, or oscilloscope. When you 'print' from your test equipment PrintCapture creates an image file on your personal computer that can be used in other Windows-based programs to help you document your hardware. PrintCapture can replace a serial printer, serial plotter, parallel printer, parallel plotter, GPIB printer or GPIB plotter. The only requirement is that your oscilloscope, logic analyzer, or spectrum analyzer must transmit Hewlett-Packard Printer Control Language (PCL), Hewlett-Packard Graphics Language (HPGL/2), or Epson ESC/P Control Code commands. One of the by-products of PCL processing is PrintCapture's ability to process "pure" text files and create a bitmap image from the text data. An HP1631D Logic Analyzer that we were working with had both a "graphics" mode and a "text" mode that it could use when it generated PCL data. Since we wanted to support as many print requests as possible we added the text mode support. As a result, PrintCapture will process any pure text file. Control codes and character codes outside of the normal alphanumeric characters will be ignored and may cause the file to be rejected as a pure text file. |
Do I have to uninstall PrintCapture before installing a new version, update, or upgrade?No. Any new version, update, or upgrade of PrintCapture can, and should, be installed over the top of an existing installation. The new installation will simply replace the existing files. |
What's the difference between an update and an upgrade?An update is generally a maintenance release. For example, moving from version 2.0.0 to 2.1.0 is considered an update. You must have an existing installation of the same major version number to install an update. Updates are free of charge. You can check to see if an update is available by visiting the downloads page. An upgrade is generally made when some new functionality is added to PrintCapture. In this case the major version number will increase (e.g. move from 2.x.x to 3.x.x). You must have an existing installation of a previous major version number to install an upgrade. Upgrades will require a small fee. You can check to see if an upgrade is available by visiting the downloads page. |
Obviously PrintCapture can't do everything for everybody. What are its limitations?PrintCapture is a printer emulator and a plotter emulator and it was originally designed to work with CRT-based test instruments. As a result the PCL (Printer Control Language), HPGL/2 (Hewlett-Packard Graphics Language), and Epson ESC/P Control Code commands that are processed are subsets of the available commands. We keep adding more command processing to make PrintCapture more and more compatible with CRT-based and PC-based test instruments. The data files that PrintCapture processes must be pure PCL or HPGL/2 commands - we haven't implemented processing of data files that contain both PCL and HPGL/2 commands. This isn't as big a drawback as it sounds. Most logic analyzers, spectrum analyzers, and digital oscilloscopes that we have seen 'print' either PCL or HPGL/2 data, but not both at the same time. The HPGL/2 command processing implemented so far seems to work well with HPGL and HPGL/2 compatible test instruments. This includes both CRT-based and PC-based digital oscilloscopes, spectrum analyzers, and logic analyzers. However, PrintCapture does not process HPGL data with multiple scale commands (IP and/or SC commands) yet. As of version 2.1.0, PrintCapture does a good job of processing data printed from a Windows 95- or Windows 98-based test instrument using one of Hewlett-Packard's HPGL plotter drivers (HP7470A, HP7475A, HP7550A, HP7580A, HP7580B, HP7585A, HP7585B, or HP7586B). Unfortunately, Windows NT, Windows 2000, and Windows XP don't have these HPGL compatible drivers - and never will. Those versions of Windows moved on to HPGL/2 compatible plotter drivers. As of version 2.2.0, PrintCapture also does a good job of processing data printed from a Windows NT- or Windows 2000-based test instrument using one of Hewlett-Packard's HPGL/2 plotter drivers (Hewlett-Packard HP-GL/2 or HP7550 Plus). Windows 95 and Windows 98 don't have these HPGL/2 compatible drivers - and never will. As of version 2.5.0, PrintCapture processes a small subset of the Epson ESC/P Control Codes since most of the control codes aren't needed to create a bitmap image from the data. We will add more processing if it is necessary and as we receive more sample Epson files to work with. |
Will you please show me PrintCapture's revision history?We continuously update PrintCapture's graphics data processing engines (HPGL, PCL, and Epson) as we get more and more raw data files to work with. If you feel the data from your logic analyzer, spectrum analyzer, or oscilloscope is not being converted to an image correctly, enable Keep Raw Data (Setup> Configuration> Image Processing> Keep Raw Data), print the image again, and e-mail the raw data file, along with as much information as you can provide to help us troubleshoot the program, to . The revision history list has gotten too large and has been moved to its own page. Click on revision history to see the list. |
What test equipment have others used with PrintCapture?The equipment list table lists some of the test equipment that others have used with PrintCapture. If you have used something not listed we would like to hear from you. We would also like to hear from you if you have used one of the models listed with a different print mode or if you have additional information that you would like to share. Please send your information to . Note of Interest: The use of PrintCapture has grown far beyond the initial target of oscilloscopes, logic analyzers, and spectrum analyzers. Customers are now using PrintCapture with many devices that we didn't envision or even know about. The equipment list table has gotten too large and has been moved to its own page. Click on equipment list to see the list. |
What can I do if my logic analyzer, spectrum analyzer, or oscilloscope doesn't have a serial printer or serial plotter output?Generally, there are two other interfaces available for hardcopy output:
|
What kind of serial cable do I need for my oscilloscope, logic analyzer, or spectrum analyzer?PrintCapture uses standard serial protocols to communicate with your oscilloscope, logic analyzer, or spectrum analyzer. PrintCapture only receives data from your test equipment - it does not transmit any data back to your test equipment. The serial communications signals discussed below are: TxD - Transmitted Data The serial port on a Windows-based computer is configured as DTE (Data Terminal Equipment). Some logic analyzers, spectrum analyzers, and oscilloscopes are also configured as DTE but some are configured as DCE (Data Communications Equipment). This configuration has more to do with the serial connector pin-outs than it does with operation. It is important to know the type of configuration on your test equipment in order to select the correct serial cable for the connection. If your test equipment is configured as DTE you will need a cable to connect DTE to DTE, or what is referred to as a "null-modem" cable, as shown below for 9-pin serial connectors. Use a Belkin F3B207 or equivalent for this cable.
If your test equipment is configured as DCE you will need a cable to connect DTE to DCE, or what is referred to as a "straight-through" cable, as shown below for 9-pin serial connectors. Use a Belkin F2N209 or equivalent for this cable.
Hardware handshaking (flow control) is used to ensure error-free data communication between PrintCapture and your oscilloscope, logic analyzer, or spectrum analyzer. Hardware handshaking uses voltage signals on the control lines of the serial cable to control whether sending or receiving is enabled. PrintCapture and the test equipment must agree on the type of handshaking used for a communications session. The following table describes the control signals, the direction of flow control, and the signal's effect on PrintCapture or the test equipment. For purposes of this discussion RTS/CTS handshaking is assumed. For DTR/DSR handshaking just switch the RTS/DTR and CTS/DSR labels.
You can change the serial port handshaking from Setup> Configuration> Serial Port> Handshake. Note: This information is also available in a PDF file that you can download by clicking here. |
I want to use National Instruments' GPIB-232CV-A or GPIB-232CT-A to convert from GPIB to serial. How do I configure these devices to work with PrintCapture?You should be aware that both of these GPIB-to-serial converters require a null-modem serial cable to connect the converter to your computer. Several of our customers have reported problems (read that as frustration) getting these GPIB-to-serial converters to work with their logic analyzer, spectrum analyzer, or oscilloscope. And, of course, we are the first place they turn to for help. Here's a little hint for you. If you decide to buy one of these GPIB-to-serial converters, and you don't know which converter will work with your test equipment, contact your local National Instruments Sales Office and talk with them. In many cases they will loan you one of their GPIB-to-serial converters, for up to 30 days, for you to try before you buy.
|
I want to use a USB-to-serial converter. Will this work with PrintCapture?Yes - and no. It appears that at least some of the USB-to-serial converter drivers don't duplicate the functionality of a normal serial port very well. The one USB-to-serial converter that we tried (it is a popular item) doesn't support handshaking at the driver level so we had to add method of controlling handshaking within the PrintCapture program. We called handshaking at the driver level automatic flow control because it is handled automatically by the serial port driver. The method of controlling handshaking within PrintCapture is called manual flow control. Beginning with version 2.9.1, the type of flow control (automatic or manual) can be changed in PrintCapture's Configuration dialog box (Setup> Configuration> Serial Port> Flow Control). This is what we found with our USB-to-serial converter:
We will add more information to this FAQ as we learn more about USB-to-serial converters. |
I want to use a Blackbox IC026A RS-232-to-IEEE-488 Interface Converter to convert from GPIB to serial. How do I configure these devices to work with PrintCapture?You should be aware that this GPIB-to-serial converter requires that you build your own serial cable to connect the converter to your computer. A standard straight-through or null-modem serial cable will not work correctly. There are serial cable wiring diagrams in the documentation for the IC026A. Several of our customers have reported problems (read that as frustration) getting this GPIB-to-serial converter to work with their logic analyzer, spectrum analyzer, or oscilloscope. And, of course, we are the first place they turn to for help. Here is how one of our customers configured his Blackbox IC026A to work with his HP8568B.
|
My test equipment has a GPIB output and my computer has a GPIB interface. Can PrintCapture be used with a GPIB interface?Yes - and no. As of version 3.0.0, PrintCapture supports GPIB interfaces that use National Instruments' NI-488.2 device driver. This includes nearly all of NI's GPIB interfaces and, perhaps, a few GPIB interfaces from other manufacturers. It is up to you to make sure that NI's NI-488.2 device driver and GPIB interface are properly installed before you attempt to use the GPIB interface with PrintCapture. See these links for specific manufacturer information: National Instruments, Agilent, Capital Equipment Corp., ICS Electronics, Keithley Instruments, Measurement Computing, Prologix. |
Can I use any of the GPIB interfaces available from National Instruments?Yes. Any of their GPIB interfaces that use the National Instruments' NI-488.2 device driver will work. National Instruments provides a handy chart on their website to help you match your operating system, an NI GPIB interface, and an NI-488.2 device driver. For a PC with a Windows operating system the typical NI GPIB interfaces include, but are not limited to: AT-GPIB ISA card series, GPIB-232CT-A RS-232 serial, GPIB-485CT-A RS-485 serial, GPIB-1284CT parallel port, GPIB-1394 Firewire, GPIB-ENET Ethernet, GPIB-USB USB, PCI-GPIB PCI card series, and PCMCIA-GPIB PC Card series. Make sure you fully understand the configuration among your computer, the NI GPIB interface, and the NI-488.2 device driver before spending your money on any of these interfaces. If you have any questions send us an email and we'll try to help you make a choice. One of our customers has both a PCMCIA-GPIB and a GPIB-USB-B interface. He found that PrintCapture worked just fine with the PCMCIA-GPIB interface but he couldn't get use his GPIB-USB-B interface at all. He solved the problem by tuning off System Controller in NI MAX (part of the NI-488.2 device driver installation) and setting PrintCapture to Listen-Only GPIB address. Please see these links for other GPIB interface manufacturer information: Agilent, Capital Equipment Corp., ICS Electronics, Keithley Instruments, Measurement Computing, Prologix. |
Can I use any of the GPIB interfaces available from Agilent?No, not at this time. We tried to add support for the Agilent device driver but ran into too many API incompatibilities. We will revisit the Agilent interfaces at some time in the future. For now, the only GPIB interfaces that can be used are the ones from National Instruments and Prologix. Please see these links for other GPIB interface manufacturer information: National Instruments, Capital Equipment Corp., ICS Electronics, Keithley Instruments, Measurement Computing, Prologix. |
Can I use any of the GPIB interfaces available from Capital Equipment Corp. (CEC)?No, not at this time. We tried to add support for the Capital Equipment (CEC) device driver but ran into too many API incompatibilities. We will revisit the CEC interfaces at some time in the future. For now, the only GPIB interfaces that can be used are the ones from National Instruments and Prologix. Please see these links for other GPIB interface manufacturer information: National Instruments, Agilent, ICS Electronics, Keithley Instruments, Measurement Computing, Prologix. |
Can I use any of the GPIB interfaces available from ICS Electronics (ICS)?No, not at this time. We tried to add support for the ICS Electronics (ICS) device driver but ran into too many API incompatibilities. We will revisit the ICS interfaces at some time in the future. For now, the only GPIB interfaces that can be used are the ones from National Instruments and Prologix. Please see these links for other GPIB interface manufacturer information: National Instruments, Agilent, Capital Equipment Corp., Keithley Instruments, Measurement Computing, Prologix. |
Can I use any of the GPIB interfaces available from Keithley Instruments?No, not at this time. We tried to add support for the Keithley device driver but ran into too many API incompatibilities. We will revisit the Keithley interfaces at some time in the future. For now, the only GPIB interfaces that can be used are the ones from National Instruments and Prologix. Please see these links for other GPIB interface manufacturer information: National Instruments, Agilent, Capital Equipment Corp., ICS Electronics, Measurement Computing, Prologix. |
Can I use any of the GPIB interfaces available from Measurement Computing?No, not at this time. We tried to add support for the Measurement Computing (MCS) device driver but ran into too many API incompatibilities. We will revisit the MCS interfaces at some time in the future. For now, the only GPIB interfaces that can be used are the ones from National Instruments and Prologix. Please see these links for other GPIB interface manufacturer information: National Instruments, Agilent, Capital Equipment Corp., ICS Electronics, Keithley Instruments, Prologix. |
Can I use any of the GPIB interfaces available from Prologix?Yes. The Prologix GPIB-USB devices use an FTDI device driver that creates a virtual COM port on your PC. And the virtual COM port can be used by PrintCapture. Be sure you printout the online manual to help you configure these devices. The Prologix GPIB-USB interface was developed by one of our customers and it works well with PrintCapture. You can find out more about this interface at Prologix. Nice little product that works well and is a very good alternative to the pricey National Instruments product lines. Please see these links for other GPIB interface manufacturer information: National Instruments, Agilent, Capital Equipment Corp., ICS Electronics, Keithley Instruments, Measurement Computing. |
Why do I receive only a partial image, or multiple incomplete images, from the same hardcopy request?The End-of-Data Processing timeout value is too short. This timeout value can be changed in PrintCapture's Configuration dialog box (Setup> Configuration> Serial Port> Timeout in seconds). Data processing for PrintCapture operates differently than data processing performed by a printer or plotter. A printer or plotter processes the data in real-time so the image is created as the data is received. PrintCapture, on the other hand, has to wait for all the data to arrive before the data can be processed to create an image. We tried to use the data itself to determine when the end-of-data occurred but ran into problems. The problem is that some oscilloscopes, logic analyzers, and spectrum analyzers have been found to send multiple end-of-data signals so PrintCapture can't really determine when the 'real' end-of-data has occurred. We settled on a timing solution. We wait for a user-selected number of seconds before deciding if the end-of-data has really occurred. If the timeout value is reached then it is assumed that all the data has been received. If more data comes in before the timeout then it is assumed that it is more image data to be processed. The timer runs at a 500 millisecond resolution. This means that the timeout values can only be in 500 millisecond increments and the lowest value is 500 milliseconds. If the image created from the data is only a partial image, increase the timeout value. But use the smallest reasonable value that works with your equipment. Note: If you print your data a second time while the data is being received from the first print request you will end up with a double image. Wait for an image to be created before printing again. |
I'm really having problems getting the serial data into my computer. What can I do to troubleshoot the serial interface?Getting the serial link between your oscilloscope, logic analyzer, or spectrum analyzer and your computer up and running can be a snap or it can frustrating as all get-out. Have patience! Sit back, take a deep breath, and let's get started. You should first read this information to get an overview of the procedure before you start troubleshooting your serial link. You need some basic information about your system in order to troubleshoot your serial link setup. And it doesn't matter if you are using a serial port straight from your test equipment or if you have to use a parallel-to-serial or GPIB-to-serial converter.
These are the items you are going to need to troubleshoot the serial link:
Now that you've gathered all the parts together it's time to start laying them out so you can see if you have everything you need. It's always easier to follow if the example is a concrete setup, so this is how we connect our Tektronix 430A to PrintCapture. Our computer has a 9-pin serial connector and the Tek 430A has a 9-pin male DTE serial connector. You will have to adjust the items a little to match your setup but it's basically the same. Don't make any connections yet - just lay them out on a table top so you can see if you have everything. Remember, this is the layout for our Tek 430A.
Now that you have the serial link all laid out on the table we can start our tests.
If you have made it this far you have all the information you need to successfully connect your oscilloscope, logic analyzer, or spectrum analyzer to your computer. Now it's time to analyze the cable that you 'constructed' above and it's pretty easy to do at this point.
At this point you should be able to print from your test equipment to PrintCapture. Note: This information is also available in a PDF file that you can download by clicking here. |
When I get a hardcopy in HPGL/2 format the image is too big or too small. What can I do about this?The method of processing HPGL/2 (Hewlett Packard Graphics Language) files lends itself to scaling. Some HPGL/2 files describe images that are too large or too small for documentation purposes. If you run across one of these files you can choose to scale the output to something that you can use. You can scale to a maximum height and/or width and you can choose to maintain the image's aspect ratio during scaling. To turn off any scaling set the height and width to 0. See Setup> Configuration> HPGL Processing> Height and Width. |
When I get a hardcopy in HPGL/2 format the image is in the wrong orientation. What can I do about this?HPGL/2 (Hewlett Packard Graphics Language) files generally have their origin in either the top-left or bottom-left corner of the image. Since there is no reliable way to tell from the data which orientation the image has, it is left up to you to decide if you want the image automatically rotated and by how much (see Setup> Configuration> HPGL Processing> Automatic Rotation). Automatic rotation is only used when an HPGL/2 file is received via the serial port. If an HPGL/2 file is opened with the File/Open menu item the image will not automatically rotate. In that case you can rotate the image with the Edit/Rotate menu item. |
When I try to get a hardcopy PrintCapture tries to process the data but then gives me a "This file was not recognized as an Epson, HPGL, PCL, or Text file." message. What's this mean?While processing the data PrintCapture couldn't find any size information in order to build the bitmap image. Usually this happens with color PCL data, although limited color processing is supported as of version 2.3.0. If you run across one of these files, enable Keep Raw Data (Setup> Configuration> Image Processing> Keep Raw Data), print the image again and e-mail the raw data file, along with as much information as you can provide to help us troubleshoot the program, to . |
I'm having some trouble getting serial data into PrintCapture. How can I test the serial port that PrintCapture is using?Getting a serial link up and running can be frustrating. Sometimes there are so many components to your serial link that it's hard to determine where the problem may be. One of the components that's relatively easy to test is the serial port being used by PrintCapture. Here is a small batch file that you can use to send data from one serial port to another (note: you will need a null-modem cable/adapter for this test): @echo off This batch file is used on our WinXP system to transmit data from COM4 to PrintCapture. COM4's serial port parameters (mode com4: ...) are set to match the parameters used by PrintCapture. You should change these parameters to match your system and setup. The batch file parameter "%1" is the name of the file you want to transmit to PrintCapture. You should put the file name in quotes (e.g. "your file name.ext") so you can use long file names. Assume the batch file is named "TestPC.bat" and the data file that you want to transmit to PrintCapture is named "Tek 430A PCL.pcw". The batch file and the data file should be in the same directory unless you install the batch file in a directory that is in your computer's environment path. To use the batch file you would enter: testpc "tek 430a pcl.pcw" You can download this batch file and its readme text file from here. For more help troubleshooting your serial link you can also look at FAQ What can I do to troubleshoot the serial interface? Note: This information is also available in a PDF file that you can download by clicking here. |
Home | Details | Downloads | FAQ | Revision History | Equipment List | Contact | LinksCopyright © 2001-2008
|
