Please enable JavaScript to view this website.

Skip to main content

Lookup & Path Selection

This page covers Phase 1 (tool record lookup and pre-initialization checks) and Phase 2 (path selection). No data is written to the tool in either phase.

Phase 1 — Tool Record Lookup​

Triggered when the operator enters a serial number. No data is written to the tool in this phase.

  1. Cloud: look up tool records by serial number. From the returned set, select the record whose serial number matches exactly and that carries an MPBID. If none, the lookup is treated as a failure (see Non-serializable fallback).
  2. Cloud: fetch unique writable data for the tool MPBID. This returns the passwords, Born-On-Date (BOD), and (if applicable) MLS certificates. A BOD must be present — if it is missing, fail.
  3. If the tool record references a linked BLE MPBID (either an explicit linked MPBID or an existing BLE context): Cloud: fetch unique writable data for that BLE MPBID. Again, a BOD must be present or fail. This becomes the tool's BLE context.
  4. Run the outdated-BLE-firmware check (below).
  5. Run the BMS-replacement check (below).
  6. On success, the tool is marked ready and the operator can start initialization.

Non-serializable fallback​

If lookup fails for any reason, before reporting failure: read the connected tool's MPBID, then Cloud: request product info for that MPBID. If the product is flagged non-serializable, skip initialization entirely (this is a normal outcome, not an error). Otherwise report the failure.

Outdated-BLE-firmware check​

Applies only to M18 tools whose module is BGM11S and which are not embedded-tick-only products.

  1. Read the BLE MAC address from the tool.
  2. If the MAC is all zeros, the module is stuck in DFU (firmware-update) mode. Read the tool MPBID, trigger the BLE repair routine, and wait for it to succeed or fail. If repair fails, abort with a DFU error.
  3. Otherwise, open an ad-hoc DFU-type BLE connection and query whether the module is in DFU mode:
    • Not in DFU: read the BLE module type. If it is BGM11S, read the BLE firmware version and log it. If the version is < 5.1.0.0, signal that a BLE firmware update is required.
    • In DFU: read the tool MPBID, trigger the BLE repair routine, wait for success/fail; fail on repair failure.

BMS-replacement check​

Applies only to 50E3 RollOn (NA or ANZ product IDs) on a CANopen tool.

  1. CANopen: read the MPBID from the BMS node.
  2. Extract the product ID from that MPBID. If it is a 51X unit (NA or ANZ), the BMS has been physically replaced — flag the BMS-replacement workflow for the initialization phase.

Phase 2 — Path Selection​

When the operator starts initialization, the path is chosen by tool class: