https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-454 Instrument control development <p>We need to be more aware of the state of the gatevalve interlock. As it stands if the interlock blocks the gatevalve open signal (thus closing it), then later unblocks it, the gatevalve will reopen. We want the interlock blocking to latch. </p> <p>More specifically, the interlock circuit can be powered down or jumpered off, which then closes the valve. Good. But if the valve is closed that way, the aDIO driver on the BEE is still requesting that the valve be open. So if later the interlock circuit is powered back up, or the jumper reinstalled, the valve immediately opens. Scary.</p> <p>JHU might change the circuit. But I'd like the XCU to be more conservative. The (C) aDIO driver from RTD supports interrupts; I'd like to have that trigger our gatevalve control to retire the open request.</p> INSTRM-454

(try to) enable interrupts for the aDIO gatevalve control.

Task Normal Done Done cloomis cloomis SM1 Thu, 23 Aug 2018 11:57:54 +0000 Wed, 14 Nov 2018 14:28:29 +0000 Wed, 14 Nov 2018 14:28:29 +0000 ics_xcu_rtdADIO 0 1 <p>The interrupts seem to work and get to userland: we can solve this in software. Their library spawns off a thread, so I still need to put in a safe transfer mechanism from the C library.</p> <p>Done. Moving python-level work to new <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-570" title="Add python-level interlock interrupt handler." class="issue-link" data-issue-key="INSTRM-570"><del>INSTRM-570</del></a></p> Relates INSTRM-570 INSTRM-406 Development Epic Link INSTRM-518 Rank 0|02qpuc:ii