VSpy 3 Documentation
All DocsProductsLearning CenterSupport
Main
Main
  • 🚗Welcome to the Vehicle Spy Help Documentation
  • Vehicle Spy Introduction
    • Vehicle Spy Overview
      • Vehicle Spy Tour
        • Vehicle Spy Tour 1: Bus Monitor
        • Vehicle Spy Tour 2: Signal Monitoring and Recording
        • Vehicle Spy Tour 3: Flight Recording
        • Vehicle Spy Tour 4: Node/Vehicle Simulation
        • Vehicle Spy Tour 5: Test Automation
        • Vehicle Spy Tour: Summary
    • Other Vehicle Spy Users
    • Vehicle Spy Specifications
    • Vehicle Spy Required Hardware PC System Requirements
    • Vehicle Spy Website
  • Vehicle Spy Tutorials
    • Vehicle Spy Tutorial Files
    • Getting Comfortable with the User Interface
    • Tabs in the User Interface
    • Tutorial 1: Basics of Vehicle Spy
      • Part 1 - Logon Screen
      • Part 2 - Monitor Message Traffic
      • Part 3 - Examine Messages
      • Part 4 - Your Message Specification in Action
      • Part 5 - Filtering Messages
      • Part 6 - More Ways to Filter in Vehicle Spy
      • Part 7 - Message Timestamps and Pausing
      • Part 8 - Save Your Messages View Buffer
      • Part 9 - Clear the Messages View Buffer
      • Part 10 - Exercises
    • Tutorial: Transmit Messages with Vehicle Spy
      • Part 1 - Load the Setup File
      • Part 2 - Enter a Transmit Message
      • Part 3 - Utilize the Alternate Workspace Panels
      • Part 4 - Manually Transmit a Message
      • Part 5 - Periodically Transmit a Message
      • Part 6 - Automatically Respond to a Message
      • Part 7 - Exercises
    • Tutorial: Decode Signals from Messages
      • Part 1 - Load a Setup File
      • Part 2 - Enter a Message
      • Part 3 - Enter an Equation for an Analog Value
      • Part 4 - View Message Data
      • Part 5 - View Message Data with the Signal List and Signal Plot
      • Part 6 - An Introduction to Signal Plot Features
      • Part 7 - Exercises
    • Tutorial: Database Setup
      • Part 1 - Platform Overview
      • Part 2 - Create a Platform
      • Part 3 - Adding Database Files
      • Part 4 - ECU Setup Wizard
      • Part 5 - Diagnostic Decoding
      • Part 6 - Conclusion
    • Tutorial: Basics of Capture Function Block and Graphical Panels
      • Part 1 - Setup the Simulation
      • Part 2 - Setup the Capture Function Blocks
      • Part 3 - Setup the Graphical Panel
      • Part 4 - Conclusion
    • Tutorial: Basics of Scripting and Playback
      • Part 1 - Setup Application Signals
      • Part 2 - Setup the Graphical Panel
      • Part 3 - Setup The Playback Function Block
      • Part 4 - Setup the Script Function Block
      • Part 5 - Summary
    • Tutorial: Request and Save DTC Data
      • Part 1 - Create a Diagnostic Job
      • Part 2 - Create Function Block to Request and Save Data
      • Part 3 - Make a Graphical Panel
      • Part 4 - Request, Save, and View the DTCs
      • Part 5 - Conclusion
    • Tutorial: DPS Programming Automation
      • Part 1 - Create DPS Programming Job
      • Part 2 - Create Function Block to Launch Programming Services
      • Part 3 - Make a Graphical Panel
      • Part 4 - Use the DPS Programming Graphical Panel
      • Part 5 - DPS Programming Automation Conclusion
    • Tutorial: Getting Fancy with Diagnostics
      • Part 1 - Read Data By Identifier Setup
      • Part 2 - Write Data by Identifier Setup
      • Part 3 - Writing the Read DID
      • Part 4 - Request Identifiers using Dynamically Define Data Identifier
      • Part 5 - Request the Dynamic Identifier
      • Part 6 - Conclusion
    • Tutorial: Sort Messages by ECU
      • Part 1 - Start a New Vehicle Spy Application
      • Part 2 - Enter ECU Source IDs to Sort
      • Part 3 - Setup Capture Type Function Blocks
      • Part 4 - Sort the ECU Messages
      • Part 5 - Setup Application Signals
      • Part 6 - Setup Playback Type Function Blocks
      • Part 7 - Setup Script Type Function Blocks
      • Part 8 - Construct a User Dialog
      • Part 9 - Run the Setup
    • Tutorial: Configuring and Using CoreMini
      • Part 1 - Creating a Tx Message
      • Part 2 - Logging Data
      • Part 3 - Loading the Script to the Hardware
      • Part 4 - How to Run the Script
      • Part 5 - Extracting Data
      • Part 6 - Viewing the Data
      • Part 7 - Conclusion
    • Tutorial: Simple Standalone Logging
      • Part 1 - Getting Started
      • Part 2 - Database/Hardware Setup
      • Part 3 - Channels
      • Part 4 - Checking Channel Selection
      • Part 5 - Standalone Logging
      • Part 6 - CoreMini Console
      • Part 7 - Extract Data
      • Part 8 - Conclusion
    • Tutorial: Standalone Video Logging
      • Tutorial: Standalone Video Logging - Part 1 - Setting up the Axis Camera
      • Tutorial: Standalone Video Logging - Part 2 - Setting Up Vehiclescape DAQ
      • Tutorial: Standalone Video Logging - Part 3 - Extracting the Video
    • Tutorial: C Code Interface
      • Part 1 - Create a Project
      • Part 2 - Adding Events
      • Part 3 - Running the Example
      • Part 4 - Debugging
      • Part 5 - Conclusion
    • Tutorial: How to run multiple devices in one VS3 file
      • Part 1 - Enabling Multiple Devices
      • Part 2 - Adding Devices
      • Part 3 - Assigning Devices
      • Part 4 - Syncing Time Across Multiple Devices
  • Tutorial Summary
  • Basic Operation of Vehicle Spy
    • The Logon Screen
    • Menus & Buttons
    • Running and Stopping
    • Data Directory
    • Create, Open, & Save Vehicle Spy Setups
    • Alternate Workspaces
    • Using Window Docking
  • Vehicle Spy Main Menus
    • Main Menu: File
      • The Logon Screen
      • Create, Open, & Save Vehicle Spy Setups
      • Import Function Blocks and Graphical Panels
      • Data Directory
      • Review Buffer
    • Main Menu: Setup
      • Setup a Network
      • Setup Platforms
      • Network Databases
      • ECUs View
        • ECU A2L Import Options
        • Edit ECU Diagnostic Database
        • ECU Diagnostic Services Tab
      • Data Cache Disk Streaming
    • Main Menu: Spy Networks
      • Snapshot
      • Messages View
        • Messages View Filter Bar
          • Messages View Custom Filters
        • Messages View Top Toolbar
          • Message Details Pane
          • Reverse Engineering
          • Messages View Timestamping
          • Pause Messages View
          • Save the Buffer
          • Clear the Buffer
        • Messages View Column Headers
        • Messages View Column Filters
        • Messages View Buffer Display
          • Displaying Signals in Messages View
          • Buffer Progress Display
          • Messages View Task Menus
        • Messages View Bottom Toolbar
          • Color Filters
          • Messages View Data Byte Format
          • Messages View Setup
      • Message Editor
        • Messages Editor: Overview
        • Messages Editor: Receive, Transmit, & Database Tables
        • Add and Delete Messages
        • Messages Editor: Cut, Copy, and Paste
        • Messages Editor: Sort and Arrange
        • Messages Editor: Pick a Network
        • Messages Editor: Right Click Menu
        • Message PT, Trgt, and Src
        • Messages Editor: Message Fields
          • Message Key
          • Message Description
          • Message Type
          • Message Arbitration ID
          • Multiframe Message
            • Receive ISO15765-2 Multiframe Message
            • Transmit ISO15765-2 Multiframe Message
          • Message Length
          • Message Data Bytes
            • Transmit Long Messages
          • Message Source Node
          • Receive Message "Tx Msg" Field
          • Message Color
        • Message Signals
          • Live Edit
          • Message Signal Type
          • Message Signal Type Analog
          • Message Signal Type Digital
          • Message Signal Type State Encoded
          • Message Signal Type Text
          • Message Signal Type DTC
          • Understanding Bit and Byte : Bit Positions
          • Message Signal Format and Units
      • Transmit Panel
        • Ways to Transmit Messages
          • Auto Tx and Transmit Rate
        • Add and Delete Transmit Messages
        • Transmit Panel Filter Bar
        • Dynamic Transmit Message Bytes
      • Networks
        • Setup a Network
        • Network Statistics
        • Moving Messages Between Networks
      • TCP/IP
      • FlexRay Controllers
        • FlexRay Controllers: State/Action Tab
        • FlexRay Controllers: Configuration Tab
        • FlexRay Controllers: Registers Tab
      • FlexRay Cycles
      • Diagnostics
        • Diagnostics View
        • Diagnostics Setup
      • Diagnostics over IP (DoIP)
      • Simulator
      • ECUs View
        • GMLAN ECUs
        • ISO 14229 ECUs
        • Keyword 2000 ECUs
    • Main Menu: Measurement
      • VehicleScape DAQ
        • VehicleScape DAQ: Database/Hardware Setup Tab
        • VehicleScape DAQ: Channels Tab
        • VehicleScape DAQ: PC Logging Tab
        • VehicleScape DAQ: Standalone Logging Tab
          • Standalone Logging: Collections and Methods
            • Collections and Methods: Message Capture Method
              • Message Capture Method: Message Collection Options
              • Message Capture Method: Start Options
            • Message Capture Method: Stop Options
              • Message Capture Method: Stop Options: Finish After Collecting Messages or When Expression is True
              • Message Capture Method: Stop Options: Pre/Post Collection
              • Message Capture Method: Stop Options: One Shot Report
            • Message Capture Method: Restart Options
            • Message Capture Method: Upload to Wireless neoVI
            • Collections and Methods: Bus Query Method
            • Collections and Methods: Histogram Method
            • Collections and Methods: Ethernet DAQ Method
          • Standalone Logging: Status Reporting
          • Standalone Logging: Power Management
          • Standalone Logging: Generation Options
        • VehicleScape DAQ: Gateway
        • VehicleScape DAQ: Online Tab
      • Signal Views
        • Signal Plot
        • Signal List
      • Graphical Panels
        • Graphical Panels: Tools
          • Graphical Panel Controls: Common Control Properties
          • Graphical Panel Controls: LED
          • Graphical Panel Controls: Text Display
          • Graphical Panel Controls: Meter
          • Graphical Panel Controls: Function Block Button
          • Graphical Panel Controls: Tx Button
          • Graphical Panel Controls: On/Off Button
          • Graphical Panel Controls: Action Button
          • Graphical Panel Controls: Diag Job Action Button
          • Graphical Panel Controls: Bargraph
          • Graphical Panel Controls: Knob
          • Graphical Panel Controls: Grid
          • Graphical Panel Controls: Numeric Entry
          • Graphical Panel Controls: Graph
          • Graphical Panel Controls: Text Entry
          • Graphical Panel Controls: Graphical Display
          • Graphical Panel Controls: Drop Down List
          • Graphical Panel Controls: Message History
          • Graphical Panel Controls: Flash Control
          • Graphical Panel Controls: Radio Button
          • Graphical Panel Controls: Bitmap Button
          • Graphical Panel Controls: Panel Button
          • Graphical Panel Controls: Hex Edit
        • Graphical Panels: Add or Delete a Tool
        • Graphical Panels: Tool Properties
        • Graphical Panels: Move a Tool
        • Graphical Panels: Resize a Tool
        • Graphical Panels: Format (Align or Resize) a Tool Group
        • Graphical Panels: Add or Delete Panels
        • Graphical Panels: Select and Work With Panels
        • Graphical Panels: Panel Properties
        • Graphical Panels: Lock Panels
        • Floating Panels
      • Logging
      • MEP (XCP/CCP) - Memory Edit Protocol
        • MEP Setup
          • MEP Setup - Properties
          • MEP Setup - Import / Export
          • MEP Setup - DAQ Tables
          • MEP Setup - Security
          • MEP Setup - Memory / Hex / S19
        • MEP Value Editor
        • MEP Curve Editor
        • MEP Map Editor
        • Data Acquisition with CCP/XCP
      • Instruments
      • Data Analysis
        • Data Analysis: Main Menus and Toolbar
        • Data Analysis: Zoom Toolbar
        • Data Analysis: X-Axis Input Toolbar and Dialog
        • Data Analysis: Plotter Setup Toolbar
      • Data Analysis: Tool Dialog
        • Data Analysis: Calculated Channels
      • Data Analysis: Plotter Area
        • Data Analysis: Plotter Options
        • Data Analysis: Advanced Plotting Methods
      • Data Analysis: Channel Value Pane
      • Data Analysis: Output Bar
      • GPS Maps
      • Video
    • Main Menu: Embedded Tools
      • ECU Flashing Documentation
        • 1. Introduction
        • 2. CAL Files and DIDs (Parameters)
        • 3. ISO 14229 Security (example)
        • 4. Requirements
        • 5. ECU Flash Designer View
        • 6. ECU Flash Manager View
        • 7. Remote Vehicle ECU Flashing
        • 8. Additional Features: ECU Flashing - EXE
      • DPS Archive Viewer
      • CAN Terminal
      • Intrepid ECU Flasher: Definitions
      • J1939 Address Manager
      • J1939 DTC Monitor
      • BitSmash
      • CAN and CAN FD Fuzzing
    • Main Menu: GMLAN
      • Virtual Networks
      • GM CGI Bus
    • Main Menu: Scripting and Automation
      • Function Blocks
        • Function Blocks Toolbar
        • Function Block List
        • Function Block Start Tab
        • Function Blocks Types
          • Script Type Function Block
          • Script Type Function Block: Script Toolbar
          • Script Type Function Block: Commands
            • Script Type Function Block Command: Clear History
            • Script Type Function Block Command: Clear Stats
            • Script Type Function Block Command: Comment
            • Script Type Function Block Command: CoreMini Action
            • Script Type Function Block Command: DAQ Action
            • Script Type Function Block Command: Diag Job Action
            • Script Type Function Block Command: Function Block Action
            • Script Type Function Block Commands: If, Else, Else If, End If
            • Script Type Function Block Command: Jump If
            • Script Type Function Block Command: Jump To
            • Script Type Function Block Command: Load Message Data
            • Script Type Function Block Command: Log Data
            • Script Type Function Block Commands: Start Loop and End Loop
            • Script Type Function Block Command: Pause
            • Script Type Function Block Command: Read Data
            • Script Type Function Block Command: Set Value
            • Script Type Function Block Command: Set Value If
            • Script Type Function Block Command: Show Panel
            • Script Type Function Block Command: Sleep
            • Script Type Function Block Command: Stop
            • Script Type Function Block Command: Test DTC
            • Script Type Function Block Command: Text API
            • Script Type Function Block Command: Transmit
            • Script Type Function Block Command: Wait For
            • Script Type Function Block Command: Wait Until
          • Script Type Function Block: Resetting the Present Flag
          • Script Type Function Block: Debugging Tools
          • Capture Type Function Block
            • Capture Type Function Block: Filter Tab
            • Capture Type Function Block: Stop and Trigger Tab
            • Capture Type Function Block: Storage Tab
            • Capture Type Function Block: Data Tab
          • Playback Type Function Block
          • Function Blocks Hotkeys
      • C Code Interface
        • Working with the C Code Interface
        • C Code Interface: Functions and Events
          • Functions and Events: Message Objects
          • Functions and Events: Application Signals
          • Functions and Events: Timers
          • Functions and Events: Common Functions and Events
          • Functions and Events: Graphical Panels
          • Functions and Events: Diagnostic Jobs
          • Functions and Events: Function Blocks
          • Functions and Events: Text API
          • Functions and Events: Network Indexes and Statistics
        • C Code Interface: Object Names, Debugging, and Common Mistakes
        • C Code Interface: Advanced Topics
        • C Code Interface: CAPL Conversion
      • Application Signals
        • Application Signals: Save and Restore
      • Text API Terminal
    • Main Menu: Run
    • Main Menu: Tools
      • Utilities: CoreMini Console
        • Utilities: CoreMini Control
        • Utilities: CoreMini Partitions
        • Utilities: CoreMini Advanced Settings
      • Utilities: Extract / Export
        • Utilities: Extract from SD Card
        • Utilities: Export VSB to Other Formats
        • Utilities: Export VSB Convert VSB (with VSDB) to Other Formats V using Command Prompt in Windows
        • Utilities: Export VSB to CSV format using DataExtract.exe
      • Tools: Problem Log
      • Utilities: File Conversions
        • VSB Editor
      • Tools: Utilities
        • Utilities: VS3EXE Generator
        • Utilities: Hardware Acceleration
        • Tools: Performance
        • Tools: Language
      • PLASMA / ION Setup
      • Tools: Options
        • Options: Spy Networks Tab
          • Spy Networks Tab: J1850 VPW Mode
        • Options: Performance Settings
        • Options: Multimedia
          • Multimedia: Joystick Setup
        • Options: Text API Options
        • Options: License System
          • License Upgrade Eligibility
        • Options: GPS Setup
        • Options: Data Directories
        • Options: Regional Settings
    • Main Menu: Help
      • Contact Information - Intrepid Control Systems, Inc.
      • Vehicle Spy Website
  • Shared Features in Vehicle Spy
    • Shared Features: Calculated Signal Editor
      • Shared Features: Calculated Analog or Digital Signals
      • Shared Features: Calculated Text Signals
    • Shared Features: DTC Database
    • Shared Features: Expression Builder
    • Shared Features: Predefined Function Keys
    • Shared Features: Starting with a Selected View
    • Shared Features: Widgets
  • Vehicle Network Interface Hardware
    • Vehicle Network Interface Hardware: neoVI FIRE
      • General Purpose IO
    • Vehicle Network Interface Hardware: neoVI RED
    • Vehicle Network Interface Hardware: neoVI Blue
      • General Purpose IO
    • Vehicle Network Interface Hardware: ValueCAN
      • Vehicle Network Interface Hardware: ValueCAN 4-2
      • Vehicle Network Interface Hardware: ValueCAN 4-4
      • Vehicle Network Interface Hardware: ValueCAN 4-2EL
      • Vehicle Network Interface Hardware: ValueCAN 4 Industrial
    • Vehicle Network Interface Hardware: RAD-wBMS
    • Vehicle Network Interface Hardware: RAD-A2B
    • Vehicle Network Interface Hardware: RAD-Gigastar
    • Vehicle Network Interface Hardware: RAD-Galaxy
    • Vehicle Network Interface Hardware: ValueLOG
    • Getting Started with neoECU
      • neoECU Requirements
      • neoECU 10
        • neoECU 10: IO Map
        • neoECU 10: Loading Scripts Over CAN
        • neoECU 10: Power Up and Buttons
        • neoECU 10: Examples
      • neoECU 12
      • neoECU 20
        • neoECU 20: Configuration
        • neoECU 20: IO Map
        • neoECU 20: Loading Scripts Over USB
        • neoECU 20: Examples
      • neoECU 22
      • neoECU Firmware Updates
      • neoECU Sleep Mode
    • Vehicle Spy Text API
      • Vehicle Spy Text API: ECU Object
      • Vehicle Spy Text API: Labview Interface
    • Vehicle Spy VSB file Spec
  • Application Notes
    • Application Note: CoreMini Partition Logging
      • Logging - Part 1: General Setup
      • Logging - Part 2: Function Block Setup
      • Logging - Part 3: Sending the Script to the Hardware
      • Logging - Part 4: Conclusion
    • Application Note: VehicleScape Standalone Logging
      • Application Note: VehicleScape Standalone Logging - Part 1: Message Collection Options
      • Application Note: VehicleScape Standalone Logging - Part 2: Collection and Restart Options
      • Application Note: VehicleScape Standalone Logging - Part 3: Reporting Options, Power Management and
      • Application Note: VehicleScape Standalone Logging - Part 4: neoVI MOTE Setup
    • Application Note: XCP Driver Example
      • Application Note: XCP Driver Example - Part 1: Process Overview
      • Application Note: XCP Driver Example - Part 2: Example XCP Driver
      • Application Note: XCP Driver Example - Part 3: ECU Simulation and Porting XCP Driver
    • Application Note: neoVI Logging neoECU DAQ
      • Application Note: neoVI Logging neoECU DAQ - Part 1: neoECU Setup
      • Application Note: neoVI Logging neoECU DAQ - Part 2: VehicleScape DAQ
      • Application Note: neoVI Logging neoECU DAQ - Part 3: Review Data
    • Application Note: Using the neoVI MOTE
      • Application Note: Using the neoVI MOTE - Part 1: Messages
      • Application Note: Using the neoVI MOTE - Part 2: Display on Screen
      • Application Note: Using the neoVI MOTE - Part 3: Using the Speaker
      • Application Note: Using the neoVI MOTE - Part 4: Home Screen and Conclusion
    • Application Note: Gateway Builder Tutorial
      • Tutorial - Gateway Builder - Part 1 - Intro
      • Tutorial - Gateway Builder - Part 2 - Gateway Builder Overview
      • Tutorial - Gateway Builder - Part 3 - Add Messages to Gateway Builder
      • Tutorial - Gateway Builder - Part 4 - Gateway Input Actions
      • Tutorial - Gateway Builder - Part 5 - Output Messages, Signals, and Triggers
    • Application Note: Dynamically Manipulating Application Signal Arrays
      • Application Note: Dynamically Manipulating Application Signal Arrays
      • Application Note: Dynamically Manipulating Application Signal Arrays
      • Application Note: Dynamically Manipulating Application Signal Arrays
      • Application Note: Dynamically Manipulating Application Signal Arrays
    • PHY Dashboard
    • Sample Replay Files
  • Contact Us
    • Contact Information - Intrepid Control Systems, Inc.
