|
Re: MQTT - NO Socket issue [message #1834165 is a reply to message #1834163] |
Wed, 04 November 2020 09:05 |
|
I'm not as fit in MQTT as I would like to be. But one thing that I noticed is that you connected your SD_1 and RD_1 to WSTRING pins. However the raw layer expects pins of type STRING.
NO_SOCKET means that you tried to send something but the FB could not be initialized. So most probably the init failed. For such test I typically do not connect INITO so that I can manually trigger the different events and see the results.
|
|
|
|
|
Re: MQTT - NO Socket issue [message #1834195 is a reply to message #1834194] |
Wed, 04 November 2020 17:25 |
|
I think it would definitely good if you familiarize yourself with MQTT. MQTT is a broker based system where your publish and subdscribes go to a dedicated broker. 4diac FORTE has currently the limitation that within one 4diac FORTE instance you can connect only to one broker. So in your use case you would have somewhere a broker and you specify the broker's address in all of your publish and subscribes.
Regarding your problem: I don't see your full subscribe and publish ID values, but from the description you gave in your first post I think you have to learn about the concept of MQTT topics. An MQTT topic is an identifer you can publish or subscribe to. If you have a publisher and a subscriber which you would like that they are communicating with each other about the same topic you have to specifiy the same topic in both. If I see your code above correctly you have a differetn topic for your subscribe. As noboday is publishing to this topic you are also not receiving anything.
I hope this helps.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03963 seconds