Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] NUC-UPS write dumped settings breaks the settings #11

Open
RafaelKa opened this issue Oct 11, 2022 · 5 comments
Open

[BUG] NUC-UPS write dumped settings breaks the settings #11

RafaelKa opened this issue Oct 11, 2022 · 5 comments

Comments

@RafaelKa
Copy link

After running
openups -t nucups -o NUCUPS_SETTINGS

the file ("NUCUPS_SETTINGS") contains:

NUC_UPS_MODE=0
UPS_ON_BATTERY_TOUT=00:00:20
INIT_TOUT=1000
VIN_MIN_STARTUP=11000
VIN_MIN_RUNNING=8000
VIN_COUNT=100
IGN_COUNT=100
IGN_HIGH_THRESHOLD=6000
IGN_LOW_THRESHOLD=5000
IGN_ON_TO_OUTPUT_ON_TOUT=2000
IGN_CANCEL_TOUT=60
OUTPUT_ON_TO_MOB_PULSE_ON_TOUT=20
IGN_OFF_TO_MOB_PULSE_OFF_TOUT=5
IOUT_OFFSET=0
MOB_PULSEWIDTH=500
HARD_OFF_TOUT=60
CONFIG1=00000111
CONFIG2=00000000
CAPACITY=3600
UPS_BUTTON_ON_TOUT=100
UPS_VCELL_MIN_START=3600
UPS_VCELL_MIN_STOP=3300
UPS_VCELL_MIN_HARD_STOP=3000
UPS_OVERLOAD=6000
DCHG_TEMP_COLD=-20
DCHG_TEMP_HOT=60
CHG_COND_TOUT=30
CHG_BULK_STOP_VOLTAGE=4100
CHG_HYSTERESIS=100
CHG_START_VOLTAGE=3850
CHG_GLOBAL_TOUT=240
CHG_TOPPING_TOUT=10800
CHG_TEMP_COLD=5
CHG_TEMP_COOL=10
CHG_TEMP_WARM=50
CHG_TEMP_HOT=55
UPS_VCELL_ADC_OFFSET=0
CHG_CELL_VCOND=3300
BAL_VCELL_MIN=3400
BAL_VCELL_DIFF_START=80
BAL_VCELL_DIFF_STOP=40
BAL_ENABLE_TOUT=72000
BAL_DISABLE_TOUT=1440
OCV_SOC0=3300
OCV_SOC10=3680
OCV_SOC25=3760
OCV_SOC50=3820
OCV_SOC75=3970
OCV_SOC100=4170
POUT_HIGH_THRESHOLD=10000
POUT_LOW_THRESHOLD=2500
WRITE_COUNT (READ ONLY)=9

Then after changing some values and write the stuff back to the UPS
and its rebooting, the values of settings are broken and following nonsense is happen:

Read configuration
NUC_UPS_MODE=0
UPS_ON_BATTERY_TOUT=00:00:00
INIT_TOUT=0
VIN_MIN_STARTUP=0
VIN_MIN_RUNNING=0
VIN_COUNT=0
IGN_COUNT=0
IGN_HIGH_THRESHOLD=0
IGN_LOW_THRESHOLD=20
IGN_ON_TO_OUTPUT_ON_TOUT=1000
IGN_CANCEL_TOUT=11000
OUTPUT_ON_TO_MOB_PULSE_ON_TOUT=80000
IGN_OFF_TO_MOB_PULSE_OFF_TOUT=0
IOUT_OFFSET=10
MOB_PULSEWIDTH=100
HARD_OFF_TOUT=6000
CONFIG1=00000101
CONFIG2=00000000
CAPACITY=0
UPS_BUTTON_ON_TOUT=0
UPS_VCELL_MIN_START=0 #################### EG: this one
UPS_VCELL_MIN_STOP=0
UPS_VCELL_MIN_HARD_STOP=0
UPS_OVERLOAD=0  #################### EG: this one
DCHG_TEMP_COLD=125
DCHG_TEMP_HOT=125
CHG_COND_TOUT=3600
CHG_BULK_STOP_VOLTAGE=10
CHG_HYSTERESIS=3600
CHG_START_VOLTAGE=3300
CHG_GLOBAL_TOUT=288
CHG_TOPPING_TOUT=3000
CHG_TEMP_COLD=-20
CHG_TEMP_COOL=-25
CHG_TEMP_WARM=125
CHG_TEMP_HOT=2
UPS_VCELL_ADC_OFFSET=3850
CHG_CELL_VCOND=240
BAL_VCELL_MIN=10800
BAL_VCELL_DIFF_START=522
BAL_VCELL_DIFF_STOP=112
BAL_ENABLE_TOUT=300
BAL_DISABLE_TOUT=35
OCV_SOC0=135
OCV_SOC10=427
OCV_SOC25=474
OCV_SOC50=0
OCV_SOC75=3300
OCV_SOC100=3400
POUT_HIGH_THRESHOLD=260181740
POUT_LOW_THRESHOLD=393220170
WRITE_COUNT (READ ONLY)=65535  ###### <- What is going on?