Powered by GitBook
LogoLogo

Applications

  • Cybersecurity
  • Data Logging
  • Simulate ECU Functions
  • Diagnostics, Testing and Validation

Products

  • Vehicle Network Adapters
  • Data Loggers
  • Software
  • Automotive Ethernet Tools

Support

  • Support Resources
  • Contact Support
  • Class Schedule & Registration
  • Training Video Library

Company

  • About
  • News
  • Events
  • Contact Us

Copyright © 2025 | All Rights Reserved

On this page
Edit on GitHub
  1. Vehicle Spy Main Menus
  2. Main Menu: Measurement

Instruments

Instrument Control in Vehicle Spy - v6.0

Overview

Instrument control in Vehicle Spy is a feature where rack-and-stack type instruments can be controlled through function blocks.

Design

Basic design is derived from Robo Technician Software which was developed by Intrepid Control Systems in VB. Below are the features or views implemented in Vehicle Spy.

Instruments View: (Vehicle Spy -> Measurements -> Instruments) -> 804.xx

This is a Table view that enables the user to add their own instrument in the Instrument Editor (Similar to adding messages into Messages Editor).

Currently, 804 supports Ethernet and RS232 Interface to communicate with Instrument. Here is the PC Setup to get either of them working.

Setup to use Instrument via Ethernet Cable:

  1. Connect the Instrument to the PC (where VSPY is installed) via RJ45 Ethernet cable.

  2. Switch on the Instrument, Find the IP and Port details of that Instrument from the Instrument Panel and the procedure to find it from the panel is manufacturer specific.

  3. Once you have the details, Launch Vehicle Spy, Go to Tools -> Options -> Enable “Use PC Ethernet Interface” -> OK -> Restart VSPY.

  4. Goto VSPY -> Measurements -> Instruments -> Click on “+” to add a new Instrument as shown in the Figure 1.Choose Ethernet as Interface.

  5. Goto Logon screen -> Choose the right network interface where the Instrument is connected and go online using any ICS hardware (like VCAN3,FIRE,FIRE2,RADGALAXY,VCAN4’s,etc.,). Please note that hardware is being used here only for licensing purpose but not for any Instrument communication at this point.

  6. Once online, goto Spy Networks -> TCP/IP. Make sure the connection is established with the Instrument IP Address. You will also see the error in VSPY after few minutes of connection establishment failure.

  7. If connection state is established, goto Instruments View and click on Test Connection button as shown in the Figure 1.

  8. If the setup is fine, Instrument name should be seen from the Instrument as a response. Else, there will be a error dialog displaying the connection failure as shown in the Figure 2.

Figure 1: Instruments Editor in Vehicle Spy (VSPY -> Measurement -> Instruments)

  • Key - Automatic entry on adding new row

  • Instrument Name - Instrument Name or Manufacturer name

  • Interface - RS232/Ethernet

  • IP Address - IP Address for Ethernet interface, GPIB address for GPIB

  • Port - Port number for RS232 or TCP

  • Test Connection - Button to implicit connectivity test and if it is successful, Instrument name will be displayed to the user. Otherwise, Connection error will be displayed

Messages View: (Vehicle Spy -> Spy Networks -> Messages) -> 804.xx

For Ethernet based Instruments, we can view the Commands/Responses in Messages View as shown in the below Figure 3.

Setup to use Instrument via Serial Cable: (USB to RS232 converter)

  1. Connect the Instrument to the PC (where VSPY is installed) where the USB side is attached to PC USB port and RS232 side is connected to the Instrument.

  2. Switch on the Instrument, Check in Device Manager to see the COM Port corresponding to the Instrument. For example COM44 (44 is the port number to be used in Vehicle Spy)

  3. Once you have the port details, Launch Vehicle Spy, Goto VSPY -> Measurements -> Instruments -> Click on “+” to add a new Instrument as shown in the Figure 4. Choose RS232 as Interface.

  4. Go online using any ICS hardware (like VCAN3,FIRE,FIRE2,RADGALAXY,VCAN4’s,etc.,). Please note that hardware is being used here only for licensing purpose but not for any Instrument communication at this point.

  5. Once online, click on Test Connection button as shown in the Figure 4.

  6. If the setup is fine, Instrument name should be seen from the Instrument as a response. Else, there will be a error dialog displaying the connection failure as shown in the Figure 5.

