The AWS function is an absolute nightmare.  I had a customer who always sticks LOGOs to control pumps and valves on CHP schemes.  It was all stand alone and working and then they asked for remote visibility.  We suggested 2 options, 1 was a Ewon and they would log in using this and access the embedded weberver, the other option was using the cloud function.

Like most I had played with the cloud function and was impressed with the speed and the fact one screen could collect data from multiple LOGOs, similar to a KTP HMI project.

We deployed the AWS LOGO Cloud solution, spent ages trying to figure out what instance we needed from AWS, still have no idea if we have the right one. 

And then came the bills, we now pay ~£40 a month for 2 x LOGOs reading about 50 points.  Note I have probably set this to update on change so it is sending a lot of messages, but I thought this was the idea with IoT.

Anyhow the customer just pays the bill, but I'm far from impressed, we also have varied bills each month based on how much the website has been looked at, which is difficult to manage.

If we did this again, I would select 'update on change' and have a go live button (would instigate a 5-minute go live timer) on the webpage, that would activate a set of mathematically instructions, or some function block that can be turned off.  This way messages are only sent when required reducing IoT and instance costs.

Siemens need to give tools to understand the number of messages and the likely costs.  They also need to allow other brokers, not just AWS.  AWS could have helped by packaging something bespoke for LOGO without the need to spend hours understanding Elastic Beanstalk, instances, EC2, and perhaps offer a cheaper package or a device based package.  Obviously AWS make it as difficult as possible to understand what is going on to charge you more.

To summarise, it was exciting, but the costs, complexity of AWS and getting LOGO on the cloud (I remember there was some bug that meant if you followed the manual it would not work) mean it is far from practical.  

Keep hoping that Siemens will release an update that makes the LOGO better, some basic ideas:

LOGO capable of 64 bit numbers via Modbus and pulses.  Also able to deal with 32-bit registers and 64bit long similar to S7-1200.

Modbus data polling to have an enable input so that polling can be stopped or time delayed in the logic.

Min/Max function so that the highest or lowest input wins without having to do this with multiple threshold block.  I do some work with Comap's PLC and it is a nice function.

LOGO natively supports email notifications without having to get a CM module.

LOGO can talk direct with TIA Portal for KTP HMI creation similar to a S7-1200 project so that dragging tags from the PLC to the HMI are automatic and not time consuming.

Better cloud function, more brokers other than AWS and able to use own brokers.

Expand the current accessory offering to bring a power meter module and more temperature monitoring i.e. thermocouples and NTC thermistors.

Add a wire so that one LOGO can branch two lines of DIN rail, LOGOs can get long and if retrofitting in an existing panel, space can become difficult and a wire to allow a module to be elsewhere would be easier.

Just my thoughts.

------------------------------------------------------------------------------------------
Split from LOGO! 25 year competition extension.