Device Library

● Not connected

DEVICENo Axiom connected

STATEOffline workspace

LIBRARY FILE—

LOCAL DRAFT

Custom package

Saved locally

Descriptor guide

JSON

A library contains a devTypes object keyed by device type name. Check messages are advice, not a complete description of what this firmware accepts.

Identity & addresses

The object key identifies the type. If deviceType is supplied, it must match that key. devInfoJson.type is metadata and can differ in existing profiles. New/Add controls accept 1–48 letters, digits, underscores or hyphens; LTR-390 is valid.

addresses lists I²C addresses or inclusive ranges, such as "0x29,0x30" or "0x10-0x18". A Robotical device identified through WHOAMI can instead declare deviceTypeId as an integer or a hex string such as "0x0084".

Some Add/Customise controls protect system profiles and addresses 0x25, 0x36 and 0x70–0x77. Firmware also protects the required MAX17048 fuel-gauge profile. Other editor checks are advice for JSON written through other paths.

Detection & initialisation

detectionValues: "0x00=0x42" writes byte 00, reads one byte and expects 42. Prefer a datasheet’s device identity register.

Join steps with & or ;. Bytes before = are the write. Detection compares the returned hex value or a byte-aligned binary mask; x ignores a position in binary, not hex.

Empty detectionValues matches on address alone. A custom profile is tried before compiled candidates, so sharing an address does not prove the attached device is the intended model.

initValues runs when identification succeeds. Use whole-byte writes and explicit decimal rN reads or pN millisecond pauses where supported by the parser. A pause needs =: =p20 waits; a bare p20 is parsed as a write.

0x0001=p25 means write 0001, then wait 25 ms. The current Test controls omit that write, so their verdict is unreliable for such sequences. Initialisation does not compare concrete expected values; put identification checks in detectionValues.

Polling & response

pollInfo.c describes the poll sequence: "0x01=r2" reads two bytes after writing 01. The AHT20 sequence "=r6&0xac3300=" reads the previous result and triggers the next measurement. Advanced syntax is defined by the pinned Raft parser.

pollInfo.i is the saved polling interval in milliseconds; 100 means 10 polls per second. Applications can override runtime polling. It is separate from publication frequency and any independently configured internal sensor measurement rate.

pollInfo.s is retained samples, not delivery QoS. Leave polling absent for an actuator that is not polled. devInfoJson.resp.b describes the response size and must agree with the poll layout; attribute metadata supplies names, units and conversion rules.

The editor displays decoder metadata as JSON. Live readings discard decoder code supplied by a profile. RaftJS receives application-owned code only for an exact reviewed device-type and decoder-name pair; other profiles retain their ordinary metadata without supplying executable code.

Install, limits & recovery

The connected device reports its file and record limits. Browser grammar advice can be stricter than the firmware parser and does not block writing. The older fixed-read, 128-byte and 16-sample rules are not the current firmware library contract.

Saving changes only the local draft. Write to Axiom replaces the whole library file; Restart Axiom applies it. Removing the file restores built-in definitions only after restart. There is no trial or automatic rollback, and firmware can accept some records while rejecting others.

A same-name custom profile has compiled fallback. {"disable": true} suppresses that type altogether. Disable keeps a saved custom definition in the entry, and Enable restores it.

Byte counts use the same two-space-indented JSON that draft export and Write to Axiom send. The limit is measured over those exact UTF-8 bytes, including indentation and multi-byte characters. Templates and catalogue labels are not proof of compatibility or tested hardware behaviour.

What will change

The write

I have reviewed what will be written and am ready to restart Axiom.

Writing replaces the whole library file and changes nothing else. Axiom keeps running its current definitions until it restarts.

The library file on Axiom

Not connected.

What Axiom did with the file it has

devlib

If something is wrong

Removing the file restores Axiom's built-in definitions on the next restart.

The bus

Not scanned yet.

Scan the bus to see what Axiom finds and which of your profiles claimed it.

Raw bus state

Reported by Axiom as-is and not interpreted here.

Run a check to read the bus state.

Selected device

Select a detected device above.

Try a detection command

Run a profile’s detectionValues against the selected device and see whether it answers as that profile expects. Nothing is installed and nothing is written to the library — this only asks the device the question the profile would ask.

Send a write

Exercise an actuator by writing bytes to the selected device. This drives real hardware as soon as you send it. The write is one-way — nothing is read back — so judge the result by what the hardware does.

USB recovery & preview limitations

Repeated software restarts can intermittently leave USB unresponsive. Unplug and reconnect Axiom, then reconnect here and refresh. Never assume an interrupted command succeeded — read the device’s state back rather than inferring it. Close other tabs or serial tools using Axiom before connecting.

This page talks to Axiom over native Web Serial, so it needs desktop Chrome or Edge; connecting over Bluetooth is not supported. Libraries can also be shared as JSON files or imported from a CORS-enabled HTTPS URL. The firmware updater remains available above.

Device Library

Custom package

What will change

The write

What Axiom did with the file it has

If something is wrong

The bus

Selected device

Temporary settings

Try a detection command

Send a write

Catalogue

Devices on this Axiom

Please confirm

Enter a value