Function Blocks View: (Vehicle Spy -> Scripting and Automation -> Function Blocks) -> 804.xx

New Step Command called “Instrument Action” will be created in order to send commands to the instrument.

  1. Option available to manually enter the commands for simple tests. Refer Figure 6 below.

  2. Option to use to choose the commands from Instrument DB for complex tests . Refer the “Instrument Database” section of this document.

Setup Instrument Action FB Command:

Instrument Name

This will be listed from the Instrument Editor and available for users to just select their Instrument in this view.

Enter Command/Filename

❖ Single Command: - Manually Type the exact command in the text box / Choose commands from Instrument DB.

❖ Multiple Commands - User can import a text file which has list of SCPI Commands in it

Assign Result to Application Signal in case of Single command (Optional - Leave it blank if the command has no response)

❖ If the command is going to have a response from instrument, then User can choose to store the result in the Application signal which can then be displayed in Graphical Panels. This option is available only for Single Command case.

Add Step

❖ Clicking this button will add the command to the Function block with all the user provided details.

Note: User can use Instrument Database while choosing Single Command option. This will enable one to just choose the command from database instead of typing it in the FB Window. Please refer “Instrument Database” section of this document

Multiple Commands - Usage Instructions:

This option is especially useful if one has list of commands to be executed either as an init sequence or Waveform Configuration or Waveform Trigger operation. This helps the user to have these list of commands to be reused between multiple Vehicle Spy setups.

