disculpen estoy tratando de enviar datos a la nube azure desde un logo 8.4 pero no me deja seguir con la configuración al parecer me parece que ese campo no debe estar vacío pero tampoco me deja ingresarlo que puede ser ?
@blociot2 ай бұрын
@@anthonymunoz437 sorry I don't understand Spanish, but with the help of translator app, I believe you have issue with connecting Azure IoT? If yes, feel free to send me a message in Linkedin with details so I might be able to help.
@anthonymunoz4372 ай бұрын
I already sent you the message please
@mohamedhamadene95796 ай бұрын
short and great explanation,... Bravo!
@blociot6 ай бұрын
Thank you for watching Mohamed 🙏
@nikolaossarakinos873915 күн бұрын
Is it possible to upload a program from Logo Web Editor to Azure?
@Best_Chuansatien7 ай бұрын
So basically. Logo became an actual PLC what a nice value
@blociot7 ай бұрын
Exactly! LOGO is now a fully functional PLC for small automation tasks.
@Artur19597 ай бұрын
You are only half way publishing data to a broker. Now we need a video of how to subscribe another LOGO 8.4 to the broker, so we can entangle two LOGOS at a distance.
@blociot7 ай бұрын
Hi Artur. I replied to your comment on the other video as well. I have not tested two LOGOs communication over MQTT but you don't need to handle any JSON. You just need to define the same topics name in both LOGOs and map a certain memory area within the pub/sub. I'll create another video for it.
@Artur19597 ай бұрын
@@blociot Thank you!!!!
@blociot7 ай бұрын
@@Artur1959 I did some test on this. It seems you cannot directly bind LOGO1 Pub topic to LOGO2 Sub topic. Because the published payload by LOGO looks like this : { "state": { "reported": { "VM4": { "desc": "V-word-4-1", "value": [ 13 ] } } } } So there is a "reported" key in the JSON payload. The LOGO expects a payload like below when subscribing to a topic: { "state": { "VM4": { "desc": "V-word-4-1", "value": [ 16 ] } } } Notice there shouldn't be any "reported" key. So if you need to send data from one LOGO to another over MQTT, you need to remove the "reported" key in the JSON before binding it to the subscribe topic. This should be done on your MQTT broker or in a a separate client on the backend. Overall, I would use LOGO MQTT to either publish some values to a broker or to subscribe some values. For connecting two LOGOs, it's more convenient to directly use the TCP or through MQTT if you can do the data manipulation. Hope this helps to answer your question.
@Artur19597 ай бұрын
Since I have two LOGO 8.4 devices in my hands, I will test the instructions you sent me on the subscriber side. By the way, I'm using HIVE MQ, which is the one depicted in the LOGO documentation. I'm stuck just where I was when I tried to link two 8.3 LOGOS over AWS. I'm pretty seasoned with LOGOS, but MQTT is new to me. You are really helping us out!! @@blociot
@dtib15395 ай бұрын
I wish logo in new version could also manage float values😒
@blociot5 ай бұрын
Good point. There are some workarounds for some floating point applications. Have you seen the I/F and F/I functions? support.industry.siemens.com/cs/mdm/100782807?c=120748741643&dl=no&lc=fr-WW Out of curiosity, hat are you trying to do?
@guilhermesouza43734 ай бұрын
Finder OPTA is better
@blociot4 ай бұрын
Never used it. But curious what do you like about it? Seems over priced and the ladder IDE is too basic.