Note that the test and measurement division of HP split of and is now called Agilent. Some of the references to HP below now are to Agilent.
Rocky Mountain BasicDuring the nineteen seventy and eighties the control language we used was HP Rocky Mountain Basic (RMB) so called because it was from the Colorado division of HP located in the Rocky Mountains. It ran on HP Work Station (WS) computers that were based on the Motorola 68xxx microprocessors. This was before there was an IBM PC.
I have HP 217, 318 and 340C+ WS computers and many version levels of RMB. To this day the instruments that HP makes that have IBasic inside the instrument are using a version of RMB. Programs can be written in HP Basic for Windows that will also run in IBasic.
Ted Dasher & Associates - TSA -Monterey Bay Communications - used HP RMB WS computers
I have developed all aspects of many dozens of ATE systems based on WS RMB. These have been used for testing microwave components and semiconductors both packaged and on wafer probes. A system was used to match the detectors for the AGM-45 Shrike missile.
Oswego UtilitiesThis was a third party software package of utilities that allowed things like restoring a "protected" RMB program. The protection was provided by (AFAICR) toggling a bit near the start of each line of code. When "protected" a printout would show the line number and just "*".
Since RMB has commands that allow peek and poke directly into the memory space many neet things can be done by writing in RMB. For example you can read the boot ROM. So the combination of the Oswego utilities and the capability of RMB allowed some very cleaver things to be done.
Interactive Test Generator HP E2000A
It may be that I have the name wrong as I write this (it's 2014). ITG seems to be about instrument drivers rather than test management. There was another software package that allow reducing the number of lines in a sub to one.
Because RMB included the ability to call subroutines and either explicitly pass parameters or make use of global parameters the subroutines could be easily added to a program. For example to set the frequency of the HP 8350B would be one sub, to set it's power level another sub, and so on. These subroutines could include printer formatting commands like a Form Feet at the top and bottom of the sub so that when you printed the program each sub was on it's own sheet of paper. By limiting the complexity of each sub so that it fit on one sheet of paper it was also easy to troubleshoot a problem with that sub.
The problem was there was a limit to the number of line numbers allowed so the complexity of any one program was limited. One way around this line limit was to use ITG. It allowed compiling a sub into something that only used one line number, so instead of using over 50 lines for a sub it now took only one line.
RMB Controllers - some called 9000 series workstations
Basic PlusThis is an extension to RMB WS, HP Basic for Windows and HTBasic that adds a GUI. Without the Plus addition the interface is either a command prompt or soft key driven. With the Plus add on the application program has a lot of the look and feel of a modern windows application.
AFAICR it requires Basic 6.2.
DOS UtilityThere is a DOS utility for WS RMB that allows programs to be written and read from 3.5" disks that are formatted in a PC as well as the classical HP LIF format that is not compatible with PC computers. There are some LIF to DOS programs that can be run on a PC, but they need just the right 3.5" disk drive to work. They will not work with most modern PC 3.5" disk drives.
Rack and Stack Systems has HP WS computers that can read these files and write the files onto DOS disks to allow transferring programs. Transferring data files requires a custom program that can read the LIF data disk and write the same data to a DOS data disk.
bySince WS RMB had a very large usage in the Automatic Test Equipment business it was clean room cloned by Trans Era. Their product is called HTBasic. By clean room cloned I mean that Trans Era developed it's HTBasic product in a legal way, it was not just a copy of the HP product.
Instrument Basic for WindowsThis was an HP product that was their first attempt to port WS RMB to the PC. It had a number of problems and was taken off the market after about a year. I used it to build an environmental step stress test system for a printed circuit board that turned on and off the DC power to the boards as well as communicating with them via RS-422 to check their status as well as logging any failures. This system has been working well and has been cloned by the customer because of it's value.
Instrument BasicInstrument Basic is a version of RMB that runs inside HP test equipment. These instruments will have a 3.5" disk drive and provision for an external keyboard (either HIL on older instruments or PS2 on newer ones). This is not a full RMB but has most of the functionality needed to control not only the instrument running it but also other instruments via the HP-IB connector. This is a very powerful way of automating a test system because it does not require a separate computer to act as the system controller. Note that features can be added to an instrument by means of a self contained IBasic program. Instrument Basic is different from Instrument Basic for Windows.
I have written a number of programs in the IBasic environment.
In order to maintain support for all their customers that were using WS RMB, HP now sells a version of HTBasic that they customize and support. It is called HP Basic for Windows and runs on WIN3.1, WIN95/98 and WINNT. It has support for HP-IB cards from many manufacturers including all the National Instruments GPIB cards. I have written a number of programs for this version of Basic.
Note that although the language is very close to the WS RMB, there are some differences in the way alpha and graphics data is displayed. This can cause some rewrite of the code when porting to HP Basic for Windows.
Because of problems with dongles and WIN NT the current version 6.32 does NOT require a dongle and is serial number locked in software.
Agilent stopped OEMing the TransEra product with version 2060D and now sends customers directly to TransEra.
Tams Basic - is a Linux vrsion
HP VEE is a product similar to LabVIEW. There are a number of differences. VEE uses a single large driver that does everything that HP thought of to control the instrument. This makes it harder to tell what is happening. Since the driver is so complex it is essentially impossible to modify it. HP supplies VEE drivers for most of it's instruments, but only supplies a few for other instrument brands. If your system uses only HP instruments and you are not trying to do something that strains the existing drivers then VEE may be a better solution in terms of time to market than LabVIEW. I am now learning VEE. There is a considerable difference in the "look" of VEE and LabVIEW data flow diagrams. I personally think the LabVIEW diagram tells you more about what the program is doing.
National Instruments started out by making HP-IB interface cards for about every computer that was popular. They grew into developing a language "LabVIEW" that has a graphical programming environment. They continue to expand their offering of both hardware and software in many market areas. N.I has started a number of independent foundations / organizations to develop standards in areas related to the hardware and software.
Although this language easily provides a Graphical User Interface (GUI) it's main advantage is that it is a graphical programming language rather than a text based language like RMB. It is a data flow language which means that the lines shown connecting the components of the graphical program represent data. Having a graphical image of the program helps to write programs that have fewer bugs as well as the automatic error checks that come with many of the constructs. Note that the time required to develop a system is about a order of magnitude quicker using LabVIEW than using WS RMB. WS RMB is at least an order of magnitude faster to develop an application than is "C". As the language goes down in level from LabVIEW to RMB to "C" more time is spent on getting all the programming details correct and less time on the heart of the code.
Note that although LabVIEW appears to be much easier to use than conventional text based languages, it still is a computer programming language and for anything more than a very simple application will require some learning on the part of the programmer. Do not think that an engineer is going to "learn" LabVIEW quickley if he has no prior programming experience.
There are dozens of add on packages for LabVIEW with more being added constantly. This is an area where National Instruments does well. In some cases N.I. has purchased a package developed by a third party and now supports the package.Rack and Stack Systems has written programs to control environmental equipment for testing fiber optic sensors used in aircraft. This included a temperature + altitude / humidity chamber, a furnace, random vibration system, a combined liquid level and flow bench and a combined pneumatic and hydralic pressure bench. Another system is used to test a large variety of military 1553 cable assemblies. This system has been cloned by the original customer since it works so well. Another system tests a PIC micro controller based circuit that dynamically drives an EL sign. A LabVIEW system to pass through HP-IB commands from the IEE-488 bus over a modem link, allowing remote control on instruments was done on a MacIntosh. Consulting on the use of LabVIEW is available from Rack and Stack Systems.
Labview Technical ResourceLTR publishes a hard copy magazine that comes with a floppy disk with the code for the example programs in each issue. They cover some needed topics in much greater depth than is covered in the LabVIEW documentation.
List Server for LabVIEW & FTP siteSend un/subscription messages to the Info-LabVIEW list processor at mailto:email@example.com
Send other administrative messages to the Info-LabVIEW list maintainer at mailto:info-labview-REQUEST@pica.army.mil
To broadcast a message to subscribers, send it to mailto:firstname.lastname@example.org
Please prefix your Subject lines with [A] for all platforms, [M] for Mac, [W] for Windows, [S] for Sun, or [H] for HP. When you respond to a message, quote pertinent sections rather than the entire message. Include your email address. If you receive a substantial number of responses to your query, particularly if they come in via private email, please post a summary of the comments.
Our ftp archives are at <ftp://ftp.pica.army.mil/pub/labview/>. If you wish to upload a vi or other material of interest, please place it in the incoming directory ftp://ftp.pica.army.mil/incoming/labview/ and email <email@example.com> with a description of what you've place there.
Brian's LabVIEW pages - Downloads -
ModemNOW! Suite - modem & pager tool kit by Microsys - also see LTR Vol 5 #1 and Vol 6 #3 for pager info
LabVIEW web ring -
SCPI - Standard Commands for Programmable InstrumentationHP developed a Test and Measurement Systems Language (TMSL) as described in "A Beginner's Guide to TMSL" HP p/n H2325-90001. In 1991 this book was re-titled "A Beginner's Guide to SCPI" HP put this language into the public domain to be administrated by the SCPI Consortium. Early test instruments had what is called R2D2 commands. For example to set the range and function you might sent the string "R2F3". This command was specific to one manufacturer and model number. If you changed the instrument you needed to change the code. With the advent of IEEE-488.2 there was a basis for a common set of commands and responses for instruments. Some instruments have the capability of using both R2D2 commands and SCPI commands. It takes much more work to write software in SCPI, but the usefulness of the code is higher with SCPI.
VISAVISA is an outgrowth of the VXIbus Consortium. Although much of it is standardized, some is not. If you have an N.I. card you can load the N.I. VISA software package into your computer and then run HP software or N.I. software and it will work. If you have an HP brand I/O card you can load the HP VISA software package and both N.I and HP software will work. If you have an N.I. I/O card, load the HP VISA package and just the N.I. VISA driver for the card it will NOT work. You must load the total VISA software package for the brand of hardware you are using. This also means that you can only have one brand of hardware in your system if you use VISA.
IVI Interchangeable Virtual InstrumentsThis is a new idea for National Instruments. To make the instrument driver independent of the manufacturer - model number. N.I has an IVI benefits web page and there is an IVI Foundation web page.
I wrote many WS RMB programs that had the interchangeable feature so that we could use different model numbers and manufacturers instruments in Automated Test Equipment. This was done using sub programs where the list of called parameters was the same for the different instruments of the same type. There was a routine that checked for the ID string of the instrument then set a parameter so that the proper sub programs for that instrument would be called by the rest of the program.
Other features of this class of program were:
- that if it was run without any instruments connected to the HP-IB, it would coach the operator in building the set up. This feature also was very helpful when an HP-IB cable became disconnected or bad.
- a sub program could be run by itself without any pass parameters. The sub program could tell that there were no pass parameters and prompt the operator for the information it needed to run. This was a great debugging feature to allow testing without the higher levels of program code.
TestStandThis is a product introduced in 1999. It is an outgrowth of the Test Executive add on to LabVIEW but now is a stand alone program. I am learning a little about it and so far it looks good.
Rack and Stack Systems is a member of the National Instruments ALLIANCE program.
Rack and Stack Systems is a CERTIFIED INSTRUMENT DRIVER DEVELOPER for LabVIEW. Note this involves not only understanding the types of problems that instruments often exhibit but also the philosophy of National Instruments that in turn is based on the VXI Plug-n-Play standards. A good driver removes all the instrument specific aspects of building an system. In some cases the driver can save 90% of the work in building a system. I have written on contract a number of drivers for HP microwave instruments. I have contributed a driver package for the Wiltron 5400 scalar network driver to the N.I. driver library.
Most systems that I work with use the IEEE-488 or now IEEE-488.2 bus. It was named HP-IB when HP invented it and National Instruments calls it the GPIB. National Instruments is promoting a change to IEEE-488 to allow a high speed version. This may not be a good idea. I have personally seen a case where the NI high speed (TNT) GPIB card and software would not work with an older instrument (HP 4278A) even though the high speed aspect was turned off. Other NI cards and HP cards all worked fine.
This is a 6 wire (1 pair serial Tx data, 1 pair serial Rx data and 1 pair DC power) high speed (100, 200, 400 Mbps and soon 1 Gbps) data bus that can handle multimedia audio and video and is being used as an alternative to IEEE-488.x for instrument control. There are slot zero cards for VXI that allow using an IEEE-1394 link between the control computer and the VXi cage. Although the data transfer rates are high, there is still overhead associated with a small packet.
About 800Mbit/sec Firewire by Michael D. Johas Teener
Zayante - silicon & software
Back to Rack and Stack Systems