similar to: Unknown model detected - please report this ID: 'SOLA'

Hi, I'm running into an issue while using FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. The ups.conf is : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Telecom Closet Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3)

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

Hello again, I have a Sola 305 (aka Powerware 3110) here connected via a serial INT-0051 cable which I am trying to get working with nut. The driver.list file indicates that nut supports the Sola 305 when connected via the INT-0025C cable using the genericups driver with upstype set to 7 but it does not mention the INT-0051. I was able to use the "Basic CheckUPS II" utility provided

Hi list, on my previous (lenny or squeeze) machine, I had it up and running, but that machine and configs are gone - and on my new jessie machine (see device and config details below) I cannot start the driver: # /lib/nut/bestups -DDDDD -a Patriot_Pro_II_750 0.000000 debug level is '5' 0.000806 send_to_all: SETINFO device.type "ups" 0.000842 send_to_all:

Hello people. My name is Rub?n. Firts, excuse me for my bad english. I run Debian 6.0.6, kernel 2.6.32-5-amd64 in my machine. I bought a ISB Sola basic UPS, model Micro SR inet, with usb conection. I Configure the nut.conf file in standalone mode and I install de isbmex driver. The ups.conf: [ISB_sola-basic] driver = isbmex port = auto With de command upsdrvctl start the

Hi Charles! Thanks a lot for your response. Now I figure why the isbmex driver was not working. On the other hand I've tried to run the command suggested. But no success. I got this information when running the dmesg command after running the modprobe $ sudo modprobe ftdi_sio vendor=0x0483 product=0x0035 [35816.111760] usbcore: registered new interface driver usbserial [35816.111792]

Hi... I'm almost to the point of pulling hair! I was recently given a SOLA-330 UPS However, it didn't come with the comms cable so I'm having some trouble trying to find a pin-out for this UPS and secondly exactly what driver to use with NUT ?? I've got the users manual for a SOLA-325 (from website) and this has a pin-out for this model but clearly it's not the same for

On Feb 26, 2014, at 2:10 AM, Victor Romero wrote: > I got a UPS Sola Basic but it is not working, I'm providing the details. I hope that someone can help me to get it working. > > Please let me know if there is some other information that I should provide :) Thank you for providing all of this information! > OS name and version > Ubuntu 12.04 > $ uname -a > Linux

> 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"

Hi To all on this list... I emailed the EATON (the company that has bought out SOLA) to request some information about the pin-out for this model UPS and I got a reply today! The answer is really simple! this model UPS just uses a normal serial cable that is pin 1-1 through to 9 -9 and I now have it work as it should via the megatec driver :) Scott Evans VK7HSE Phone: +61362291658 Mobile:

I got a UPS Sola Basic but it is not working, I'm providing the details. I hope that someone can help me to get it working. Please let me know if there is some other information that I should provide :) OS name and version Ubuntu 12.04 $ uname -a Linux olimpo 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Exact NUT version, 2.7.1

Hi, All ! I'm trying to use nut 2.0.5 on FreeBSD 4.11-STABLE with UPS INELT Monolith II 1000LT UPS connected to box with RS-232 cable. In ups.conf: [apc] driver = megatec port = /dev/cuaa1 desc = "UPS" When starting /usr/local/etc/rc.d/nut.sh start got: Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues (c)

Hi There, We have this rather large-ish floor-standing Best Axxium Pro, Model Series 0650. I tried using both the "bestups" and "blazer_ser" drivers with it, but no go. So before I go any further: *Should* one of these work with it and, if not, do I have any options? (E.g.: Modify a current driver, resuscitate one that was started and abandoned, etc.? I can code.) My test

Hi, FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. I set the ups.conf up as : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3) Could not get multiplier table: using raw

Hi Charles, thank you VERY MUCH for all your hints. > If you have a jumper wire handy, you can connect the PC's TxD to RxD I should have tried to connect from another computer in the first place. Or access another device known to work from this computer. It turned out that the shield I used to connect the mainboard connector to the PC case expected another mainboard pin layout. So all I

On Nov 7, 2014, at 5:31 PM, hyouko at gmail.com wrote: >> Sure enough, it turned off after about 30 seconds (t=228). I unplugged it for about five seconds, and it came back on three minutes after 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

hi.... I'm using Wine 20030408 on FreeBSD 4.6.2 I believe the instalation is ok (made by ports....) I've to run some applications wich does some file manipulations, such as creating and removing.... Creating a file is ok, but when it tries to remove it, the app shows a message box sayng it was not possible to rename the file . Disk access error. (actually, it creates a file and add

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

I've built samba by hand before , but I've never seen this message, perhaps you can shed some light. I suddenly can't get past the ./configure script. ./configure --prefix=/usr/samba --with-winbind --with-automount gives me the following error: checking for conflicting AUTH_ERROR define in rpc/rpc.h ... no checking for test routines ... configure: error: can't find