Archive by Author

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 100 total)
  • Author
  • in reply to: Deburring #20262


    Deburring with just about any reasonably sized somewhat hard object is the solution for that problem. I have also added pieces of kapton-tape over the holders to be sure. Its easier to fix by yourself than to document the situation for exchange process..

  • in reply to: open source firmware #20108


    As you probably know, app is already open. Many things could be improved without touching the firmware at all..

    Something like this for example:

    As an electrician, I’m a big fan of current clamps and it would be really nice to see actual current and power and not to get confused while calculating everything in my head.*

    Next step for me would be “multi-step-math”. For example to calculate short circuit currents. I would measure current and voltage with small load, save the values and measure again with bigger load and get impedance and short circuit current as a result. In this case, it would be nice to go back and forth few times and keep the stable values, so other fluctuations on the line voltage would not affect my results.

    I’m sure there would be many more requests coming your way, if you show some interest in the app and implement some feature request from this forum or from that github issue list.

    * – I have at least four different values for my current clamps, some with current and some with voltage outputs, ranging from 5:1 to 1000:1. It would be nice to just select a preset with the name of my clamp and get correct values on the screen.

    Then we should start to log what preset is in use on the phone and maybe add at least the used formula on the log files while transferring them over bluetooth.. And while waiting for more data, just add more columns and calculate correct values, so that we don’t have to do it by hand on excel/librecalc etc.. And then graph it on the phone.. And send a report to your customer. Or make it so easy, I could just send new mooshimeter to my customer and they could check that their Tesla would get enough charge over night with their current electric service ;) (not really, our law says that common people die instantly when opening any electrical cabinet)

  • in reply to: DC current with clamp #20100


    CutterSlade, I’m not sure, but that clamp might have automatic shutdown. That would kill any hopes about longer logging sessions.

    You could use aux-channel to measure voltage drop over some cabling etc that is already there on your setup and calculate current from it, if it is somehow too hard to use regular current measurement through mooshimeter (up to ~10 amps).

    It’s nice to handle mostly AC-stuff, so current is easily measured by current clamps that you could get for couple dollars/euros.. I’m still keeping my eyes open for compatible DC-clamp though, just not planning to pay very much for one.

  • in reply to: NiZn in place alkaline batteries #20089


    Hmm.. Forum probably filtered my earlier message, as it had only this link in it:

  • in reply to: Mooshimeter alone #20087


    You need a phone for setup. Ranges, sampling, logging interval etc. And for starting up logging to microsd-card. After that, you could disconnect and let the mooshimeter do its thing.

    I’m a bit paranoid about crashes and would not leave my mooshimeters unattended for much over a day, but i have had two mooshimeters logging total electrical consumption of my house for 10 days now with daily bluetooth downloads of logs. Everything seems to work just like expected. Both are on 1 minute logging intervals, but still, surprisingly stable results.

    Off topic.. I have three 30A/1V current transformers connected to voltage/aux-voltage channels and as i still had one channel available, i hooked it to one of the 230V lines. Day worth of data graphs nicely on libreoffice calc (or excel), but week is hard to do so that it is easily readable.

  • in reply to: DOA? #20061


    You said you removed batteries.. But did you try with fresh ones? Most mooshimeter problems are solved with just that.

    Does that blinking pattern react to memory card?

  • in reply to: Logging – What causes reinsertion of header rows? #20054


    I’m not sure, but i think that mooshimeter does not know where those settings came from. That auto-mode is probably just in the app, where it “suggests” what should work for the selected range. Setting those manually should not make a difference in this case.

    What were you measuring in that sample data? Did the voltage really change from 230 to 100 volts and back? There was also that 0.00 volts, which sounds unlikely, unless your leads were shorted.

    One thing popped to my mind while writing this, did you have long wires or large inductive/capacitive loads in your setup? Could it have been some spike while switching that crashed mooshimeter? That measured ~100 volts after crash might be from a floating conductor?

    Then there is our all time favorite, almost empty batteries, even if the meter states that you still have tens of percents left.

    If there is still no explanation to this behavior and logged values seem to be correct, just sort your spreadsheet by its first column and go on. It seems* that intervals survive those crashes just fine and extra headers are mostly visual problem in raw data.

    * – it might be really hard to tell what really happens on a crash and mooshimeter might just assume a short glitch and if it has lost the track of time, set the clock by the last logged line and continue hoping that everything went fine.

  • in reply to: iOS UI not stable #20002


    My mooshimeters have never met ios-devices, so i can’t really say if that is “normal” or just bad luck.

    But, there is one thing, which does help in many problems with mooshimeter.. Have you tried new batteries? Even if battery status says that there is lot of percents left. “Idle” voltage on some batteries does not degrade linearly with the available capacity and might screw the results of indicators that only check voltage, like mooshimeters. So, even if there seems to be adequate voltage left, it might dip too much when trying to do something and crash the system.

  • in reply to: Can't measure 120v AC #19997


    Easiest way to check mooshimeters (or almost any multimeter) high current fuse is to set your device on resistance and short ohm and A-connectors with your probe(s).

    Like there, on page 17:

    Mooshimeter can’t give very accurate values near zero, but it’s not that common for these better fuses to show couple ohms when failed. If you get some ohms, there is more likely problem with your probes or meter calibration etc. I just tried my mooshimeter and it said negative 0,5 ohms, which would be impossible. I assume that everything is ok.

    That fuse is only for current measurements, so it can’t affect resistance or voltage.

    • This reply was modified 1 year ago by  ville. Reason: ul-tag did something strange, i thought it was underline
  • in reply to: Can't measure 120v AC #19992


    You have samples set to manual 32. Auto offers 256.

    If i assume (60 Hz?) and calculate right, your settings let mooshimeter see about half of the sine wave you are measuring.

    If you set samples to automatic (or just 256) there would be almost 4 full waves to analyze per round. Should give better results then.

  • in reply to: logging not working #19987


    I’m on android, but i think that most things should work the same on ios.

    There are multiple reasons for empty/extra log-files to appear.. Maybe you toggled logging on/off while messing with app and ~forget, changed settings while logging was enabled, mooshimeter crashed and rebooted (it should be able to continue on same file) etc.

    You can delete logs via app, you just need to view them first for some reason. While you are transferring single file, there is a trashcan icon. Its easier to delete tens of files with pc though.

    Its not that often that i need to send my raw logs by email, but as i tried, i got to see the file just fine as attachment on gmail-app*. Maybe your email-client does not like to send stuff back to itself? What if you save that mail as a draft? Should be able to open it on another device, if email is the way you want to go.. I “share” my logs to google-drive if further processing on another device is needed.

    * – on gmail, i did not have to write whole address, after couple letters it offers right address, like always. What options does ios offer for sharing, as android gives me million choices for how to share things, not just one email-client?

  • in reply to: logging not working #19982


    Sounds like it works just as expected.

    You have found some old instructions and app/device has got some updates since those. It was hard for users to remember what settings they had for logging and you had to check things elsewhere. So it was changed to show those settings when starting to log. Now you are “forced” to check your settings to match your setup and are more likely to get what you were aiming for.

  • in reply to: How to measure 230V AC? #20036


    That firmware is quite old (I have 1522204715). Fw-updating has its problems and might took several tries, so those are not forced anymore to those of us that do not use 10 minute intervals etc.

    I get that the “Hz” setting means how frequently the instantaneous DC voltage is measured so as to figure the AC characteristics.
    But what does the “samples” setting mean?

    It just means how many of those dc-samples are taken in one go and then analyzed. For example, you need to allow mooshimeter to see a whole sine wave to calculate its rms-value, by keeping amount of samples large enough at the sample rate you have selected. You can check what mooshimeter really sees and uses as a base for calculations, if you go to graph mode -> config -> buffer mode. It then displays your sample buffer snapshots without processing.

  • in reply to: How to measure 230V AC? #20034


    Is higher Hz and higher samples always more accurate?
    Basically yes. There has been little problems with 8 kHz sampling, where you can see random spikes at random times. It might be just fine for hours or screw your whole setup. I would stay at 4 kHz and lower, if possible.

    Does it shorten battery life?
    I would guess that it depends on how long it takes to take those samples, so lowest Hz and highest samples would use more energy than max Hz and lowest samples. Shorter logging interval drains batteries faster, but you should get several days in any case.

    After initial tests …
    Which firmware/app versions do you have? There was a bug that made 10 minute intervals unusable and generated 10.176 second intervals instead. That should have been fixed a long time ago, but as most of us at this forum use beta-app, its hard to say what you really get from app/play-stores outside beta program.

  • in reply to: Continuity Beep? #20023


    Diode drop mode seems to do it. With auto on both sampling settings it was extremely slow (second channel at internal temp, so 125Hz/64smpl = beep delay seems like seconds).

    If i set sampling to 8kHz/32smpl it gets about acceptable. There is still bit of a delay, but it can (maybe, not measured) detect something like 100 milliseconds of short circuit.

    Some quess work:
    32/8000 = 4 ms set of samples, but processing+bluetooth takes just under 100 ms between sampling. ~2-100 ms minimum contact time might be enough for beep, unless it actually needs two trigger events back to back, so then it might be closer to 100-200 ms.

    If I just bounce test leads to each other, it seems to get some pretty quick touches and beep. Then there is that delay, sound would not start at the moment the probes touch, BUT it does beep after you have disconnected, so it is hard to miss that you had a connection just hundreds of milliseconds ago.

    I just tried to give it a go with real time application and checked which contacts on a relay board are NO or NC, i got reliable beeps and could not move probes any faster. In this case mooshimeter did the job way better than i first thought (as i had probably tried it in the past with just automatic sampling settings).

    Wish for better beeps, should be possible on the app side:
    It would be easier to find, and more reliable to use, if beep-mode had its own thing on the mode selection, where it would set max sample rate with least samples per round to give it some real time feel. Diode drop is so different application that most of us wont know it has a beep mode in it and those auto-settings for it wont do what we need for beeps.

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