I recently was gifted a PokitMeter (HW 1.7, FW 1.4), but so far had mediocre experience with it. I am working on a LG G6 / Samsung S7 both with Android 9. I can connect to it and read measurements, however there are apparently some serious software bugs (Software 1.1.0) - or the device itself is horribly broken (but I highly suspect the software).
On both phones, the issues that keep me from using the PokitMeter are identical:
* Frequent disconnects/reconnects, between every 5-20 seconds, in any mode
* By this, an update to FW 1.5 is impossible
* Probably also caused by this, Trigger issues in oscilloscope mode (suddenly not triggering in auto or in manual when it was already working the measurement seconds before, works again after e.g. restarting the oscilloscope mode)
* The division labels in oscilloscope mode are wrong. E.g. it's written 400 mS/Div for a 1 mS time window when it should be written 400 µS/Div. I assume that the displayed unit/div is for some reason 1 magnitude higher than it should be based on the data: mS/div when it should be µS/div, S/div when it should be mS/div, and still S/div for S/div window (but e.g. 400 S/div for a 1 S/div window). This is consistent throughout all time-ranges
* Maybe partially coupled to the aforementioned issue, scaling the frequency window in frequency mode does not work at all. It is set to 100 Hz standard and cannot be changed since the wheel, which is working for the time-window, does not work for frequencies. I am unable to detect e.g. the base frequency of a 10 kHz square PWM signal due to this.
* Zoom in oscilloscope along the time-axis is limited to 400 mS/div (or as it should be properly displayer: 400 µS/Div). It's not possible to zoom in more, like 10 µS/Div, although the device can measure higher frequencies than just a few kHz. Also videos of previous versions showed lower time/div settings than 400 µS/div.
Edit: I now also double-checked with my Surface Go and JDon's Windows App (thanks a lot for the effort @JDon). The read-out of the temperature apparently works without any disconnect/reconnect issues, no blue LED blinking to indicate a reconnect as with using my Android phones, no interruptions of measurements observed. Using the phones after, the issues are back. So I guess the Android version 1.1.0 seems to be the overall issue.
Please sign in to leave a comment.