Skip to content

Queue new sensor settings

POST
/saveSettings
curl --request POST \
--url http://localhost:80/PhantomService.svc/saveSettings \
--header 'Content-Type: application/json' \
--data '{ "phantomType": 11, "phantomCode": 189247628, "IntervalSendData": 60, "Range": 16, "IntervalRMS": 30, "alarm1": 6.4, "alarm2": 8.6, "alarm3": 10 }'

Writes settings to a JSON file. The sensor picks them up the next time it asks for its configuration, not immediately.

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

Media typeapplication/json
object
phantomType
required

Sensor type code. See the Sensor types page for the full table.

integer
phantomCode
required

Sensor serial number. ⚠️ Aquí es ENTERO, mientras que en UpdateConfig el mismo dato es una cadena.

integer
IntervalSendData
required

Minutes between full data sends. Minimum 10 (status 503).

integer
Range
required

Sensor range in G. Invalid values return status 502.

integer
IntervalRMS
required

Seconds between alarm checks. Minimum 30 (status 504).

integer
alarm1
required

Alarm threshold in mm/s. Minimum 0.5 (status 505).

number format: float
alarm2
required

Alarm threshold in mm/s. Minimum 0.5 (status 505).

number format: float
alarm3
required

Alarm threshold in mm/s. Minimum 0.5 (status 505).

number format: float
Example
{
"phantomType": 11,
"phantomCode": 189247628,
"IntervalSendData": 60,
"Range": 16,
"IntervalRMS": 30,
"alarm1": 6.4,
"alarm2": 8.6,
"alarm3": 10
}

The outcome of the operation.

Media typeapplication/json

The Key half of every response envelope.

object
StatusNumber
required

0 means OK. See the Status codes page.

integer
Description
required
string
Configs
Array<object>
object
Example
{
"Description": "OK"
}