Page 2 of 2

Re: Different value in "upis" (PiCO) vs serial @status call

Posted: Fri Oct 17, 2014 4:02 am
by Pimaster
Kai wrote:Just for consideration:

a) Could that spikes be related to the data transfer of the I2C Interface itself. It uses pull-ups (but these are usually in the 1 to 10 K Ohm range)

b) I have also seen in other applications during the I2C-Ack cycle a pin-driver crash generating a high current spike due to wrong timing (usually the sink is stronger and thus the software works fine since it sees the Slave-Ack).

Hi,

It could be, and for that reason, we need to setup a special testing workbench to analyze it in very depth. For that reason we kindly asking to be patient, as far it not affect the system functionality.

Warmest Regards
Pi Master

Re: Different value in "upis" (PiCO) vs serial @status call

Posted: Sat Jan 17, 2015 11:13 am
by flyvert
Pimaster wrote:... For that reason we kindly asking to be patient ...

Warmest Regards
Pi Master
Three months have passed, have you been able to find the reason for the discrepancy between PiCO vs @STATUS methods to poll for volts, amps, etc info?

/f

Re: Different value in "upis" (PiCO) vs serial @status call

Posted: Fri Feb 06, 2015 8:20 pm
by Pimaster
Hi,

It could be, however we will be able to work on it when finished the firmware Version 2.0, as we changed practically everything, and many thing are similar to the PIco.

My Warmest Regards
Pi Master

Re: Different value in "upis" (PiCO) vs serial @status call

Posted: Sun Feb 08, 2015 12:48 pm
by pepino
I installed firmware version 1.096.
The value that gives me the serial port for EPR is 00.00V. This values is correct. But if I see that value using i2c me back 0.99V. Why are not equal???

Re: Different value in "upis" (PiCO) vs serial @status call

Posted: Mon Mar 16, 2015 8:08 am
by Pimaster
Hi, Bug in the firmware. Or rather on the RS232 readings the values are smoothed, on the I2C reading are as it is. Will be corrected in the ongoing version 2.0

BR PiM