Add content properties to the message sent to the output about iot-edge-modbus HOT 4 CLOSED

We are also facing the similar issues. The messages stored to blob storage through message routing mechanism are all encoded because of content type.

from iot-edge-modbus.

I forked this repo to https://github.com/sandervandevelde/iot-edge-modbus and fixed a few things.

Try my module and enjoy the .net core 3.1 version of iot-edge-modbus.

Some considerations and limitations:

• Prebuilt modules available at https://hub.docker.com/repository/docker/svelde/iot-edge-modbus
• Bumped to .Net core version to 3.1
• .Net Core 3.1 supports SerialPort on multiple operating systems so C code is dropped.
• Messages now encoded to utf-8 instead of ASCII
• Added Message properties for ensuring UTF8 encoding
• SQLiteCommandMessage removed
• Deployment limited to Windows/Linux/Raspberry Pi 32bits linux; Non Debug versions
• Documentation (readme etc.) is not updated.
• See https://github.com/iot-edge-foundation/iot-edge-serial#configure-create-options for the Windows Create options

Note: This is tested using the Linux version of the containers only. Please perform your own extensive tests.

A pull request is added.

from iot-edge-modbus.

Thanks for the information sharing.

Just wanna clarify that this "ASCII encoding is not supported by the IoT Hub routing." statement is true ONLY when utilizing Azure Storage as a routing point.
Please read the document here:
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-d2c#azure-storage-as-a-routing-endpoint

For those who don't setup Azure storage in routing endpoint, the d2c message in ASCII won't cause issue.

We'll include this fix. And thanks for the catch!

from iot-edge-modbus.

Please fork or clone the code for further modification/customization to build modbus module that fullfill your need.
This repository is no longer being actively maintained and will be archived. Open issues will be closed.

from iot-edge-modbus.