Hi,
I'm trying to configure my ups with nut which is a locally made one. It
uses a rs232 port to talk to the computer and comes with a software called
"Powermanager Lite" which is provided by Richcomm and supports
Windows,
Linux and UNIX. According to the manual it uses the Richcomm circuitry to
talk to the computer and uses a drycontact protocol. Unfortunately I
couldn't find any driver for Richcomm serial interface, there's a
richcomm_usb however. I've tried all of the genericups drivers and the
megatec driver even a USB to Serial converter cable (Prolific chipset) but
no luck. Any suggestion about which driver to choose or what I'm doing
wrong?
I'm using NUT on FreeNAS 0.7.2 which uses NUT 2.60. Below is the link to
the Richcomm product product page.
Powermanager lite:
http://www.richcomm.com/en/productshow.php?ippt_product_id=65
Thanks for your time.
Manzoor
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110423/2a5a398c/attachment.htm>
Citeren Manzoor e Elahi <manzoor.e.elahi op gmail.com>:> I'm trying to configure my ups with nut which is a locally made one. It > uses a rs232 port to talk to the computer and comes with a software called > "Powermanager Lite" which is provided by Richcomm and supports Windows, > Linux and UNIX. According to the manual it uses the Richcomm circuitry to > talk to the computer and uses a drycontact protocol. Unfortunately I > couldn't find any driver for Richcomm serial interface, there's a > richcomm_usb however. I've tried all of the genericups drivers and the > megatec driver even a USB to Serial converter cable (Prolific chipset) but > no luck. Any suggestion about which driver to choose or what I'm doing > wrong?If it indeed uses a dry contact interface, it is supported by the genericups driver. If not through one of the existing 'upstype' settings, you should be able to override the 'CP', 'OL', 'LB' and/or 'SD' configuration directives to make it so. This is essentially what the 'richcomm_usb' driver does for USB.> I'm using NUT on FreeNAS 0.7.2 which uses NUT 2.60. Below is the link to > the Richcomm product product page. > > Powermanager lite: > http://www.richcomm.com/en/productshow.php?ippt_product_id=65This is not a description of a dry contact interface. If this is what your UPS is using, it requires something different. Assuming the people who designed this did not create a smart protocol using the modem control lines (which would be insane, since using the TXD/RXD lines would be much simpler instead), I would say this is a smart protocol which is not supported through either genericups or richcomm_usb. The best advice we can give you is to first find out what protocol is used by the UPS (possibly by snooping the serial port when running the bundled software). Unless you have dozens of devices you have to use and/or you hourly wages are close to zero, it is probably better to ditch the UPS and buy something that is supported out of the box. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected)
Thanks for your replay. Actually my UPS uses a lite version of that software and only reports mains on/off, ups on/off and ups connected/disconnected status. I also think the genericups driver should work and tried all the driver types without any luck. Unfortunately I can't afford to ditch the UPS right now. I'll try the serial sniffing technique or use a multimeter to find out what's happening through the serial port. I've some experience with those. Can you give me some idea what I should be looking for? One more question. Is it possible to use a USB to serial cable for a serial UPS with generic UPS driver? This combination works in Windows with the official software but what about NUT? Is any special configuration required for this? Thanks again... Manzoor On Sat, Apr 23, 2011 at 3:54 PM, Arjen de Korte <nut+users at de-korte.org>wrote:> Citeren Manzoor e Elahi <manzoor.e.elahi at gmail.com>: > > > I'm trying to configure my ups with nut which is a locally made one. It >> uses a rs232 port to talk to the computer and comes with a software called >> "Powermanager Lite" which is provided by Richcomm and supports Windows, >> Linux and UNIX. According to the manual it uses the Richcomm circuitry to >> talk to the computer and uses a drycontact protocol. Unfortunately I >> couldn't find any driver for Richcomm serial interface, there's a >> richcomm_usb however. I've tried all of the genericups drivers and the >> megatec driver even a USB to Serial converter cable (Prolific chipset) but >> no luck. Any suggestion about which driver to choose or what I'm doing >> wrong? >> > > If it indeed uses a dry contact interface, it is supported by the > genericups driver. If not through one of the existing 'upstype' settings, > you should be able to override the 'CP', 'OL', 'LB' and/or 'SD' > configuration directives to make it so. This is essentially what the > 'richcomm_usb' driver does for USB. > > > I'm using NUT on FreeNAS 0.7.2 which uses NUT 2.60. Below is the link >> to >> the Richcomm product product page. >> >> Powermanager lite: >> http://www.richcomm.com/en/productshow.php?ippt_product_id=65 >> > > This is not a description of a dry contact interface. If this is what your > UPS is using, it requires something different. Assuming the people who > designed this did not create a smart protocol using the modem control lines > (which would be insane, since using the TXD/RXD lines would be much simpler > instead), I would say this is a smart protocol which is not supported > through either genericups or richcomm_usb. > > The best advice we can give you is to first find out what protocol is used > by the UPS (possibly by snooping the serial port when running the bundled > software). Unless you have dozens of devices you have to use and/or you > hourly wages are close to zero, it is probably better to ditch the UPS and > buy something that is supported out of the box. > > Best regards, Arjen > -- > Please keep list traffic on the list (off-list replies will be rejected) > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110424/1ede8f6e/attachment.htm>
On Mon, May 2, 2011 at 4:23 AM, Charles Lepple <clepple at gmail.com> wrote:> On May 1, 2011, at 4:07 PM, Manzoor e Elahi wrote: > > On Sun, May 1, 2011 at 2:26 AM, Charles Lepple <clepple at gmail.com> wrote: >> >> On Apr 30, 2011, at 12:15 PM, Arjen de Korte wrote: >>> >>> Citeren Manzoor e Elahi <manzoor.e.elahi at gmail.com>: >>> >>>> >>>> Thanks for your instruction. I tried the portman under XP. The log file >>>> >>>>> is >>>>> attached with the mail. Please check that out and let me know what you >>>>> think >>>>> or any further instruction. Thanks for your time. >>>>> >>>>> >>>> This is almost certainly supported by one of the genericups models. The >>>> log is too short to determine which exactly. You'll need to make sure >>>> you >>>> also see the modem status *and* make sure the UPS goes through an online >>>> - >>>> on battery - online sequence to see which is reporting the on battery >>>> status. >>>> >>>> >>> Also, it would be interesting to see what character is being written: >>> >>> 11 0.00000000 PMLiteServer.ex IRP_MJ_WRITE Serial0 Length 1: . >>> >>> Is there an option to log the data in hex? >>> >> >> >> Alright, here comes some more logs. This time I've gone through online - >> on battery - online sequence as you instructed. There's an option for >> showing hex in portmon that I didn't notice before. But turning that >> didn't >> show anything new in the log. So I tried another soft. As a result the >> logs >> looks different. Let me know what you think. >> > > It doesn't look like the attachments came through. >Here's something more I've found using the new soft. Please take a look. Thanks... Manzoor -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110502/d2619079/attachment-0001.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: pin.zip Type: application/zip Size: 6371 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110502/d2619079/attachment-0001.zip>