Re: [Nut-upsuser] Richcomm Serial driver

2011-05-01 Thread Manzoor e Elahi
On Sun, May 1, 2011 at 2:26 AM, Charles Lepple clep...@gmail.com wrote:

 On Apr 30, 2011, at 12:15 PM, Arjen de Korte wrote:

  Citeren Manzoor e Elahi manzoor.e.el...@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.  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.

Thanks... Manzoor
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Richcomm Serial driver

2011-05-01 Thread Charles Lepple

On May 1, 2011, at 4:07 PM, Manzoor e Elahi wrote:

On Sun, May 1, 2011 at 2:26 AM, Charles Lepple clep...@gmail.com  
wrote:



On Apr 30, 2011, at 12:15 PM, Arjen de Korte wrote:

Citeren Manzoor e Elahi manzoor.e.el...@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.  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.

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] Richcomm Serial driver

2011-04-29 Thread Manzoor e Elahi
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.

Take care, Manzoor


Portmon.log
Description: Binary data
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Richcomm Serial driver

2011-04-24 Thread Arjen de Korte

Citeren Manzoor e Elahi manzoor.e.el...@gmail.com:


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?


In case of contact closure devices, the easiest way to find this out  
is by using a RS-232 breakout box. You would find these in the toolbox  
of any engineer dealing with TTY consoles on mainframes a few decades  
ago. See for an example


http://en.wikipedia.org/wiki/Breakout_box

I actually have the model that is depicted on this page. This will  
indicate the status of the modem control lines by means of colored  
LEDs, making it very easy to see what happens. You could probably also  
do this with Portmon for Windows, by this requires more effort on your  
side. See


http://msdn.microsoft.com/en-us/library/bb896644.aspx

If you can lay your hands on a RS-232 breakout box, the few bucks you  
might need to pay for it are well worth it.



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?


This depends on whether or not your kernel supports this device. If it  
is supported, usually a /dev/ttyUSBn (n = 0..15) port will be created  
by the kernel. You then connect the genericups driver to this as if it  
was a regular serial port.


Best regards, Arjen

PS  Please do not top-post on this list.
--
Please keep list traffic on the list (off-list replies will be rejected)


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


[Nut-upsuser] Richcomm Serial driver

2011-04-23 Thread Manzoor e Elahi
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
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Richcomm Serial driver

2011-04-23 Thread Arjen de Korte

Citeren Manzoor e Elahi manzoor.e.el...@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@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


[Nut-upsuser] Richcomm Serial driver

2011-04-23 Thread Manzoor e Elahi
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+us...@de-korte.orgwrote:

 Citeren Manzoor e Elahi manzoor.e.el...@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@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser