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

Stress test the plug and unplug, pause/resume, Bluetooth module #45

Open
KamranBinaee opened this issue Oct 23, 2020 · 5 comments
Open
Assignees

Comments

@KamranBinaee
Copy link
Contributor

Hi all,
In reference to our previous conversations @marklescroart @phausamann, I'm opening this issue to run some tests.
These tests include,

  • Making sure the audio packages are installed and imported correctly (I had issues with this).
  • Making sure the beeps are being generated correctly.
  • Making sure the Bluetooth connectivity is robust, i.e.
    • does it need reset every few minutes?
    • What happens if we don't do that?
    • How do we recover?
    • Update the documentation accordingly.
  • Making sure the pause/resume happens properly using the Bluetooth module.
  • Stress test laptop USB connections while in the backpack and make sure it is being reported properly.
@KamranBinaee KamranBinaee self-assigned this Oct 23, 2020
@KamranBinaee
Copy link
Contributor Author

Hi @mrgreene09,
Please feel free to add/modify the list.
Maybe if you could share the log files, that would be great.
Thanks

@phausamann phausamann transferred this issue from vedb/pupil_recording_interface Oct 23, 2020
@mrgreene09
Copy link

I can confirm that my system is not beeping. Upon pulling out a plug, there is a brief error about not being able to work with pulse (I can't quite read the whole thing before it is erased in a core dump). I have tried installing pulseaudio, but the issue remains even with a restart. Would love some pointers to the additional audio libraries that I should install. Thanks!

@phausamann
Copy link
Contributor

@mrgreene09 a couple of things to narrow down the issue:

  • Does your sound work otherwise, e.g. if you play an audio file?
  • What does cat /proc/asound/cards print out?
  • It would be very helpful to see the actual error. When you get the core dump, are you able to scroll up in the terminal output and copy it?

@KamranBinaee
Copy link
Contributor Author

How about the log file? Would that be helpful to take a look at it?

@phausamann
Copy link
Contributor

A low-level error that causes a core dump and kills the process will most likely not be picked up by the logger. But there might still be some useful info in the logs.

@mrgreene09 they are saved to vedc.record.log in the recording folder.

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

3 participants