Displaying 5 results from an estimated 5 matches for "blazer_process_status_bit".
Did you mean:
blazer_process_status_bits
2014 Nov 02
2
nutdrv_qx and Best Power equipment
...fter I plugged it back in. However, the bypass bit inversion might be responsible for this:
228.304623 send: 'Q1'
228.515426 read: '(119.0 119.0 000.0 000 60.0 13.5 XX.X 00001010'
228.515494 ups_infoval_set: non numerical value [ups.temperature: XX.X]
228.515506 blazer_process_status_bits: output voltage too low
228.515510 Communications with the UPS lost: status read failed!
Similarly, when I unplugged the unit around t=638, I also got "data stale" messages from upsd (probably at t=662.124768). I let it run the battery down, and plugged it back in just before t=261...
2014 Nov 07
0
nutdrv_qx and Best Power equipment
...n. However, the bypass bit inversion might be responsible for this:
>
> 228.304623 send: 'Q1'
> 228.515426 read: '(119.0 119.0 000.0 000 60.0 13.5 XX.X 00001010'
> 228.515494 ups_infoval_set: non numerical value [ups.temperature: XX.X]
> 228.515506 blazer_process_status_bits: output voltage too low
> 228.515510 Communications with the UPS lost: status read failed!
>
> Similarly, when I unplugged the unit around t=638, I also got "data stale" messages from upsd (probably at t=662.124768). I let it run the battery down, and plugged it back in jus...
2014 Nov 09
3
nutdrv_qx and Best Power equipment
...ypass bit inversion might be responsible for this:
>>
>> 228.304623 send: 'Q1'
>> 228.515426 read: '(119.0 119.0 000.0 000 60.0 13.5 XX.X 00001010'
>> 228.515494 ups_infoval_set: non numerical value [ups.temperature: XX.X]
>> 228.515506 blazer_process_status_bits: output voltage too low
>> 228.515510 Communications with the UPS lost: status read failed!
>>
>> Similarly, when I unplugged the unit around t=638, I also got "data stale" messages from upsd (probably at t=662.124768). I let it run the battery down, and plugged it...
2014 Nov 02
0
nutdrv_qx and Best Power equipment
> I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1.
>
> It looks like things mostly work:
Nice, merging bestups.c into nutdrv_qx has been on my todo list for a
while, let's see how far we can get.
> 1) The bestups driver uses an "ID"
2014 Nov 01
3
nutdrv_qx and Best Power equipment
Hi Daniele,
I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1.
It looks like things mostly work:
bestups:
battery.charge: 100.0
battery.voltage: 13.9
battery.voltage.nominal: 12
device.mfr: Best Power
device.model: Patriot Pro II 400
device.type: ups