stefandreyer / codesys-mqtt Goto Github PK

Dear Stefan,

I tried your great MQTT-library in my Codesys 3.5.16.0 on a PFC200 G2 for my home. I adapted only little references to the recent oscat libraries (little changes because of compatibility with recent codesys version) and your GreatExampleOfAdvantages is running for a few days now.

I have problems to understand how the topics are created. I see the instance name correct but I think MyTopicSend and MyTopicReceive does not include the "block"name. So only the Lamp1 in the example is working fine by the Topic. I cannot control Lamp2 and Lamp3 and I donot receive changes from them. Do you see a problem in my attached pictures?

Thank you and btw: Ich spreche auch Deutsch ;-)

annD

The Common Helper for development Library (CommonTypesAndFunctions) is not provided, so the project cannot compile succesfully.
Maybe a .Projectarchive would be more fitting? i.e. all dependancies (libs etc) can be attached.

Hi Stefan, I am interested in your Codesys-MQTT project. Unfortunately, I found these errors after I have installed all libraries from the project's repository. The version of Codesys is Codesys V3.5 SP 15 Patch 1 (32 bit). Is there any problem with the version I am using?

Kommando zurück, hat sich erledigt. Konnte es doch finden.

Hello Stefan,
I am interested in using MQTT on codesys using the library that you created. However, when I try to add the library, an error like this appears:

what should I do?

Since http://test.mosquitto.org doesn't seem to work anymore I want to test my setup with a different broker. Is there a way to configure the broker in the test function.
Or is it better to go directly to the normal functions and the real-life examples?

I was able to successfully publish to an MQTT broker using this function block in Codesys running on a raspberry pi but the function block did not have a subscribe option... can anyone help?

Hi Stefan,

correct me if I'm wrong but it seems that the will topic is currently a hardcoded concatination of 'clientId' + '/MQTTWill/' + 'clientId' + 'Topic', any chance you could change this so we can full configure the topic ourselves? (this breaks the convention for all my other devices..)

Also, if you could support MQTT birth messages that would be great, very handy to know if the PLC is available in combination with MQTT will messages :)

can you provide a very simple example.
I think a clean raspberry project with just sending a message and subscribe to a topic would be great.
I would help with this but.. I don't get it to work because there are so many variables and structs.. I don't really see whats going on there and I can't get it to work in an other project.
Thank you

Is there a way to convert this project to be able to use in a Phoenix Contact PLC?
Or can you give us the raw ST code of the library?

Hi Stefan,
Whats the best way to have multiple instances of the subscribe function .
Have been trying with the example "TestMQTTGithubInterfaceExampleTopicAndPayloadRaspberry" but for the SONOFF with the Tasmota Firmware the topic are quite long.
For example I need to extract the payload from the the fallowing topics
HOME/GARAGE/tele/STATE { "Vcc":3.12, "Power":ON, "Level":High }
HOME/GARAGE/stat/POWER ON

HOME/IRIGATION/tele/STATE { "Vcc":3.12, "Power":OFF, "Temperature":21.7 }
HOME/IRIGATION/stat/POWER OFF

Any help is much appreciated.

The compiler throws some errors, please have a look at the picture below. What can I do?
My PLC ist a Wago PFC200.

In multiple places receive and received are written as recive and recived.
Not a big problem, but something that I noticed 😟.

Hi,

I have you done any work to-date to enable the MQTT library to work on 64 PLC devices?

From what I can see its the reliance on SysSocket23 library that is not supported. I have tried to replace it with another that works on 64 PLCs but it just seams to create more errors.

Any thoughts would be appreciated as it worked well on our original system.

Thanks.

Has anyone tested this on the wago pfc 100?
It tried to execute TestOutOfTheBoxNoTLS and on build it says.
C0265: No memory for dynamic object creation defined for application 'Device.Application'

Does anyone know what this means and how to fix it?

