Sensor types

Every read endpoint takes a phantomType identifying which kind of sensor you are asking about.

Code	Sensor
10	Triaxial Expert, low range
11	Triaxial Expert, high range
12	Biaxial
14	All in One
15	Triaxial ATEX, low range
16	Triaxial ATEX — see note
17	Triaxial G2, low range
18	Triaxial G2 — see note
20	Temperature, non-contact
21	Temperature, thermocouple v1
25	Temperature, thermocouple v2
30	Current
31	Current v2
40	RPM
60	General Purpose
61	General Purpose, 4-20 mA
62	Dry contact
63	Voltmeter

Duplicated labels in the source

The SDK documentation labels both 15 and 16 as “Triaxial ATEX Low Range”, and both 17 and 18 as “Triaxial G2 Low Range”. Given the pattern of every other pair in the table, the second of each is almost certainly the high range variant — but that is an inference, not something the source states, so it is not asserted here.

Pending confirmation from engineering.

These codes are not universal

The Modbus register block uses a different type table — it reports triaxial accelerometers as 3, 5 and 6, and biaxial as 50. Do not reuse this table for Modbus, or the other way round.

Reconciling the two is pending with engineering.

Which endpoint takes which type

The service does not reject a mismatched pair outright, so passing a temperature sensor’s type to getAccelData returns “No data” rather than an error. Match the endpoint to the sensor:

Endpoint	Types
getAccelData, getStateData, getSettingsData	10–18
getGPStateData, getGPSettingsData	60
getTempData	20, 21, 25
getCurrentData	30
getCurrentV2Data, getAccCurrentData	31
getRPMData	40
get4_20GPData	61
getDryContactData	62
getVoltData	63
getRSSIData	any

Only triaxial, biaxial and General Purpose vibration sensors accept settings — anything else returns status 506.