I tracked down some of the problem. In megatec_usb it reads 48 bytes like this:
28 31 31 33 2e 38 20 31 30 30 31 30 30 30 d 33 2e 38 20 30 33 38 20 36 30 2e 30 20 35 34 2e 31 20 35 30 2e 36 20 30 30 30 30 31 30 30 30 d 33 but in a later routine saw only 14 bytes. Notice that there are TWO sets of "d 33" in there. The code in 2.2.2 only expects the latter set, to drop the message down from 48 bytes to 46. ser_get_line in megatec.c passes ENDCHAR as \r, or hex d. So it truncates at the first d instead of the second, and ends up with the 14 byte line. Here it is translated in a nicer format: (113.8 1001000<CR>3.8 038 60.0 54.1 50.6 00001000<cr>3 What do these messages look like on other Phoenixtec UPS devices? I'll build the trunk after lunch. I tried just putting in megatec_usb.c but it had some incompatibility with the rest of 2.2.2. Thanks, David Mathog [EMAIL PROTECTED] Manager, Sequence Analysis Facility, Biology Division, Caltech _______________________________________________ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
