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.98.100.19 with SMTP id y19mr6389142pfb.6.1460759983874; Fri, 15 Apr 2016 15:39:43 -0700 (PDT) X-Received: by 10.182.49.197 with SMTP id w5mr265017obn.16.1460759983719; Fri, 15 Apr 2016 15:39:43 -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!g8no1900624igr.0!news-out.google.com!u9ni166igk.0!nntp.google.com!g8no1900615igr.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 15 Apr 2016 15:39:43 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=80.119.168.149; posting-account=O3LyFwoAAACc1uh60ZcOUmAGdDmGsEcV NNTP-Posting-Host: 80.119.168.149 References: <6d3b7ac5-8fc6-406c-8aac-947d25a78249@googlegroups.com> <7474e1d5-6b54-4c81-8cf0-372d478ed041@googlegroups.com> <2fee69ac-ae44-47b6-8ed3-4cf15368622a@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <345ec086-6c03-4212-ab06-7dc0ab18fe2a@googlegroups.com> Subject: Re: Simple Components 4.12 with MQTT implementation released From: slos Injection-Date: Fri, 15 Apr 2016 22:39:43 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:30146 Date: 2016-04-15T15:39:43-07:00 List-Id: Le vendredi 15 avril 2016 18:39:42 UTC+2, Dmitry A. Kazakov a =E9crit=A0: > On 2016-04-15 18:00, slos wrote: > > Le vendredi 15 avril 2016 17:34:36 UTC+2, Dmitry A. Kazakov a =E9crit : >=20 > >> You can sit and wait for something reasonable to come, or you can star= t > >> using things you consider right. I prefer the latter. > > And reinvent the wheel ? > > > > If you want drives, encoders, IO modules, etc... you have them all > > using those standard field buses. Would you create your own ? >=20 > No, I would dock them to the middleware using whatever protocol they=20 > run. That is one of the key advantages of a proper middleware over OPC,= =20 > i.e. an abstraction of the hardware. You seem to consider me as a supporter of the OPC or MQTT technologies. I won't discuss their merits since I am just a user of those. Those are technologies already available and supported by major organizatio= ns. And at some point you need to use them/ >=20 > With OPC/MQTT approach you must wait until the vendor of the encoder=20 > will write an OPC/MQTT server for you. He might do it or decide in favor= =20 > of something else ModBus, ProfiNET, CAN etc. Vendors have limited=20 > resources and even more limited software development competence to=20 > expect them to offer the exactly "standard" you consider standard. Oh Lord, please don't let me be misunderstood... Dmitry, I like you for providing interesting Ada components and sometimes h= elp and good advice. But we end up discussing the up and downs of the protocols versus your midd= leware and this seems to lead nowhere. "Ada for Automation" targets manufacturing control applications, no rockets= or weapons. There the protocols we have discussed are established since ye= ars and there is a huge ecosystem that allow one to pick the components of = his choice and build the solution he can, although being a not so competent= engineer. >=20 > --=20 > Regards, > Dmitry A. Kazakov > http://www.dmitry-kazakov.de Have a nice week end. BR, St=E9phane