So anyone have an idea how I should configure this? It seems from the above I have the USB Driver setup and now the software is looking through the USB serial device and knows its not connected? Maybe? So…I set the config all back to default and tried the command “sudo apcaccess” $ sudo apcaccess So I moved on to try to setup the config files but I may be on the wrong track and got loads of errors after editing the config files to use a smart cable. usb 1-1.3: pl2303 converter now attached to ttyUSB0 usb 1-1.3: Manufacturer: Prolific Technology Inc. usb 1-1.3: Product: USB-Serial Controller D usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Look here for advice that works to setup the usb-serial device: usb 1-1.3: New USB device found, idVendor=0557, idProduct=2008, bcdDevice= 3.00 To be clear…the FTDI was just plugged in to the pi USB and nothing else was connected to it. So it seems (the pi) does recognise the FTDI device also but does that also indicate the driver is in place as well? My guess is no? Out of interest I plugged in my FTDI that I use to flash my devices (with Tasmota etc) and the below output was observed after running “lsusb” command: $ lsusbīus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC I have searched for answers but not sure I was able to come up with relavent search terms for this problem. If that is likely how do I ensure the driver is installed? I am a reasonably new player on these but know enough to get up and running to this point. The output above seems to confirm that the RS232 to USB serial adaptor is detected by the pi but that the UPS is not communicating it seems? Could this be because the serial adaptor (although detected) does not have the necessary driver installed on the pi? Just to confirm the pi is connected to my APC SmartUPS 3000XL via a RS232 (9 pin) serial cable (Part No: 940-0024) which is connected to a RS232 to USB serial adaptor. USB 2.0 Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub USB 2.0 Hubīus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. Processing triggers for systemd (241-7~deb10u1+rpi1) $ lsusbīus 001 Device 006: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port īus 001 Device 004: ID 0424:7800 Standard Microsystems Corp.īus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. Processing triggers for man-db (2.8.5-2). Ĭreated symlink /etc/systemd/system//rvice → /lib/systemd/system/rvice. Selecting previously unselected package s-nail. The output included the below: Unpacking apcupsd-doc (3.14.14-2). Once installed run this command to verify the device is visible
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |