Re: [Nut-upsuser] Network UPS Tools version 2.0.5 released
I guess. You'll *have* to connect a UPS, otherwise there is nothing to verify. We already know the genericups driver works with other UPS'es, so there is no need to check that. You need to check if it works with *your* UPS. I have a UPS connected, I meant running the driver manually without running upsd. You'd better start upsd too, in order to make upsc work (to query for the line status). Best regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Network UPS Tools version 2.0.5 released
On Tue, 16 Jan 2007, Arjen de Korte wrote: From the FAQ: Any time there is a gap in features, it's usually because the group of people who own that hardware and the group of people who write code don't overlap. The fix is to make them overlap - turn an owner into a developer or vice-versa. Unless someone picks up writing a driver around the protocol specification that was committed by Alexey Sidorov (December 22nd), this may never happen. None of the active developers has one of these devices, as far as I know. I'm eagerly awaiting them -- if there's a cvs snapshot or something I can check out I can help you with testing. See above. Don't hold your breath. digging back the powercom king-pro thread, I don't see anything more than it doesn't work with the powercom driver but it should with genericups I've tried with GenericUPS, had no luck (didn't get any response from the driver at all indicating it was online (or that serial comms were happening at all). I'll double check this more in the coming week, it's possible I have a wrong cable or something. It should be possible to test this with just the driver, manually, in debug mode, right? Or have I been going about this all wrong? I never heard of you again after suggesting to try the genericups driver. That doesn't really help in persuading me to look into this. Apologies for that, been working in drop everything and fix X now mode for a while now, and having this up just hasn't been the greatest of priorities. I'm trying to get my hands on an rs232 tester, which should simplify doing this the dumb way. I should have it in a few days, and that should definitively tell me which signals are high and which are not in which modes. My offer stands as to if there's something someone wants to code a working driver (ranging from cash to a free UPS or something like that) please contact me offlist. -Dan -- Station! -Bill Ted's Bogus Journey Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Network UPS Tools version 2.0.5 released
I've tried with GenericUPS, had no luck (didn't get any response from the driver at all indicating it was online (or that serial comms were happening at all). I'll double check this more in the coming week, it's possible I have a wrong cable or something. There will be no feedback, other than the OL OB LB status indication. The genericups 'protocol' just looks at modem status lines, there is nothing more to display. All other variables are just hardcoded. It should be possible to test this with just the driver, manually, in debug mode, right? No, without connecting a UPS this is useless. Or have I been going about this all wrong? I guess. You'll *have* to connect a UPS, otherwise there is nothing to verify. We already know the genericups driver works with other UPS'es, so there is no need to check that. You need to check if it works with *your* UPS. Best regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Network UPS Tools version 2.0.5 released
On Mon, 29 Jan 2007, Arjen de Korte wrote: I've tried with GenericUPS, had no luck (didn't get any response from the driver at all indicating it was online (or that serial comms were happening at all). I'll double check this more in the coming week, it's possible I have a wrong cable or something. There will be no feedback, other than the OL OB LB status indication. The genericups 'protocol' just looks at modem status lines, there is nothing more to display. All other variables are just hardcoded. It should be possible to test this with just the driver, manually, in debug mode, right? No, without connecting a UPS this is useless. Or have I been going about this all wrong? I guess. You'll *have* to connect a UPS, otherwise there is nothing to verify. We already know the genericups driver works with other UPS'es, so there is no need to check that. You need to check if it works with *your* UPS. I have a UPS connected, I meant running the driver manually without running upsd. -Dan -- You're a thucking reyer! -Richard Bozzello, who believed tongue piercing was painless. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Network UPS Tools version 2.0.5 released
Hi Dan, 2007/1/15, Dan Mahoney, System Admin [EMAIL PROTECTED]: On Mon, 15 Jan 2007, Arnaud Quette wrote: Arnaud, Any idea when those committed powercom specs will be incorporated? I'm eagerly awaiting them -- if there's a cvs snapshot or something I can check out I can help you with testing. digging back the powercom king-pro thread, I don't see anything more than it doesn't work with the powercom driver but it should with genericups I don't see any commited specs too?! Maybe Arjen can complete... Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Network UPS Tools version 2.0.5 released
Any idea when those committed powercom specs will be incorporated? From the FAQ: Any time there is a gap in features, it's usually because the group of people who own that hardware and the group of people who write code don't overlap. The fix is to make them overlap - turn an owner into a developer or vice-versa. Unless someone picks up writing a driver around the protocol specification that was committed by Alexey Sidorov (December 22nd), this may never happen. None of the active developers has one of these devices, as far as I know. I'm eagerly awaiting them -- if there's a cvs snapshot or something I can check out I can help you with testing. See above. Don't hold your breath. digging back the powercom king-pro thread, I don't see anything more than it doesn't work with the powercom driver but it should with genericups I never heard of you again after suggesting to try the genericups driver. That doesn't really help in persuading me to look into this. I don't see any commited specs too?! Since the specifications were posted in the development mailing list, but nobody picked up the task for writing a driver for it, I don't see any need to rush it. Best regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Network UPS Tools version 2.0.5 released
Network UPS Tools version 2.0.5 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.0/nut-2.0.5.tar.gz - News: http://www.networkupstools.org/source/2.0/new-2.0.5.txt - ChangeLog: http://www.networkupstools.org/source/2.0/ChangeLog ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
