Sure, it is a proof-of-concept, not a product. I'm quite sure that 100, maybe
500 bytes per second are possible, but the firmware needs to use a diferent
approach.
This list is about libraries, and what you need is not easily or efficiently
realised as a library, it's a project. I have some
HI Kiste
Unfortunately that is way too slow. I need to send and read a set of at
least 9 bytes with an interval of no more than 3 seconds.
regards
Hans
Op zondag 27 februari 2022 om 08:45:40 UTC+1 schreef Kiste:
> Hi Hans,
>
> sorry for chiming in again with another warning: Rob called the set
Hi Hans, Kiste,
The POC (proof of concept) was just to create a trigger signal based on an
audio tone. It was not meant as a way to store data with a certain bitrate.
As I mentioned earlier, it measures the tone for 100 ms to determine if the
tone is there (in my example I detect two different
Branch: refs/heads/master
Home: https://github.com/jallib/jallib
Commit: 7659dba560c82a6226373a76af69674b7ea4bab9
https://github.com/jallib/jallib/commit/7659dba560c82a6226373a76af69674b7ea4bab9
Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
Date:
Branch: refs/heads/master
Home: https://github.com/jallib/jallib
Commit: 209cef485347aef83f3efecbeb39861080e2772a
https://github.com/jallib/jallib/commit/209cef485347aef83f3efecbeb39861080e2772a
Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
Date:
Hi guys,
This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot
Build Reason:
Build Source Stamp: HEAD
Blamelist: rob.jansen
Build succeeded!
Logs are attached.
sincerely,
-The Buildbot
--
You received this message because you are
