2008/10/28 Arjen de Korte <[EMAIL PROTECTED]>: > Citeren Daniel O'Connor <[EMAIL PROTECTED]>: > >> When it loses comms I see stuff like this.. >> entering shut_get_report(id: 2f, len: 1800) >> shut_wait_ack(): ACK received >> entering shut_get_report(id: 20, len: 1800) >> shut_wait_ack(): ACK received >> entering shut_get_report(id: 07, len: 1800) >> shut_wait_ack(): NACK received >> shut_wait_ack(): NACK received >> shut_wait_ack(): NACK received >> shut_wait_ack(): NACK received >> shut_wait_ack(): NACK received >> shut_wait_ack(): NACK received >> shut_wait_ack(): Unknown byte 24 >> shut_wait_ack(): ACK received >> entering shut_get_report(id: 0a, len: 1800) >> shut_wait_ack(): Unknown byte 132 >> shut_wait_ack(): Unknown byte 136 >> shut_wait_ack(): Unknown byte 7 >> shut_wait_ack(): Unknown byte 119 >> Max tries reached while waiting for ACK, still getting errors >> entering shut_ups_start() > > Looking at the above, you're probably using the newmge-shut driver, > right? In that case, running it in debug mode (-DD) might reveal what > is going on.
not at all, this is the oldish mge-shut. trying newmge-shut might be a good idea, but I would not recommend it yet for a production system. I really have to finish that one! >> I added the 'unknown byte x' stuff - I wanted to see what it was throwing >> away :) >> >> Does anyone have such a UPS working with NUT + RS232? I'll try to do some test asap on an EX 1500. Arnaud -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
