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

LipSync doesn't travel well #31

Open
bradleywell opened this issue Nov 25, 2024 · 3 comments
Open

LipSync doesn't travel well #31

bradleywell opened this issue Nov 25, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@bradleywell
Copy link
Contributor

Some clinicians say that the LipSync does not travel well and need recalibration and re-setup at every location. They have asked for some sort of travel cover that covers the gimbal and prevents it from being jostled or bumped in transit. Following up with them for more detail.

@bradleywell bradleywell added the enhancement New feature or request label Nov 25, 2024
@bradleywell
Copy link
Contributor Author

Following up with the clinician and got the following feedback. Sounds like an underlying bug and not an issue with travel itself.

"What I had found with the LipSync is that something about transporting it is causing errors, and a full factory reset seems to be required to get it functioning again. This happened when transporting it for a demo at a university, and also happened to a client who moved house recently and found that it would be detected by the computer after the move but would not display a cursor or seemed to have any control over mouse movement. This client had customized the sip/puff strength and duration to match his wheelchair, so was frustrated at having to do the factory reset to get it working again. He wished there was an easy readout screen showing any changes made from default settings that he could have taken a picture of for reference before resetting."

@jakemcivor
Copy link
Member

I suspect the root cause of this is probably automatically switching to Bluetooth (i.e., #23). The 4.1 firmware update will resolve that. In the meantime, changing the operating mode back to USB Mouse instead of doing a Factory Reset will enable the user to resolve the problem without losing their settings.

Will add a corresponding feature request for the ability to more easily restore user settings, although that would be challenging with current hardware.

@bradleywell
Copy link
Contributor Author

I've passed this along to the clinician and asked her if she can test this and try changing it to USB mouse and see if that fixes it.

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

No branches or pull requests

2 participants