Instrument Database: -> 804.xx

  1. Add the command details in to the database by invoking the database from Measurement -> Instruments -> Instrument Database

Fields and its explanation: (with Example command)

Index – Read only auto generated index

Instrument type: For example, power supply

Instrument Name: For example, N7971A => Instrument name should match the one in Instruments editor

Command name: Identify instrument

Command String: *IDN?

Command response: Instrument name with model number

This DB will be created/Saved as XML file and by default it will be opened/stored from/to Default data directory. There is an option “Load default database” which will be provided by Intrepid for all the users which will have basic commands that is supposed to work with all kinds of SCPI instruments. User can use this as “model” to add more commands to his DB. There is an option to Import DB, Add Entries, Delete Entries and then Export DB.

Note: When you write FB Scripts for instrument control, FB Step command has an option to choose the instrument (instrument name), Once User chooses the instrument name, existing commands for that instrument will be fetched from the currently loaded DB which matches that instrument name.

Note: When you open VSPY for first time, no DB exists. However, you can load the default one by clicking “Load default database” before start writing the FB Scripts. You can edit or add to the default database and export it to a different name.

VS3 will remember the currently used DB when you open it next time.

VS3ZIP will include the DB file as part of the package and use it whenever opened next time.

FB window single command will list all the commands for the current instrument name from the loaded database.

