Incorrect reading but only when using data logger

Answered

Aaron Power

• January 24, 2019 08:04

Connect Pokit to 24V solar batteries. Voltmeter reads correctly

 

Change to Oscilloscope mode and again it reads correctly (not very interesting as it is just a static DC voltage, but it does read :) )

 

But, when I select Data Logger mode, the voltage reading drops to around 7V

 

If I switch back to standard voltmeter, it again reads as roughly 24V. The Pokit is located inside the closed battery compartment and I am not moving the leads between tests. The results are repeatable. I have tried manually selecting the 30V range within the data logger, but no matter what, it still continues to read 7V.

1

• Official comment

  

  Pokit Support Team

  • February 04, 2019 00:07

  Hi All,

   

  This is a known Android Issue. The problem relies on the setting the correct range when in logger mode. We will provide a fix to this problem in a new app release which is due soon.

   

  Apologies for the inconvenience and hope this helps.

   

  Thanks to you all.
• 

  David Hoyle

  • January 25, 2019 21:03

  I have a similar issue.

   

  Read a 9.8 volt battery and it indicates okay at 9.6V in meter mode or o'scope mode.

   

  Use the data logger and it indicates 0.507 volts . Setting the voltage window from 10 Volts to 60 volts makes no difference. I am in DC mode as well. 

  2
• 

  Eric Udell

  • February 01, 2019 20:31

  I see the same thing as David. Getting 13.3v with the multimeter, .507v on the data logger.

  That's three of us.

  Hey Pokit, what's going on with this?

  1
• 

  David Hoyle

  • February 06, 2019 23:54

  I checked out the POKIT on an I-Phone instead of my Android (Samsung S-6) and the POKIT s/w works flawlessly on the I-phone.

   

  So  the POKIT s/w guys can just fix the s/w as it is not a hardware bug. So hopefully in the near future we just need the update!

  1
• 

  Aaron Power

  • January 26, 2019 08:41

  Thanks David. Good to know at least I'm not alone :)

  0
• 

  Phil Symonds

  • February 21, 2019 01:12

  Version 1.0.1 of the Android app fixes this bug and is rolling out now.

  0

Please sign in to leave a comment.