BHARAT TEST SUITE by Raju Bros Softech Pvt ltd

Learning Centre · Instrument communication

Connect and check
a SCPI instrument.

First confirm the connection, then verify a documented query and its actual reply. This guide covers a first communication check; measurement commands and limits must come from your instrument and product specifications.

Explore device connectivity
/01

Before you start

Reviewed 15 October 2026 · Raju Bros Softech Pvt ltd · Based on documented application behavior; validate your station.

  • Use ADMIN access with Device Configuration permissions to save settings. Manual checks require authorised Maintenance access; production must be stopped.
  • Have the exact instrument model, its programming manual, supported interface, required vendor driver and communication settings available.
  • Confirm that the instrument supports *IDN?. Use its documented identification query if it does not. Put the station in its approved safe state before manual communication.
Availability. Device categories and catalogue entries do not establish compatibility with every model. Confirm the required adapter, driver and licence package for your station.
/02

Configure the instrument

  1. Create or select the device

    Open Device Configuration. Choose NEW DEVICE or an existing row. Enter a unique Device Name, category and role, then select the correct Brand, Model, Communication Type and Protocol.

  2. Set the connection details

    For COM / Serial, use REFRESH COM PORTS and select the connected device. Review USB identity and match Baud Rate, Data Bits, Parity and Stop Bits to the instrument. For LAN/TCP, use the instrument endpoint. For an IVI/VISA connection, select the appropriate VISA resource and install its required runtime.

  3. Review framing and timeout

    Match the transmit termination, receive framing and timeout to the instrument manual. A correct port with the wrong line ending can still produce no response. Keep the command and configured terminator consistent to avoid sending an extra terminator.

  4. Check and save

    Select TEST CONNECTION and read the complete result. Save the reviewed configuration with SAVE DEVICE. If a duplicate USB identity warning appears, resolve the binding before relying on automatic reconnection.

Device configuration Inside the software
Actual application capture · COM / Serial setup for a new device, before instrument details are entered.
/03

What does TEST CONNECTION prove?

Connection path What the application checks What to verify next
Plain COM / Serial or RS485 Detects the configured COM device and reports the identity match. A detected port does not prove the instrument answered. Run a supported read-only query.
Raw LAN / TCP Attempts the TCP connection without a command. A connected socket does not prove the SCPI protocol or response is correct.
IVI / VISA Sends *IDN? through the selected resource and reports the result. Compare the returned identity with the intended instrument. Check the instrument manual if the query is unsupported.
/04

Send and inspect an identification query

  1. Select the saved device

    Open the Maintenance communication workspace and select the intended enabled device. Confirm its endpoint before sending.

  2. Prepare the query

    In TX CONSOLE, choose ASCII for TX Format. Enter *IDN? only for a compatible instrument. Set Line Ending to Device Default if the saved termination is correct, or choose the documented ending. Select AnyResponse as the initial Response Mode to require received data.

  3. Inspect and send

    Click BUILD / PREVIEW and inspect Final Request. Click SEND ONCE for this check. Review the TX / RX TRAFFIC and result; compare the actual response with the instrument identity you expect.

  4. Record the result before extending the sequence

    Retain the settings, transmitted command and reply. AnyResponse proves that data was received, not that it is the right instrument or a valid measurement. For a production step, configure the required response comparison or numeric limits and validate the complete step.

Communication Studio Inside the software
Actual application capture · Maintenance workspace with example configured devices and no transmitted traffic.
/05

Troubleshoot a missing or incorrect reply

Symptom Check next
No COM device is detected Check instrument power, USB cable and the Windows device driver. Refresh ports, then follow the COM recovery guide.
Detected or connected, but no RX Check whether the device supports the query, the exact selected endpoint, line ending, receive framing and timeout. Confirm the port is not held by another tool.
Garbled or incomplete reply Check serial baud/parity/data/stop settings, encoding and receive framing against the instrument manual.
Reply identifies another instrument Stop the trial and correct the selected device or USB/resource binding before any further command.
Identity works but a measurement fails Review the measurement command, selected function/range, response parser, units and limits. Identity success alone does not validate measurement behaviour.
Can I use the same SCPI command for every multimeter?

No. Use the programming manual for the exact model. An identification query and supported measurement commands may differ; a catalogue listing does not guarantee every command is supported.

Does a green connection result mean my test station is validated?

No. The connection check has a defined scope. You still need to validate instrument identity, the measurement or action, response interpretation and the complete station workflow.

Recover a changed COM port ↗ Validate barcodes and MES checks ↗ Devices and connectivity ↗

Need help with your test station?

Share your instruments, intended workflow and the question you need to resolve.

Discuss your station

BHARAT TEST SUITE · Application screen