-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add radmonflag #29
base: master
Are you sure you want to change the base?
Add radmonflag #29
Conversation
A few more edits
source/radmon_flag.rst
Outdated
|
||
* Send an email to the ACIS team at the official anomaly email address, ``acis-anomaly -at- googlegroups -dot- com``. | ||
If it is off-hours, another ACIS Ops team member should call Peter | ||
Ford, Jim Francis, and Bob Goeke. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we think this is the event going on, does Bob really need to be part of the initial software checks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I copied the notifications from another anomaly page and we could certainly discuss who gets notified when. If we're diagnosing an unknown or not seen before anomaly, I think we would want the whole brain trust including Bob. He may not be as expert as Peter and Jim, but is still more expert than the rest of us.
radiation monitor flag has been enabled and that science data will | ||
not be collected until it is disabled. | ||
* Recommend to the Lead Systems Engineer and the Flight Director to | ||
send the command 1RMONIRM (v=0) to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Equivalent bcmd "set radiationmonitor low". (Which do they use in practice?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a hardware command, so the FOT needs the actually command. https://acis.mit.edu/acis/ipcl/ipcl-cmds-08jun98.html I'm not sure what the equivalent bcmd is for. Can you tell me where you saw it?
ACIS Commands | ||
+++++++++++++ | ||
|
||
* ``1RMONIRM(0)`` De-assert Radiation Monitor Flag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same note as above regarding "set radiationmonitor low"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above ;-)
source/radmon_flag.rst
Outdated
|
||
Spurious high level pulse commands to the PSMC have caused anomalies, but there have been no spurious serial digital commands as of yet. | ||
|
||
Note that the radiation monitor flag discussed here is entirely different from the TXINGS patch, which uses ACIS data to detect high radiation environment and then sets the ACIS bilevels to a particular pattern for the OBC to act upon. The ACIS radiation monitor flag is not used in current operation at all. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest moving this up slightly to under "Relevant Notes/Memos".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually thought about putting it all the way at the top of the page, since the potential confusion starts with the name of the anomaly. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I had a few small things I commented on in there.
Hey Catherine,
Thanks for the replies. I nabbed that bcmd from the FSWUG, Section 3.9,
this table: Radiation Alert Hardware Serial Digital Command Mnemonics. I
think your suggestion to move that warning note up to the top of the page
sounds just right.
-Jack
On Mon, Dec 14, 2020 at 7:35 PM cegrant ***@***.***> wrote:
@cegrant commented on this pull request.
________________________________
In source/radmon_flag.rst:
> +
+What is the response?
+---------------------
+
+(will this show up in a standard SOH by OC/CC? Don't think so but
+need to check)
+We need to:
+
+* Send an email to the ACIS team at the official anomaly email address,
``acis-anomaly -at- googlegroups -dot- com``.
+ If it is off-hours, another ACIS Ops team member should call Peter
+ Ford, Jim Francis, and Bob Goeke.
+* Send an email to ***@***.***`` announcing that the ACIS
+ radiation monitor flag has been enabled and that science data will
+ not be collected until it is disabled.
+* Recommend to the Lead Systems Engineer and the Flight Director to
+ send the command 1RMONIRM (v=0) to
It's a hardware command, so the FOT needs the actually command.
https://acis.mit.edu/acis/ipcl/ipcl-cmds-08jun98.html I'm not sure what the
equivalent bcmd is for. Can you tell me where you saw it?
…
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Further updates including - moving the TXINGS note to the top of the page - adding the expected DEA current, DPA current, and 1STAT1ST - adding text on the FOT state of health check (which I do not think would see this anomaly)
Thanks Jack, I've moved the TXINGS note to the top and made a few more text changes. |
Added a draft anomaly page for the radmon flag. Ready for reviews and edits from the team.