Hello Aron, I did check very briefly for support using upd(4), but stopped after being unable to register the UPS with that driver. This would allow sysctl keep information on the ups. I guess that to give it another go, I will have to change the kernel. This task is not a priority since NUT is already an acceptable interface as long as we can make it work.
Regards,
Marcos Madeira
On 07/01/20 23:38, Marcos Madeira | Secure Networks wrote:
> Hello again,
>
> I have a tried a few other things, but without much success.
>
> In regards to using to using ucycom0 or uhidev0 or ucom0 as the virtual
> devices, I was not able to do this, because of how NUT needs a device to
> connect to. None of those devices have a file like /dev/ucycom0 .
>
> In regards to using a serial driver, NUT mentions that the supported
> driver is riello_usb. I did try riello_ser, but it makes the system drop
> to ddb after service start. The nut driver port in this case is
> /dev/cuaU0. I actually reached a somewhat interesting state, where at
> every boot the system drops to ddb, because the upsd service is enabled.
> I am not sure if this is expected behavior as far as OpenBSD goes. I can
> gather more data, but need to get different hardware, because (I assume)
> that the problem is in the USB stack resulting in the keyboard not being
> available to even do 'show panic'. Should this error be pursued or is it
> expected? It can be replicated by using cu -l /dev/cuaU0. The error is
> as follows:
>
> (0, 0, 1) -> e
>
> kernel: page faut trap, code=0
>
> Stopped at usbd_is_dying+0xb: cmpb $0,0x8(%ecx)
>
> ddb{0}>
>
>
> Finally, when using the riello_usb driver, I get much different upsc
> output on Ubuntu as compared to OpenBSD. For example, the ups.status
> does not even change when unplugging the UPS. I will be checking this
> separately as it could be just a problem with the versions of the nut
> port. The following is the relevant output:
>
> $ upsc ups@127.0.0.1
>
> battery.capacity: 7
> battery.charge: 64720
> battery.charge.low: 40
> battery.runtime: 3145920
> battery.voltage: 5243.2
> battery.voltage.nominal: 12
> device.mfr: RPS S.p.a.
> device.model: USV5
> device.serial:
> device.type: ups
> driver.flag.ignorelb: enabled
> driver.name: riello_usb
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.parameter.synchronous: no
> driver.version: 2.7.4
> driver.version.internal: 0.03
> input.bypass.frequency: 5243.20
> input.bypass.voltage: 52432
> input.frequency: 5243.20
> input.voltage: 52432
> output.frequency: 0.00
> output.frequency.nominal: 50.0
> output.L1.current: 52432
> output.L1.power: 52432
> output.L1.realpower: 52432
> output.L2.current: 52432
> output.L2.power: 52432
> output.L2.realpower: 52432
> output.L3.current: 52432
> output.L3.power: 52432
> output.L3.realpower: 52432
> output.power.percent: 64720
> output.voltage: 52432
> output.voltage.nominal: 230
> ups.firmware: SWM036-01-02
> ups.load: 64720
> ups.mfr: RPS S.p.a.
> ups.model: USV5
> ups.power.nominal: 800
> ups.productid: 5500
> ups.realpower.nominal: 480
> ups.serial:
> ups.status: OL OFF
> ups.temperature: 64720
> ups.vendorid: 04b4
>
> Thank you for your consideration,
>
> Marcos Madeira
> Secure Networks Lda
> Tel.: 911 881 590
> mmade...@securenetworks.pt
> https://www.securenetworks.pt
>
> On 03/01/20 11:58, Marcos Madeira | Secure Networks wrote:
>> Hello misc,
>>
>> I am looking to use several Riello UPSs of model IPG 800 DE with
>> OpenBSD through the nut port. These UPSs also go by the name iPlug.
>> This is a compact UPS with only a single USB-B connector for
>> connectivity as is usual with low-end UPSs. However, I am facing an
>> obstacle due to how OpenBSD is discovering the UPS via the USB interface.
>>
>> Thank you for your consideration,
>>
>> --
>> Marcos Madeira
signature.asc
Description: OpenPGP digital signature