“N7971A” is the instrument name in Instruments Editor as well as in the Instrument database.

Hence, in FB Script, when user chooses the Instrument as “N7971A” , Commands will be loaded from DB for that instrument. These are going to be command names. When user selects it, Command string corresponding to that Command name will be used in the FB Step command.

User can opt to see all the commands in the Database irrespective of the instrument name by Unchecking the check box “Show commands for the selected Instrument”

Instrument Settings:-> 804.xx

RS232 Instrument Settings:

  • Baud rate/Data Bits/Parity/Stop Bits/Flow Control : These are the instrument settings which can be changed in the Instrument Panel and VSPY. Flow control settings are not supported yet.

  • Command Termination: Most of the RS232 Instruments needs the commands to be terminated with . This can be set to a different value as per the Instrument requirement.

  • Response Termination: Not supported yet. If Instrument allows this to be controlled from the Instrument Panel, then it will be supported.

  • Default timeout: Timeout Value in ms to wait for Instrument response

Ethernet Instrument Settings:

  • Command Termination: Most of the Ethernet Instruments needs the commands to be terminated with or . This can be set to a different value as per the Instrument requirement.

  • Response Termination: Not supported yet. If Instrument allows this to be controlled from the Instrument Panel, then it will be supported.

  • Default timeout: Timeout Value in ms to wait for Instrument response

PreviousData Acquisition with CCP/XCPNextData Analysis

Last updated 2 months ago

Figure 1: Configuring Ethernet Instruments from Vehicle Spy - Connection success
Figure 2: Configuring Ethernet Instruments from Vehicle Spy - Connection Failure
Figure 3: Messages View displaying the commands sent to the Instrument
Figure 4: RS232 Instrument setup - Connection success
Figure 5: RS232 Instrument setup - Connection Failure
Figure 6: “Instrument Action” FB command in Vehicle Spy
Figure 7: Setup Function Block for Instrument Action
Figure 8: Multiple Commands Usage
Figure 9: Instrument Database
Figure 10: Choosing commands from Instrument Database
Figure 11: RS232 Instrument settings
Figure 12: Ethernet Instrument settings
Configuring Ethernet Instruments from Vehicle Spy - Connection success
Configuring Ethernet Instruments from Vehicle Spy - Connection Failure
Messages View displaying the commands sent to the Instrument
RS232 Instrument setup - Connection success
Figure 5: RS232 Instrument setup - Connection Failure
Instrument Action FB command in Vehicle Spy
Setup Function Block for Instrument Action
Multiple Commands Usage
Instrument Database
Choosing commands from Instrument Database
RS232 Instrument settings
Ethernet Instrument settings