HTTP Push / Motor Sense
These are two modes for receiving values from external IT systems / measurement solutions rather than from a PLC.
| Mode | When to use it |
|---|---|
| HTTP Push | When an external system "sends" values to the gateway. Example: an in-house MES pushes a batch name, a barcode scanner pushes a value |
| Motor Sense (MOTOR_SENSE) | When polling vibration/status data from the KOPENS Motor Sense solution |
HTTP Push Mode
Instead of the gateway "going out to read" values from a PLC, an external system pushes the values in.
Registration form entries
| Field | What to enter |
|---|---|
| IP address | (not actually used, for identification only) — e.g. 127.0.0.1 |
| Port | (not actually used) — e.g. 0 |
| Collection interval | The interval at which the gateway reads and processes externally pushed values from its cache — normally 1000 |
PLC address notation for tags
A free-form key string. This is the identifier the external system uses when pushing values.
| Example | Meaning |
|---|---|
temperature | Free-form name |
line/A/rpm | Slashes allowed |
barcode.last | Dots allowed |
How to send values from outside
Send an HTTP request in the following format to the gateway.
POST http://<gateway-ip>/api/v1/tag/<tag-id>/value
Content-Type: application/json
{ "value": "25.7" }
Alternatively, see the "Writing values" section of the Advanced — REST API page.
Once a value arrives, it appears on screen at the next collection cycle and is transmitted via MQTT / Sparkplug and so on, just like any PLC value.
Common use cases
| Case | How |
|---|---|
| MES pushes a batch name | Create a tag such as recipe.name with data type String |
| Collecting barcode scanner results | barcode.last, String |
| Relaying values from an external PLC (one that cannot be connected) | Have that system send pre-converted values |
| Sending in external analysis results | quality.score, Float |
Motor Sense
A dedicated mode for retrieving data from the KOPENS Motor Sense solution.
Differences from a standard PLC
| Item | Standard PLC | Motor Sense |
|---|---|---|
| Screen display | Tag table | Per-asset cards (HEALTH INDEX / SIGNAL) |
| Tag registration | Entered one by one by the user | Auto-generated (signals + health_index) |
| Refresh interval | Screen 5 s | 1 s background refresh |
| Data format | Free-form | JSON array (multiple assets grouped) |
Registration form entries
| Field | What to enter |
|---|---|
| API KEY | API key issued by KOPENS |
| Customer ID | Customer identifier issued by KOPENS |
| Asset list URL | URL for querying the asset list |
| Asset signal URL | URL for asset signal data |
| Asset health index URL | URL for asset status (health index) |
| Load waveform/spectrum | Whether to also retrieve the heavy waveform data |
The URLs must start with http:// or https://.
Auto-generated tags
The gateway automatically creates two tags.
| Tag name | Meaning |
|---|---|
signals | Per-asset bundle of signals such as vibration / temperature / voltage (JSON array) |
health_index | Per-asset health indices (imbalance / alignment / bearing, etc., JSON array) |
The data for each asset is expanded into card format.
Common problems and solutions
HTTP Push mode
| Symptom | Cause | Solution |
|---|---|---|
| No values arriving | The external system did not push, or the tag ID is misspelled | Check the external system log. Verify that POST /api/v1/tag/.../value returns 200 OK |
| Values update slowly | Collection interval is too long | Reduce [Collection interval] in the PLC registration (e.g. 500ms) |
Motor Sense mode
| Symptom | Cause | Solution |
|---|---|---|
| "drive not on classpath" | Motor Sense jar not installed | Ask your system administrator to install the Motor Sense jar |
| 401 Unauthorized | API KEY / Customer ID error | Verify the KOPENS-issued key carefully |
| URL rejected | Does not start with http:// or https:// | Check the URL format |
More detailed examples / automated registration
See the HTTP / Motor Sense examples in Advanced — REST API.