Click here to see reports of other supported models from PiSupply.
|
When a user reports that a variable/command is not right then it will be highlighted by a red underline. Bad values/ranges/etc… will get a red dashed outline or red solid left border. The accompanying explaining comment - if provided - will be emphasized through a red dotted border on the left. |
2.8.3
Report #1 with driver pijuice (detailed comments available)
This device is known to work with driver pijuice.
You can grab a dummy-ups compliant .dev file to simulate this device clicking here.
Some more detailed comments are available after the "Known supported…" sections.
Known supported variables
This device is known to support the following variables (values are just examples):
|
battery.capacity
|
|
|
battery.charge
|
|
|
battery.charge.low
|
|
|
battery.charger.status
|
|
|
battery.current
|
Not really bad, battery is charging over GPIO with power plugged into Pi itself, not the HAT |
|
battery.packs
|
|
|
battery.packs.bad
|
|
|
battery.temperature
|
Probably a 10x factor error, and for some reason inverted (also in vendor tools, says -2*C there though - a 100x factor?) |
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.type
|
|
|
driver.debug
|
|
|
driver.flag.allow_killpower
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.state
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.current
|
Not really bad, battery is charging over GPIO with power plugged into Pi itself, not the HAT |
|
input.voltage
|
|
|
ups.date
|
HAT RTC clock not set yet |
|
ups.firmware
|
|
|
ups.mfr
|
|
|
ups.status
|
|
|
ups.time
|
|
|
ups.type
|
|
About this device
Vendor/Manufacturer information:
Report #2 with driver pijuice (detailed comments available)
This device is known to work with driver pijuice.
You can grab a dummy-ups compliant .dev file to simulate this device clicking here.
Some more detailed comments are available after the "Known supported…" sections.
Known supported variables
This device is known to support the following variables (values are just examples):
|
battery.capacity
|
|
|
battery.charge
|
|
|
battery.charge.low
|
|
|
battery.charger.status
|
|
|
battery.current
|
Not really bad, battery is charging over GPIO with power plugged into Pi itself, not the HAT |
|
battery.packs
|
|
|
battery.packs.bad
|
|
|
battery.temperature
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.type
|
|
|
driver.debug
|
|
|
driver.flag.allow_killpower
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.state
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.current
|
Not really bad, battery is charging over GPIO with power plugged into Pi itself, not the HAT; the reported current fluctuates (and even the sign changes) as the battery gets more full |
|
input.voltage
|
|
|
ups.date
|
|
|
ups.firmware
|
|
|
ups.mfr
|
|
|
ups.status
|
|
|
ups.time
|
|
|
ups.type
|
|
About this device
Vendor/Manufacturer information:
2.8.0
Report #1 with driver pijuice (detailed comments available)
This device is known to work with driver pijuice.
You can grab a dummy-ups compliant .dev file to simulate this device clicking here.
Some more detailed comments are available after the "Known supported…" sections.
Known supported variables
This device is known to support the following variables (values are just examples):
|
battery.capacity
|
|
|
battery.charge
|
|
|
battery.charge.low
|
|
|
battery.charger.status
|
|
|
battery.current
|
|
|
battery.packs
|
|
|
battery.packs.bad
|
|
|
battery.temperature
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.current
|
|
|
input.voltage
|
|
|
ups.date
|
|
|
ups.firmware
|
|
|
ups.mfr
|
|
|
ups.status
|
|
|
ups.time
|
|
|
ups.type
|
|
About this device
Reported at:
Vendor/Manufacturer information:
Further system data or configuration example:
[hat]
driver = pijuice
port = /dev/i2c-1
desc = "PiJuice HAT"Report #2 with driver pijuice (detailed comments available)
This device is known to work with driver pijuice.
You can grab a dummy-ups compliant .dev file to simulate this device clicking here.
Some more detailed comments are available after the "Known supported…" sections.
Known supported variables
This device is known to support the following variables (values are just examples):
|
battery.capacity
|
Actual battery was 1820 mAh; possibly wrong DIP switch combo was in place to configure the HAT |
|
battery.charge
|
|
|
battery.charge.low
|
|
|
battery.charger.status
|
|
|
battery.current
|
|
|
battery.packs
|
|
|
battery.packs.bad
|
|
|
battery.temperature
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.current
|
|
|
input.voltage
|
|
|
ups.date
|
|
|
ups.firmware
|
|
|
ups.mfr
|
|
|
ups.status
|
|
|
ups.time
|
|
|
ups.type
|
|
About this device
Reported at:
Vendor/Manufacturer information:
Further system data or configuration example:
[hat]
driver = pijuice
port = /dev/i2c-1
desc = "PiJuice HAT"Report #3 with driver pijuice (detailed comments available)
This device is known to work with driver pijuice.
You can grab a dummy-ups compliant .dev file to simulate this device clicking here.
Some more detailed comments are available after the "Known supported…" sections.
Known supported variables
This device is known to support the following variables (values are just examples):
|
battery.capacity
|
Actual battery was 12000 mAh; possibly wrong DIP switch combo was in place to configure the HAT |
|
battery.charge
|
(?) Not 100% but charger is "resting"… |
|
battery.charge.low
|
|
|
battery.charger.status
|
|
|
battery.current
|
|
|
battery.packs
|
|
|
battery.packs.bad
|
|
|
battery.temperature
|
Probably a 10x factor error |
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.current
|
|
|
input.voltage
|
|
|
ups.date
|
|
|
ups.firmware
|
|
|
ups.mfr
|
|
|
ups.status
|
|
|
ups.time
|
|
|
ups.type
|
|
About this device
Reported at:
Vendor/Manufacturer information:
Further system data or configuration examples:
[hat]
driver = pijuice
port = /dev/i2c-1
desc = "PiJuice HAT" 0.000000 [D5] send_to_all: SETINFO driver.parameter.port "/dev/i2c-1"
0.000247 [D1] debug level is '6'
0.001303 [D5] send_to_all: SETINFO device.type "ups"
0.001446 [D3] get_firmware_version
0.002954 Unknown Firmware release: 1.4
0.003016 [D1] UPS Firmware Version: 1.4
0.003074 [D5] send_to_all: SETINFO ups.firmware "1.4"
0.003136 [D5] send_to_all: SETINFO driver.version "2.7.4-4385-g2bd17f540"
0.003195 [D5] send_to_all: SETINFO driver.version.internal "0.9"
0.003252 [D5] send_to_all: SETINFO driver.name "pijuice"
0.003309 [D5] send_to_all: SETINFO ups.mfr "PiJuice"
0.003365 [D5] send_to_all: SETINFO ups.type "HAT"
0.003422 [D5] send_to_all: SETINFO device.mfr "PiJuice"
0.003477 [D5] send_to_all: SETINFO device.type "HAT"
0.003533 [D1] Low Battery Threshold: 25%
0.003589 [D5] send_to_all: SETINFO battery.charge.low "25"
0.003642 [D1] Nominal Battery Voltage: 4.180V
0.003697 [D5] send_to_all: SETINFO battery.voltage.nominal "4.180"
0.003747 [D3] get_i2c_address
0.004934 [D1] I2C Address: 0x14
0.005001 [D1] Found device '0x14' on port '/dev/i2c-1'
0.005049 [D3] get_battery_profile
0.009196 [D1] Battery Capacity: 1.820Ah
0.009271 [D5] send_to_all: SETINFO battery.capacity "1.820"
0.009321 [D3] get_battery_profile_ext
0.014312 [D1] Battery Chemistry: LiPO
0.014389 [D5] send_to_all: SETINFO battery.type "LiPO"
0.014444 [D3] get_status
0.015638 [D1] Battery Status: Normal
0.015703 [D5] send_to_all: SETINFO battery.packs "1"
0.015763 [D5] send_to_all: SETINFO battery.packs.bad "0"
0.015814 [D1] Power Input: Not Present
0.015862 [D1] Power Input 5v: Present
0.015910 [D3] get_charge_level_hi_res
0.017323 [D1] Battery Charge Level: 51.0%
0.017389 [D5] send_to_all: SETINFO battery.charge "51.0"
0.017437 On USB power
0.017548 [D1] On USB power [1:0:0]
0.017599 [D1] Battery Charger Status: resting
0.017653 [D5] send_to_all: SETINFO battery.charger.status "resting"
0.017698 [D3] get_battery_temperature
0.018972 [D1] Battery Temperature: 123°C
0.019030 [D5] send_to_all: SETINFO battery.temperature "123"
0.019074 [D3] get_battery_voltage
0.020351 [D1] Battery Voltage: 3.700V
0.020406 [D5] send_to_all: SETINFO battery.voltage "3.700"
0.020448 [D3] get_battery_current
0.021728 [D1] Battery Current: 0.264A
0.021791 [D5] send_to_all: SETINFO battery.current "0.264"
0.021834 [D3] get_io_voltage
0.023122 [D1] Input Voltage: 4.994V
0.023176 [D5] send_to_all: SETINFO input.voltage "4.994"
0.023219 [D3] get_io_current
0.024520 [D1] Input Current: 0.064A
0.024578 [D5] send_to_all: SETINFO input.current "0.064"
0.024621 [D3] get_time
0.027337 [D1] UPS Time: 21:48:40.41
0.027400 [D5] send_to_all: SETINFO ups.time "21:48:40.41"
0.027445 [D1] UPS Date: 2022-01-21
0.027493 [D5] send_to_all: SETINFO ups.date "2022-01-21"
0.027536 [D3] get_power_off
0.028605 [D1] Power Off: DISABLED
0.028660 [D5] send_to_all: SETINFO ups.status "OL"
0.028705 [D5] send_to_all: DATAOK
0.028754 [D5] send_to_all: SETINFO driver.parameter.pollinterval "2"
0.028803 [D5] send_to_all: SETINFO driver.parameter.synchronous "no"
0.028851 [D3] get_status
0.029951 [D1] Battery Status: Normal
0.030010 [D1] Power Input: Not Present
0.030052 [D1] Power Input 5v: Present
0.030092 [D3] get_charge_level_hi_res
0.031379 [D1] Battery Charge Level: 51.0%
0.031431 [D1] On USB power [1:0:0]
0.031472 [D1] Battery Charger Status: resting
0.031516 [D3] get_battery_temperature
0.032790 [D1] Battery Temperature: 251°C
0.032845 [D5] send_to_all: SETINFO battery.temperature "251"
0.032888 [D3] get_battery_voltage
0.034167 [D1] Battery Voltage: 3.828V
0.034228 [D5] send_to_all: SETINFO battery.voltage "3.828"
0.034270 [D3] get_battery_current
0.035546 [D1] Battery Current: 0.264A
0.035596 [D3] get_io_voltage
0.036884 [D1] Input Voltage: 4.991V
0.036937 [D5] send_to_all: SETINFO input.voltage "4.991"
0.036979 [D3] get_io_current
0.038280 [D1] Input Current: 0.064A
0.038387 [D3] get_time
0.041102 [D1] UPS Time: 21:48:40.39
0.041158 [D5] send_to_all: SETINFO ups.time "21:48:40.39"
0.041202 [D1] UPS Date: 2022-01-21
0.041247 [D3] get_power_off
0.042321 [D1] Power Off: DISABLED
0.042380 [D3] get_status
0.043475 [D1] Battery Status: Normal
0.043527 [D1] Power Input: Not Present
0.043568 [D1] Power Input 5v: Present
0.043610 [D3] get_charge_level_hi_res
0.044899 [D1] Battery Charge Level: 51.0%
0.044952 [D1] On USB power [1:0:0]
0.044994 [D1] Battery Charger Status: resting
0.045038 [D3] get_battery_temperature
0.046314 [D1] Battery Temperature: 251°C
0.046372 [D3] get_battery_voltage
0.047647 [D1] Battery Voltage: 3.700V
0.047701 [D5] send_to_all: SETINFO battery.voltage "3.700"
0.047743 [D3] get_battery_current
0.049021 [D1] Battery Current: 0.264A
0.049071 [D3] get_io_voltage
0.050360 [D1] Input Voltage: 4.988V
0.050420 [D5] send_to_all: SETINFO input.voltage "4.988"
0.050462 [D3] get_io_current
0.051760 [D1] Input Current: 0.064A
0.051812 [D3] get_time
0.054527 [D1] UPS Time: 21:48:40.38
0.054588 [D5] send_to_all: SETINFO ups.time "21:48:40.38"
0.054633 [D1] UPS Date: 2022-01-21
0.054678 [D3] get_power_off
0.055747 [D1] Power Off: DISABLED
0.055797 [D3] Entering dstate_dumpReport #4 with driver pijuice (detailed comments available)
This device is known to work with driver pijuice.
You can grab a dummy-ups compliant .dev file to simulate this device clicking here.
Some more detailed comments are available after the "Known supported…" sections.
Known supported variables
This device is known to support the following variables (values are just examples):
|
battery.capacity
|
|
|
battery.charge
|
|
|
battery.charge.low
|
|
|
battery.charger.status
|
|
|
battery.current
|
|
|
battery.packs
|
|
|
battery.packs.bad
|
|
|
battery.temperature
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.current
|
|
|
input.voltage
|
|
|
ups.date
|
|
|
ups.firmware
|
|
|
ups.mfr
|
|
|
ups.status
|
|
|
ups.time
|
|
|
ups.type
|
|
About this device
Reported at:
Vendor/Manufacturer information:
Further system data or configuration example:
# Using NUT v2.8.0 packaged in Debian 12 (Bookworm)
[pijuice-ups]
driver = pijuice
port = /dev/i2c-1
desc = "PiJuice HAT"
