![]() |
>>>>> "Ramana" == Ramana Juvvadi <juvvadi@lekha.org> writes: Ramana> I have a Cardinal MVPV34I. Setting send trigger to 022 solved the Ramana> problem. If the chipset is similar it might work. Here is what I Ramana> have in my config file. Ramana> ModemSendFillOrder: LSB2MSB # as expected Ramana> ModemRecvFillOrder:MSB2LSB # opposite of what makes sense Ramana> Class2RecvDataTrigger: "\022" # character sent to modem to start recv Well, that seems to work. I looked at the received fax it appears to be all there. I am a little worried though -- the sessions trace indicates that there was a problem Oct 28 15:39:36.39: [26541]: RECV: begin page Oct 28 15:39:36.40: [26541]: MODEM set XON/XOFF/FLUSH: input ignored, output gen erated Oct 28 15:39:36.40: [26541]: RECV: send trigger 022 Oct 28 15:39:36.40: [26541]: <-- data [1] Oct 28 15:40:11.50: [26541]: RECV/CQ: Bad 1D pixel count, row 2122, got 0, expec ted 1728 Oct 28 15:40:11.50: [26541]: RECV/CQ: Bad 1D pixel count, row 2123, got 0, expec ted 1728 Oct 28 15:40:11.51: [26541]: RECV/CQ: Bad 1D pixel count, row 2124, got 0, expec ted 1728 Oct 28 15:40:11.51: [26541]: RECV/CQ: Bad 1D pixel count, row 2125, got 0, expec ted 1728 Oct 28 15:40:11.51: [26541]: RECV/CQ: Bad 1D pixel count, row 2126, got 0, expec ted 1728 Oct 28 15:40:11.65: [26541]: RECV/CQ: Bad 1D pixel count, row 2127, got 3134, ex pected 1728 Oct 28 15:40:11.65: [26541]: RECV/CQ: Adjusting for trailing noise (6 run) Oct 28 15:40:11.65: [26541]: RECV: 2122 total lines, 0 bad lines, 0 consecutive bad lines Oct 28 15:40:11.65: [26541]: MODEM set XON/XOFF/DRAIN: input interpreted, output disabled Oct 28 15:40:11.66: [26541]: --> [17:+FPTS: 2,2219,0,0] Oct 28 15:40:12.89: [26541]: --> [7:+FET: 2] I see similar results for a multi-page fax -- should I be concerned? -- Eric M. Boehm boehm@engineous.com Senior System Analyst Engineous Software, Inc.