Hello, I am having a minor issue in plc to Aws communication, basically I want to publish real time data from sensor to aws iot core, I had already configured the lmqtt library and client also uploaded the certificates and followed steps as mention in respective document from siemens, my device is s7-1200 1215c. Please assist me regarding this issue thank you
Hello sir, I have a question about what to do if you expect a json to come in. Is it possible to receive it in this function block? I know that siemens also has block to deserialize a list of bytes that is in the json structure. Our client wants to use this form of communication in there system. Regards, Briyan
Hello. Not sure if you are still active. I am trying to achieve the same thing but my aws mqtt topic start with $aws and LMQTT can't send to the correct topic. Everytime I key in $aws in the topic field, it changed to $Lws . Help pls
When I toggle connect bit.... The status bit shows code 16#7002 I am stuck at this.....enable to publish msg....what could be the possible cause and solution of this.....
16#8620 error seems to be "Encoding of the received message could not be detected or is not supported". Are you sending your message through as hex? Or something like an ASCII JSON? Full error list can be found here in the "Libraries for Communication for SIMATIC Controllers" PDF download: support.industry.siemens.com/cs/document/109780503/libraries-for-communication-for-simatic-controllers?dti=0&lc=en-US Hope this helps!
Hmmm, my first port of call for a connection issue would be to re-issue the certificates and make sure they're configured properly in the PLC. 9 times out of 10, when I've had an initial connection issue its because I've made a mistake with the certificates.
Hello, I am having a minor issue in plc to Aws communication, basically I want to publish real time data from sensor to aws iot core, I had already configured the lmqtt library and client also uploaded the certificates and followed steps as mention in respective document from siemens, my device is s7-1200 1215c. Please assist me regarding this issue
thank you
Hello sir,
I have a question about what to do if you expect a json to come in. Is it possible to receive it in this function block? I know that siemens also has block to deserialize a list of bytes that is in the json structure. Our client wants to use this form of communication in there system.
Regards,
Briyan
Hello, im not sure if this is still working after the update of aws. Seem to only be able to get 80e1
do you connect an actual plc while doing this? my tia portal is asking me to
Hello. Not sure if you are still active. I am trying to achieve the same thing but my aws mqtt topic start with $aws and LMQTT can't send to the correct topic. Everytime I key in $aws in the topic field, it changed to $Lws . Help pls
Did you get any solution actually iam also facing the same problem pls help
Hi I got error 16#8730 and subfunction diagnostic says 5. Where could be a problem?
When I toggle connect bit.... The status bit shows code 16#7002 I am stuck at this.....enable to publish msg....what could be the possible cause and solution of this.....
Do you have any one for siemens and a thingsboard instance?
This is only monitoring right? How can we publish data?
Thanks for this video. Really appreciate you work
My pleasure! Glad you enjoyed!!
Thanks for the video! I tried to configure here but I was unsuccessful. I receive 16#8620 error.
16#8620 error seems to be "Encoding of the received message could not be detected or is not supported". Are you sending your message through as hex? Or something like an ASCII JSON?
Full error list can be found here in the "Libraries for Communication for SIMATIC Controllers" PDF download:
support.industry.siemens.com/cs/document/109780503/libraries-for-communication-for-simatic-controllers?dti=0&lc=en-US
Hope this helps!
@@Intrigued_Engineer the error occurs while trying to connect to AWS. Do you have any idea how to solve?
Hmmm, my first port of call for a connection issue would be to re-issue the certificates and make sure they're configured properly in the PLC. 9 times out of 10, when I've had an initial connection issue its because I've made a mistake with the certificates.
I think the problem is in the "use router" part, how to know the PLC is connected to the network
ntp server ?!