|
Re: MQTT Clarification [message #1764106 is a reply to message #1764007] |
Wed, 24 May 2017 22:11 |
|
You are right you only need paho for the FORTEs which are using paho. However when compiling such a FORTE you need to enable the MQTT Paho module in FORTE. Which I assume you did.
however I think your ID is not perfectly right. In mqtt you have to specifiy which protocol to use as part of the broker's address. For using tcp it would be tcp://192.168.1.200:1883
|
|
|
|
|
|
|
|
|
Re: MQTT Clarification [message #1764273 is a reply to message #1764197] |
Sat, 27 May 2017 17:35 |
|
As pointed out by Jose. raw requires that the received or sent data is of type STRING. When you are not connected your input or output then it has type any. this is an error condition for the raw layer and you get the terminated when you invoke send or recieve. furthermore raw only allows one input or one output.
|
|
|
|
|
Re: MQTT Clarification [message #1766401 is a reply to message #1766399] |
Wed, 21 June 2017 06:51 |
|
The problem with MQTT is that it does not define a payload. Therefore in 4diac we decided, for giving you more flexibility, that on top of the mqtt layer you need a second layer which will take inputs of a publish FB and generate an according payload for MQTT or take the MQTT message and parse it on the outputs. If you both sides (i.e., PUBLISH and SUBSCRIBE) are in 4diac than you can exchange the raw with fbdk and connect any data type. Here you can even have more then one in or output. fbdk will encode the data in an asn1 data format as defined in the "IEC 61499 compliance profile for feasibility demonstrations", which is a very efficient encoding format.
If you have other encodings you may want to write your own layer. Please have a look in the FORTE development documentation to get more information on that.
|
|
|
Powered by
FUDForum. Page generated in 0.06609 seconds