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. > 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? Have you also tried the mge-shut driver? Best regards, Arjen -- Please keep list traffic on the list _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
