search

geeekpi / upsplus

UPS Plus is a new generation of UPS power management module. It is an improved version of the original UPS prototype. It has been fixed the bug that UPS could not charge and automatically power off during work time. It can not only perform good battery power management, but also provide stable voltage output and RTC functions. At the same time,it support for FCP, AFC, SFCP fast charge protocol, support BC1.2 charging protocol, support battery terminal current/voltage monitoring and support two-way monitoring of charge and discharge. It can provide programmable PVD function. Power Voltage Detector (PVD) can be used to detect if batteries voltage is below or above configured voltage. Once this function has been enabled, it will monitoring your batteries voltage, and you can control whether or not shut down Raspberry Pi via simple bash script or python script. This function will protect your batteries from damage caused by excessive discharge. It can provide Adjustable data sampling Rate. This function allows you to adjust the data sampling rate so that you can get more detailed battery information and also it will consume some power. The data sampling information can communicate with the upper computer device through the I2C protocol. UPS Plus supports the OTA firmware upgrade function. Once there is a new firmware update, it is very convenient for you to upgrade firmware for UPS Plus. The firmware upgrade can be completed only by connecting to the Internet,and execute a python script. Support battery temperature monitoring and power-down memory function. UPS Plus can be set to automatically start the Raspberry Pi after the external power comes on. The programmable shutdown and forced restart function will provide you with a remote power-off restart management method. That means you don’t need to go Unplug the power cable or press the power button to cut off the power again. You can set the program to disconnect the power supply after a few seconds after the Raspberry Pi is shut down properly. And you can also reconnect the power supply after a forced power failure to achieve a remote power-off and restart operation. Once it was setting up, you don't need to press power button to boot up your device which is very suitable for smart home application scenarios.
https://wiki.52pi.com/index.php?title=UPS_Plus_SKU:_EP-0136
MIT License
73 stars 25 forks source link

[Feature Request] Maximum battery charge limit #16

Closed leandroalbero closed 3 years ago

leandroalbero commented 3 years ago

Hello, lots of phone or laptop manufacturers are including optimised battery charging into their devices. What this does is halt charge at around 80% instead of holding the battery cells at 100% charge during long periods of time. This greatly reduces battery ageing. Is it possible to do this via software on upsplus?

nickfox-taterli commented 3 years ago

At the moment is to try to keep it around 95%, that is why always see in the charge, we are considering a more optimal battery protection method, if you have reference to the open source project, you can also recommend us.

leandroalbero commented 3 years ago

9B8AEE37-2AE6-4F68-956B-C7BE74FD41D0 Maybe it is possible to set the battery type (VSET) via the raspberry pi and thus lower the charge threshold. Don't know much about how this product is built, I was just asking if theres any chance of limiting the maximum charge via software. Thanks!

nickfox-taterli commented 3 years ago

Due to the characteristics of the battery, it will be used for the first time as heavy as possible to the highest voltage (charging current of less than 10mA considered full), and then dynamically set the VSET, we plan to design a function that can use software control VSET, which is supported in the hardware design (PCB Version > PCB01b), which generally affects the 80% to 100% charging stage.

nickfox-taterli commented 3 years ago

We have developed a feature(beta), please update the firmware to version 7, to add a new register FixedVbat (Reg Addr:0x2A), when set to 1, the Full Voltage and Empty Voltage registers are(must) manually edited,when FixedVbat is 1,make the battery Full Voltage always lower than Full Voltage, but Full Voltage only can be set to 4200mV or upper, which is the charge management chip lower-limit.

tokp commented 3 years ago

Could you put a example to write and read these values?

I thin to enable FixedVBat it can be "bus.write_byte_data(DEVICE_ADDR, 42, 1)", and to set and read the full/empty voltage?

nickfox-taterli commented 3 years ago

After you execute "bus.write_byte_data(DEVICE_ADDR, 42, 1)", you can adjust the [ Full Voltage and Empty Voltage registers ] registers manually, if you execute "bus.write_byte_data(DEVICE_ADDR, 42, 0)", the firmware will adjust them automatically, the automatic adjustment means that the battery maximum voltage is full and the minimum voltage is empty, regardless of the automatic or manual setting, the battery enters trickle charge mode when it reaches 90%.

Serhii020472 commented 3 years ago 
Updated to version 7 and.... not changed [Full Voltage] [Empty Voltage]

pi@raspberrypi:~/bin $ i2cget -y 1 0x17 0x28 w
0x0007
pi@raspberrypi:~/bin $ i2cget -y 1 0x17 0x2A b
0x01
pi@raspberrypi:~/bin $ i2cget -y 1 0x17 0x0D w
0x1082
pi@raspberrypi:~/bin $ i2cget -y 1 0x17 0x0F w
0x102e
pi@raspberrypi:~/bin $ i2cget -y 1 0x17 0x11 w
0x0e10
pi@raspberrypi:~/bin $ i2cset -y 1 0x17 0x0D 0x1078 w
pi@raspberrypi:~/bin $ i2cset -y 1 0x17 0x0F 0x0D48 w
pi@raspberrypi:~/bin $ i2cset -y 1 0x17 0x11 0x0F55 w
pi@raspberrypi:~/bin $ i2cget -y 1 0x17 0x0D w
0x1082
pi@raspberrypi:~/bin $ i2cget -y 1 0x17 0x0F w
0x102e
pi@raspberrypi:~/bin $ i2cget -y 1 0x17 0x11 w
0x0f55
deHarro commented 3 years ago

@Serhii020472 Can you please edit your posting to show all lines as they are (without strike through). To achive this you should select all your text and then click on teh icon with "<>" in the caption bar of the edit box.

Like this: grafik

Thanks! Harry

deHarro commented 3 years ago

Hi @nickfox-taterli I updated my UPS to FW 7. After reboot I wrote a short Python script to set the voltages as you described above.

# set_Vfull_Vempty.py

import smbus2

DEVICE_BUS = 1
DEVICE_ADDR = 0x17
SAMPLE_TIME = 1

# new values for Full Voltage and Empty Voltage parameters
FULLVOLTAGE = 4200
EMPTYVOLTAGE = 3700

bus = smbus2.SMBus(DEVICE_BUS)

# enable writing to Full Voltage and Empty Voltage registers
bus.write_byte_data(DEVICE_ADDR, 42,1)

# write to the now enabled registers for Full Voltage and Empty Voltage
print("Set Full Voltage register to: %d" % FULLVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 13, FULLVOLTAGE)
print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE)

# check result
print("FixedVbat register is: %d" %  bus.read_byte_data(DEVICE_ADDR, 42))

print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13))
print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15))

The corresponding output is:

~/bin $ python set_Vfull_Vempty.py
Set Full Voltage register to: 4200
Set Empty Voltage register to: 3700
FixedVbat register is: 1
Full Voltage register is: 4293
Empty Voltage register is: 3601

The voltages are not altered, they remain as set by the firmware.

Is the procedure I implemented in my script correct? Thanks!

Harry

deHarro commented 3 years ago

@nickfox-taterli Any idea on that?

Harry

leandroalbero commented 3 years ago

Hi @nickfox-taterli I updated my UPS to FW 7. After reboot I wrote a short Python script to set the voltages as you described above.

# set_Vfull_Vempty.py

import smbus2

DEVICE_BUS = 1
DEVICE_ADDR = 0x17
SAMPLE_TIME = 1

# new values for Full Voltage and Empty Voltage parameters
FULLVOLTAGE = 4200
EMPTYVOLTAGE = 3700

bus = smbus2.SMBus(DEVICE_BUS)

# enable writing to Full Voltage and Empty Voltage registers
bus.write_byte_data(DEVICE_ADDR, 42,1)

# write to the now enabled registers for Full Voltage and Empty Voltage
print("Set Full Voltage register to: %d" % FULLVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 13, FULLVOLTAGE)
print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE)

# check result
print("FixedVbat register is: %d" %  bus.read_byte_data(DEVICE_ADDR, 42))

print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13))
print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15))

The corresponding output is:

~/bin $ python set_Vfull_Vempty.py
Set Full Voltage register to: 4200
Set Empty Voltage register to: 3700
FixedVbat register is: 1
Full Voltage register is: 4293
Empty Voltage register is: 3601

The voltages are not altered, they remain as set by the firmware.

Is the procedure I implemented in my script correct? Thanks!

Harry

Hello, same result here:

pi@raspberrypi:~/upsplus$ python3 prueba.py 
Set Full Voltage register to: 4200
Set Empty Voltage register to: 3700
FixedVbat register is: 1
Full Voltage register is: 4284
Empty Voltage register is: 3700
nickfox-taterli commented 3 years ago

assign to @yoyojacky for testing.

leandroalbero commented 3 years ago
image

I am using NCR18650B and according to the data-sheet its discharge-end voltage is 2.5V, I set the UPSPLUS (soft v8) empty voltage register to 3.2v to get more mAh out of the battery, but noticed that once it gets to 3.35v the battery voltage is incorrect. I measured voltage with a multimeter and it dropped as low as 2.5v. Is this a limitation of the voltmeter on the board?

Also, this does not seem to change "empty voltage" register, what am I missing?

pi@raspberrypi:~/upsplusv5-battery-logger$ i2cget -y 1 0x17 0x0f b
0xac
pi@raspberrypi:~/upsplusv5-battery-logger$ i2cget -y 1 0x17 0x10 b
0x0e
pi@raspberrypi:~/upsplusv5-battery-logger$ i2cset -y 1 0x17 0x10 0x0c
pi@raspberrypi:~/upsplusv5-battery-logger$ i2cset -y 1 0x17 0x0f 0x80
pi@raspberrypi:~/upsplusv5-battery-logger$ i2cget -y 1 0x17 0x0f w
0x0eac
pi@raspberrypi:~/upsplusv5-battery-logger$ 
pi@raspberrypi:~/upsplusv5-battery-logger$ i2cdump -y 1 0x17
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: 01 e7 0c 85 13 6b 10 ca 12 0c 00 2e 00 bc 10 ac    ?????k????...???
10: 0e 80 0c 60 00 1e 00 01 00 01 00 00 88 5a 00 00    ???`.?.?.?..?Z..
20: fc f0 00 00 2a 16 00 00 08 00 01 00 00 00 00 00    ??..*?..?.?.....
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
pi@raspberrypi:~/upsplusv5-battery-logger$
ArjenR49 commented 3 years ago

I have the same sort of batteries and in v.7 or earlier there was no problem going so low and have the ups Shut off when the batteries got discharged. I would say it is not a hardware limitation. V.8 brought changes but not for the better ... Type journalctl -f in a terminal and have a good look there.

Arjen (On The Road)

Op di 1 jun. 2021 13:50 schreef Leandro Albero @.***>:

[image: image] https://user-images.githubusercontent.com/12993089/120310570-d0fd8e80-c2d6-11eb-96f6-ec9f074867e9.png I am using NCR18650B and according to the data-sheet its discharge-end voltage is 2.5V, I set the UPSPLUS (soft v8) empty voltage register to 3.2v to get more mAh out of the battery, but noticed that once it gets to 3.35v the battery voltage is incorrect. I measured voltage with a multimeter and it dropped as low as 2.5v. Is this a limitation of the voltmeter on the board?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/geeekpi/upsplus/issues/16#issuecomment-852026740, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANCBKNT4UKZFYH4AIXQSBCTTQS3PXANCNFSM44O6EFTA .

leandroalbero commented 3 years ago

I have the same sort of batteries and in v.7 or earlier there was no problem going so low and have the ups Shut off when the batteries got discharged. I would say it is not a hardware limitation. V.8 brought changes but not for the better ... Type journalctl -f in a terminal and have a good look there. Arjen (On The Road) Op di 1 jun. 2021 13:50 schreef Leandro Albero @.***>: …

Have tried using journalctl -f while using i2cset, but I can't find any errors related to that command. Setting 0x10 register to 0x0c and confirming value not changed:

pi@raspberrypi:~$ i2cset -y 1 0x17 0x10 0x0c
pi@raspberrypi:~$ i2cget -y 1 0x17 0x10 b
0x00

journalctl output after above i2cset:

Jun 01 15:31:03 raspberrypi CRON[752]: (CRON) info (No MTA installed, discarding output)            
Jun 01 15:31:03 raspberrypi CRON[752]: pam_unix(cron:session): session closed for user pi
nickfox-taterli commented 3 years ago

In addition, the protection voltage is determined by the protection voltage register, and the output will be turned off when the protection voltage is reached, the minimum voltage is used for battery estimation, not the shutdown function.

Please set the registers in order, for example, 0x0F and 0x10 are a group.

If your goal is to use more power, set a lower protection voltage as your request.

leandroalbero commented 3 years ago
  • I just tested with the script provided in our repo, set the protection voltage 3700 mV, the battery cut off smoothly.
  • Then change the protection to 3500 mV (readback to check) and run stress -c 4 to pressurize the system.
  • reach the protection voltage, smoothly cut off the power, using a multimeter to measure the voltage, indicating that the battery has 3.51V.

In addition, the protection voltage is determined by the protection voltage register, and the output will be turned off when the protection voltage is reached, the minimum voltage is used for battery estimation, not the shutdown function.

Please set the registers in order, for example, 0x0F and 0x10 are a group.

If your goal is to use more power, set a lower protection voltage as your request.

I understand, but my problem is that none of the registers seem to get modified. Have tried manually using i2cset, also tried modifying protection voltage on upsplus.py and finally tried using this script: 

# set_Vfull_Vempty.py

import smbus2

DEVICE_BUS = 1
DEVICE_ADDR = 0x17
SAMPLE_TIME = 1

# new values for Full Voltage and Empty Voltage parameters
FULLVOLTAGE = 4200
EMPTYVOLTAGE = 3700

bus = smbus2.SMBus(DEVICE_BUS)

# enable writing to Full Voltage and Empty Voltage registers
bus.write_byte_data(DEVICE_ADDR, 42,1)

# write to the now enabled registers for Full Voltage and Empty Voltage
print("Set Full Voltage register to: %d" % FULLVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 13, FULLVOLTAGE)
print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE)

# check result
print("FixedVbat register is: %d" %  bus.read_byte_data(DEVICE_ADDR, 42))

print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13))
print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15))

Nothing seems to change registers going from 0x0D to 0x12, I am using version 8 of the firmware

leandroalbero commented 3 years ago

Got an unanswered question :(

tokp commented 3 years ago
  • I just tested with the script provided in our repo, set the protection voltage 3700 mV, the battery cut off smoothly.
  • Then change the protection to 3500 mV (readback to check) and run stress -c 4 to pressurize the system.
  • reach the protection voltage, smoothly cut off the power, using a multimeter to measure the voltage, indicating that the battery has 3.51V.

In addition, the protection voltage is determined by the protection voltage register, and the output will be turned off when the protection voltage is reached, the minimum voltage is used for battery estimation, not the shutdown function. Please set the registers in order, for example, 0x0F and 0x10 are a group. If your goal is to use more power, set a lower protection voltage as your request.

I understand, but my problem is that none of the registers seem to get modified. Have tried manually using i2cset, also tried modifying protection voltage on upsplus.py and finally tried using this script:

# set_Vfull_Vempty.py

import smbus2

DEVICE_BUS = 1
DEVICE_ADDR = 0x17
SAMPLE_TIME = 1

# new values for Full Voltage and Empty Voltage parameters
FULLVOLTAGE = 4200
EMPTYVOLTAGE = 3700

bus = smbus2.SMBus(DEVICE_BUS)

# enable writing to Full Voltage and Empty Voltage registers
bus.write_byte_data(DEVICE_ADDR, 42,1)

# write to the now enabled registers for Full Voltage and Empty Voltage
print("Set Full Voltage register to: %d" % FULLVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 13, FULLVOLTAGE)
print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE)

# check result
print("FixedVbat register is: %d" %  bus.read_byte_data(DEVICE_ADDR, 42))

print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13))
print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15))

Nothing seems to change registers going from 0x0D to 0x12, I am using version 8 of the firmware

I have the same issue

nickfox-taterli commented 3 years ago

Please write byte by byte, please follow the example in the example to write two data byte by byte.

--------------原始邮件-------------- 发件人："tokp @.>; 发送时间：2021年6月16日(星期三) 凌晨4:27 收件人："geeekpi/upsplus" @.>; 抄送："Tater Li @.>;"State change @.>; 主题：Re: [geeekpi/upsplus] [Feature Request] Maximum battery charge limit (#16)

I just tested with the script provided in our repo, set the protection voltage 3700 mV, the battery cut off smoothly.

Then change the protection to 3500 mV (readback to check) and run stress -c 4 to pressurize the system.

reach the protection voltage, smoothly cut off the power, using a multimeter to measure the voltage, indicating that the battery has 3.51V.

In addition, the protection voltage is determined by the protection voltage register, and the output will be turned off when the protection voltage is reached, the minimum voltage is used for battery estimation, not the shutdown function. Please set the registers in order, for example, 0x0F and 0x10 are a group. If your goal is to use more power, set a lower protection voltage as your request.

I understand, but my problem is that none of the registers seem to get modified. Have tried manually using i2cset, also tried modifying protection voltage on upsplus.py and finally tried using this script:

set_Vfull_Vempty.py import smbus2 DEVICE_BUS = 1 DEVICE_ADDR = 0x17 SAMPLE_TIME = 1 # new values for Full Voltage and Empty Voltage parameters FULLVOLTAGE = 4200 EMPTYVOLTAGE = 3700 bus = smbus2.SMBus(DEVICE_BUS) # enable writing to Full Voltage and Empty Voltage registers bus.write_byte_data(DEVICE_ADDR, 42,1) # write to the now enabled registers for Full Voltage and Empty Voltage print("Set Full Voltage register to: %d" % FULLVOLTAGE) bus.write_word_data(DEVICE_ADDR, 13, FULLVOLTAGE) print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE) bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE) # check result print("FixedVbat register is: %d" % bus.read_byte_data(DEVICE_ADDR, 42)) print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13)) print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15))

Nothing seems to change registers going from 0x0D to 0x12, I am using version 8 of the firmware

I have the same issue

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

ArjenR49 commented 3 years ago

I have the same problem and I never used word write nor read. Always taking the value to be written apart in LSB and MSB and then write the bytes one by one. LSB first to lower address.

I have a similar setting program for protection voltage and sampling interval. One works, the other not. I forgot which, since so much time has passed and no new f/w version has come. I think it was the voltage setting that didn't work. Fortunately I have a sensible values there already.

I am not using the UPS Plus now. It's just sitting there under my Pi doing @.*** crunching. Not UPS scripts installed at all now. The UPS with v.8 as it is now cannot protect against power failure because the scripts cannot write to the i2c registers.

With v.7 we didn't have this problem.

Op 16-06-2021 om 04:14 schreef Tater Li:

Please write byte by byte, please follow the example in the example to write two data byte by byte.

--------------原始邮件-------------- 发件人："tokp @.>; 发送时间：2021年6月16日(星期三) 凌晨4:27 收件人："geeekpi/upsplus" @.>; 抄送："Tater Li @.>;"State change @.>; 主题：Re: [geeekpi/upsplus] [Feature Request] Maximum battery charge limit (#16)

I just tested with the script provided in our repo, set the protection voltage 3700 mV, the battery cut off smoothly.

Then change the protection to 3500 mV (readback to check) and run stress -c 4 to pressurize the system.

reach the protection voltage, smoothly cut off the power, using a multimeter to measure the voltage, indicating that the battery has 3.51V.

In addition, the protection voltage is determined by the protection voltage register, and the output will be turned off when the protection voltage is reached, the minimum voltage is used for battery estimation, not the shutdown function. Please set the registers in order, for example, 0x0F and 0x10 are a group. If your goal is to use more power, set a lower protection voltage as your request.

I understand, but my problem is that none of the registers seem to get modified. Have tried manually using i2cset, also tried modifying protection voltage on upsplus.py and finally tried using this script:

set_Vfull_Vempty.py import smbus2 DEVICE_BUS = 1 DEVICE_ADDR = 0x17

SAMPLE_TIME = 1 # new values for Full Voltage and Empty Voltage parameters FULLVOLTAGE = 4200 EMPTYVOLTAGE = 3700 bus = smbus2.SMBus(DEVICE_BUS) # enable writing to Full Voltage and Empty Voltage registers bus.write_byte_data(DEVICE_ADDR, 42,1) # write to the now enabled registers for Full Voltage and Empty Voltage print("Set Full Voltage register to: %d" % FULLVOLTAGE) bus.write_word_data(DEVICE_ADDR, 13, FULLVOLTAGE) print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE) bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE) # check result print("FixedVbat register is: %d" % bus.read_byte_data(DEVICE_ADDR, 42)) print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13)) print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15)) Nothing seems to change registers going from 0x0D to 0x12, I am using version 8 of the firmware

I have the same issue

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/geeekpi/upsplus/issues/16#issuecomment-861935329, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANCBKNUEW7X3SANCAQOPX2TTS73GZANCNFSM44O6EFTA.

tokp commented 3 years ago

Please write byte by byte, please follow the example in the example to write two data byte by byte. … --------------原始邮件-------------- 发件人："tokp @.>; 发送时间：2021年6月16日(星期三) 凌晨4:27 收件人："geeekpi/upsplus" @.>; 抄送："Tater Li @.>;"State change @.>; 主题：Re: [geeekpi/upsplus] [Feature Request] Maximum battery charge limit (#16) ----------------------------------- I just tested with the script provided in our repo, set the protection voltage 3700 mV, the battery cut off smoothly. Then change the protection to 3500 mV (readback to check) and run stress -c 4 to pressurize the system. reach the protection voltage, smoothly cut off the power, using a multimeter to measure the voltage, indicating that the battery has 3.51V. In addition, the protection voltage is determined by the protection voltage register, and the output will be turned off when the protection voltage is reached, the minimum voltage is used for battery estimation, not the shutdown function. Please set the registers in order, for example, 0x0F and 0x10 are a group. If your goal is to use more power, set a lower protection voltage as your request. I understand, but my problem is that none of the registers seem to get modified. Have tried manually using i2cset, also tried modifying protection voltage on upsplus.py and finally tried using this script: # set_Vfull_Vempty.py import smbus2 DEVICE_BUS = 1 DEVICE_ADDR = 0x17 SAMPLE_TIME = 1 # new values for Full Voltage and Empty Voltage parameters FULLVOLTAGE = 4200 EMPTYVOLTAGE = 3700 bus = smbus2.SMBus(DEVICE_BUS) # enable writing to Full Voltage and Empty Voltage registers bus.write_byte_data(DEVICE_ADDR, 42,1) # write to the now enabled registers for Full Voltage and Empty Voltage print("Set Full Voltage register to: %d" % FULLVOLTAGE) bus.write_word_data(DEVICE_ADDR, 13, FULLVOLTAGE) print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE) bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE) # check result print("FixedVbat register is: %d" % bus.read_byte_data(DEVICE_ADDR, 42)) print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13)) print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15)) Nothing seems to change registers going from 0x0D to 0x12, I am using version 8 of the firmware I have the same issue — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

I have update my script to use byte by byte and still have same issues. A sample of my script:

import smbus2

DEVICE_BUS = 1
DEVICE_ADDR = 0x17
FULLVOLTAGE = 4200
EMPTYVOLTAGE = 3300

bus = smbus2.SMBus(DEVICE_BUS)

bus.write_byte_data(DEVICE_ADDR, 42,1)

print("Set Full Voltage register to: %d" % FULLVOLTAGE)
bus.write_byte_data(DEVICE_ADDR, 13, FULLVOLTAGE & 0xFF)
bus.write_byte_data(DEVICE_ADDR, 14, (FULLVOLTAGE >> 8)& 0xFF)
print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE)

print("FixedVbat register is: %d" %  bus.read_byte_data(DEVICE_ADDR, 42))

print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13))
print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15))
mmaga commented 2 years ago

Please write byte by byte, please follow the example in the example to write two data byte by byte. … --------------原始邮件-------------- 发件人："tokp @.**>; 发送时间：2021年6月16日(星期三) 凌晨4:27 收件人："geeekpi/upsplus" @.**>; 抄送："Tater Li @.**>;"State change @.**>; 主题：Re: [geeekpi/upsplus] [Feature Request] Maximum battery charge limit (#16) ----------------------------------- I just tested with the script provided in our repo, set the protection voltage 3700 mV, the battery cut off smoothly. Then change the protection to 3500 mV (readback to check) and run stress -c 4 to pressurize the system. reach the protection voltage, smoothly cut off the power, using a multimeter to measure the voltage, indicating that the battery has 3.51V. In addition, the protection voltage is determined by the protection voltage register, and the output will be turned off when the protection voltage is reached, the minimum voltage is used for battery estimation, not the shutdown function. Please set the registers in order, for example, 0x0F and 0x10 are a group. If your goal is to use more power, set a lower protection voltage as your request. I understand, but my problem is that none of the registers seem to get modified. Have tried manually using i2cset, also tried modifying protection voltage on upsplus.py and finally tried using this script: # set_Vfull_Vempty.py import smbus2 DEVICE_BUS = 1 DEVICE_ADDR = 0x17 SAMPLE_TIME = 1 # new values for Full Voltage and Empty Voltage parameters FULLVOLTAGE = 4200 EMPTYVOLTAGE = 3700 bus = smbus2.SMBus(DEVICE_BUS) # enable writing to Full Voltage and Empty Voltage registers bus.write_byte_data(DEVICE_ADDR, 42,1) # write to the now enabled registers for Full Voltage and Empty Voltage print("Set Full Voltage register to: %d" % FULLVOLTAGE) bus.write_word_data(DEVICE_ADDR, 13, FULLVOLTAGE) print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE) bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE) # check result print("FixedVbat register is: %d" % bus.read_byte_data(DEVICE_ADDR, 42)) print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13)) print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15)) Nothing seems to change registers going from 0x0D to 0x12, I am using version 8 of the firmware I have the same issue — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

I have update my script to use byte by byte and still have same issues. A sample of my script:

import smbus2

DEVICE_BUS = 1
DEVICE_ADDR = 0x17
FULLVOLTAGE = 4200
EMPTYVOLTAGE = 3300

bus = smbus2.SMBus(DEVICE_BUS)

bus.write_byte_data(DEVICE_ADDR, 42,1)

print("Set Full Voltage register to: %d" % FULLVOLTAGE)
bus.write_byte_data(DEVICE_ADDR, 13, FULLVOLTAGE & 0xFF)
bus.write_byte_data(DEVICE_ADDR, 14, (FULLVOLTAGE >> 8)& 0xFF)
print("Set Empty Voltage register to: %d" % EMPTYVOLTAGE)
bus.write_word_data(DEVICE_ADDR, 15, EMPTYVOLTAGE)

print("FixedVbat register is: %d" %  bus.read_byte_data(DEVICE_ADDR, 42))

print("Full Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 13))
print("Empty Voltage register is: %d" % bus.read_word_data(DEVICE_ADDR, 15))

@tokp, @ArjenR49 , @leandroalbero, @deHarro

I managed this script to work adding time.sleep(1) after each bus.write_byte_data() :-)

Sleeping time worked on avoiding Remote I/O error (#121), even when reading a long sequence of bytes from the I2C interface.

The fixes are:

import time ... bus.write_byte_data(DEVICE_ADDR, 42, 1) time.sleep(1) bus.write_byte_data(DEVICE_ADDR, 13,FULLVOLTAGE & 0xFF) time.sleep(1) bus.write_byte_data(DEVICE_ADDR, 14,(FULLVOLTAGE >> 8)& 0xFF) time.sleep(1) bus.write_byte_data(DEVICE_ADDR, 15,EMPTYVOLTAGE & 0xFF) time.sleep(1) bus.write_byte_data(DEVICE_ADDR, 16,(EMPTYVOLTAGE >> 8)& 0xFF) time.sleep(1) ...

Cheers!