[INSTRM-454] (try to) enable interrupts for the aDIO gatevalve control. Created: 23/Aug/18 Updated: 14/Nov/18 Resolved: 14/Nov/18 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | ics_xcu_rtdADIO |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | cloomis |
| Resolution: | Done | Votes: | 0 |
| Labels: | SM1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Epic Link: | SM1 Visible R+B readiness | ||||||||||||
| Description |
|
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. 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. 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. |
| Comments |
| Comment by cloomis [ 30/Aug/18 ] |
|
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. |
| Comment by cloomis [ 14/Nov/18 ] |
|
Done. Moving python-level work to new |