{"action":"opened","issue":{"url":"https://api.github.com/repos/epics-modules/asyn/issues/58","repository_url":"https://api.github.com/repos/epics-modules/asyn","labels_url":"https://api.github.com/repos/epics-modules/asyn/issues/58/labels{/name}","comments_url":"https://api.github.com/repos/epics-modules/asyn/issues/58/comments","events_url":"https://api.github.com/repos/epics-modules/asyn/issues/58/events","html_url":"https://github.com/epics-modules/asyn/issues/58","id":246900465,"number":58,"title":"New generic testing driver request","user":{"login":"MarkRivers","id":6115534,"avatar_url":"https://avatars0.githubusercontent.com/u/6115534?v=4","gravatar_id":"","url":"https://api.github.com/users/MarkRivers","html_url":"https://github.com/MarkRivers","followers_url":"https://api.github.com/users/MarkRivers/followers","following_url":"https://api.github.com/users/MarkRivers/following{/other_user}","gists_url":"https://api.github.com/users/MarkRivers/gists{/gist_id}","starred_url":"https://api.github.com/users/MarkRivers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MarkRivers/subscriptions","organizations_url":"https://api.github.com/users/MarkRivers/orgs","repos_url":"https://api.github.com/users/MarkRivers/repos","events_url":"https://api.github.com/users/MarkRivers/events{/privacy}","received_events_url":"https://api.github.com/users/MarkRivers/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-07-31T22:14:54Z","updated_at":"2017-07-31T22:14:54Z","closed_at":null,"body":"Ralph Lange has suggested a new generic driver that can be used for testing databases in the absence of a real device.  He proposed:\r\n\r\n> We are using the standard ASYN EPICS support, so that a dummy emulation port driver might work as an emulation replacement for *any* asyn based driver, which would make the approach very efficient.\r\n\r\nMy question:\r\n> Can you explain how you see such a generic driver working. How would you set the new value of an input record? How would that message get to the driver?\r\n\r\nRalph's answer:\r\n> (In first iteration) I would make that dummy driver as simple as possible:\r\n> - Writes do nothing.\r\n> - Reads do not update the record, set the timestamp from the IOC clock (ignoring TSE) and set STAT/SEVR to SIMM//NO_ALARM.\r\n> - I/O Intr records are processed every dd seconds (per port configuration option).\r\n>\r\n> Aim is that everything is \"green\" for the user (while the special mode is still visible in the STAT of all records), the IOC console is reasonably quiet, and they can run tests (programmatically or manually) by writing to the VAL fields of input records.\r\n\r\nMy question:\r\n> What value does the driver pass to device support for I/O Intr records?\r\n\r\nRalph's answer:\r\n> The driver should not set a value. The user will write their test value from above (CA or DB), the driver must set STAT, the timestamp and trigger processing.\r\n"}}
{"actor":{"display_login":"MarkRivers"}}