Hello,
what is the best way to implement/use MQTT on NetDCUx device?
Is there somewhere a library or some example code, I could use?
Best regards,
Andy
MQTT client support
-
-
Hello,
you may try this "MQTT Client Library for .Net and WinRT" (https://github.com/eclipse/paho.mqtt.m2mqtt). According summary it works under WEC7/CF3.5 and WEC2013/CF3.9 (so i assume it should work under WCE6/CF3.5 too).
PS: at the time we deliver following NetDCUx.
OS NetDCU9.2/11.2: WEC6
OS NetDCU14: WCE6/WEC7
OS NetDCUA5: WCE6/WEC7/WEC2013
OS NetDCUA9: WEC7/WEC2013
-
Hello,
I tried but aren't able to use it.
Compiled the dll sucessfully but cannot use it in my NetDCU project.
First I cannot enable the /clr option (not available in project).
I tried on Win7 and there was a /clr option, but then I ran into 2nd problem:
I don't know how to access to Object names and methods of .Net Dll.
Do you have some examples or other tips to get this to run?
-
Hello,
you may try similar like this https://support.microsoft.com/…c-code-in-visual-studio-n . But i dont know if it is a good idea to do this. Why you do not write this program part in .NET?
-
Hello,
the reason is I have already a big tool/program written in C++.
In that I would just like to send/publish MQTT messages to a broker.
To convert my main program into .NET would take months...
-
Hello,
so use just a small memory (e.g. file) which is shard between both applications so .NET part does only read the information and send/publish it.
-
There are lots of software solutions for MQTT:
Client side: https://github.com/mqtt/mqtt.github.io/wiki/libraries
Server side: https://github.com/mqtt/mqtt.github.io/wiki/servers
There should be something among all these libraries and solutions that works for you.
Your F&S Support Team
-
Hello,
after trying several methods:
shared memory, named pipes (not supported on .NET 3.5 ),
Clipboard (did not work),
communication over files (too many write operations would cause an earlier death of flash memory),
I decided to communicate over network.
Application 1 (c++) sends messages to Application 2 (c#) on same device (WinCE).
This 2nd application forwards the received messages to its defined MQTT broker.
This seems to work sufficently.
Best regards, Andy
-
Hello,
ok - use Network may also be a good solution.
>> shared memory, named pipes (not supported on .NET 3.5 )
<< Assume it is possibel to use DLL import to implement this features into a c# project.
