-
Notifications
You must be signed in to change notification settings - Fork 121
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
Decoding failed #51
Comments
For what it's worth, I'm having similar problems. I'm running the sender and receiver on the same computer. I've also tried against the Android app. I believe the only success I've had is from the computer to the app. Here are my logs for a local calibration and test, and the matplotlib graphs (of a subsequent test). |
Ok, so I DID just manage to get a message from the phone to the computer. I turned down the volume on my phone and the mic on the computer and put the speaker within an inch of the microphone. Looks like it's just not very tolerant of noise? Is there a way to improve that? Further reduce the bitrate or something? |
Ah - one problem is that aplay and arecord don't play at the correct samplerates, I think. A little more investigation to follow. |
I dunno. :/ In increments, I've turned the symbol length up by a factor of 20, decreased the frequency to 6e2, increased the sample rate to 32e3, left Npoints at 2, messed a lot with the volumes - nothing seems to work. |
Have you tried sending more data, like the 60 kB example in Readme.md? |
Hi!
I am testing this on some of my systems and can't get a transfer to work:
Sender (using aplay because amodem picks the wrong interface):
Receiver:
However, calibration seems good?
Can you advise? Thanks
The text was updated successfully, but these errors were encountered: