From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.157.3.149 with SMTP id f21mr2332852otf.18.1460733449264; Fri, 15 Apr 2016 08:17:29 -0700 (PDT) X-Received: by 10.182.144.226 with SMTP id sp2mr237825obb.13.1460733449227; Fri, 15 Apr 2016 08:17:29 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!g8no1632975igr.0!news-out.google.com!j7ni403igm.0!nntp.google.com!g8no1632968igr.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 15 Apr 2016 08:17:28 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=193.251.73.50; posting-account=O3LyFwoAAACc1uh60ZcOUmAGdDmGsEcV NNTP-Posting-Host: 193.251.73.50 References: <6d3b7ac5-8fc6-406c-8aac-947d25a78249@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <7474e1d5-6b54-4c81-8cf0-372d478ed041@googlegroups.com> Subject: Re: Simple Components 4.12 with MQTT implementation released From: slos Injection-Date: Fri, 15 Apr 2016 15:17:29 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:30127 Date: 2016-04-15T08:17:28-07:00 List-Id: Le vendredi 15 avril 2016 17:05:56 UTC+2, Dmitry A. Kazakov a =E9crit=A0: > On 2016-04-15 12:06, slos wrote: >=20 > > We share some of the vision. > > "Ada for Automation" is a framework with which one can build his own > > control application using Ada. I would not call it a middleware. >=20 > Why not? >=20 > > And MQTT or OPC UA would just connect it to some SCADA or cloud based > > application like one using IBM BlueMix. >=20 > Neither is good for SCADA, especially regarding safety requirements and= =20 > performance. >=20 > >> Note that without OPC UA everything could work far better and require > >> far less resources. E.g. having all process data the OPC cannot access > >> because it is too slow to pace with the middleware capable to deliver > >> data at less than 1ms rate and does not properly support > >> push-subscriptions, does not support distributed time stamping, physic= al > >> units, error states etc. > >> > > I agree that OPC UA does not fit where EtherCAT, Sercos III or PROFINET= IRT would. > > OPC was created for office and SCADA / GUI applications access to > > PLC data, not for IO processing. >=20 > Why SCADA or DB server should ever use some other middleware protocols?= =20 > The point is that one middleware can stretch from the ERP levels down to= =20 > the field. But when the middleware is OPC or MQTT you cannot not put it= =20 > into a device and expect that working. This is the reason we must live=20 > with EtherCAT, ProfiNET down there, which are nightmare to any system=20 > integrator. That defeats the very idea of a middleware. >=20 > The real advantage of Ada is that it is scalable from heavy duty to hard= =20 > real-time embedded. The ugly protocols like XML, HTTP, OPC etc only=20 > hinder developing of safe and efficient systems. >=20 > --=20 > Regards, > Dmitry A. Kazakov > http://www.dmitry-kazakov.de Standards are created for interoperability. If you don't need interoperability, you don't need standards. Hence you need standards since you leave in an interconnected world now. BR, St=E9phane