|
Configure the uplink to AT&T's M2X service.
AT&T has discontinued support for M2X.
Expect LOGGER support to be removed in a future release.
M2X allows a sensor device to log sensor history in the cloud. Applications
can then be written that use the cloud data as a proxy for the sensor itself.
Using a proxy has the advantage that a recent sensor value is always available
to the application even though the sensor is not able to respond directly
when the application makes the request.
| M2X Keys |
|---|
|
| (This signature is the Access Key) |
|
| (This is the Device Key) |
|
| |
If the keys are changed the system must be rebooted.
|
Choose the sensor streams to send to the IoT uplink service.
These streams must also be configured as streams of the device on the M2X server.
A green background is shown for sensor streams that will send data to the uplink server.
Also a green box shows the current state of the sensor stream.
| Stream ID | Current Sensor Value |
|---|
| | Controls |
|---|
| A | 0.475 |
| |
|
| DragonnorthKwh | 8606711 |
| |
|
| Frequency_0 | 0.05 |
| |
|
| Pulse_1 | 0 |
| |
|
| Frequency_1 | 0.00 |
| |
|
| Pulse_2 | 0 |
| |
|
| Frequency_2 | 0.00 |
| |
|
| Pulse_3 | 0 |
| |
|
| Frequency_3 | 0.00 |
| |
|
| Pulse_4 | 0 |
| |
|
| Frequency_4 | 0.00 |
| |
|
| Pulse_5 | 0 |
| |
|
| Frequency_5 | 0.00 |
| |
|
| Pulse_6 | 0 |
| |
|
| Frequency_6 | 0.00 |
| |
|
| Pulse_7 | 0 |
| |
|
| Frequency_7 | 0.00 |
| |
|
| IO1_P00 | 0 |
| |
|
| IO1_P01 | 0 |
| |
|
| IO1_P02 | 0 |
| |
|
| IO1_P03 | 0 |
| |
|
| IO1_P04 | 0 |
| |
|
| IO1_P05 | 0 |
| |
|
| IO1_P06 | 0 |
| |
|
| IO1_P07 | 0 |
| |
|
| IO1_P10 | 0 |
| |
|
| IO1_P11 | 0 |
| |
|
| IO1_P12 | 0 |
| |
|
| IO1_P13 | 0 |
| |
|
| IO1_P14 | 0 |
| |
|
| IO1_P15 | 0 |
| |
|
| IO1_P16 | 0 |
| |
|
| IO1_P17 | 0 |
| |
|
| Temperature_0 | 20.56 |
| |
|
| MS_Pressure | 1016.78 |
| |
|
| MS_Temperature | 21.28 |
| |
|
| MS_Humidity | 31.3% |
| |
|
|