-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
|
|
|
@davidxingy have you checked the things related to item 4 above? |
@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? |
@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). |
Situations:
@davidxingy @nicoleprovenza could you help fill in what should happen in all of these cases?
The text was updated successfully, but these errors were encountered: