Member Since: August 7, 2012

Country: United States

  • My approach is at:

    I found 168 hits for mystery set 1, and 160 for mystery set 2.

    detected 77 hits for the 3-77 dataset

    detected 78 hits for the 4-81 dataset

    detected 93 hits for the 5-93 dataset

    detected 83 hits for the 6-79 dataset

    There seem to be some leading and trailing events in most data sets - not sure if they are actual hits as the spacing between them are larger than the others in the main body of data. These could be a source of variability. Another challenge is detecting a “weak” hit event, which may be due to a soft blow or a blow when the stand is oscillating (the blow could land when the stand is “moving away” and the net acceleration is lower, possibly zero.)

    It’s also curious that there are so many accelerometer timeout events. Some of the hits may be missing….. Any thoughts? Maybe due to display data line sharing/multiplexing?

    Thanks for the challenge!


  • POSSIBLE BUG : If a zero data length packet is received with a CRC error, no subsequent valid packets can be received until the device is reset via power recycle (maybe with a soft reset.) I had attempted to use zero data length packets for ACK/NAK responses and into this problem. Once I changed them to one data byte packets all was well - going to contact HopeRF and SiLabs.

    Overall, this is a great module and I highly recommend it!

  • Nice vid - Keep in mind that the LM358 output only swings from 0 to VCC-1.5V… If your divider gives about 1.67V bias the output will clip at 1.83V, limiting the AC peak amplitude to 0.16V.. If you change the bias to 0.9V the AC peak will be increased to, well, about 0.9V. If you have a rail-to-rail amp that would be even better.

No public wish lists :(