[Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Peter Selinger selinger at mathstat.dal.ca
Mon Jun 19 03:23:35 UTC 2006


Great. You'll have to play with "upstype" a bit more to figure out the
correct settings for your UPS. See the genericups man page, it
contains a lot of information. -- Peter

Eli Wapniarski wrote:
> 
> Peter
> 
> I think thats that. Just connected the UPS via serial cable and it
> seems to be working. So, I think I will revert to the stable version
> supplied by FC extras. I will keep the work that we've done together
> for a little while in case you decide to conitnue to work with me to
> get this to work with the usb interface.
> 
> Currently my ups.conf contains
> 
> [Gamatronic_D-Compact]
>     driver = genericups
>     upstype = 22
>     port = /dev/ttyS0
>     desc = "Gamatronic D-Compact
> 
> and upsc Gamatronic_D-Compact at localhost produces
> 
> driver.name: genericups
> driver.parameter.port: /dev/ttyS0
> driver.parameter.upstype: 22
> driver.version: 2.1.0
> driver.version.internal: 1.32
> ups.mfr: Gamatronic Electronic Industries
> ups.model: Generic Alarm UPS
> ups.status: LB OB
> 
> Once again your help has been very much appreicated
> 
> Eli
> 
> On Sunday, 18 =D7=91June 2006 09:07, Eli Wapniarski wrote:
> > Hi Peter
> >
> > First let me say that I have appreciated you're help up to now and was
> > quite amazed at how quickly (real time) we were able to get nut to
> > detect the ups.
> >
> > I understand that the rest of this is a different kettle of fish
> > altogether, so I do understand you're reluctance to dig into this
> > deeper. I will try to obtain serial cables over the next couple of
> > days and let you know.
> >
> > If you would be willing to continue with this, I remain available to
> > assist you in anyway that I can. If there is anything relatively quick
> > that can be done to at least get the parameter that says that "the ups
> > is now running on the battery as opposed to the regular electricity,
> > shutdown the computer now" that would be really great, and good enough.
> >
> > In any case with great appreciation
> >
> > Thank You
> >
> > Eli
> >
> > Quoting Peter Selinger <selinger at mathstat.dal.ca>:
> > > Eli Wapniarski wrote:
> > >> Here you go
> > >>
> > >> As you can see not very much information is available.
> > >>
> > >> upsc Gamatronic_D-Compact at localhost produces
> > >>
> > >> driver.name: newhidups
> > >> driver.parameter.port: auto
> > >> driver.version: 2.1.0
> > >> driver.version.data: RICHCOMM HID 0.9
> > >> driver.version.internal: 0.28
> > >> ups.mfr: Richcomm Tech
> > >> ups.model: UPS2004
> > >>
> > >> So what's next?
> > >
> > > I am afraid that this is bad news.  This device does not seem to
> > > follow the standard USB "HID" protocol. This means that the device
> > > probably follows some proprietary custom communications protocol.
> > > There is not much I can do to reverse-engineer such a protocol.
> > > It would be a lot of work and very difficult; perhaps impossible.
> > >
> > > You options:
> > >
> > > * use the serial port instead of USB, if your UPS has one,
> > > * use a manufacturer-supplied driver instead of NUT, if there is one, or
> > > * buy a USB that is supported by NUT.
> > >
> > > I am sorry that I can't do more. Unless someone else on this mailing
> > > list has an idea...?
> > >
> > > -- Peter
> >
> > _______________________________________________
> > Nut-upsuser mailing list
> > Nut-upsuser at lists.alioth.debian.org
> > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
> 




More information about the Nut-upsuser mailing list