I can't open a project for windows 10 64 bits, through 32 bit libraries, what would be the way to open *. project with its corresponding libraries for 64 bits?

Dear Stefan,

Trying to run your MQTT library on an Epec 6200 controller. Codesys 3.5.13 (newer is not recommended for now by Epec).

I managed to get all the libraries installed (downloading missing libraries only helped partially). To compile the application all works fine now (I had to add ^ to DATA.PayloadString and StrPt in ReceiveValue.PublishReceived and had to change CommonTypesAndFunctions.FindLastDot to CommonTypesAndFunctions.FindLasDot until I realized that you have an updated version of the library in a different repository, still version 1.0.0.0 according to Codesys though).

So it compiles with no errors. But after downloading I get 20 errors, all Unresolved references related to Crypto. I did install the CmpCrypto library, version 3.5.11.0. Don't know whether it is actually related to this library. Any idea what this could be? Is there a way to work around this?

Out of curiosity: Yesterday you replaced MQTT.library v1.1.0.0 with a different v1.1.0.0. What changed?

Thanks, Martijn

Hello Dreyer,

I'm Using your newest MQTT Library Ver 1.1.03 on Wago PLC PFC2000.
My Schemes Are Sending Data From Omron PLC (Publish) to my PFC2000 PLC (Subscribe) Through MQTT with mosquitto as my mqtt broker.
I have been successfully connected to both PLC, it is indicates from the mosquitto side.
But i cannot find my data on my PLC Wago, it should be on this picture Below right?

the data is retrived to my PFC2000 but i cannot find a way to see it and move it to my own variable (Data is null like the picture above).after i open the receiver and put breakpoint into it, the data exist on 'PayloadString^' like this picture below :

my question is , how do i get that received data and move to my own variable?im new to codesys, im expecting your answer.

*PS: i have been searching the same issue on your post and i found same similar case with me, but the case is closed and i still dont understand how to get my var...

Hi, in the timeDate\RTC_2 FB, the VAR_OUTPUT LDT is giving me an error. Can this be happenning because of the LDT data type already in codesys?
https://help.codesys.com/api-content/2/codesys/3.5.16.0/en/_cds_datatype_date_and_time_of_day/

Should this variable be renamed?

Hallo Herr Dreyer,

meine Firma und ich möchten uns wegen dem guten Support gern erkenntlich zeigen. Gibt es eine Möglichkeit Ihnen eine Spende zukommen zun lassen, per Paypal zb. ?

Mit freundlichen Grüßen
Sven Jödicke

Hi! Can i use this library in Codesys v3.5 SP11 Patch 5? Can you send me example for my codesys version? Thanks!

Hallo Stefan,

erstmal vielen Dank für die gute Arbeit. Ich habe dein Beispiel TestMQTTGithubInterfaceExampleTopicAndPayloadRaspberry zum laufen gebracht und bekomme auch eine Verbindung hin. Allerdings habe ich das mit dem Subscribe noch nicht verstanden. In Meinem Beispiel will ich einfachen Integer aus "home/messwerte" abonieren und in CODESYS abspeichern. Aber ich erhalte nirgendwo einen Integer, der meinem MQTTExplorer Wert entspricht.

Wo finde ich finde ich ankommende Daten?

