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

Gemini 2 serial alignment bug #8

Open
bgottula opened this issue Feb 20, 2018 · 1 comment
Open

Gemini 2 serial alignment bug #8

bgottula opened this issue Feb 20, 2018 · 1 comment
Labels

Comments

@bgottula
Copy link
Collaborator

While testing the Gemini 2 serial interface in a control loop I encountered a problem where I would hit a timeout while waiting for a response to a get position command. After this occurred, I found using minicom that I would only get a response to the command being sent after sending the first character of the next command. The only way to recover seemed to be unplugging the USB cable or power cycling Gemini 2. The control loop was also sending some native commands that do not produce any response, so one hypothesis is that commands were being sent to Gemini 2 too quickly. I no longer encountered the issue after inserting echo commands in between each of the native commands that had no response, the thought being that the code would wait for responses to the echos before proceeding to the next important command.

@bgottula
Copy link
Collaborator Author

Wireshark capture of the USB serial interface. The issue begins near the end of the capture (filter on usb.addr).
serial_busted.pcapng.zip

@bgottula bgottula added the bug label Aug 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant