Skip to content
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

Troubleshooting tips #9

Open
mcmcgrath13 opened this issue Oct 8, 2019 · 6 comments
Open

Troubleshooting tips #9

mcmcgrath13 opened this issue Oct 8, 2019 · 6 comments
Assignees

Comments

@mcmcgrath13
Copy link
Contributor

Situations:

  • zmq timeout - summit api probably needs to be relaunched - how to handle this?
  • INS disconnected - how to handle this?
  • battery low - charge it?
  • other?

@davidxingy @nicoleprovenza could you help fill in what should happen in all of these cases?

@nicoleprovenza
Copy link
Contributor

nicoleprovenza commented Oct 10, 2019

  1. Summit API is timing out -> was never launched or crashed
    --> user message: restart the app.
    --> to do: make a power shell that runs both exe's. however, if David's summit backend is hidden, then it can't be closed unless the MyRC+S app can call David's summit backend

  2. CTM is not connected
    --> user message: ensure the CTM is charged, on, and nearby the surfaceGo

  3. INS is disconnected
    --> user message: RC+S is disonnected. Ensure the CTM is nearby. Trying to reconnect (1/3).
    if still not connected:
    --> user message: RC+S is still disconnected. Trying to reconnect (2/3).
    if still not connected:
    --> user message: RC+S is still disconnected. Trying to reconnect (3/3).
    if still not connected:
    --> user message: Unable to connect to RC+S. Please call technical support.

@nicoleprovenza
Copy link
Contributor

  1. INS battery is low
    --> if the recording button is pressed: RC+S battery is insufficient to record. Please recharge your RC+S.
    --> if the recording is started and the button is pressed to stop recording & error message appears (tbd: Press the stop recording button again)
    --> to do: David will check the low battery error message
    --> to do: David if you are sensing, and INS is disconnected, is it still sensing?

@nicoleprovenza
Copy link
Contributor

  1. For all other errors, user message: 'there was an unexpected error. Please notify tech support.'

@fernandogelin
Copy link
Contributor

@davidxingy have you checked the things related to item 4 above?

@fernandogelin
Copy link
Contributor

@davidxingy will the summit interface send error messages if it doesn't complete the steps: connect to CTM, connect to INS? Or will it only respond to any requests after it is connected to the INS? Will the electron side be able to differentiate erros 1,2 and 3? Or will it be all the same?

@davidxingy
Copy link
Contributor

@fernandogelin right now, if it's for the initial connection to the CTM/INS upon startup, if it is unable to connect then the program will just be stuck in a retrying loop (until you close it), so there will be no receiver for your socket and you'll get a timeout. If it's already connected and established the connection with the Electron App, then it will send an error message (right now I've only defined two messages, out of battery and INS disconnected, so it doesn't differential between INS vs CTM disconnect).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants