EPICS Re: Possible Access Rights improvement?

2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024	Index	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 ==>

Hmmm....

What I remember:

When you connect a widget to an CS-Studio/BOY internal sim channel providing a sine wave, you see it as read-only with all graphical balderdash that goes with it.

When you connect the same widget to an EPICS calc record providing a sine wave, it appears writable, and while writing seems to work, it doesn't.

Shouldn't both behave the same?

And:

In a panel used for testing, that indeed routinely connects controller widgets to input records, everything works fine as long as the hardware is disconnected, i.e. you can flicker your input bits and see them on the operation panels under test.

As soon as the hardware is connected, the test panel stops working, and there's no easy way to tell. (Writing seems to work, but it doesn't.)

My recent work on the simulation mode is trying to fix the second case towards being able to use the simulation mode to simulate missing hardware (which currently doesn't work - see other thread). When that eventually works, the testing panel will connect to SVAL fields, the alarm status (SIM) can be used to signal simulation mode, and you don't have to disconnect the hardware.

The first case ... I don't know.

Cheers,
~Ralph

On Thu, Aug 24, 2017 at 5:46 PM, Kasemir, Kay <[email protected]> wrote:

What is the use case?

Assume I have an AI record that reads from a PLC.

So I display that as a text update field on the UI.

Would you routinely display that record as a text entry field?

-Kay

From: [email protected] <[email protected]> on behalf of Ralph Lange <[email protected]>
Sent: Thursday, August 24, 2017 3:34 AM
To: EPICS Core Talk
Subject: Possible Access Rights improvement?

Dear Core-talkers,

There is a possible request from our operations group to show VAL fields of input records as having no write access, if the device support would overwrite any value written at the next record processing.

Technically, these fields are writable.

Functionally, there are issues:

The writing client (even using put-callback) will get the new value and show the operation as having succeeded.

Other clients doing gets or creating new subscriptions (e.g. newly opened panels) will see the new value.

Existing subscriptions (e.g. archivers, gateways, already open panels) will not get an update and have no clue.

Depending on the situation (DTYP, SCAN) this inconsistent state may last a while.

What are your thoughts on this?

Thanks,

~Ralph

Subject:	Re: Possible Access Rights improvement?
From:	Ralph Lange <[email protected]>
To:	EPICS Core Talk <[email protected]>
Date:	Thu, 24 Aug 2017 22:32:29 +0200

Experimental Physics and Industrial Control System