Salut Patrick,<br><br><div><span class="gmail_quote">2005/12/9, Patrick Agrain <<a href="mailto:patrick.agrain@alcatel.fr">patrick.agrain@alcatel.fr</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all<br><br>Arnaud,<br>Some newly purchased Ellipse ASR-model UPS find their way to my office for<br>a first evaluation test.<br>It concerns the Ellipse 1500 and Ellipse 1000 models.<br><br>As you know we are still working with hidups.
</blockquote><div><br>
think seriously about the newhidups switch. I'll definitly kill hidups by the 2.2 release (this lets you some time ;-)<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Peripheral recognition, start of NUT, mains short interruptions management,<br>all that work fine... as expected ;-)
<br><br>But changes occured on the delayed shutdown procedure after the generation<br>of the FSD message.<br><br>The USB analyzer shows :<br>- that the UPS_WAKEDELAY (0x840056) and UPS_GRACEDELAY (0x840057) pages<br>were linked to another Report ID as for previous Ellipse model.
<br>---> This is problably normal. I think these models have another mapping.</blockquote><div><br>
yep, the PowerSummary HID collection has now been standardised,
which means that you can now hard code the ReportID for all new USB
models).<br>
IIRC, the previous ReportID should have been used, but I might be wrong!<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">- that the programmed value was 0 ( not foreseen ) instead of those written<br>in
hidups.h . Therefore, the UPS cut off the power supply as soon as<br>programmed.</blockquote><div><br>
strange as there is no DelayBefore* objects redundancy (ie on Outlet) which would lead to that kind of problem.<br>
Moreover, I've made another test with newhidups, and everything works as expected. Do you have some debug trace for this?<br>
</div><br>
For the moment, I would more tend to a conversion issue, but only the trace of the sent frame can confirm it.<br>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Is a report descriptor tree available anywhere, just to be sure we are<br>pointing to the right Report ID ?
<br>For information, previous Ellipse model have their descriptor tree shown in<br>an MGE document ref. 34003616ZA.<br><br>Is such a document also available for the new ASR model ?</blockquote><div><br>
I've not had time to update this doc (nor to make it more useful than it is)<br>
but I'll check for this too.<br>
</div><br>
Following the receival of the above info, I'll check with the ASR team.<br></div><br>AmitiƩs de Grenoble ;-)<br clear="all">Arnaud<br>-- <br>Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt<br>Network UPS Tools (NUT) Project Leader -
<a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a><br>OpenSource Developer - <a href="http://arnaud.quette.free.fr/">
http://arnaud.quette.free.fr/</a>