Why there are no protective validators for settings/options?
Why there is no option or command for "factory reset"
Is this device reliable and safe to operate with Li-Ion at all?

The NUC-UPS has the
Firmware Version: (null):
VerMajor: 1
VerMinor: 3

Why i need to write settings:
The device didn't charge the cells and was stucking on "State machine CHG: END ||| State machine UPS: LPWR(or similar)"
even worse it discharged the cells.
So i found the setting "VIN_MIN_STARTUP=20000"(is it set from factory?) and decided to switsch to 11.5V...
And now I have broken device?

@frahe-ama
Copy link

frahe-ama commented Oct 21, 2022

I have the same problem!
One fix: Flashing the firmware resets all parameters and one get a "working" device.

I also want to change some values. After doing so with a changed dump file, the NUCUPS stops charging, cause it starts to measure a voltage of > 18V in "BatPack" but "BatteryOverallVolage" is around 14.7V. This seems to happen only when parameters are written. In factory mode it seems working ok. Seems that this software write in the wrong memory areas.

This software seems to be buggy. you should not use it to write parameters.

Also the Windows software has some issues it worked only at the third computer.

@RafaelKa
Copy link
Author

@frahe-ama

Also the Windows software won't work.

Try to use the zipped binaries from "Software download" Link on https://www.mini-box.com/NUC-UPS
I vas able to connect to the NUCUPS

Flashing the firmware resets all parameters and one get a "working" device.

Which firmware and how did you flashed the NUCUPS?

@nicupavel
Where to get the Version 1.3 of NUCUPS firmware?

@RafaelKa
Copy link
Author

@nicupavel
Please prioritise this issue, because the NUCUPS device is really not usable.
Please provide the 1.3 firmware on official site.
Please provide the ability to reset the devices(not only NUCUPS) to factory reset.

Please implement the confident mechanism in firmware(ignoring all settings) to avoid deep discharge at all and specially on present DC-IN(I'm confused, why in general this happens?), because of cell blowing hazard on cells without protection circuit.

Don't disdain the Li-Ion are really dangerous on wrong usage!

@frahe-ama
Copy link

frahe-ama commented Oct 24, 2022

Which firmware and how did you flashed the NUCUPS?

Here is the "manual" for the NUCUPS: https://wiki.mini-box.com/index.php?title=NUC-UPS#Features
On this page you will find a section with description of the firmware update. There you can also find the updater and the firmware 1.3: https://wiki.mini-box.com/index.php?title=NUC-UPS#Firmware_update

@frahe-ama
Copy link

It needed three computers to get the Windows software working. I found one older device, which is possibly not on the newest updates? Don't know what the software is doing. So far it seems that the NUCUPS work as expected when configuring with Windows software.
So this Linux Software must have a big bug regarding the NUCUPS. I would not recommend it anymore for configuring the NUCUPS.
Sadly the is the issue with the Windows software not running on all Windows devices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants