API Interface

  • Downloads
  • SPECIFICATIONS
  • SUPPORT
  • REQUEST A QUOTE
  • The API Interface supports analyzer trace capturing with predefined setups
  • The API Interface supports protocol checker functionality and most Exerciser functionalities
  • The API Interface provides programming language and platform-independent interface to Vanguard Bus Analyzers
BusView Graphical User Software

BusView Graphical User Software

The Curtiss-Wright BusView Graphical User Interface Software for Vanguard Bus and Protocol Analyzers is easy to use and uses the same software for PCI/PCI-X, cPCI, PMC, and VME analysis. BusView...

Vanguard CompactPCI Bus Analyzer, Exerciser, Protocol Checker and Compliance Checker

Vanguard CompactPCI Bus Analyzer, Exerciser, Protocol Checker and Compliance Checker

The Vanguard CompactPCI Bus Analyzer offers the PCI / PCI-X analysis, exercising, protocol detection, and compliance checking in cPCI systems. With a 10/100 Mbit/s Ethernet interface, this...

Vanguard PCI Bus Analyzer, Exerciser, Protocol Checker, and Compliance Checker for 133MHz

Vanguard PCI Bus Analyzer, Exerciser, Protocol Checker, and Compliance Checker for 133MHz

The Vanguard PCI Bus Analyzer offers the complete solution for PCI/PCI-X debug, analysis, exercising, protocol detection, and compliance checking. With a 10/100 Mbit/s Ethernet interface, the...

Vanguard PCI-0-SL PCI/PCI-X Bus Analyzer, Exerciser, Protocol Checker, and Compliance Checker for 133MHz DUT

Vanguard PCI-0-SL PCI/PCI-X Bus Analyzer, Exerciser, Protocol Checker, and Compliance Checker for 133MHz DUT

The Vanguard PCI-0-SL PCI-X Bus Analyzer allows testing in single-slot systems at up to 133 MHz, whilw isolating the PCI/PCI-X bus and uses a bridge to locate the Device Under Test from the...

Vanguard PMC Bus Analyzer, Exerciser, Protocol Checker & Compliance Checker

Vanguard PMC Bus Analyzer, Exerciser, Protocol Checker & Compliance Checker

The Vanguard PMC Bus Analyzer offers the complete solution for PCI / PCI-X analysis, exercising, protocol detection, and compliance checking in a PMC environment. With a 10/100 Mbit/s Ethernet...

Vanguard VME Bus Analyzer, Exerciser, and Protocol Checker for VME, VME64, 2eVME, and 2eSST

Vanguard VME Bus Analyzer, Exerciser, and Protocol Checker for VME, VME64, 2eVME, and 2eSST

The Vanguard VME Bus Analyzer, a complete solution for VMEbus analysis, detects exercising and protocol errors and supports new VME standards, including 2eSST. USB, Application Programming...

CONTACT SALES/SUPPORT


For Vanguard Bus Analyzers

What sets apart the Curtiss-Wright API Interface for Vanguard Bus Analyzers?

The API Interface for Vanguard Bus Analyzers provides two alternative API client interfaces using a Remote Procedure Calling (RPC) paradigm

  • The API Interface supports analyzer trace capturing with predefined setups
  • The API Interface supports protocol checker functionality and most Exerciser functionalities
  • The API Interface provides programming language and platform-independent interface to Vanguard Bus Analyzers

The Vanguard API Interface accommodates users of Vanguard Analyzers to access Vanguard device functionality without using the BusView GUI. It also allows the Vanguard API to incorporate Vanguard functionality in dedicated applications running on a wide-range of platforms and use a variety of programming languages.

The Vanguard API engine is implemented as a TCP/IP based server on the Vanguard device, using simple ASCII-formatted data for both requests and responses. The API is therefore accessible to every client platform that has basic TCP/IP support. The API engine integrates with the main Vanguard device firmware as follows:

The API engine integrates with the device firmware as a communications handler, in addition to the BusView Ethernet and USB communication handlers.

As with other Vanguard firmware, the API engine acts as a BusView emulator. This means simultaneous API and BusView connections are not possible and initialization overhead is needed each time an API client connects to the Vanguard API engine. When using the API, you should maintain the same TCP/IP connection throughout the API session.

Curtiss-Wright API Interfaces for Clients

Two client interfaces are available for using the Vanguard API. The XML-RPC interface transmits the requests and responses as XML-formatted messages using HTTP. The raw ASCII interface transmits RPC requests and responses as simple ASCII-coded strings and uses basic TCP/IP socket client/server communication for the transport.

The Vanguard API server selects the interface mode based on the incoming command data.

Raw ASCII interface - To use the Raw ASCII interface, a standard TCP/IP socket connection to the Vanguard API server needs to be established. Due to a certain API initialization overhead when creating a server connection, the client should keep the same connection open throughout the entire API session.

The raw ASCII interface accepts requests as a set of ASCII strings, and returns data in a similar format. Each string should be terminated with a pair of carriage-return and line-feed ASCII characters (CR/LF pair).

XML-RPC Interface - XML-RPC is a Remote Procedure Calling (RPC) protocol which uses HTTP for the transport and XML for encoding. XML-RPC is designed to be simple, while allowing complex data structures to be transmitted, processed and returned. XML-RPC client libraries are freely available for a number of programming languages. (See www.xmlrpc.org for more XML-RPC specification.)

The Vanguard API XML-RPC server accepts API request parameters passed as a single XML-RPC array parameter or as individual XML-RPC parameters (strings, integers and booleans).

Product Finder

Connect With Curtiss-Wright Connect With Curtiss-Wright Connect With Curtiss-Wright
Sales

CONTACT SALES

Contact our sales team today to learn more about our products and services.

YOUR LOCATION

PRODUCT INFORMATION

Support

GET SUPPORT

Our support team can help answer your questions - contact us today.

REQUEST TYPE

SELECT BY

SELECT Topic