BHARAT TEST SUITE by Raju Bros Softech Pvt ltd

Instruments & integration

Device compatibility
and driver requirements.

Check the complete combination: instrument model, communication option, driver, commands, licence and test workflow. Existing profiles help with setup; the final station still needs validation.

Check your device list
/01

What compatibility means here

Reviewed 15 October 2026 · Raju Bros Softech Pvt ltd

The tables below identify profiles and communication routes implemented in BHARAT TEST SUITE. They distinguish that software support from a completed physical-hardware acceptance test.

Profile available

A model-specific action library supplies starting commands for a named instrument. Confirm that its commands and responses match your firmware and measurement task.

Integration available

The application has a communication or vendor-API route. The exact device, driver version and required operation must still fit that route.

Station validated

The selected hardware and software combination has passed an agreed acceptance test. A public list of hardware-validated combinations and driver versions is not yet available on this page.

Confirm before purchase. A device category, brand image, catalogue entry or available profile is not proof that every model or function in that family has been tested. Ask the team to confirm your exact combination.
/02

Available instrument action profiles

Instrument or family Available starting point Confirm for your station
OWON XDM1041 multimeter SCPI action profile with identification and measurement configuration commands. Physical connection, command termination, measurement ranges, reply parsing and firmware behaviour.
OWON SPE3102 power supply SCPI action profile with output, setpoint and query operations. Communication interface, operating limits, safe output state and the required readback commands.
UNI-T UDP6722 power supply SCPI action profile with output, setpoint and query operations. Exact model/firmware, command format, response termination and fixture operating limits.
Waveshare Modbus RTU relay family Relay action profile with mapped coil operations. Exact module, relay count, slave address, serial settings and coil-address mapping.
FEASA LED analyzers ASCII capture and reading actions for the supported analyzer workflow. Analyzer variant, firmware, channel configuration and required capture/readback operations.

These are available configuration profiles, not a claim that these exact model/driver/firmware combinations passed hardware testing during this website review.

/03

Interfaces and vendor dependencies

Connection or integration Software route Driver and setup considerations
COM / Serial and RS485 Configured serial commands and supported Modbus RTU operations. A working Windows serial/USB-converter driver; matching baud rate, parity, framing, device address and USB identity where available.
LAN / TCP Configured TCP commands and supported Modbus TCP operations. Reachable instrument address/port and the exact command or register map. An Ethernet socket does not imply support for every PLC or camera protocol.
SCPI over GPIB, USB or VISA resources Message-based IVI/VISA sessions. An appropriate NI-VISA, Keysight VISA or IVI VISA runtime and a valid resource. Review model-specific commands and response termination.
NI data acquisition NI-DAQmx integration and supported channel operations. NI-DAQmx native runtime plus matching .NET API/dependencies. Device and channel discovery must succeed; a simulated NI device is not physical-hardware validation.
Advantech data acquisition DAQNavi integration. DAQNavi/XNavi drivers and a loadable supported API. Confirm the module and its required analog/digital operations.
PEAK CAN / CAN FD PCAN API integration. Compatible PEAK hardware and PCAN driver package; CAN feature access. Confirm channel, bitrate, bus wiring and required frame mode.
PEAK LIN PLIN API integration. Compatible PEAK LIN hardware and PLIN driver/API; LIN feature access. Confirm channel, bitrate and master/slave workflow.
UVC camera capture Configured Windows DirectShow or Media Foundation capture route. A confirmed camera model, suitable Windows capture driver, supported resolution and controllable camera settings; applicable Vision access.
Windows system requirements ↗ Explore hardware families ↗ Licensing and bundles ↗
/04

Confirm a hardware combination

  1. Send the exact device list

    Include manufacturer, full model and option codes, firmware, physical interface, adapter model, Windows build and installed driver/API versions.

  2. Define the required operations

    List measurements, ranges, commands, response format, throughput target and any outputs or programming operations. Include the manufacturer’s communication documentation.

  3. Check discovery and a suitable read operation

    Verify the device in its vendor tool, then configure it in BHARAT TEST SUITE. Use an identification or read-only query supported by that model to inspect the response.

  4. Validate the intended sequence

    Run the approved test on the actual fixture, including limits, timing, disconnect behaviour, stopping and report evidence. Only perform output or programming operations under the station’s controlled procedure.

  5. Record the approved combination

    Save device, firmware, driver, Windows and application versions with the accepted operations and limitations. Recheck relevant behaviour when any of those components changes.

Request a compatibility review ↗ Technical support checklist ↗
/05

Device compatibility questions

Does SCPI support mean every SCPI instrument will work?

No. SCPI commands, optional interfaces, measurement features and reply formats differ by model. Confirm the required operations, transport and parsing against the instrument documentation.

Are NI and Advantech drivers included automatically?

The corresponding vendor runtime and supported API must be available on the station. Confirm approved driver installation and deployment with the team; the application alone does not replace the hardware vendor’s driver.

Are the listed devices certified or hardware-tested by this page?

This page verifies available software profiles and integrations. It does not publish a certified-device list or a completed physical test for every listed combination. Request the evidence and acceptance scope for your chosen hardware.

Can an unlisted instrument be evaluated?

Yes. Provide the exact model, interface, protocol documentation and required operations. The team can review whether an existing configurable route is sufficient or additional integration is needed.

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