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@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@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
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
