Experimental Physics and Industrial Control System
Hi Mark,
I hope you are well?
I implemented this API for the Galil 3-0 driver on git. The structure of the API worked well for the Galil machine too.
We have a Newport XPS controlling the DCM on XAS beamline here. This project was delivered around April this year. You kindly provided Pier Valitutti support for this endeavour at the time.
Have a good time at the conference.
Best wishes,
Mark
Dr. Mark Clift
Senior Controls Engineer
Australian Synchrotron
800 Blackburn Road
Clayton 3168
Ph: +613 8540 4264
Fax: +613 8540 4200
Mail: [email protected]
________________________________________
From: [email protected] [[email protected]] on behalf of [email protected] [[email protected]]
Sent: Sunday, 24 September 2017 03:00
To: [email protected]
Subject: Tech-talk Digest, Vol 11, Issue 347
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. Control System Engineer Opening at Lawrence Berkeley
Laboratory (Robert Gunion)
2. Spurious "Channel write request failed" messages (Michael Ritzert)
3. Re: Spurious "Channel write request failed" messages (Ralph Lange)
4. Coordinated motion with EPICS motor record (Mark Rivers)
----------------------------------------------------------------------
Message: 1
Date: Sat, 23 Sep 2017 00:05:24 +0000
From: Robert Gunion <[email protected]>
To: EPICS mailing list <[email protected]>
Subject: Control System Engineer Opening at Lawrence Berkeley
Laboratory
Message-ID:
<CA+EA2h4xjXCXjjztocFHRzrc-9hReHgy55xnY4Pbysd7tD1Jow@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi all,
We have an opening for a relatively early-career control system engineer at
the Advanced Light Source in Berkeley, California. Please see
https://lbl.taleo.net/careersection/engineer/jobdetail.ftl?job=83809
Though this is initially a 2-year term appointment, the intent is to roll
it into a career position.
We have lots to do at the ALS, plus we're in the planning stages for ALS-U,
a major upgrade. Note that ALS-U will also enable additional hiring in the
next several years, including more experienced engineers who may be
overqualified for this particular posting.
If interested parties are at the EPICS/ICALEPCS meeting in Barcelona, look
for me and we'll chat.
Cheers,
Bob Gunion
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.aps.anl.gov/pipermail/tech-talk/attachments/20170923/a059835e/attachment.html>
------------------------------
Message: 2
Date: Sat, 23 Sep 2017 10:47:20 +0100
From: Michael Ritzert <[email protected]>
To: [email protected]
Subject: Spurious "Channel write request failed" messages
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi all,
since upgrading from 3.14 to 3.16.1, I see the following messages on the console of an IOC:
DB CA Link Exception: channel "dest1"
DB CA Link Exception: native T=DBR_DOUBLE, request T=DBR_DOUBLE, native N=1, request N=1, access rights {RW}
DB CA Link Exception: "Channel write request failed", context "dest1"
This is from a dfanout record that simply pushes a value to another IOC.
However, the write succeeds.
It's totally reproducible with these two DBs run in softIOCs:
sender.db:
record(calc, "count") {
field(SCAN, "1 second")
field(VAL, "0")
field(PINI, "YES")
field(INPA, "count")
field(CALC, "A+1")
}
record(dfanout, "send1") {
field(DOL, "count CPP")
field(OMSL, "closed_loop")
field(OUTA, "dest1")
}
record(dfanout, "send2") {
field(OMSL, "supervisory")
field(OUTA, "dest2")
}
receiver.db:
record(ao, "dest1") {
}
record(ao, "dest2") {
}
There's one messages every second about dest1, and one on every write to send2.
Cheers,
Michael
--
Dr. Michael Ritzert Tel: +49 621 181 2883
Schaltungstechnik und Simulation Fax: +49 621 181 2734
Technische Informatik, Uni Heidelberg [email protected]
68131 Mannheim, Germany http://sus.ziti.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5308 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mailman.aps.anl.gov/pipermail/tech-talk/attachments/20170923/445694eb/attachment.p7s>
------------------------------
Message: 3
Date: Sat, 23 Sep 2017 13:15:34 +0200
From: Ralph Lange <[email protected]>
To: EPICS Tech Talk <[email protected]>
Cc: Michael Ritzert <[email protected]>
Subject: Re: Spurious "Channel write request failed" messages
Message-ID:
<CAGJXJ2F7sFMCmTdLMzku5NQzZ6u9orRbx+4E1oRXX51M1n0UHw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Michael,
That erroneous behavior was described in
http://www.aps.anl.gov/epics/core-talk/2017/msg00503.php, and has been
fixed on the 3.16 branch.
Alas, there's no bug in the issue tracker for it, and it is not mentioned
on the "Known Issues" page. We should probably add the latter at least.
Thanks for pointing this out!
~Ralph
On Sat, Sep 23, 2017 at 11:47 AM, Michael Ritzert <
[email protected]> wrote:
> Hi all,
>
> since upgrading from 3.14 to 3.16.1, I see the following messages on the
> console of an IOC:
> DB CA Link Exception: channel "dest1"
> DB CA Link Exception: native T=DBR_DOUBLE, request T=DBR_DOUBLE, native
> N=1, request N=1, access rights {RW}
> DB CA Link Exception: "Channel write request failed", context "dest1"
>
> This is from a dfanout record that simply pushes a value to another IOC.
>
> However, the write succeeds.
>
> It's totally reproducible with these two DBs run in softIOCs:
>
> sender.db:
> record(calc, "count") {
> field(SCAN, "1 second")
> field(VAL, "0")
> field(PINI, "YES")
> field(INPA, "count")
> field(CALC, "A+1")
> }
>
> record(dfanout, "send1") {
> field(DOL, "count CPP")
> field(OMSL, "closed_loop")
> field(OUTA, "dest1")
> }
>
> record(dfanout, "send2") {
> field(OMSL, "supervisory")
> field(OUTA, "dest2")
> }
>
> receiver.db:
> record(ao, "dest1") {
> }
>
> record(ao, "dest2") {
> }
>
> There's one messages every second about dest1, and one on every write to
> send2.
>
> Cheers,
> Michael
> --
> Dr. Michael Ritzert Tel: +49 621 181 2883
> Schaltungstechnik und Simulation Fax: +49 621 181 2734
> Technische Informatik, Uni Heidelberg [email protected]
> heidelberg.de
> 68131 Mannheim, Germany http://sus.ziti.uni-heidelberg.de
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.aps.anl.gov/pipermail/tech-talk/attachments/20170923/c3ef589a/attachment.html>
------------------------------
Message: 4
Date: Sat, 23 Sep 2017 14:13:42 +0000
From: Mark Rivers <[email protected]>
To: tech-talk <[email protected]>
Subject: Coordinated motion with EPICS motor record
Message-ID:
<70AE7462E7AD054C89DCBA45343D499A660BECF9@CARSMAIL2.CARS.APS.ANL.GOV>
Content-Type: text/plain; charset="us-ascii"
Folks,
I am giving a talk at the motion control workshop at ICALEPCS in two weeks titled "Complex coordinated motion in EPICS". This is about using the ProfileMove API that is supported in the Model 3 motor API in asynMotorController and asynMotorAxis. This API allows defining complex trajectories in N-space and then executing them.
>From asynMotorController.h
/* These are the functions for profile moves */
virtual asynStatus initializeProfile(size_t maxPoints);
virtual asynStatus buildProfile();
virtual asynStatus executeProfile();
virtual asynStatus abortProfile();
virtual asynStatus readbackProfile();
>From asynMotorAxis.h
virtual asynStatus initializeProfile(size_t maxPoints);
virtual asynStatus defineProfile(double *positions, size_t numPoints);
virtual asynStatus buildProfile();
virtual asynStatus executeProfile();
virtual asynStatus abortProfile();
virtual asynStatus readbackProfile();
I have implemented this API on the Newport XPS controller. What I would like to know is if other sites have implemented this API for other controllers, and/or if they are using it on the Newport XPS.
Thanks,
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.aps.anl.gov/pipermail/tech-talk/attachments/20170923/fc287a1e/attachment.html>
------------------------------
_______________________________________________
Tech-talk mailing list [email protected]
https://mailman.aps.anl.gov/mailman/listinfo/tech-talk
End of Tech-talk Digest, Vol 11, Issue 347
******************************************
- Replies:
- RE: Coordinated motion with EPICS motor record Mark Rivers
- Navigate by Date:
- Prev:
Coordinated motion with EPICS motor record Mark Rivers
- Next:
RE: Coordinated motion with EPICS motor record Mark Rivers
- 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
- Navigate by Thread:
- Prev:
Re: Coordinated motion with EPICS motor record Mooney, Tim M.
- Next:
RE: Coordinated motion with EPICS motor record Mark Rivers
- 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