21
edits
Changes
Correct terminology mistakes. Direct method term does not use any uppercases
For testing and demonstration purposes we will use the Azure IoT Explorer application. The Azure IoT Explorer is a graphical tool for interacting with devices connected to your IoT hub. To learn more about this tool you can follow the Microsoft documentation [https://learn.microsoft.com/en-us/azure/iot/howto-use-iot-explorer here].
For testing and demonstration purposes we will use the Azure IoT Explorer application. The Azure IoT Explorer is a graphical tool for interacting with devices connected to your IoT hub. To learn more about this tool you can follow the Microsoft documentation [https://learn.microsoft.com/en-us/azure/iot/howto-use-iot-explorer here].
After enabling the Direct Method feature go to Azure IoT Explorer, select the appropriate device identity and navigate to the Direct Methods tab. All our devices support the '''"api_call"''' direct method which exposes the API interface to be used from the Azure side. In this example we will make a simple GET request to retrieve the I/O status of the device. Full documentation of Teltonika devices API can be found [https://developers.teltonika-networks.com/ here] .
After enabling the direct method feature go to Azure IoT Explorer, select the appropriate device identity and navigate to the direct methods tab. All our devices support the '''"api_call"''' direct method which exposes the API interface to be used from the Azure side. In this example we will make a simple GET request to retrieve the I/O status of the device. Full documentation of Teltonika devices API can be found [https://developers.teltonika-networks.com/ here] .
The Azure IoT Explorer Direct Method tab will have a Payload field. In this field the '''"api_call"''' method expects JSON formatted data.
The Azure IoT Explorer direct method tab will have a Payload field. In this field the '''"api_call"''' method expects JSON formatted data.
[[File:Azure RutOSconf 20.png|border|class=tlt-border]]
[[File:Azure RutOSconf 20.png|border|class=tlt-border]]
===Dynamically monitoring Modbus data===
===Dynamically monitoring Modbus data===
This example shows how to monitor and dynamically control Modbus data purely from the Azure cloud. We will set up a simple Modbus TCP server and client with Data to Server which will forward all the incoming Modbus data to Azure IoT Hub. In the end, using Direct Methods we will showcase how Modbus TCP client can collect and report different data from the cloud.
This example shows how to monitor and dynamically control Modbus data purely from the Azure cloud. We will set up a simple Modbus TCP server and client with Data to Server which will forward all the incoming Modbus data to Azure IoT Hub. In the end using direct methods we will showcase how Modbus TCP client can collect and report different data from the cloud.
[[File:697131 TOPO.png|border|class=tlt-border]]
[[File:697131 TOPO.png|border|class=tlt-border]]
[[File:Azure modbus example 5.png|border|class=tlt-border]]
[[File:Azure modbus example 5.png|border|class=tlt-border]]
This concludes the Azure IoT Hub guide. Using Direct Methods with device API is a powerful tool that unlocks new capabilities of device monitoring and control from the cloud. Nearly all features available via device WebUI are also available using API.
This concludes the Azure IoT Hub guide. Using direct methods with device API is a powerful tool that unlocks new capabilities of device monitoring and control from the cloud. Nearly all features available via device WebUI are also available using API.
'''
'''
