Hi Users NUT,
I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a
raspberry-pi. In compatibility list, is listed to use the blazer_ser
driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow
the comands e confs.
root at rasp:/home/pi# lsusb
*Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
Port*
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The description of equipment don't appear.
In the ups.conf, i used the follow lines.
[ups]
driver = blazer_ser
port = /dev/ttyUSB0
desc = "SMS 8 KVA"
When start the process by the nut, i received a Error message:
root at rasp:/etc/nut# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Megatec/Q1 protocol serial driver 1.57 (2.7.4)
No supported UPS detected
Driver failed to start (exit status=1)
Somebody could help me to accomplish the monitoring.
Regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190806/4fb7e095/attachment.html>
On 06/08/2019 23.14, Mario Michielin Neto wrote:> Hi Users NUT, > > I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. > > root at rasp:/home/pi# lsusb > *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > The description of equipment don't appear. > > In the ups.conf, i used the follow lines. > > [ups] > driver = blazer_ser > port = /dev/ttyUSB0 > desc = "SMS 8 KVA"Try driver = usbhid-ups Many brands are now supported by this driver. Maybe even: port = auto> When start the process by the nut, i received a Error message: > > root at rasp:/etc/nut# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Network UPS Tools - Megatec/Q1 protocol serial driver 1.57 (2.7.4) > No supported UPS detected > Driver failed to start (exit status=1) > > > Somebody could help me to accomplish the monitoring. > > > Regards.-- Eyal at Home (eyal at eyal.emu.id.au)
I am far from expert on these matters. But have a couple questions: 1. Are you sure that /dev/ttyUSB0 exists and is the result of the Prolific USB->serial converter? For example, if you yank the Prolific and reboot, is /ttyUSB0 there still? It is possible that there is another /dev/ttyUSBx out there.I doubt this but wonder. 2. I have recently been fuddled due to permission problems of various sorts. Are you sure that the user under which nut is running is able to access the /dev/ttyUSB file? On 8/6/2019 6:14 AM, Mario Michielin Neto wrote:> Hi Users NUT, > > I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a > raspberry-pi. In compatibility list, is listed to use the blazer_ser > driver. I use a USB adapter to RS-232 conected in to the No-Breake. > Follow the comands e confs. > > root at rasp:/home/pi# lsusb > *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 > Serial Port* > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. > SMSC9512/9514 Fast Ethernet Adapter > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > The description of equipment don't appear. > > In the ups.conf, i used the follow lines. > > [ups] > driver = blazer_ser > port = /dev/ttyUSB0 > desc = "SMS 8 KVA" > > > When start the process by the nut, i received a Error message: > > root at rasp:/etc/nut# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Network UPS Tools - Megatec/Q1 protocol serial driver 1.57 (2.7.4) > No supported UPS detected > Driver failed to start (exit status=1) > > > Somebody could help me to accomplish the monitoring. > > > Regards. > > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
Hi , The device /dev/ttyUSB0 exist, and i have adjust the permission to rw- rw- rw-. So the permission is not the problem. Em ter, 6 de ago de 2019 às 21:11, David White <whitedavidp at yahoo.com> escreveu:> I am far from expert on these matters. But have a couple questions: > > 1. Are you sure that /dev/ttyUSB0 exists and is the result of the > Prolific USB->serial converter? For example, if you yank the Prolific > and reboot, is /ttyUSB0 there still? It is possible that there is > another /dev/ttyUSBx out there.I doubt this but wonder. > > 2. I have recently been fuddled due to permission problems of various > sorts. Are you sure that the user under which nut is running is able to > access the /dev/ttyUSB file? > > > On 8/6/2019 6:14 AM, Mario Michielin Neto wrote: > > Hi Users NUT, > > > > I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a > > raspberry-pi. In compatibility list, is listed to use the blazer_ser > > driver. I use a USB adapter to RS-232 conected in to the No-Breake. > > Follow the comands e confs. > > > > root at rasp:/home/pi# lsusb > > *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 > > Serial Port* > > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. > > SMSC9512/9514 Fast Ethernet Adapter > > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > > > The description of equipment don't appear. > > > > In the ups.conf, i used the follow lines. > > > > [ups] > > driver = blazer_ser > > port = /dev/ttyUSB0 > > desc = "SMS 8 KVA" > > > > > > When start the process by the nut, i received a Error message: > > > > root at rasp:/etc/nut# upsdrvctl start > > Network UPS Tools - UPS driver controller 2.7.4 > > Network UPS Tools - Megatec/Q1 protocol serial driver 1.57 (2.7.4) > > No supported UPS detected > > Driver failed to start (exit status=1) > > > > > > Somebody could help me to accomplish the monitoring. > > > > > > Regards. > > > > > > > > _______________________________________________ > > Nut-upsuser mailing list > > Nut-upsuser at alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190806/029dad12/attachment.html>
On Aug 6, 2019, at 7:33 PM, Eyal Lebedinsky <eyal at eyal.emu.id.au> wrote:> >> I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. >> root at rasp:/home/pi# lsusb >> *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* >> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter >> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub >> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> The description of equipment don't appear. >> In the ups.conf, i used the follow lines. >> [ups] >> driver = blazer_ser >> port = /dev/ttyUSB0 >> desc = "SMS 8 KVA" > > Try > driver = usbhid-ups > Many brands are now supported by this driver. Maybe even: > port = autoAlthough usbhid-ups does support a number of USB-based UPSes, it does not handle any USB-to-serial converters. If the blazer_* drivers don't work, we generally recommend trying the nutdrv_qx driver instead. So something like this: [ups] driver = nutdrv_qx port = /dev/ttyUSB0 desc = "SMS 8 KVA" If that doesn't work, let us know - there are some debugging flags you can use.