Bugs or feature

Support for the UPS PIco HV3.0A Plus and UPS PIco HV3.0B Plus

Bugs or feature

Postby Sailor » Fri Sep 08, 2017 9:02 pm

Dear PicoUps Development Team

I am an (almost) satisfied customer of your
Hardware: UpsPico HV 3.0 Plus with a 8000mAh LiFePO4 - Q
Firmware: 0x35

I have been programming an module for this UpsPico for the fhem home automation and I am about to release the module.
Refer: http://fhem.de/fhem.html

However I found some bugs/problems on my UpsPico and I wonder whether you might already know about them or whether you have an explanation for them.

Thanks a lot

Sailor

#########################################################################################################
Register Block: Start Time Stamp
Register Name: active
Chip Address: 0x6c
Register: 0x00

Problem: The command „sudo i2cget -y 1 0x6c 0x00 b“ results in 0x00 => „not active“
The dump command shows however

pi@DoorStation:~ $ sudo i2cdump -y -r 0-255 1 0x6c
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 80 00 00 00 00 00 00 ff ff ff ff ff ff ff ff ff ?...............
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
which is 0x80 = 0b11110000 => undefined

However, if I enter the original command straight after it shows in that order

pi@DoorStation:~ $ sudo i2cget -y 1 0x6c 0x00 b
0x80
pi@DoorStation:~ $ sudo i2cget -y 1 0x6c 0x00 b
0x00
pi@DoorStation:~ $ sudo i2cget -y 1 0x6c 0x00 b
0x00

#########################################################################################################

Register Block: Module Status
Register Name: key
Chip Address: 0x69
Register: 0x1a

Problem: If I do not press any key and enter the command „sudo i2cget -y 1 0x69 0x1a b“ results in 0x01 => „Key A pressed“
If I press and hold the Key A and enter the command „sudo i2cget -y 1 0x69 0x1a b“ results in 0x02 => „Key B pressed“
If I press and hold the Key B and enter the command „sudo i2cget -y 1 0x69 0x1a b“ results in 0x02 => „Key B pressed“
If I press and hold the Key C and enter the command „sudo i2cget -y 1 0x69 0x1a b“ results in 0x03 => „Key C pressed“

#########################################################################################################

Register Block: Module Status
Register Name: batlevel
Chip Address: 0x69
Register: 0x08

Problem: The values are, after correction, only in 0.1V Steps between 2.9V (0%) and 3.6V (100%) = 0.7V.
That means the charging steps are 16% per step.
Is there a possibility to raise the accuracy to 0.01V Steps?
Sailor
 
Posts: 4
Joined: Sun Jun 18, 2017 7:35 pm

Return to UPS PIco HV3.0A Plus and HV3.0B Plus

Who is online

Users browsing this forum: No registered users and 1 guest

cron