1. Manuals
  2. Brands
  3. Omega Manuals
  4. Controller
  5. OMB-PER-488/W95
  6. User manual

Omega OMB-PER-488/W95 User Manual

Pc/ieee 488 controllers for windows 95/nt
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the OMB-PER-488/W95 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Omega OMB-PER-488/W95

Summary of Contents for Omega OMB-PER-488/W95

  • Page 2 Toll Free in England: 0800-488-488 e-mail: uk@omega.com It is the policy of OMEGA to comply with all worldwide safety and EMC/EMI regulations that apply. OMEGA is constantly pursuing certification of its products to the European New Approach Directives. OMEGA will add the CE mark to every appropriate device upon certification.
  • Page 3 Introduction to this Manual This manual is the Personal488 User’s Manual for Windows 95 and Windows NT. The material in this manual discusses PC/IEEE 488 controller interface hardware and their accompanying 32-bit driver software. This material is divided into the following sections: •...
  • Page 4 Notes Personal488 User's Manual For Windows 95 and Windows NT...

  • Page 5: Table Of Contents

    Table of Contents 1 – Personal488 Overview 5 – Personal488/AT (with AT488) Hardware Products……1 Introduction……15 Personal488/PCI (with PCI488)……1 The Package……15 Personal488/ATpnp (with At488pnp)……1 AT488 Specifications……15 Personal488/CARD (with CARD488)……1 Configuring the New Hardware……16 Personal488/AT (with AT488)……1 Installing the New Hardware & Hardware Personal488 (with GP488B)……1 Drivers……20 Personal488/MM (with GP488B/MM)……1...
  • Page 6 9 – API Command Reference Remote……95 RemoteList……96 Introduction……47 RemoveDevice……97 Abort……48 Request……98 Arm……49 Reset……99 AutoRemote……50 Resume……100 Buffered……51 SendCmd……101 BusAddress……52 SendData……102 CheckListener……53 SendEoi……103 Clear……54 SPoll……104 ClearList……55 SPollList……105 Close……56 Status……106 ControlLine……57 Stop……108 DigArm……58 Talk……109 DigArmSetup……59 Term……110 DigRead……60 TermQuery……111 DigSetup……61 TimeOut……112 DigWrite……62 TimeOutQuery……113 Disarm……63 Trigger……114 EnterX……64 TriggerList……115...

  • Page 7: Personal488 Overview

    Personal488 Overview Hardware Products……1 Personal488/PCI (with PCI488)……1 Personal488/ATpnp (with At488pnp)……1 Personal488/CARD (with CARD488)……1 Personal488/AT (with AT488)……1 Personal488 (with GP488B)……1 Personal488/MM (with GP488B/MM)……1 Hardware Accessories……2 Hardware Connection……2 Software Products……2 Driver488/W95 & Driver488/WNT……2 Hardware Products The family of Personal488 PC/IEEE 488 controller interfaces includes the six (6) interfaces which are discussed in this manual.

  • Page 8: Hardware Accessories

    Hardware Accessories The available hardware accessories are listed below by part number. Refer to your product catalog for details. Connector Cable • CA-7-3: Shielded IEEE 488 cable, 6 ft. Controller Device • IOT7210(P/T): IEEE 488 Controller Chip. Note: These specifications are subject to change without notice. Name: IOT7210 IEEE 488 Controller Chip Compatibility: 100% compatible with the NEC µ...

  • Page 9: Personal488/Pci (With Pci488)

    Personal488/PCI (with PCI488) Introduction……3 The Package……3 PCI488 Specifications……3 Controller Interface……3 Installing the New Hardware & Hardware Drivers……4 Updating the Existing Hardware Drivers……6 Introduction The Package The Personal488/PCI, including the IEEE 488 interface board and the Driver488 software, is carefully inspected, both mechanically and electrically, before shipment. When you receive the product, unpack all items carefully from the shipping carton and check for any obvious signs of physical damage that may have occurred during shipment.

  • Page 10: Installing The New Hardware & Hardware Drivers

    Installing the New Hardware & Hardware Drivers Typical IEEE 488 interface boards are installed into expansion slots inside the PC's system unit. Typical PCs have the following types of expansion slots • ISA expansion slots. ISA slots can either be an 8-bit slot with one card-edge receptacle (PC-bus compatible), or a 16-bit slot with two card-edge receptacles (AT-bus compatible).
  • Page 11 6. Replace the cover slot holding screw to secure the board in place. 7. Replace the computer's cover and screws. Then reconnect all power cords and cables to the back of the computer. If available, connect your external data acquisition instrument to the IEEE 488 port connector on the interface.

  • Page 12: Updating The Existing Hardware Drivers

    Updating the Existing Hardware Drivers Updating the PCI488 Interface Hardware Drivers 1. Insert the disk titled "Driver488 Driver Disk, 1 of 1" into the floppy disk drive. 2. Open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab.

  • Page 13: Personal488/Atpnp (With At488Pnp)

    Personal488/ATpnp (with AT488pnp) Introduction……7 The Package……7 AT488pnp Specifications……7 Controller Interface……7 Installing the New Hardware & Hardware Drivers……8 Updating the Existing Hardware Drivers……10 Introduction The Package The Personal488/ATpnp, including the IEEE 488 interface board and the Driver488 software, is carefully inspected, both mechanically and electrically, before shipment. When you receive the product, unpack all items carefully from the shipping carton and check for any obvious signs of physical damage that may have occurred during shipment.

  • Page 14: Installing The New Hardware & Hardware Drivers

    Installing the New Hardware & Hardware Drivers Typical IEEE 488 interface boards are installed into expansion slots inside the PC's system unit. Typical PCs have the following types of expansion slots • ISA expansion slots. ISA slots can either be an 8-bit slot with one card-edge receptacle (PC-bus compatible), or a 16-bit slot with two card-edge receptacles (AT-bus compatible).
  • Page 15 6. Replace the cover slot holding screw to secure the board in place. 7. Replace the computer's cover and screws. Then reconnect all power cords and cables to the back of the computer. If available, connect your external data acquisition instrument to the IEEE 488 port connector on the interface.

  • Page 16: Updating The Existing Hardware Drivers

    Updating the Existing Hardware Drivers Updating the AT488pnp Interface Hardware Drivers 1. Insert the disk titled "Driver488 Driver Disk, 1 of 1" into the floppy disk drive. 2. Open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab.

  • Page 17: Personal488/Card (With Card488)

    Personal488/CARD (with CARD488) Introduction……11 The Package……11 CARD488 Specifications……11 Controller Interface……11 Installing the New Hardware & Hardware Drivers……12 Updating the Existing Hardware Drivers……14 Introduction The Package The Personal488/CARD, including the IEEE 488 interface PC Card and the Driver488 software, is carefully inspected, both mechanically and electrically, before shipment. When you receive the product, unpack all items carefully from the shipping carton and check for any obvious signs of physical damage that may have occurred during shipment.

  • Page 18: Installing The New Hardware & Hardware Drivers

    Installing the New Hardware & Hardware Drivers Unlike typical IEEE 488 interface boards which are installed into expansion slots inside the PC’s system unit, the CARD488 PC Card interface is installed into the PC Card slot of the computer. The computer does not need to be turned off.
  • Page 19 Step 3: Verifying the CARD488 Interface Installation & Driver488 Software Settings 1. To confirm proper installation, open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab. Look for a device type named "IEEE488.2 Controllers"...

  • Page 20: Updating The Existing Hardware Drivers

    Updating the Existing Hardware Drivers Updating the 32-Bit Personal488/CARD Hardware Drivers 1. Insert the disk titled "Driver488 Driver Disk, 1 of 1" into the floppy disk drive. 2. Open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab.

  • Page 21: Personal488/At (With At488)

    Personal488/AT (with AT488) Introduction……15 The Package……15 AT488 Specifications……15 Configuring the New Hardware……16 Installing the New Hardware & Hardware Drivers……20 Updating the Existing Hardware Drivers……22 Introduction The Package The Personal488/AT, including the IEEE 488 interface board and the Driver488 software, is carefully inspected, both physically and electronically, before shipment.

  • Page 22: Configuring The New Hardware

    Configuring the New Hardware The following text will guide you through the setup of your IEEE 488 controller interface. It includes instructions on how to verify the resource settings of ports in your system, and how to properly configure the switches/jumpers on your interface board. To avoid a configuration conflict, you must first verify which I/O addresses, IRQs, and DMAs are being used by existing ports in your system, prior to configuring and installing the IEEE 488 controller interface.
  • Page 23 Step 2: Configuring the AT488 Interface I/O Base Address 1. The factory default I/O base address is . If this creates a conflict, reset switch S1 according to 02E1 the figure and following table. The register addresses will be automatically relocated at fixed offsets from the base address.
  • Page 24 Step 3: Configuring the AT488 Interface Interrupt (IRQ) 1. The factory default Interrupt (IRQ) is 7. If this creates a conflict, reset switch S2 and jumper IRQ according to the figure. The switch and jumper settings must both indicate the same interrupt level for correct operation with interrupts.
  • Page 25 Step 4: Configuring the AT488 Interface DMA Channel 1. The factory default DMA channel is 5. If this creates a conflict, reset jumpers DACK and DRQ according to the figure. Both the DRQ and DACK jumpers must be set to the desired DMA channel for proper operation.

  • Page 26: Installing The New Hardware & Hardware Drivers

    Installing the New Hardware & Hardware Drivers Typical IEEE 488 interface boards are installed into expansion slots inside the PC's system unit. Typical PCs have the following types of expansion slots • ISA expansion slots. ISA slots can either be an 8-bit slot with one card-edge receptacle (PC-bus compatible), or a 16-bit slot with two card-edge receptacles (AT-bus compatible).
  • Page 27 Step 3: Verifying the AT488 Interface Installation & Driver488 Software Settings 1. To confirm proper installation, open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab. Look for a device type named "IEEE488.2 Controllers"...

  • Page 28: Updating The Existing Hardware Drivers

    Updating the Existing Hardware Drivers Updating the AT488 Interface Hardware Drivers 1. Insert the disk titled "Driver488 Driver Disk, 1 of 1" into the floppy disk drive. 2. Open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab.

  • Page 29: Personal488 (With Gp488B)

    Personal488 (with GP488B) Introduction……23 The Package……23 GP488B Specifications……23 Configuring the New Hardware……24 Installing the New Hardware & Hardware Drivers……28 Updating the Existing Hardware Drivers……30 Configuring Other Hardware Settings……31 Introduction The Package The Personal488, including the IEEE 488 interface board and the Driver488 software, is carefully inspected, both mechanically and electrically, before shipment.

  • Page 30: Configuring The New Hardware

    Configuring the New Hardware The following text will guide you through the setup of your IEEE 488 controller interface. It includes instructions on how to verify the resource settings of ports in your system, and how to properly configure the switches/jumpers on your interface board. To avoid a configuration conflict, you must first verify which I/O addresses, IRQs, and DMAs are being used by existing ports in your system, prior to configuring and installing the IEEE 488 controller interface.
  • Page 31 Step 2: Configuring the GP488B Interface I/O Base Address 1. The factory default I/O base address is . If this creates a conflict, reset SW1 microswitches 4 02E1 and 5 according to the figure and following table. The register addresses will be automatically relocated at fixed offsets from the base address.
  • Page 32 Step 3: Configuring the GP488B Interface Interrupt (IRQ) 1. The factory default Interrupt (IRQ) is 7. If this creates a conflict, reset SW1 microswitches 1, 2, and 3, and jumper J4 according to the figure. The switch and jumper settings must both indicate the same interrupt level for correct operation with interrupts.
  • Page 33 Step 4: Configuring the GP488B Interface DMA Channel 1. The factory default DMA channel is 1. If this creates a conflict, reset jumper J3 according to the figure. 2. If reset, record the new DMA channel being used. Direct Memory Access (DMA) is a high-speed method of transferring data from or to a peripheral, such as a digitizing oscilloscope, to or from the PC’s memory.

  • Page 34: Installing The New Hardware & Hardware Drivers

    Installing the New Hardware & Hardware Drivers Typical IEEE 488 interface boards are installed into expansion slots inside the PC's system unit. Typical PCs have the following types of expansion slots: • ISA expansion slots. ISA slots can either be an 8-bit slot with one card-edge receptacle (PC-bus compatible), or a 16-bit slot with two card-edge receptacles (AT-bus compatible).
  • Page 35 Step 3: Verifying the GP488B Interface Installation & Driver488 Software Settings 1. To confirm proper installation, open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab. Look for a device type named "IEEE488.2 Controllers"...

  • Page 36: Updating The Existing Hardware Drivers

    Updating the Existing Hardware Drivers Updating the GP488B Interface Hardware Drivers 1. Insert the disk titled "Driver488 Driver Disk, 1 of 1" into the floppy disk drive. 2. Open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab.

  • Page 37: Configuring Other Hardware Settings

    Configuring Other Hardware Settings Configuring the GP488B Interface Wait State The GP488B is fast enough to be compatible with virtually every PC/XT/AT-compatible computer on the market. Even if the computer is very fast, the processor is normally slowed to 8 MHz or below when accessing the I/O channel.
  • Page 38 Notes Personal488 (with GP488B) Personal488 User's Manual For Windows95 and Windows NT...

  • Page 39: Personal488/Mm (With Gp488B/Mm)

    Personal488/MM (with GP488B/MM) Introduction……33 The Package……33 GP488B/MM Specifications……33 Configuring the New Hardware……34 Installing the New Hardware & Hardware Drivers……38 Updating the Existing Hardware Drivers……40 Configuring Other Hardware Settings……40 Introduction The Package The Personal488/MM, including the IEEE 488 interface board and the Driver488 software, is carefully inspected, both mechanically and electrically, before shipment.

  • Page 40: Configuring The New Hardware

    Configuring the New Hardware The following text will guide you through the setup of your IEEE 488 controller interface. It includes instructions on how to verify the resource settings of ports in your system, and how to properly configure the switches/jumpers on your interface board. To avoid a configuration conflict, you must first verify which I/O addresses, IRQs, and DMAs are being used by existing ports in your system, prior to configuring and installing the IEEE 488 controller interface.
  • Page 41 The I/O base address, IRQ, and DMA settings are switch/jumper selectable via the following locations on the GP488B/MM interface board: One 8-microswitch DIP switch labelled SW1, two 12-pin headers labelled JP2 and JP3, and one 3-pin header labelled JP1. The DIP switch settings, and the arrangement of the jumpers on the headers set the hardware configuration.
  • Page 42 Step 3: Configuring the GP488B/MM Interface Interrupt (IRQ) 1. The factory default Interrupt (IRQ) is 7. If this creates a conflict, reset SW1 microswitches 1, 2, and 3, and jumper JP3 according to the figure. The switch and jumper settings must both indicate the same interrupt level for correct operation with interrupts.
  • Page 43 Step 4: Configuring the GP488B/MM Interface DMA Channel 1. The factory default DMA channel is 1. If this creates a conflict, reset jumper JP2 according to the figure. 2. If reset, record the new DMA channel being used. Direct Memory Access (DMA) is a high-speed method of transferring data from or to a peripheral, such as a digitizing oscilloscope, to or from the PC’s memory.

  • Page 44: Installing The New Hardware & Hardware Drivers

    Installing the New Hardware & Hardware Drivers Unlike typical IEEE 488 interface boards which are installed into expansion slots inside the PC’s system unit, the GP488B/MM Mini-Module interface board is installed into the Ampro PC/104 board by using its “stack-through” connector. For technical assistance, see chapter Troubleshooting on page 119 in this manual, or the troubleshooting section in your PC’s manual.
  • Page 45 Step 3: Verifying the GP488B/MM Interface Installation & Driver488 Software Settings 1. To confirm proper installation, open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab. Look for a device type named "IEEE488.2 Controllers"...

  • Page 46: Updating The Existing Hardware Drivers

    Updating the Existing Hardware Drivers Updating the GP488B/MM Interface Hardware Drivers 1. Insert the disk titled "Driver488 Driver Disk, 1 of 1" into the floppy disk drive. 2. Open the Control Panel window from the Start > Settings menu, click on the System icon, and select the Device Manager tab.

  • Page 47: Driver488/W95 & Driver488/Wnt

    Driver488/W95 & Driver488/WNT Introduction……41 Differences from 16-Bit Driver488 Software……41 Programming Support……42 16-Bit Driver488/W95 Compatibility Layer……42 Configuration Utility……42 Configuring the Driver488 Software Settings……43 Introduction Differences from 16-Bit Driver488 Software The following list provides the general differences between 32-bit Driver488 software (for Windows 95 and Windows NT), and 16-bit Driver488 software (for Windows 3.X).

  • Page 48: Programming Support

    Programming Support Driver488/W95 and Driver488/WNT both provide language interfaces for Microsoft C, Visual Basic, Borland C++, and Borland Delphi. These 32-bit drivers make IEEE events in your C or C++ applications conform to Windows’ standard event handling scheme, passing IEEE events such as bus errors and SRQs to Windows as standard messages.

  • Page 49: Configuring The Driver488 Software Settings

    Configuring the Driver488 Software Settings Note: The following configuration information is software oriented. It is assumed that you have already successfully performed the necessary hardware and hardware driver installations, as provided in the appropriate hardware chapter of this manual. Step 1: Opening the Configuration Utility 1.
  • Page 50 • Interrupt: This field is the hardware interrupt level (IRQ). IRQ is not an option; it is a requirement. Valid settings for the interrupt levels of specific boards, are provided in the chart. • DMA: A DMA channel can be specified for use. If DMA is to be used, select a channel as per the hardware setting.
  • Page 51 1. From the Interfaces and Devices tab of the IEEE 488 Interface Properties dialog box, click on the “+” node symbol located just to the left of the desired interface. A list of external devices associated with that interface will display. 2.
  • Page 52 Notes Driver488/W95 & Driver488/WNT Personal488 User's Manual For Windows95 and Windows NT...

  • Page 53: Introduction

    API Command Reference OnDigEventVDM……82 Introduction……47 OnEvent……83 Abort……48 OnEventVDM……84 Arm……49 OpenName……86 AutoRemote……50 OutputX……87 Buffered……51 PassControl……89 BusAddress……52 PPoll……90 CheckListener……53 PPollConfig……91 Clear……54 PPollDisable……92 ClearList……55 PPollDisableList……93 Close……56 PPollUnconfig……94 ControlLine……57 Remote……95 DigArm……58 RemoteList……96 DigArmSetup……59 RemoveDevice……97 DigRead……60 Request……98 DigSetup……61 Reset……99 DigWrite……62 Resume……100 Disarm……63 SendCmd……101 EnterX……64 SendData……102 Error……66 SendEoi……103 FindListener……67...

  • Page 54: Api Command Reference

    Abort Syntax INT WINAPI Abort(DevHandleT devHandle); refers to either an IEEE 488 hardware interface or an external device. If devHandle devHandle refers to an external device, the Abort command will act on the hardware interface to which the external device is attached. Returns if error Mode...

  • Page 55: Arm

    Syntax INT WINAPI Arm(DevHandleT devHandle, ArmCondT condition); refers to either an IEEE 488 hardware interface or an external device. If devHandle devHandle refers to an external device, the command acts on the hardware interface to which the external device is attached. condition is one of the following: acError...

  • Page 56: Autoremote

    AutoRemote Syntax INT WINAPI AutoRemote(DevHandleT devHandle, BOOL flag); refers to either an IEEE 488 hardware interface or an external device. If devHandle devHandle refers to an external device, the AutoRemote command acts on the hardware interface to which the external device is attached. flag may be either Returns...

  • Page 57: Buffered

    Buffered Driver488/W95 only Syntax LONG WINAPI Buffered(DevHandleT devHandle); refers to either an IEEE 488 hardware interface or an external device. If devHandle devHandle refers to an external device, the Buffered command acts on the hardware interface to which the external device is attached. Returns if error 1,048,575(2 20 -1)

  • Page 58: Busaddress

    BusAddress Syntax INT WINAPI BusAddress (DevHandleT devHandle, BYTE primary, BYTE secondary); devHandle refers to either an IEEE 488 hardware interface or an external device. primary is the IEEE 488 bus primary address of the specified device. secondary is the IEEE 488 bus secondary address of the specified device. If the specified device is an IEEE 488 hardware interface, this value must be since there are no secondary addresses for the IEEE 488 hardware interface.

  • Page 59: Checklistener

    CheckListener Syntax INT WINAPI CheckListener(DevHandleT devHandle, BYTE primary, BYTE secondary); devHandle refers to either an IEEE 488 hardware interface or an external device. If devHandle refers to an external device, the CheckListener command acts on the hardware interface to which the external device is attached. primary is the primary bus address to check for a Listener ( secondary...

  • Page 60: Clear

    Clear Syntax INT WINAPI Clear(DevHandleT devHandle); refers to either an IEEE 488 hardware interface or an external device. If devHandle devHandle refers to a hardware interface, then a Device Clear ( ) is sent. If devHandle refers to an external device, a Selected Device Clear ( ) is sent.

  • Page 61: Clearlist

    ClearList Syntax INT WINAPI ClearList(DevHandlePT dhList); is a pointer to a list of device handles that refer to external devices. If a hardware dhList interface is in the list, is sent instead of Returns if error Mode ATN• • DCL Bus States (all devices) ATN•...

  • Page 62: Close

    Close Syntax INT WINAPI Close(DevHandleT devHandle); refers to either an IEEE 488 interface or an external device. devHandle Returns if error Mode Bus States Completion of any pending I/O activities Example errorcode = Close(wave); See Also OpenName, MakeDevice, Wait command waits for I/O to complete, flushes any buffers associated with the device that is Close being closed, and then invalidates the handle associated with the device.

  • Page 63: Controlline

    ControlLine Syntax INT WINAPI ControlLine(DevHandleT devHandle); returns a bit mapped number. ControlLine refers to the I/O adapter. If refers to an external device, the devHandle devHandle ControlLine command acts on the hardware interface to which the external device is attached. Response if error otherwise, a bit map of the current state of the IEEE 488 interface.

  • Page 64: Digarm

    DigArm AT488pnp and PCI488 only Syntax INT WINAPI DigArm(DevHandleT devHandle, BOOL bArm); refers to an interface handle. devHandle bArm refers to a value that arms or disarms event generation. TRUE = Arm, FALSE Disarm. Returns if neither nibble is set for input, or other error Mode Bus States None...

  • Page 65: Digarmsetup

    DigArmSetup AT488pnp and PCI488 only Syntax INT WINAPI DigArmSetup(DevHandleT devHandle, BYTE byMatchValue); devHandle refers to an interface handle. byMatchValue refers to a value that is compared against the digital I/O inputs Returns if error Mode Bus States None Example DigArmSetup(devHandle, 0xA5); Sets the match value to 0xA5 See Also...

  • Page 66: Digread

    DigRead AT488pnp and PCI488 only Syntax INT WINAPI DigRead(DevHandleT devHandle); refers to an interface handle. devHandle Returns if no part of the port is configured for input, or other error otherwise, integer between if the entire digital I/O port is configured for input; or integer between if only one nibble (either low or high) is configured for input Mode...

  • Page 67: Digsetup

    DigSetup AT488pnp and PCI488 only Syntax INT WINAPI DigSetup(DevHandleT devHandle, BOOL bLowOut, BOOL bHighOut); devHandle refers to an interface handle. bLowOut refers to the lower nibble setup. TRUE = output, FALSE = input. bHighOut refers to the upper nibble setup. TRUE = output, FALSE...

  • Page 68: Digwrite

    DigWrite AT488pnp and PCI488 only Syntax INT WINAPI DigWrite(DevHandleT devHandle, BYTE byDigData); refers to an interface handle. devHandle byDigData refers to a value to write to the digital output port, where the integer range is between if the entire digital I/O port is configured for output, or between if only one nibble (either low or high) is configured for output.

  • Page 69: Disarm

    Disarm Syntax INT WINAPI Disarm(DevHandleT devHandle, ArmCondT condition); refers to either an IEEE 488 interface or an external device. If devHandle devHandle refers to an external device, then the Disarm command acts on the hardware interface to which the external device is attached. condition specifies which of the conditions are no longer to be monitored.

  • Page 70: Enterx

    EnterX Syntax LONG WINAPI EnterX(DevHandleT devHandle, LPBYTE data,DWORD count,BOOL forceAddr,TermT*term,BOOL async,LPDWORD compStat); devHandle refers to either an IEEE 488 interface or an external device. data is a pointer to the buffer into which the data is read. count is the number of characters to read. forceAddr is used to specify whether the addressing control bytes are to be issued for each...
  • Page 71 Enter Syntax LONG WINAPI Enter(DevHandleT devHandle, LPBYTE data) Remarks is equivalent to the following call to Enter EnterX EnterX(devHandle,data,sizeof(data),1,0L,0,0L); function passes the device handle and a pointer to the data buffer to the function. Enter EnterX It determines the size of the data buffer that you provided, and passes that value as the count parameter.

  • Page 72: Error

    Error Syntax INT WINAPI Error(DevHandleT devHandle, BOOL display); refers to either an IEEE 488 interface or an external device. devHandle indicates whether the error message display should be display Returns if error Mode Bus States None Example errorcode = Error(ieee, OFF); See Also OnEvent, GetError, GetErrorList, Status command enables or disables automatic on-screen display of Driver488 error messages.

  • Page 73: Findlistener

    FindListeners Syntax INT WINAPI FindListeners(DevHandleT devHandle, BYTE primary, LPWORD listener, DWORD limit); devHandle refers to either an IEEE 488 interface or an external device. If devHandle refers to an external device, then the FindListeners command acts on the hardware interface to which the external device is attached. primary is the primary IEEE 488 bus address to check.

  • Page 74: Finish

    Finish Driver488/W95 only Syntax INT WINAPI Finish(DevHandleT devHandle); devHandle refers to either an IEEE 488 interface or an external device. If devHandle refers to an external device, the Finish command acts on the hardware interface to which the external device is attached. Returns if error Mode...

  • Page 75: Geterror

    GetError Syntax ErrorCodeT WINAPI GetError(DevHandleT devHandle, LPSTR errText); devHandle refers to either the IEEE 488 interface or the external device that has the associated error. errText is the string that will contain the error message. If errText is non-null, the string must contain at least 247 bytes.

  • Page 76: Geterrorlist

    GetErrorList Syntax ErrorCodeT WINAPI GetErrorList(DevHandlePT dhList, LPSTR errText, DevHandlePT errHandle); dhList is a pointer to a list of external devices that was returned from a function, due to an error associated with one of the external devices in the list. errText is the text string that contains the error message.

  • Page 77: Hello

    Hello Syntax INT WINAPI Hello(DevHandleT devHandle, LPSTR message); refers to either an IEEE 488 interface or an external device. If devHandle devHandle refers to an external device, the Hello command acts on the hardware interface to which the external device is attached. message is a character pointer that contains the returned message.

  • Page 78: Keepdevice

    KeepDevice Syntax INT WINAPI KeepDevice(DevHandleT devHandle); refers to an external device. devHandle Returns if error Mode Bus States None Example errorcode = KeepDevice(scope); See Also MakeDevice, MakeNewDevice, RemoveDevice, OpenName Note: will update an existing device or will create a new device in the Registry. This KeepDevice update feature is new and useful.

  • Page 79: Listen

    Listen Syntax INT WINAPI Listen(DevHandleT devHandle, BYTE pri, BYTE sec); refers to either an IEEE 488 interface or an external device. If devHandle devHandle refers to an external device, the Listen command acts on the associated interface. specify the primary and secondary addresses of the device which is to be addressed to listen.

  • Page 80: Local

    Local Syntax INT WINAPI Local(DevHandleT devHandle); refers to either an IEEE 488 interface or an external device. devHandle Returns if error Mode Bus States *REN Examples errorcode = Local(ieee); To unassert the Remote Enable ( ) line, the IEEE 488 interface is specified. errorcode = Local(wave);...

  • Page 81: Locallist

    LocalList Syntax INT WINAPI LocalList(DevHandlePT dhList); refers to a pointer to a list of external devices. dhList Returns if error Mode Bus States ATN• • UNL, MTA, LAG,GTL Example deviceList[0] = wave; Sends the Go To Local ( ) bus deviceList[1] = timer;...

  • Page 82: Lol

    Syntax INT WINAPI Lol(DevHandleT devHandle); refers to either an IEEE 488 interface or an external device. If devHandle devHandle refers to an external device, the command acts on the hardware interface to which the external device is attached. Returns if error Mode ATN•...

  • Page 83: Makedevice

    MakeDevice Syntax INT WINAPI MakeDevice(DevHandleT devHandle, LPSTR name); refers to an existing external device. devHandle is the device name of the device that is to be made and takes the configuration of the name device given by devHandle Returns if error otherwise, the of the new device.

  • Page 84: Makenewdevice

    MakeNewDevice Syntax DevHandleT WINAPI MakeNewDevice(LPSTR iName, LPSTR aName,BYTE primary,BYTE secondary,TermPT In,TermPT Out,DWORD tOut); devHandle refers to the new external device. iName is the user name of the interface on which the device is to be created. aName is the user name of the device. are the secondary and primary bus addresses to be specified.

  • Page 85: Mylistenaddr

    MyListenAddr Syntax INT WINAPI MyListenAddr (DevHandleT devHandle); devHandle refers to either an interface or an external device. If devHandle refers to an external device, the MyListenAddr command acts on the associated interface. Returns if error Mode Bus States ATN, MLA Example errorcode = MyListenAddr (ieee);...

  • Page 86: Mytalkaddr

    MyTalkAddr Syntax INT WINAPI MyTalkAddr (DevHandleT devHandle); refers to either an interface or an external device. If refers to an devHandle devHandle external device, the MyTalkAddr command acts on the associated interface. Returns if error Mode Bus States ATN, MTA Example errorcode = MyTalkAddr (ieee);...

  • Page 87: Ondigevent

    OnDigEvent AT488pnp and PCI488 only Syntax INT WINAPI OnDigEvent(DevHandleT devHandle, HWND hwnd, OpaqueP lParam); devHandle refers to an interface handle. hwnd is the window handle to receive event notification. lParam value will be passed in the notification message. Returns if error Mode Bus States None...

  • Page 88: Ondigeventvdm

    OnDigEventVDM AT488pnp and PCI488 only Syntax INT WINAPI OnDigEventVDM(DevHandleT devHandle, DigEventFuncT func, OpaqueP lParam); devHandle refers to an interface handle. func is a user-defined function to be called when the digital match event is triggered. lParam value will be passed in the notification message. Returns if error Mode...

  • Page 89: Onevent

    OnEvent Syntax INT WINAPI OnEvent(DevHandleT devHandle, HWND hWnd, OpaqueP lParam); devHandle refers to either an interface or an external device. hWnd is the window handle to receive the event notification. lParam value will be passed in the notification message. Returns if error Mode Bus States...

  • Page 90: Oneventvdm

    OnEventVDM Syntax INT WINAPI OnEventVDM(DevHandleT devHandle, EventFuncT func); refers to either an interface or an external device. devHandle is a user-specified interrupt-handler function that is to perform some user-defined func function, when one of the ed conditions occur. Returns if error Mode Bus States None...
  • Page 91 // Normally, your program would be off doing other work, for // this example we will just hold here for a short time. For(result = 0; result 30000; result++) { printf(“Result is %06d\r”, result); printf(“\n\n”); qsk(xfered, Spoll(wave16)); qsk(x, Close(wave14)); qsk(x, Close(wave16)); qsk(x, Close(ieee0));...

  • Page 92: Openname

    OpenName Syntax DevHandleT WINAPI OpenName(LPSTR name); is the name of an interface or external device. name Returns if error otherwise, the device handle associated with the given name Mode Bus State None Examples dmm = OpenName(“DMM”); Opens the external device dmm = OpenName(“IEEE:DMM”);...

  • Page 93: Outputx

    OutputX Syntax LONG WINAPI OutputX(DevHandleT devHandle, LPBYTE data, DWORD count, BOOL last, BOOL forceAddr, TermT *terminator, BOOL async, LPDWORD compStat); devHandle refers to either an interface or an external device. If devHandle refers to an external device, the OutputX command acts on the hardware interface to which the external device is attached.
  • Page 94 Additional Output Functions Driver488 provides additional functions that are short-form versions of the function. Output OutputX The following functions are already defined in your header file. Output Output Syntax LONG WINAPI Output(DevHandleT devHandle,LPBYTE data); Remarks Output is equivalent to the following call to OutputX OutputX(devHandle,data,strlen(data),1,1,0L,0,0L);...

  • Page 95: Passcontrol

    PassControl Syntax INT WINAPI PassControl(DevHandleT devHandle); devHandle refers to an external device to which control is passed. Returns if error Mode ATN• • UNL, MLA, TAG, UNL, TCT, *ATN Bus States Example errorcode = PassControl(scope); See Also Abort, Reset, SendCmd command allows Driver488 to give control to another controller on the bus.

  • Page 96: Ppoll

    PPoll Syntax INT WINAPI PPoll(DevHandleT devHandle); refers to either an interface or an external device. If refers to an devHandle devHandle external device, then the PPoll command acts on the hardware interface to which the external device is attached. Returns if error otherwise, a number in the range 0 to 255 Mode...

  • Page 97: Ppollconfig

    PPollConfig Syntax INT WINAPI PPollConfig(DevHandleT devHandle,BYTE ppresponse); refers to either an interface or an external device to configure for the Parallel devHandle Poll. is the decimal equivalent of the four binary bits , and where ppresponse the Sense bit, and , and assign the bus data line used for the response.

  • Page 98: Ppolldisable

    PPollDisable Syntax INT WINAPI PPollDisable(DevHandleT devHandle); is either an interface or an external device that is to have its Parallel Poll devHandle response disabled. Returns if error Mode Bus States ATN• • UNL, MTA, LAG, PPC, PPD Example errorcode = PPollDisable(dmm); Disables Parallel Poll of device See Also PPoll, PPollConfig, PPollUnconfig...

  • Page 99: Ppolldisablelist

    PPollDisableList Syntax INT WINAPI PPollDisableList(DevHandlePT dhList); is a pointer to a list of external devices that are to have their Parallel Poll response dhList disabled. Returns if error Mode Bus States ATN• • UNL, MTA, LAG, PPC, PPD Example deviceList[0] = wave; deviceList[1] = timer;...

  • Page 100: Ppollunconfig

    PPollUnconfig Syntax INT WINAPI PPollUnconfig(DevHandleT devHandle); refers to a hardware interface. If refers to an external device, devHandle devHandle then the PPollUnconfig command acts on the hardware interface to which the external device is attached. Returns if error Mode ATN• • PPU Bus States Example errorcode = PPollUnconfig(ieee);...

  • Page 101: Remote

    Remote Syntax INT WINAPI Remote(DevHandleT devHandle); refers to either an interface or an external device. If refers to an devHandle devHandle interface, then the Remote Enable ( ) line is asserted. If devHandle refers to an external device, then that device is addressed to Listen and placed into the Remote state.

  • Page 102: Remotelist

    RemoteList Syntax INT WINAPI RemoteList(DevHandlePT dhList); is a pointer to a list of devices. dhList Returns if error Mode SC• • CA REN, ATN• • UNL, MTA, LAG Bus States Example deviceList[0] = wave; Asserts the bus line and deviceList[1] = timer; addresses a list of specified devices to Listen, to place deviceList[2] = dmm;...

  • Page 103: Removedevice

    RemoveDevice Syntax INT WINAPI RemoveDevice(DevHandleT devHandle); specifies an interface or an external device to remove. devHandle Returns if error Mode Bus States None Example errorcode = RemoveDevice(dmm); See Also MakeDevice, KeepDevice command removes the specific temporary or permanent Driver488 device that RemoveDevice was created with either the command or the startup configuration.

  • Page 104: Request

    Request Syntax INT WINAPI Request(DevHandleT devHandle, BYTE spstatus); refers to either an interface or an external device. If refers to an devHandle devHandle external device, the Request command acts on the hardware interface to which the external device is attached. spstatus is the Service Request status in the range Returns...

  • Page 105: Reset

    Reset Syntax INT WINAPI Reset(DevHandleT devHandle); refers to either an interface or an external device. If refers to an devHandle devHandle external device, the Reset command acts on the hardware interface to which the external device is attached. Returns if error Mode Bus States None...

  • Page 106: Resume

    Resume Driver488/W95 only Syntax INT WINAPI Resume(DevHandleT devHandle, BOOL monitor); devHandle refers to either an interface or an external device. If devHandle refers to an external device, then the Resume command acts on the hardware interface to which the external device is attached. monitor is a flag that when it is , Driver488 monitors the data.

  • Page 107: Sendcmd

    SendCmd Syntax INT WINAPI SendCmd(DevHandleT devHandle, LPBYTE commands, DWORD len); devHandle refers to an interface handle. commands points to a string of command bytes to be sent. is the length of the command string. Response None Mode Bus States User-defined Example char command[] = “U?0";...

  • Page 108: Senddata

    SendData Syntax INT WINAPI SendData(DevHandleT devHandle, LPBYTE data, DWORD len); devHandle refers to an interface handle. data points to a string of data bytes to be sent. is the length of the data string. Response None Mode Bus States User-defined Example char data[] = “W0X”;...

  • Page 109: Sendeoi

    SendEoi Syntax INT WINAPI SendEoi(DevHandleT devHandle, LPBYTE data, DWORD len); devHandle refers to an interface handle. data points to a string of data bytes to be sent. is the length of the data string. Response None Mode Bus States User-defined Example char data[] = “W0X”;...

  • Page 110: Spoll

    SPoll Syntax INT WINAPI SPoll(DevHandleT devHandle); refers to either an interface or a specific external device. devHandle Returns if error otherwise, (hardware interface) in the range (external device) Mode Bus States ATN• • UNL, MLA, UNT, TAG, SPE, *ATN, ATN• • SPD, UNT Examples errorcode = SPoll(ieee);...

  • Page 111: Spolllist

    SPollList Syntax INT WINAPI SPollList(DevHandlePT dhList, LPBYTE result, BYTE flag); dhList is a pointer to a list of external devices. result is an array that is filled in with the Serial Poll results of the corresponding external devices. flag refers to either WHILE_SRQ , or UNTIL_RSV...

  • Page 112: Status

    Status Syntax INT WINAPI Status(DevHandleT devHandle, IeeeStatusPT result); refers to either an IEEE 488 interface or an external device. If devHandle devHandle refers to an external device, Status acts on the hardware interface to which the external device is attached. result is a pointer to a Status...
  • Page 113 • The ByteIn ( ) indicator is set when the I/O adapter has received a byte that can be read by .byteIn command. The ByteOut ( ) indicator is set when the I/O adapter is ready to Enter .byteOut output data. The Service Request field ( ), as an active controller, reflects the IEEE 488 bus .SRQ line signal.

  • Page 114: Stop

    Stop Driver488/W95 only Syntax INT WINAPI Stop(DevHandleT devHandle); devHandle refers to either an interface or an external device. If devHandle refers to an external device, the Stop command acts on the hardware interface to which the external device is attached. Returns if error Mode...

  • Page 115: Talk

    Talk Syntax INT WINAPI Talk(DevHandleT devHandle, BYTE pri, BYTE sec); refers to either an interface or an external device. If refers to an devHandle devHandle external device, the Talk command acts on the associated interface. specify the primary and secondary addresses of the device which is to be addressed to Talk.

  • Page 116: Term

    Term Syntax INT WINAPI Term(DevHandleT devHandle, TermT *terminator, DWORD TermType); devHandle refers to either an interface or an external device. terminator is a pointer to the terminator structure. TermType can be either TERMIN TERMOUT , or TERMIN+TERMOUT , specifying whether input, output, or both are being set.

  • Page 117: Termquery

    TermQuery Syntax INT TermQuery(DevHandleT devHandle, TermT *terminator, INT TermType); devHandle refers to either an interface or an external device. terminator is a pointer to the terminator structure. TermType can be either TERMIN TERMOUT , or TERMIN+TERMOUT , specifying whether input, output, or both are being set. Returns if error Mode...

  • Page 118: Timeout

    TimeOut Syntax INT WINAPI TimeOut(DevHandleT devHandle, DWORD millisec); refers to either an IEEE 488 interface or an external device. devHandle is a numeric value given in milliseconds. millisec Returns if error Mode Bus States None Example errorcode = TimeOut(ieee,100); Sets the timeout value to 100 msec. See Also TimeOutQuery, Reset command sets the number of milliseconds that Driver488 waits for a transfer before...

  • Page 119: Timeoutquery

    TimeOutQuery Syntax INT WINAPI TimeOutQuery(DevHandleT devHandle,DWORD millisec); refers to either an IEEE 488 interface or an external device. devHandle is a numeric value given in milliseconds. millisec Returns if error Mode Bus States None Example None provided. See Also TimeOut, Reset This is a new function in Driver488/W95.

  • Page 120: Trigger

    Trigger Syntax INT WINAPI Trigger(DevHandleT devHandle); refers to either an IEEE 488 interface or an external device. devHandle Returns if error Mode Bus States ATN• • GET With interface handle: ATN• • UNL, MTA, LAG, GET With external device handle: Examples Issues a Group Execute Trigger ( ) bus command to those...

  • Page 121: Triggerlist

    TriggerList Syntax INT WINAPI TriggerList(DevHandlePT dhList); is a pointer to a list of external devices. dhList Returns if error Mode Bus States ATN• • UNL, MTA, LAG, GET Example deviceList[0] = wave; Issues a Group Execute Trigger ) bus command to a deviceList[1] = timer;...

  • Page 122: Unlisten

    UnListen Syntax INT WINAPI UnListen (DevHandleT devHandle); refers to either an interface or an external device. If refers to an devHandle devHandle external device, the UnListen command acts on the associated interface. Returns if error Mode Bus States ATN, UNL Example errorcode = UnListen (ieee);...

  • Page 123: Untalk

    UnTalk Syntax INT WINAPI UnTalk (DevHandleT devHandle); refers to either an interface or an external device. If refers to an devHandle devHandle external device, the UnTalk command acts on the associated interface. Returns if error Mode Bus States ATN, UNT Example errorcode = UnTalk (ieee);...

  • Page 124: Wait

    Wait Driver488/W95 only Syntax INT WINAPI Wait(DevHandleT devHandle); devHandle refers to either an interface or an external device. If devHandle is an external device, the Wait command acts on the hardware interface to which the external device is attached. Returns if error Mode Bus States...

  • Page 125: Troubleshooting Radio Interference Problems

    Troubleshooting Radio Interference Problems……119 IEEE 488 Bus Errors……119 Hardware-Software Conflicts……120 Checking Hardware & Software Settings……120 Radio Interference Problems Personal488 hardware systems generate, use and can radiate radio frequency energy, and if not installed and not used correctly, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation.

  • Page 126: Hardware-Software Conflicts

    Hardware-Software Conflicts Note: If your Personal488 package includes a plug-and-play interface – such as the Personal488/PCI (with PCI488), Personal488/ATpnp (with AT488pnp), or Personal488/CARD (with CARD488) packages – disregard the list below. • I/O Base Address: Check to make sure that the I/O base address selected through the configuration utility of Driver488, matches the interrupt setting configured through the appropriate DIP switch on your IEEE 488 interface.

  • Page 127: Ascii Codes

    Appendix IEEE 488 Bus & Serial Bus……121 IEEE 488 Bus Commands……122 ASCII Codes……123 ASCII Code Summary……123 ASCII Code Details……125 IEEE 488 Bus & Serial Bus Lines Bus State Bus Line Data Transfer (DIO) Lines Bus Management Lines Interface Clear Remote Enable IEEE 488 Interface: Bus Management Lines Attention ($04) End-Or-Identify ($80)

  • Page 128: Ieee 488 Bus Commands

    IEEE 488 Bus Commands Bus State IEEE 488 Bus Command Data Transfer (DIO) Lines (ATN is asserted “1”) Device Clear Group Execute Trigger ($08) Go To Local ($01) Listen Address Group ($20-3F) Local Lock Out ($11) My Listen Address My Talk Address Parallel Poll Config Parallel Poll Disable ($07) Parallel Poll Unconfig ($15)

  • Page 129: Ascii Codes

    ASCII Codes ASCII Code Summary Decimal Values 00 to 63 – ACG, UCG & LAG Box Items Hexadecimal Value Decimal Value Bus Message (in center) ASCII Character Addressed Command Group ( 00 $01 01 $02 02 $03 03 $04 04 $05 05 $06 06 $07 08 $09...
  • Page 130 Decimal Values 64 to 127 – TAG & SCG Box Items Hexadecimal Value Decimal Value Bus Message (in center) ASCII Character Talk Address Group ( 64 $41 65 $42 66 $43 67 $44 68 $45 69 $46 70 $47 72 $49 73 $4A 74 $4B 75 $4C...

  • Page 131: Ascii Code Details

    ASCII Code Details Decimal Values 00 to 31 – ACG & UCG Characteristics ASCII Control Codes (Decimal 00 to 31) Character & Name Bus Message Value Value ($) Abbreviation Addressed Command Group ( None / NUL Null None ^A / SOH Start of Header Go To Local ( Start of Text...
  • Page 132 Decimal Values 00 to 31 – ACG & UCG Descriptions ASCII Control Codes (00 to 31) Name Description Addressed Command Group ( Null ( Space filler character. Used in output timing for some device drivers. Start of Header ( Marks beginning of message header. Start of Text ( Marks beginning of data block (text).
  • Page 133 Decimal Values 32 to 63 – LAG ASCII Character Set (Decimal 32 to 63) Character Name Bus Message Listen Address Group (LAG) Space Bus address 00 <space> Exclamation Point Bus address 01 “ Quotation Mark Bus address 02 Number Sign Bus address 03 Dollar Sign Bus address 04...
  • Page 134 Decimal Values 64 to 95 – TAG ASCII Character Set (Decimal 64 to 95) Character Name Bus Message Talk Address Group (TAG) At Sign Bus address 00 Capital A Bus address 01 Capital B Bus address 02 Capital C Bus address 03 Capital D Bus address 04 Capital E...
  • Page 135 Decimal Values 96 to 127 – SCG ASCII Character Set (96 to 127) Character Name Bus Message Secondary Command Group (SCG) Grave Command 00 ’ Lowercase A Command 01 Lowercase B Command 02 Lowercase C Command 03 Lowercase D Command 04 Lowercase E Command 05 Lowercase F...
  • Page 136 Notes Appendix Personal488 User's Manual For Windows95 and Windows NT...

  • Page 137: Index

    Index Controller Active, 48, 89, 98, 104, Group Execute Trigger (GET), 114, 105, 106 controller device, 2 Abort, 48, 89, 99 ControlLine, 57 accessories hardware, 2 hardware Active Controller, 48, 89, 98, 104, connection, 2 105, 106 data transfer, 27, 48, 87, 102, 103, products, 1 address 106, 110...
  • Page 138 OnDigEventVDM, 82 Remote Enable (REN), 44, 50, 74, System Controller, 44, 48, 74, 75, 87, OnEvent, 83 87, 95, 96 89, 99, 106 OnEventVDM, 84 RemoteList, 96 OpenName, 86 RemoveDevice, 72, 97 operating mode, 74, 89, 98, 104, 105, Request, 98, 105 Talk, 64, 80, 87, 100, 106, 109 Request for Service (rsv), 98, 104, Output, 51, 88, 114, 115...
  • Page 139 Notes Personal488 User's Manual For Windows 95 and Windows NT Index...

  • Page 140: Abbreviations

    Abbreviations Ÿ Ÿ *SCŸ Ÿ CA (bullet symbol) “and” (e.g. Federal Communications Commission (asterisk symbol) “unasserted” (e.g. Form Feed (ASCII Code) Not Controller Active mode File Separator (ASCII Code) Not System Controller mode Group Execute Trigger bus command GPIB Analog-to-Digital General Purpose Interface Bus Addressed Command Group Group Separator (ASCII Code)
  • Page 141 SCPI Standard Cmds. for Programmable Instruments Substitute (ASCII Code) SCSI Small Computer System Interface bus Synchronous Idle (ASCII Code) Selected Device Clear bus command Thermocouple Shift In (ASCII Code) Talk Address Group bus command Shift Out (ASCII Code) Take Control bus command Start of Header (ASCII Code) Transistor-Transistor Logic Serial Poll Disable bus command...
  • Page 142 Notes Abbreviations Personal488 User's Manual For Windows95 and Windows NT...
  • Page 143 OMEGA's Customer Service Department will issue an Authorized Return (AR) number immediately upon phone or written request. Upon examination by OMEGA, if the unit is found to be defective it will be repaired or replaced at no charge. OMEGA's WARRANTY does not apply to defects resulting from any action of the purchaser,...
  • Page 144 TEMPERATURE þ Thermocouple, RTD & Thermistor Probes, Connectors, Panels & Assemblies þ Wire: Thermocouple, RTD & Thermistor þ Calibrators & Ice Point References þ Recorders, Controllers & Process Monitors þ Infrared Pyrometers PRESSURE, STRAIN AND FORCE þ Transducers & Strain Gauges þ...

This manual is also suitable for:

Omb-per-488/wnt

Table of Contents