1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 <2024> | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 <2024> |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: OPC UA build problem |
From: | "Knap, Giles \(DLSLtd,RAL,LSCI\) via Tech-talk" <tech-talk at aps.anl.gov> |
To: | EPICS Tech Talk <tech-talk at aps.anl.gov>, Ralph Lange <ralph.lange at gmx.de> |
Date: | Fri, 26 Jan 2024 16:59:47 +0000 |
Hello Vivien, Ralph,
I have successfully built the opcua support module with the
open62541 client
library and made an IOC instance that connects to an Omron PLC.
I'm sharing the container I used to do this so you can see the build options and also
immediately experiment with pre-built code. This is a Generic IOC as discussed in another thread but it has an example instance embedded in it. To use:
To read more about the epics-containers framework that built this and perhaps to make some IOC instances that use it see:
Regards,
giles
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>
Sent: 11 January 2024 08:04 To: EPICS Tech Talk <tech-talk at aps.anl.gov> Subject: Re: OPC UA build problem Dear Vivien,
On Wed, 10 Jan 2024 at 16:02, LORIOT Vivien via Tech-talk <tech-talk at aps.anl.gov> wrote:
In the OPC UA Device Support module, CONFIG_SITE defines '-DUSE_TYPED_RSET' for C++ compilation. [1]
That definition is missing on the compile line you are showing above - it probably slipped your migration to the Nix build system.
In case you are supporting Secure OPC UA: Other users are having issues with recent Linuxes (new API of openssl) and the Open62541 release 1.3, which show as crashes when the IOC starts. If you get it working, I'd be interested to know the details of your
setup.
Cheers,
~Ralph
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |