Archive by Author

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 642 total)
  • Author
    Posts
  • in reply to: App need firmware update again and again #19816

    James
    Keymaster

    Hi Marcin,

    What kind of phone are you using? Android or iOS? It sounds like it might be Android and that the phone is saving wrong information about the meter, causing connection problems. Can you go to settings->Bluetooth and make sure to delete any pairing information for the meter?

    ~James

  • in reply to: Issues connecting to iOS device. #19780

    James
    Keymaster

    Thanks for the follow up Alex, glad it’s working!


  • James
    Keymaster

    Hi Ville,

    Regarding recovery from reboot: I looked at the code, and it seems that while the channel 1 and channel 2 settings are stashed and restored, the auxiliary channel setting was not. This is why after the reboot, you were connected to the aux channel but with the default setting (aux voltage DC). I’ve patched this in firmware and will release it shortly. Thank you for finding another edge case.

    Regarding why we reboot at all: Honestly I’ve struggled with this a lot and I don’t have a great answer. It’s quite hard to diagnose because it only happens once after a few days. It seems to happen in the SD card initialization period when the meter is waking up to take a reading, but that’s about as far as I’ve gotten. So far, making reboot recovery robust has been a good time investment compared to the weeks I spend chasing flaky errors.

    Thanks again, best
    ~James

  • in reply to: Issues connecting to iOS device. #19776

    James
    Keymaster

    Hi Alex,

    Sorry for the delay on this. iOS is usually quite reliable on connecting to the meter. Is it possible bluetooth is turned off on the phone? You can go to settings->bluetooth to check. The app should prompt you if that is the issue, but maybe something changed in iOS that I need to investigate.

    Best
    ~James

  • in reply to: SD Card Log Rate Limited to 12Hz max? #19766

    James
    Keymaster

    Hi Daniel,

    The sample rate and buffer depth do affect the logging rate, so I recommend raising the sampling rate if you want to log data faster.

    However the other constraint is the amount of time it actually takes to log to the SD card, which unfortunately varies from card to card. So to push it as fast as it can go, I recommend setting your sampling rate to 2000Hz, buffer depth 32, logging with no wait between readings. If this does not give you a satisfactory logging interval, I suggest swapping out the SD card for one of lower capacity (I’ve found them to be quicker in the Mooshimeter, not 100% sure why).

    ~James

  • in reply to: Connection problem. Dead meter? #19759

    James
    Keymaster

    Hi Philip,

    What kind of phone are you using? I hear about behavior like this when Android’s bluetooth stack gets confused. Can you try rebooting the phone?

    ~James


  • James
    Keymaster

    Hi Don,

    I think the issue is the range on the channel. The voltage channel has 2 available ranges – 60V and 600V. I think you’re in the 60V range and the channel is saturating, which is why you’re seeing the RMS peak out around 85V.

    With your initialization commands, add
    CH2:RANGE_I range 1 (code 31, byte 1, assuming 147xxx firmware)

    Best
    ~James

  • in reply to: logging interval 600s -> 10s #19734

    James
    Keymaster

    MrPeak – thank you for investigating. Regarding your earlier question about the timing drifting slightly, your analysis is correct that the logging system in firmware is waking up, setting an alarm, then going back to sleep, and that the variance in wakeup time is causing the slow drift. I think it’s more pronounced with logging period of 60s because when the logging period is long, the meter puts the SD card to sleep and wakes it up every time, which I’ve learned from experience is a very variable process.

    Ville – your analysis of the 10minute logging interval problem is 99.9% correct and I can’t believe I made such a mistake. Internally in the meter, it’s a 16 bit integer storing the logging interval, but it’s stored in seconds. I made it that way because I wanted to avoid overflow, which you are right to be concerned about. But the internal timing mechanisms of the firmware deal in milliseconds, and I performed the conversion wrong. Here is the offending line:
    osal_start_timerEx( APP_TID, SBP_LOG_TIMER_EVT, (meter_state.log_settings.interval_s)*1000 );
    Since meter_state.log_settings.interval_s is a uint16, the compiler does a 16 bit multiply with 1000, which overflows of course. And the result of that overflow is (600*1000) mod (2^16-1) = 10.185 seconds, exactly as MrPeak reported!

    I’ve corrected the firmware. Before I release though I should update the apps to make firmware updates opt-in instead of opt-out, because I don’t think this change merits the struggle of a firmware update for most users.

    Thank you again for your diagnosis – please email me if I can send you any swag (test leads? extra cases?), I really appreciate the help.

    ~James

  • in reply to: Magic Blue Smoke (and flat batteries) #19660

    James
    Keymaster

    Hi Guy,

    Thanks for the description. I think the part you’re describing is this one:

    Which is part of this circuit:

    This is there to protect the meter from the batteries being reversed. Clearly this component has failed on your PCB, and it sounds like it has failed in a short circuit. This should not have happened. Email me with shipping info and I’ll get you a replacement. Or if you’re comfortable soldering and want to attempt a repair, the rest of the circuit might be intact: remove the offending component and bridge across these pads:

    This will bypass the reverse battery protection. Best
    ~James

    • This reply was modified 1 year, 9 months ago by  James.
  • in reply to: James – help! Need replacement circuit board #19654

    James
    Keymaster

    Wait! It’s my fault. Found your emails in the spam folder, not sure why they ended up there. I changed my filter rules so it won’t happen again and am replying to you now.

    My mistake, sorry!
    ~James

  • in reply to: James – help! Need replacement circuit board #19653

    James
    Keymaster

    Hi Mark! I just replied in the other thread, I don’t see any emails from you. Please make sure you’re sending to hello@moosh.im or james@moosh.im and I will arrange this for you.

    ~James

  • in reply to: Defective product, not too impressed with company support #19651

    James
    Keymaster

    Hi Mark – I apologize, I don’t see any emails from the address listed on your comment (it’s not publicly available but since I’m site admin I can see it). Where have you been sending messages?

    Also – thank you for the kind words and I’m glad you’re enjoying the product :) It’s actually a 1 person company.

    Best
    ~James

    • This reply was modified 1 year, 9 months ago by  James.
  • in reply to: Updating firmware #19597

    James
    Keymaster

    Hi Johnathan,

    99% of the time, firmware update failure is due to low battery on the Mooshimeter. Can you try with a fresh set of batteries?

    Also, the upgrade process is usually more reliable from an Apple device than Android, so if you have easy access to an iPhone or iPad I suggest giving that a try as well.

    ~James

  • in reply to: Firmware #19559

    James
    Keymaster

    Hi Aaron,

    Sorry for slow response on this. I think you’re getting hit with the issue where Android/iOS caches the services offered by the device and shows the meter in bootloader mode when it really isn’t. You can verify the status of the meter by looking at the LED on the device. If it’s flashing slowly 1sec on, 1sec off, it’s in bootloader mode. If it is not in bootloader mode, try rebooting the phone and reconnecting.

    Thanks
    ~James

  • in reply to: Unable to resurrect mooshimeter after changing dead batteries #19516

    James
    Keymaster

    Hi Paul,

    It sounds like you’ve done everything I would suggest, sorry for the trouble! Please email me at hello@moosh.im with your shipping address and I’ll get you a replacement ASAP.

    Sorry for the trouble,
    ~James

Viewing 15 posts - 1 through 15 (of 642 total)