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: EPICS for CompactRio |
From: | "Paduan Donadio, Marcio" <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Thu, 7 Jun 2018 23:26:29 +0000 |
I would recommend you not to use NI shared variables architecture. I had a problem with arrays being read as a waveform record and discovered that NI implemented NORD and NELM concepts wrongly. In fact, one of this fields does not even exist.
I contacted the support and the answer was something like "we never mentioned 'IOC' or 'record' concepts in our material and, so, we do not expect that our solution will work exactly as an EPICS record". The solution they gave to me was to make clear that the documentation will mention that they do not provide IOCs or records.
Many of the fields you would expect in an EPICS record are not present.
I suggest that, if you can, use the other solutions mentioned previously in this email thread.
Best regards,
Márcio Paduan Donadio
Control Systems Engineer
SLAC National Accelerator Laboratory
Advanced Instrumentation for Research Division
2575 Sand Hill Rd
Menlo Park CA 94025
Office (650) 926-5007
De: [email protected] <[email protected]> em nome de LOTRUS Paul <[email protected]>
Enviado: quinta-feira, 7 de junho de 2018 08:52:28 Para: Diego Sanz Hernando; Hartman, Steven M.; Florian Feldbauer Cc: [email protected] Assunto: RE: EPICS for CompactRio You have a good presentation on NI website:
http://download.ni.com/pub/branches/uk/handson_followup/epics_ral.pdf
There is no alarm on RT target. Some EPICS alarm fields are there, and you can change them with a caput, but it is not enough to make it work. In addition, I have a LV EPICS solution that is working pretty well on cRIO-9074 (VxWorks) and not starting well on cRIO-9039 (Linux). Best, Paul -----Message d'origine----- De : [email protected] <[email protected]> De la part de Diego Sanz Hernando Envoyé : jeudi 7 juin 2018 16:02 À : Hartman, Steven M. <[email protected]>; Florian Feldbauer <[email protected]> Cc : [email protected] Objet : RE: EPICS for CompactRio As another testimony.... I confirm that the best way, in this case, is using an intermediate real IOC, to read from NI shared variables, and have the full EPICS features in the real IOC.... about the first initialization fails, I have had similar behavior. Regards Diego -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Hartman, Steven M. Sent: jueves, 7 de junio de 2018 15:50 To: Florian Feldbauer <[email protected]> Cc: [email protected] Subject: Re: EPICS for CompactRio > On Jun 7, 2018, at 5:18 AM, Florian Feldbauer <[email protected]> wrote: > > I have seen, that NI provides a so called EPICS Server I/O Servers plugin which, as far as I understood, can be used on the CompactRIO system to publish shared variables as PVs to EPICS CA Clients. > > I’d like to know if anyone has experience using the CompactRIO with EPICS? We are using it. It is functional but it is not a full feature CA server. We are treating it like remote I/O with CA as the field bus. We have other records on an actual IOC that take the cRIO PVs as inputs. Scaling, alarms, etc are all handled by the actual IOC and clients (display manager, alarms, archive) generally interact with the IOC PVs rather than the ones served by the cRIO. One peculiarity we have seen with the cRIO is that the first client that connects does not always get a valid response. > Does the plugin support fields like HIHI, HHSV, ADEL, MDEL? HIHI and HHSV: yes ADEL and MDEL: no -- Steven Hartman [email protected] P Please consider the environment before printing this e-mail. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________ |