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-791 Instrument control development <p>See <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-790" title="ion pumps communication issue" class="issue-link" data-issue-key="INSTRM-790">INSTRM-790</a>. I think adding a proper actor is easiest.</p> INSTRM-791

For a single SM, add either an ionpumpActor or a program sequencing ionpump commands to the MOXA.

Task Normal Done Done cloomis cloomis SPS Mon, 7 Oct 2019 18:36:16 +0000 Wed, 24 May 2023 18:46:33 +0000 Wed, 24 May 2023 18:46:33 +0000 0 2 <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=fmadec" class="user-hover" rel="fmadec">fmadec</a>: is this needed to be fixed soon? And when?</p> <p>Bump for NIRs. For a single cryostat, a <tt>status</tt> command requires 14 controller commands spanning 1.5s or so. With three arms independently chattering that way the current command failure rate will get ugly. I have not been able to come up with a better/simpler alternative than adding an ion pump actor.</p> <p>Bump. With three cameras this is becoming a problem.</p> <p>Specifically, from 2023-04-11 15:46Z to 16:13Z, at 15s sampling, we got no good readings.</p> <p>I decided that embracing the unavoidable contention should be done first: blocking the single TCP connection for all of the ~10 status commands, and expecting the first connection to have to wait for ~2s or so. Running at JHU, and seems to work. </p> <p>Tagged 2.2.11</p> Relates INSTRM-790 Development Rank 0|02qpuc:i6001gr068fhw9qo4p Story Points 2.0