I have a Wago PFC100 and I have a mqtt server running in my local network without authentication.
I have tried the testMQTT(client:={mqttserver:1883} test function but the plc doesn't seem to connect to the mqtt server.
When I look at MQTTClient > MQTT_Control > sResultIp the value is empty.
When I look at #3 I think this value should be set. If this doesn't works it suggest a dns issue?

Hello Stefan,

I am raising this issue as im am trying to implement the library as a follow on from issue 33.
#33

I successfully connected a test project and get feedback from my devices.
see below image with realtime status of some my devices.

However using this same

project and adding an alarm manager and a trend manager I get the below compile errors.

I have tried everything I can to resolve (changing library version, changing codesys version etc) but nothing works. They seem to be storage related errors. I have attached the export of the working test project.

If you open it and add an alarm or trend manager and try and compile you will see the errors.

Can you let me know if you are too using an alarm manager or trend manager with any use case of your projects.

Perhaps this is a conflict not yet identified?.

TEST_MQTT.zip

Hi Stefan.

I've been very interested in implementing your library in my project using home assistant and a local broker on my network ( I wont be using an online broker).

I've had numerous library errors but I'm now down to 3 errors on your example project. On the Publish received method I am getting the following error pointer to string error.

I can't edit this method so i'm not sure what to do next?.

Do you have any ideas?.

Thanks again.

Hi Stefan,

first of all; very nice work, it's great to see an open source library with advanced functionality for Codesys mqtt!

I currently have a program where multiple FB's publish updates to a queue and I'm now looking in transmitting the updates to an mqtt broker one by one.

I've checked your docs on the FB's and the examples used, in your examples your using a timer to create a positive edge to trigger a send each two seconds yet the MQTTPublish FB had an output done to indicate when a successful transmit has occurred.

Now my question: is it sufficient to verify if done is high to start a new mqtt publish? What would be the best way to publish messages at a high rate at QOS2? (I read throughput of 120 messages/second here somewhere and was wondering how they are achieved )

Hello Stefan

I get the following error on a Rpi. How can this be resolved?

Thank you!

Hello:
First of all congratulations for the work
I have tested your library for mqtt and it works very well. I tried to mount some tests in cloudMQTT that requires username and password and I have not managed to publish or subscribe to any topic.
Could you tell me how to do it?

tried using all of the examples and tests, tried to execute every one of the "github" tests as well. Hundreds of errors all showing ambiguous use of "find" and ambiguous use of "TON"

I do MQTT and PLC communications for a living. And I have never been so frustrated and struggled so hard to publish some topics then trying to use Codesys and any one of 4 or 5 different libraries including the demo from 3S.

Please Mr Stefan, point me in the right direction. I am totally lost at using libraries on windows 10 or Windows 7 64 bit with Codesys 3.5.15

Hey

I'm getting an exception when running the lib in the raspberry, it works fine for the PC.

Any idea?

Hello Stefan,

Downloading the following missing Libraries doesn't work:
Library: OSCAT NETWORK, 1.30 (OSCAT)
Status: Download fehlgeschlagen
URL: https://store.codesys.com/CODESYSLibs/OSCAT/OSCATNETWORK/1.30

Library: Common Helper for developement, 1.0.0.0 (Stefan Dreyer)
Status: Download fehlgeschlagen
URL: https://store.codesys.com/CODESYSLibs/Stefan Dreyer/CommonHelperfordevelopment/1.0.0.0

Only Version 1.2.1.1 of the OSCAT NETWORK Library is available in the CODESYS Store.
Can you provide us the missing packages/libs?

Thank you for developing this MQTT Lib.
Kurt

I'm looking at the GreatExampleOfAdvantages project
In the MQTT_STUFF (FB) is this piece of code.

Client(
MQTT_IN_OUT:= GVL_MQTT.MQTT_IN_OUT,
ENABLE:= TRUE,
URL:= 'test.mosquitto.org:1883',
TIMEOUT:= T#10S);

When I build the project I get the following error.
C0039: VAR_IN_OUT 'MQTT_INFO' must be assigned in call of 'HANDLE_MQTT'
I think the MQTT_INFO must be set in the function call?

Hallo,

we use your MQTT Library successfully with Raspberry PI and we are satisfied with it. But the same source code creates reference errors when the plc goes to run.

wir nutzen die MQTT-Bibliothek sehr erfolgreich und mit Begeisterung mit dem Raspberry PI. Nun müssen wir aber diese auch auf unserer hausinternen Steuerung von Eckelmann zum laufen bekommen, bekommen aber sobald die Steuerung in den Run geht, Ausnahmefehler bezüglich unaufgelöster Referenzen. Mit Eckelmann konnten wir schon diverse Sachen eingrenzen, was Richtung openSSL betrifft. Jedoch gibt es immernoch diverse Probleme. Ist es möglich sie diesbezüglich offiziell zu kontaktieren, zum Beispiel über XING???

Ein Support wäre echt cool und ich würde es mir für diese tolle Lib echt wünschen, dass sie weiter getragen wird. Wir sehen in dieser großes Potential.

Mit freundlichen Grüßen

M.Eng. Sven Jödicke
Maschinenautomation
Systemarchitekt

Fichtenweg 36, 99098 Erfurt
Telefon +49 36203 9591-260
Fax +49 36203 9591-10
[email protected]
www.rex-at.de

Hallo Herr Dreyer,

Ich habe folgendes Problem. Ich habe in einem Objekt einen Request-Kanal (MQTTPublish) und einen Response-Kanal (MQTTSubcribe) aufgesetzt. Sobald ich einen Request absetze, bekomme ich von der Gegenstelle einen Response. Dieses Prinzip funktioniert soweit ganz gut. Aber leider nur 3 mal. Ab den 4. mal liefert die FUNCTION GetRemainingLength bei RemainingLength eine 0 zurück, obwohl ein valider Payload im Buffer ist. Was mir aber aufgefallen ist, dass lediglich der Header des Buffers leicht differiert, was zu dieser zurückgegebenen 0 führt. Ich habe leider keine Ahnung, was diese Werte in diesem Header bedeuten. Siehe folgenden Abbildungen.

Gutfall:

Schlechtfall:

In beiden Fällen ist zu erkennen, dass der Payload ein und der selbe ist.

Im Schlechtfall sieht man, dass die BufferSize statt 258, dann 259 ist, dass das zweite und das dritte Byte im Buffer [128, 2] ist, anstatt [255,1].

Leider weiß ich noch nicht, was diese Header-Werte im einzelnen bedeuten. Es wäre schön, wenn sie Herr Dreyer da Licht ins Dunkel bringen könnten.

MFG Sven Jödicke

Hello:
Incredible work in the library, its functionality in the number of shipments is simply perfect.
Now I find a problem I have very large messages and I was wondering if it was possible to easily read messages of more than 255 characters.

And this would be awesome for the library!

Lots of missing libraries using the 3.5.11.zip file :(

Hallo Stefan,

ich habe mal deinen MQTT Baustein geladen und den Beispielprogramm ausprobiert. Leider funktioniert nur die TLS Variante.
Die ohneTLS Variante verbindet sich weder auf test.mosquitto.org noch meinen lokalen MQTT server.
Muss ich bestimmte Versionen von den LIB's laden oder funktioniert es auch mit den neusten?
Aktuell verwende ich Codesys 3.5 SP13 Patch2.

Gruss Markus

Hi,

I downloaded version 3.5.15 and upgraded it to 3.5.16 and used the project: Interation HowTo.project.
I use the free hivemq open broker for testing purpose (https://www.hivemq.com/public-mqtt-broker/).

First problem:
I tried to connect to "broker.hivemq.com", where TLS is false. This works the 'connected' value becomes true.

Thereafter set the TLS to true and got instant pointer error (in IP_CONTROL [From Common Helper for development]):

To solve this problem I added the pointer to tls_config, which was previously pointing to 0.
Although the exception is gone, the connection is still being refused.

I added the error history. Hope you know what is going wrong, and which values I have to use for tlsMethod, chiperList and verifymode.

Hi Stefan
Thank you very much for your works!!!
I´m new with MQTT so sorry if is a dumb question.
I´m able to connect to the broker (mosquitto), I have the simulation
mosquitto_pub -h 127.0.0.1 -t mytopic -m MessagetoCodesys
From Codesys I can subscribe to a Topic mytopic.
But, I don´t see the publish message, what is the right function to read the message
I have tried to adapt the demo project, but unable to read the publish message where I´m subscrite, from codesys only want to read messages, not public messages.

Thank you very much for your time
Best Regards

Hi Stefan ,
I have a little problem with the payload size for the SD_MQTT.CallbackCollector , thru receiver : SD_MQTT.ReciveString; , also with SD_MQTT.ListStringCallback; I get only 80 Characters even thou the payload strings are SET for 255 characters .
NOW with SD_MQTT.SingelStringCallback; I get up to 2000 characters on the payload string , as that is the max config for the handier.

Can you advice on the problem ?

Hi Stefan,

Thanks again for the static ip fix.
I've been building on your library for a few days now and I've noticed that if many messages are sent in rapid succession, not all are treated by the library. (I suspect that the payload is overwritten by the value of the next message before the process has time to finish processing the original payload)

I have placed a rate limiter in my node-red flow to slow down the rate of messages posted to the mqtt broker, but it would be great if this was directly handled by the subscribing client. (1 msg per 0.05 seconds is the limit for my PLC to handle, but for 32 outputs to switch individually this takes 1.6 seconds...)

It is probably nit-picking, but I like to stress-test my implementation to know it can handle it when push comes to shove. :)

Thanks,
Yorick

Hallo Herr Dreyer,

wir haben das Problem, dass nach einem gewissen Datentransfer scheinbar der Socket wegfliegt. Die MQTT-Library meldet den Fehler "HARD_DISCONNECT" und vom MQTT-Broker (mosquitto) wird der Fehler geloggt, dass der Socket einen Fehler hatte. Kennen sie dieses Fehlerbild ???

we have a problem, that the socket has an error while running. The MQTT-Library report the error message "HARD_DISCONNECT" and the broker (mosquitto) logs the message "socket error". Do you know anything about this error?

MFG / with kind regards
S Jödicke

This happpends:

Im working on it...

BR Stefan

I want to write my switching logic in an external system (OpenHab)
Because of that I would like to have a switchbase fb that just publishes to mqtt and maybe a variable for testing and fallback scenarios. But without the statemanagement.
Bonus points for also having different messages for a short and a long press or or adding pressdown time.

And a lampbase that listens to mqtt and maybe a variable for testing and fallback scenarios.
This should probably have statemanagement.

Can I just copy the lampbase and take out the statemanagement and recieving logic?

Hi stefan

I'm new to PLc programing, I installed the latest version of your MQTT library, but I have an issue with BASIC library ( PS : I installed ther Basic library in ur repos)

Thnaks in advance.

When I open the one of the projects the error log reports the following missing libraries:

• IoStandard
• CmpLog
• CAA Types
• Component Manager
• CmpApp
• SysCpuHandeling
• CmpEventMgr
• CAA Behavior Model
• CAA FB Factory
• SysSocket
• CAA DTUtility
• CAA Tick
• CAA TickUtil
• CAA RTCLK
• CmpCrypto
• SysTime
• SysTimeCore
• SysFile
• Cmp
• CmpChannelClientIec
• CmpBinTagUtilIec
• SysMem
• CAA MemblockMan
• CAA Callback
• CAA Async Manager
• CAA ResMan
• CAA Storage
• SysTimeRtc
• CmpSchedule

Is this normal? Which libraries should I install?
I have installed the following libraries:

• Basic
• Building
• CommonTypesAndFunctions
• MQTT
• OSCAT NETWORK

Hello,

I want to add your MQTT library to SoMachine 4.3 but thows dependencies errors (missing libraries):

As I have Codesys development too, I've tried to add the libraries from Codesys but I suspect that SoMachine uses an older version of Codesys.
Do you have experience with SoMachine? Will try to make it work, but I have little experience dealing with libraries...

Hi,

In an attempt to avoid paying 300 euro to Wago, I'm trying to implement your MQTT library on my PFC200.
I copied the code from your example into the codesys project and have all dependent libraries installed.

However when I run the code it is not connecting to the mosquitto ip. Is this code dependant on a Pi specific implementation?