Topic | Mooshi Broken?

Home Forums Mooshimeter Support Mooshi Broken?

Viewing 4 reply threads
  • Author
    Posts
    • #13916 Reply
      Tom Feist
      Guest

      I purchased my Mooshimeter on May 2/16 and have used it almost daily (until July 10/16) as a data logger to record charges and discharges of batteries. I was one of the lucky folk that only had a few minor problems with the meter. Any issues I’ve had were quickly resolved thanks to James and the Beta Testers for posting their input on the forum.

      I did a firmware update (1467155160) on July 10/16. My meter has never been the same since that time. I would set up for a 24 hour test to later find the first few hours of data wasn’t logged. It was the first time I experienced multiple CSV files too. Sometimes the meter worked flawlessly. Most times it didn’t. Also, the meter has lost its stability. The readings, when viewed through the app or the logged data, would show spikes. These spikes were much more often than prior to this update.

      Firmware update 1469410939 corrected most of the problems with exception to the spiking. I believe the July 10th update didn’t take proper hold as well as it damaged the meter. The 1469410939 update cleared the bad update but I’m still stuck with a data file that takes a long time to clean up before its usable.

      As an example, during the good times, graphing the data went fairly smooth. There would be the occasional recording that took a few minutes of massaging to bring it in line. Now, it’s necessary to go through each of the >8000 (at 10 sec intervals x 24 hrs) data points before creating the graph. There were over 140 corrections to be made from the last test.

      I’ve been watching the forum for other owners with a similar problem but it seems to be just me. I’ve tried resetting the meter, cleaning the SD card contacts, replacing the cells after removing the old ones for a good 10 minutes, reboot my phone and even went so far as delete the app and reinstall it. Same deal.

      Any suggestions?

    • #13917 Reply
      admin
      Keymaster

      Hi Tom,

      I recently (Sunday 8/21/2016) pushed the beta branch to production, along with a firmware issue that addresses many of the logging issues you found in the beta releases, including the occasional data spikiness. The latest firmware version is 1470628829.

      If convenient, can you send me one of the logfiles you got from the meter that required lots of manual cleanup? You can put it on dropbox and link from the forum, or send it to james@moosh.im. I’ve seen failures from many iterations of the beta firmware, I may be able to say if these are the kinds of issues that would be addressed by the latest firmware or not.

      Last thing – sorry to put you through the same process again, but can you update to the latest app and firmware one more time? Much of the last few months has been hunting down edge cases in the logging, I expect you will get better behavior.

      Of course if we do find your meter is somehow defective I will send you a replacement.

      Best
      ~James

    • #13918 Reply
      Anonymous
      Guest

      Many thanks for the quick reply.

      I should still have the last original CSV file I had to tweak saved on my office computer. I’ll check Tomorrow morning.

    • #13922 Reply
      Anonymous
      Guest

      Thanks for offering to replace my meter. It appears it won’t come to that. Somehow, I didn’t think twice about why the latest app update didn’t prompt me to update the firmware like it has done every time in the past. The meter’s firmware is now operating on the same page as the app.

      I only had time to do a 4 hour test. There were ZERO data points to correct.

      Thanks again for your immediate attention to correct my problem.

    • #13932 Reply
      admin
      Keymaster

      Hooray! Very happy it’s working as expected :)

      Best
      ~James

Viewing 4 reply threads
Reply To: Mooshi Broken?
Your information:




This site is protected by reCaptcha and the Google Privacy Policy and Terms of Service apply.