27- Siemens LOGO! V8.4 Now Supports Azure, Alibaba and AWS Clouds and Any MQTT Broker!!
Вставка
- Опубліковано 2 січ 2024
- Siemens released the new version of LOGO! Soft Comfort V8.4, which is packed with several new features! In this new video, we will show you:
Where to download the new V8.4 upgrade
How to install it
A first look at and finding possible changes in the UI
Overview of the LOGO help system and available documentation
Overview of the new features in 8.4:
Connecting to any MQTT broker such as Mosquitto or HiveMQ
Support for Azure and Alibaba clouds (only AWS was supported in the previous version)
Batch Download to several LOGO devices in one click
Sending custom emails to configured recipients with a trigger
Addition of two new memory areas (VX and VR) besides the existing V memory area
There are other improvements and additions to LOGO V8.4, such as Data log download in RUN mode and new tools like LOGO Web Editor V1.2, Access Tool, and Integrity test. However, for us, the support of local/remote MQTT brokers was the main source of excitement!
Please let us know what you think about this upgrade. - Наука та технологія
short and great explanation,... Bravo!
Thank you for watching Mohamed 🙏
So basically. Logo became an actual PLC
what a nice value
Exactly! LOGO is now a fully functional PLC for small automation tasks.
I wish logo in new version could also manage float values😒
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?
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.
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.
@@blociot Thank you!!!!
@@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.
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
Finder OPTA is better
Never used it. But curious what do you like about it? Seems over priced and the ladder IDE is too basic.