public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: jan.kiszka@siemens.com (Jan Kiszka)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Open Source OPC UA
Date: Wed, 30 Nov 2016 12:07:52 +0100	[thread overview]
Message-ID: <e309a68a-d22f-ba8c-e930-d1fc604486eb@siemens.com> (raw)
In-Reply-To: <95c6526d-aba5-b321-d086-34e958083e89@linux-kernel.net>

On 2016-11-30 11:41, Wolfgang Mauerer wrote:
> Am 29/11/2016 um 20:36 schrieb Jan Kiszka:
> 
>> does anyone already have some experience with OSS OPC UA
>> implementations, specifically for resource constrained devices? We
>> stumbled over
>>
>> http://open62541.org
>>
>> which seems like being on the right path. There are more
>>
>> https://github.com/open62541/open62541/wiki/List-of-Open-Source-OPC-UA-Implementations
>>
>> but not all look that attractive for embedded devices, due to language,
>> license or main drivers.
> 
> there's another tiny implementation from some of the Ostwestfalen-Lippe
> (OWL) group of people in Germany, but since it targets devices with
> only 10s of KiB of RAM and ROM, I don't think it's suitable for our
> purposes.

If you have a link (and the project has a proper license), maybe send a
PR to the open62541.org to extend their list.

> 
> As for language and main drivers: Do we have an agreement or an idea
> in the group what suitable languages are, and what characteristics main
> drivers should have? Considering the size of systems we're targeting, I
> personally would not see C (and possibly C++) as the only admissible
> language.

If we only had higher languages, that would be a major limitation. It's
not so much about their size, more about their amount of dependencies
and their suitability for embedded processors (just having "fun" with Go
on Intel Quark...).

But also having bindings for Java, C#, python, JavaScript, Go,
you-name-them, would be valuable. So I would recommend to start with a
common core - thus a native one - and add those bindings to them. Later
on, if there is added value, we could also consider alternative core
implementations.

Regards,
Jan

> 
> Best regards, Wolfgang
>>
>> I think, eventually, CIP should look into the topic free and
>> standard-conforming OPC UA as well because it is gaining a lot of
>> traction as THE protocol for data exchange in automation industry.
>>
>> Regards,
>> Jan
>> _______________________________________________
>> cip-dev mailing list
>> cip-dev at lists.cip-project.org
>> https://lists.cip-project.org/mailman/listinfo/cip-dev
>>

      reply	other threads:[~2016-11-30 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 19:36 [cip-dev] Open Source OPC UA Jan Kiszka
2016-11-30 10:41 ` Wolfgang Mauerer
2016-11-30 11:07   ` Jan Kiszka [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e309a68a-d22f-ba8c-e930-d1fc604486eb@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox