EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  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  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re:problems solved about EPICS V4 4.5.0 compiling
From: "Qiao Yusi" <[email protected]>
To: [email protected]
Date: Thu, 14 Jan 2016 11:25:47 +0800 (GMT+08:00)
Hi,everyone:

Sorry to reply the mail so late. After updating the gcc to version 4.8.0,the compiling is ok now. Thanks for your advicce!


> -----原始邮件-----
> 发件人: [email protected]
> 发送时间: 2016年1月12日 星期二
> 收件人: [email protected]
> 抄送: 
> 主题: Tech-talk Digest, Vol 10, Issue 14
> 
> Send Tech-talk mailing list submissions to
> 	[email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://mailman.aps.anl.gov/mailman/listinfo/tech-talk
> or, via email, send a message with subject or body 'help' to
> 	[email protected]
> 
> You can reach the person managing the list at
> 	[email protected]
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tech-talk digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: problems about EPICS V4 4.5.0 compiling (Shen, Guobao)
>    2. Re: MTCA4 HW management (Konrad, Martin)
>    3. Re: MTCA4 HW management (Sonya Hoobler)
>    4. RE: MTCA4 HW management (Hill, Jeff)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 11 Jan 2016 10:02:04 -0500
> From: "Shen, Guobao" <[email protected]>
> To: <[email protected]>
> Subject: Re: problems about EPICS V4 4.5.0 compiling
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="gbk"; format=flowed
> 
> Michael is always one step faster than me.
> 
> I guess you are using Linux, but it will help to give more details about which exact distro/version (Debian, RHEL, CentOS...) you are using.
> If possible, update gcc to 4.x would solve your problem.
> 
> Guobao
> 
> On 1/11/16 9:53 AM, Michael Davidsaver wrote:
> >> My EPICS Base version is 3.14.12.1, my gcc version is 3.4.6.
> > Can you provide some more details about your environment (eg. OS version)?  Also, when reporting compilation errors please always include the arguments passed to the compiler in addition to the error message.
> >
> >> I don't know how to solve it, should I update my EPICS Base or gcc? Or make some other configurations? Hope someone can help me! Thanks!
> > I don't think you need to change your Base version, but an update to 3.14.12.5 should only help your situation.
> >
> > gcc 3.4.6 is 2 months away from being 10 years old.  I would suggest that an upgrade is in order.  This is probably the source of the error.
> >
> >
> > On 01/10/2016 10:14 PM, Qiao Yusi wrote:
> >> Hi, everyone:
> >>
> >> I?m having some problems with EPICS V4 (C++? 4.5.0). When building the EPICS V4 core C++ implementation, I issued make from the top level directory of pvDataCPP, and errors occurred like this:
> >>
> >>                   from ../../src/misc/bitSet.cpp:16:
> >>
> >> /home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvCommonCPP/include/boost/smart_ptr/shared_ptr.hpp:491: error: expected `)' before '<' token
> >>
> >> /home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvCommonCPP/include/boost/smart_ptr/shared_ptr.hpp:556: error: `unique_ptr' is not a member of `std'
> >>
> >> /home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvCommonCPP/include/boost/smart_ptr/shared_ptr.hpp:556: error: expected primary-expression before ',' token
> >>
> >> /home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvCommonCPP/include/boost/smart_ptr/shared_ptr.hpp:556: error: expected primary-expression before '>' token
> >>
> >> /home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvCommonCPP/include/boost/smart_ptr/shared_ptr.hpp:556: error: label `r' referenced outside of any function
> >>
> >> /home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvCommonCPP/include/boost/smart_ptr/shared_ptr.hpp:557: error: declaration of `operator=' as non-function
> >>
> >> /home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvCommonCPP/include/boost/smart_ptr/shared_ptr.hpp:557: confused by earlier errors, bailing out
> >>
> >> make[3]: *** [bitSet.o] Error 1
> >>
> >> make[3]: Leaving directory `/home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvDataCPP/src/O.linux-x86'
> >>
> >> make[2]: *** [install.linux-x86] Error 2
> >>
> >> make[2]: Leaving directory `/home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvDataCPP/src'
> >>
> >> make[1]: *** [src.install] Error 2
> >>
> >> make[1]: Leaving directory `/home/qys/CPP_EPICS_V4/EPICS-CPP-4.5.0/pvDataCPP'
> >>
> >>   
> >>
> >> My EPICS Base version is 3.14.12.1, my gcc version is 3.4.6.
> >>
> >> I don't know how to solve it, should I update my EPICS Base or gcc? Or make some other configurations? Hope someone can help me! Thanks!
> >>
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 11 Jan 2016 15:10:00 +0000
> From: "Konrad, Martin" <[email protected]>
> To: "[email protected]" <[email protected]>
> Subject: Re: MTCA4 HW management
> Message-ID:
> 	<[email protected]>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi Han,
> >> I've heard that SLAC and DESY heavily (?) use that platform so
> >> far, but there are no EPICS related activities I can find in
> >> teck-talks and others.
> DESY is using MTCA heavily for Flash and XFEL (hundreds of chassis).
> They do not use EPICS, though. Unfortunately MTCA.4 has not seen too 
> much use in the US (where most of the EPICS facilities are) so far. I 
> believe this might be caused by the way US labs are funded (first 
> priority for us is to build our machine - maintenance cost is not taken 
> into account in the same way it is in other countries).
> 
> > SLAC is not using any uTCA. That decision was changed. The engineers
> > found that it had several disadvantages: little real estate for
> > analog boards
> That's true. And to my understanding that is the main reason why they
> dropped MTCA.4. Note however that there is one important thing that in
> my mind distinguishes successful and less successful MTCA users:
> Successful labs put one functionality on each card. A LLRF system for 
> example consists of multiple cards like an FPGA card with an RTM for RF 
> in/out, a separate stepper-motor card for the tuner,... They do NOT try 
> to combine the whole LLRF system into one card. If you do you loose the 
> modularity of the standard and you can easily run out of real estate. 
> Don't look at FRIB's hardware for good examples - most of our 
> architecture designs date back to the pre-MTCA days at FRIB...
> 
> > the standard was not so standard
> There have been severe problems with hardware not complying to the 
> pretty extensive standards documentation in the past. This led to tons 
> of compatibility problems. But as of today most hardware works pretty 
> well :-)
> 
> > and the boards were expensive.
> Bob is right: The price tag of an empty chassis + power module + 
> management controller are quite high. On the other hand their
> extensive management features can help to reduce maintenance cost in the 
> long run. Labs like DESY believe that MTCA's TCO will be competitive. 
> Also note that hardware prices went down significantly within the last 
> two years.
> 
> > The crates were also very large.
> Since ~1 year you can buy smaller 2 or 4 slot chassis as well (e.g. 
> Vadatech, eicsys, NAT). There are also cheap chassis with built-in 
> management controllers and power supplies. Note that you loose some of 
> MTCA's flexibility if you go the built-in route, though.
> 
> > SLAC will be using ATCA
> Which does not make a big difference regarding the management software.
> 
> > FRIB is using uTCA for their applications.
> Yes, we do. And so far we are quite happy with it.
> 
> > It would be nice if someone developed some open source cards that
> > could provide a starting point for people attempting to use the
> > standard.
> There are quite a few open hardware AMCs (e.g. [1,2,3,4,5]). And of
> course hundreds of COTS cards.
> 
> But back to your question about management software: So far we did not 
> develop any MTCA-specific EPICS software (yet). For now we are using 
> Zabbix for monitoring (no need to develop anything since it already 
> comes with IPMI support). For EPICS integration you might want to have a 
> look at [6]. Note that in most cases software is not MTCA-specific but 
> compliant to standards like PCIe, IPMI, HPM.1,... so you might need to 
> look for these keywords.
> 
> Cheeers,
> 
> Martin
> 
> [1] http://www.ohwr.org/projects/mtca-4-timing-module
> [2] http://www.ohwr.org/projects/amc-cpu-com6
> [3] http://www.ohwr.org/projects/afck
> [4] http://www.ohwr.org/projects/afc
> [5] http://frib.msu.edu/content/frib-general-purpose-digital-board
> [6] http://icalepcs.synchrotron.org.au/papers/wepgf024.pdf
> 
> > I am looking for any existent EPICS support of MicroTCA HW
> > management or any plan for that. I've heard that SLAC and DESY
> > heavily (?) use that platform so far, but there are no EPICS related
> > activities I can find in teck-talks and others.
> >
> > Currently, my concern is to to maintain all MTCA4 HW (Chassis,
> > Carrier Hub, Backplane, Power Modules, Cooling Units, etc), because
> > MTCA.4 HW is still unstable (I mean comparing with any VME HW (I
> > might be wrong) and ESS will use several hundred MicroTCA Chassis
> > (crate).
> >
> > This maintenance has the following activities:
> >
> > * monitor/change a status of MicroTCA HW though EPICS *
> > update/revert the corresponding firmware through EPICS * all
> > activities are recorded into a EPICS archive service (AA) (it is
> > clear evidence with EPICS)
> >
> > So, we can scale this activities up to massive MicroTCA HW easily.
> >
> > Please let me know if you know much better idea than my naive one,
> > and would you recommend what you're using?
> >
> >
> > Thanks, Han
> >
> >
> >
> >
> >
> 
> 
> -- 
> Martin Konrad
> Control System Engineer
> Facility for Rare Isotope Beams
> Michigan State University
> 640 South Shaw Lane
> East Lansing, MI 48824-1321, USA
> Tel. 517-908-7253
> Email: [email protected]
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Mon, 11 Jan 2016 09:01:56 -0800 (PST)
> From: Sonya Hoobler <[email protected]>
> To: [email protected]
> Cc: Han Lee <[email protected]>
> Subject: Re: MTCA4 HW management
> Message-ID:
> 	<[email protected]>
> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
> 
> Dear Han,
> 
> In fact, SLAC does have a few MicroTCA systems. We did develop EPICS 
> monitoring for these systems, though it was never completed and still 
> contains some known bugs. This software discovers the shelf configuration 
> and monitors the shelf sensors.
> 
> We plan to fix these early this year and to add support for some of our 
> other IPMI-based systems. We would be happy to share this code with you at 
> that time.
> 
> Best regards,
>    Sonya
> 
> Sonya Hoobler
> SLAC National Accelerator Laboratory
> Instrumentation and Controls Division
> 
> 
> >
> > On Mon, Jan 11, 2016 at 4:42 AM, Jeong Han Lee <[email protected]>
> > wrote:
> >
> >> Hi all,
> >>
> >>   I am looking for any existent EPICS support of MicroTCA HW management or
> >> any plan for that. I've heard that SLAC and DESY heavily (?) use that
> >> platform so far, but there are no EPICS related activities I can find in
> >> teck-talks and others.
> >>
> >>   Currently, my concern is to to maintain all MTCA4 HW (Chassis, Carrier
> >> Hub, Backplane, Power Modules, Cooling Units, etc), because MTCA.4 HW is
> >> still unstable (I mean comparing with any VME HW (I might be wrong) and ESS
> >> will use several hundred MicroTCA Chassis (crate).
> >>
> >> This maintenance has the following activities:
> >>
> >>   * monitor/change a status of MicroTCA HW though EPICS
> >>   * update/revert the corresponding firmware through EPICS
> >>   * all activities are recorded into a EPICS archive service (AA) (it is
> >> clear evidence with EPICS)
> >>
> >>   So, we can scale this activities up to massive MicroTCA HW easily.
> >>
> >>   Please let me know if you know much better idea than my naive one, and
> >> would you recommend what you're using?
> >>
> >>
> >>   Thanks,
> >>   Han
> >>
> >>
> >>
> >>
> >>
> >
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Mon, 11 Jan 2016 17:49:24 +0000
> From: "Hill, Jeff" <[email protected]>
> To: Han Lee <[email protected]>, "[email protected]"
> 	<[email protected]>
> Subject: RE: MTCA4 HW management
> Message-ID:
> 	<[email protected]>
> Content-Type: text/plain; charset="us-ascii"
> 
> Han,
> 
> FWIW, LANL decided to go with 3U VPX instead of uTCA. We created a chassis design enclosing a 6 slot 3u VPX backplane, a 6u Compact PCI backplane, and also four 3u Compact PCI modular redundant power supplies. The VPX hosts the COTS Altera DSP boards with FMC mezzanine modular COTS ADC, and the Compact PCI hosts the analog cards, general purpose IO, and MRF timing etc. We interconnect the two backplanes with PCIe over cable standard. We run EPICS on FPGA embedded nios2 soft-cores running RTEMS. We have a presentation at the last ICALEPCS.
> 
> Jeff
> 
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]]
> > On Behalf Of Sonya Hoobler
> > Sent: Monday, January 11, 2016 10:02 AM
> > To: [email protected]
> > Cc: Han Lee
> > Subject: Re: MTCA4 HW management
> > 
> > Dear Han,
> > 
> > In fact, SLAC does have a few MicroTCA systems. We did develop EPICS
> > monitoring for these systems, though it was never completed and still
> > contains some known bugs. This software discovers the shelf configuration
> > and monitors the shelf sensors.
> > 
> > We plan to fix these early this year and to add support for some of our
> > other IPMI-based systems. We would be happy to share this code with you at
> > that time.
> > 
> > Best regards,
> >    Sonya
> > 
> > Sonya Hoobler
> > SLAC National Accelerator Laboratory
> > Instrumentation and Controls Division
> > 
> > 
> > >
> > > On Mon, Jan 11, 2016 at 4:42 AM, Jeong Han Lee <[email protected]>
> > > wrote:
> > >
> > >> Hi all,
> > >>
> > >>   I am looking for any existent EPICS support of MicroTCA HW management
> > or
> > >> any plan for that. I've heard that SLAC and DESY heavily (?) use that
> > >> platform so far, but there are no EPICS related activities I can find in
> > >> teck-talks and others.
> > >>
> > >>   Currently, my concern is to to maintain all MTCA4 HW (Chassis, Carrier
> > >> Hub, Backplane, Power Modules, Cooling Units, etc), because MTCA.4 HW is
> > >> still unstable (I mean comparing with any VME HW (I might be wrong) and
> > ESS
> > >> will use several hundred MicroTCA Chassis (crate).
> > >>
> > >> This maintenance has the following activities:
> > >>
> > >>   * monitor/change a status of MicroTCA HW though EPICS
> > >>   * update/revert the corresponding firmware through EPICS
> > >>   * all activities are recorded into a EPICS archive service (AA) (it is
> > >> clear evidence with EPICS)
> > >>
> > >>   So, we can scale this activities up to massive MicroTCA HW easily.
> > >>
> > >>   Please let me know if you know much better idea than my naive one, and
> > >> would you recommend what you're using?
> > >>
> > >>
> > >>   Thanks,
> > >>   Han
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Tech-talk mailing list [email protected]
> https://mailman.aps.anl.gov/mailman/listinfo/tech-talk
> 
> 
> End of Tech-talk Digest, Vol 10, Issue 14
> *****************************************



Navigate by Date:
Prev: Skip updating an output link in aSub ? Lingyun Yang
Next: Re: Issues with building EDM on Debian 8 32bit Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Skip updating an output link in aSub ? Priller, John
Next: EPICS Multiple Archiver Appliance problem "남승희"
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 15 Jul 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·