Changing a sensor’s address is three operations, not one. Skipping the third is the most common reason a sensor “disappears” right after being configured.

  ① host → sensor's current subnet
② change the sensor's IP      ← the only software-specific part
③ host → sensor's new subnet, then verify with ping
  

① Align the host first

If you cannot reach the sensor, you cannot configure it. Set your adapter to a free address on the sensor’s current subnet — usually the factory one. The procedure is in Network & host setup.

Confirm before continuing:

  ping -c 3 <sensor-current-ip>
  

② Change the sensor address

③ Re-align the host and verify

Move your adapter to the new subnet, then confirm:

  ping -c 3 <sensor-new-ip>
  

If ping fails, check in this order:

CheckFix
Adapter still on the old subnetMove it — this is the usual cause
Address already in usePick another; see IP conflict
Wrong subnet maskMask must match the sensor’s exactly
Sensor still rebootingWait 30 s and retry

Record the assignment

Add the sensor to your installation’s address table: sensor serial, address, physical location. Service visits years later depend on it.

Next

Address set and reachable? Move on to Calibration.