Sensor compatibility

RangeFinder Studio works with any device that speaks SCIP. The protocol version is auto-detected on connect, so SCIP 2.0 and 2.2 sensors stream without configuration. Hokuyo's full Ethernet and USB lineup is the primary target. Third-party SCIP-compliant devices connect the same way.

Protocol

Commands supported

The Gateway workspace speaks the standard SCIP command set. The Proxy workspace passes everything through byte-for-byte, so commands the editor does not implement still reach the sensor unchanged.

Command	Use
VV	firmware version + protocol negotiation
II	identity (vendor, model, serial)
PP	parameters (FOV, step count, angular resolution)
BM	beam on
QT	quit / standby
RS	reset
GD / GE	one-shot distance / distance + intensity scan
MD / ME	continuous distance / distance + intensity stream
$IP	set the sensor IP (with confirm + power-cycle reminder)

Simulation profiles

For the Simulation workspace, the editor needs to know a sensor's geometry (FOV, step count, angular resolution), range envelope, and datasheet noise. Profiles ship as small JSON files. When a connected sensor reports an identity that matches a bundled profile, the profile is selected automatically. To simulate a sensor that's not bundled, drop a JSON file into the editor's profiles directory:

{
  "identity": {
    "vendor": "Hokuyo",
    "model":  "UST-30LX",
    "protocol": "SCIP 2.2"
  },
  "geometry": {
    "first_step": 0,
    "last_step":  1080,
    "angular_resolution_deg": 0.25
  },
  "range":  { "min_mm": 23,  "max_mm": 30000 },
  "timing": { "scan_rpm": 2400 },
  "capabilities": { "multiecho": false, "intensity": true }
}

Field accuracy reflects the sensor datasheet, not a measurement. Profiles are loaded at startup; a hot reload command is on the deferred list.

Verify your sensor

Easiest path: open the Gateway workspace, type the sensor's IP and port, click Connect. The editor sends VV followed by II, prints the detected version and identity, and the connection is live. If the editor reports a SCIP error or a timeout, the device is either off the network or not speaking SCIP.

From a terminal, the same probe is one line:

# Send VV (version), read response. Sensor returns "VV\n00P\n\n..." on success.
printf "VV\n" | nc 192.168.0.10 10940