IOT edge runtime modules

Stross, Jared 41

I have a Linux VM created and hooked up with an IOT edge device that I plan on using as a gateway. It is saying my edgeHub module is not online or connected, how would I go about getting this issue fixed?

QuantumCache 20,031 Reputation points

2022-08-08T16:57:43.587+00:00
Hello @Stross, Jared

Could you please share more information on this issue, such as,

IoT Edge version used?

any IoT Edge logs? or

any error screenshots?

Any particular documentation or tutorial followed?

Troubleshoot your IoT Edge device

What do you see if you run the following command?

sudo iotedge check
Sander van de Velde 28,236 Reputation points MVP

2022-08-08T18:50:32.373+00:00

Hello @Stross, Jared ,

did you already deploy an IoT Edge module to the edge device?

By default, only the edgeAgent is deployed at first. Once you deploy a regular module, the edgeHub is deployed too.
Stross, Jared 41 Reputation points

2022-08-09T11:53:24.153+00:00
Hi @QuantumCache , so I deleted my previous VM and IOT edge device and made new ones. They are online now and my edgeHub is connected but my Agent is not. How would I go about getting my Agent connected? As for the other information

1.3

I have attached a picture of the logs for edgeAgent after I ran "iotedge logs edgeAgent"

I have attached a picture of the "Get module info" from VS code

Yes, I am trying to use the modbus module to store data from a PLC to the cloud https://learn.microsoft.com/en-us/azure/iot-edge/deploy-modbus-gateway?view=iotedge-2020-11

I attached snippets of this

Thank you so much for the help I appreciate it!
Stross, Jared 41 Reputation points

2022-08-09T11:57:01.183+00:00

Hello @Sander van de Velde

I did not at first, but I made a new device and deployed the modbus module and it seemed to work. The modbus and edgeHub are connected and running, my edgeAgent is only running not connected. I feel like I might be missing something, do I need containers registry's, manifestations, or anything else of that nature for my device to be fully connected and running?

Thank you in advance for the help!
Stross, Jared 41 Reputation points

2022-08-09T12:57:13.13+00:00

My bad I forgot to attach them
Stross, Jared 41 Reputation points

2022-08-09T14:04:14.88+00:00

Additionally, I am confused as to how I would go about doing the routing for the modbus link I attached earlier.

From the link I want to try and send Data/messages being from a modbus device to the modbus module. I want to then have the modbus module use telemetry to send the data to iot edge runtime. Then from runtime to my hub via AMQP. The only problem is the guide doesn't give any help on how to set that routing up.

Accepted answer

Sander van de Velde 28,236 Reputation points MVP

2022-08-09T15:45:21.133+00:00

Hello @Stross, Jared ,

I expect you are using the Microsoft Azure IoT Edge modbus module, as seen here: https://github.com/Azure/iot-edge-modbus

This module is connecting to some modbus source and is capable of both reading data and making modbus changes.

That said, it's just another custom Azure IoT Edge module so you need to route the modbus messages, sent to the output on the module, to $upstream (the EdgeHub, the local IoT Hub proxy). Or you can put a module in between to take action or filter or transform.

In the past, I have worked with the module a number of times. Here are some blog posts 1 2 I wrote to the know the module.

Please invest some time in learning about Azure IoT Edge, using this free learning path (and more)

Then you have a better understanding of the responsibilities of the edgeAgent and the edgeHub modules. And you learn about routing.

Regarding the edgeAgent output, this seems ok. The edgeAgent is mainly responsible for the 'life and death' of other modules. I ask for the deployment manifest and based on the changes, new containers are loaded and started and deprecated once are deleted. There is also some metrics scraping but that is apart from the deployment manifest actions.
Please sign in to rate this answer.

1 person found this answer helpful.
Stross, Jared 41 Reputation points

2022-08-09T16:49:13.55+00:00

@Sander van de Velde Thank you for the help I appreciate it!

Sander van de Velde 28,236 Reputation points MVP

2022-08-09T16:55:10.703+00:00

Hello @Stross, Jared ,

Check the "Version" property to switch between the PP (Public Preview) and the latest Message Payload format. (valid value for PP: "1", all other values will switch to the latest format)

The PP format version is a bit simpler and on par with the latest one,

----------

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, all community members who have a similar issue will benefit. Your contribution is highly appreciated.

Stross, Jared 41 Reputation points

2022-08-09T17:47:10.56+00:00

@Sander van de Velde Would this be the right configuration and routing? To me it seems all I would have to do know is make sure that the Modbus server device is writing from the holding register.

Sander van de Velde 28,236 Reputation points MVP

2022-08-09T19:24:43.837+00:00

Hello @Stross, Jared ,

you have to understand edge modules are decoupled.

Each module can have multiple inputs and outputs.

The modbus module read modbus messages and sends them to an output (I believe 'output1'). It also takes messages on an input so it can change modbus values.

It is you who connects the 'dots'. You connect inputs and outputs using routing.
Sign in to comment

IOT edge runtime modules

0 additional answers