I have a Canon iP5000 hanging from my airport express. Pretty standard setup.
I believe that printers that work over airport express implement the riousbprinting protocol, which plops usb commands in tcp/ip packets and sends them to the airport, which decodes them and send them as USB to the printer. Works backwards too, I think. PrintJobMgr does the work, calling on canon's drivers to format the page, and then speaking to the IO Module, which I guess does the riousbprinting. Canon driver is theirs, from ip5000osx419ej7.dmg, released Jan 2007.
Now, on a long job, the printer can stop printing: front light flashes, but no print comes out. When the printer hangs, PrintJobMgr takes up all the remaining processor resource, and stays that way until force quit (or just quit). Looks like random failure to me. Printer appears to work perfectly when attached directly.
Using Eavesdrop.app, a wonderful tool, I've been able to capture the TCP packets to the airport express. They look like this:
and so on until the printer hangs and then they look like this:
and that 00 00 10 00 is always the last line. I can post more, if you need to see it.
Now, my guess is that the printer has a race condition which is being exposed by the different timings between riousbprinting and the direct usb printing.
I want so much for my printer to work. I don't speak USB. Can any one help?
Bets wishes, Jon
I believe that printers that work over airport express implement the riousbprinting protocol, which plops usb commands in tcp/ip packets and sends them to the airport, which decodes them and send them as USB to the printer. Works backwards too, I think. PrintJobMgr does the work, calling on canon's drivers to format the page, and then speaking to the IO Module, which I guess does the riousbprinting. Canon driver is theirs, from ip5000osx419ej7.dmg, released Jan 2007.
Now, on a long job, the printer can stop printing: front light flashes, but no print comes out. When the printer hangs, PrintJobMgr takes up all the remaining processor resource, and stays that way until force quit (or just quit). Looks like random failure to me. Printer appears to work perfectly when attached directly.
Using Eavesdrop.app, a wonderful tool, I've been able to capture the TCP packets to the airport express. They look like this:
Code:
MacOXS print system says:
00 00 00 01 00 00 00 01 00 00 00 00 00 00 00 13 | ........ ........
00 00 00 00 00 00 00 00 | ........
Printer replies:
43 61 6E 6F 6E 20 69 50 35 30 30 30 20 32 32 37 | Canon iP 5000 227
39 37 46 | 97F
MacOXS print system says:
00 00 00 02 00 00 00 01 00 00 00 00 00 00 00 00 | ........ ........
00 00 00 00 80 9E 3B A0 | .....;.
Printer replies:
00 00 00 01 00 00 00 05 00 00 00 01 00 00 00 08 | ........ ........
00 00 00 00 80 9E 3B A0 | .....;.
MacOXS print system says:
00 00 00 01 00 00 04 00 | ........
Printer replies:
00 00 00 02 00 00 00 05 00 00 00 01 00 00 00 6D | ........ .......m
00 00 00 00 80 9E 3B A0 | .....;.
Mac OSX print system says:
4D 46 47 3A 43 61 6E 6F 6E 3B 43 4D 44 3A 42 4A | MFG:Cano n;CMD:BJ
4C 2C 42 4A 52 61 73 74 65 72 33 2C 42 53 43 43 | L,BJRast er3,BSCC
65 3B 53 4F 4A 3A 54 58 54 30 31 3B 4D 44 4C 3A | e;SOJ:TX T01;MDL:
69 50 35 30 30 30 3B 43 4C 53 3A 50 52 49 4E 54 | iP5000;C LS:PRINT
45 52 3B 44 45 53 3A 43 61 6E 6F 6E 20 69 50 35 | ER;DES:C anon iP5
30 30 30 3B 56 45 52 3A 31 2E 30 38 3B 53 54 41 | 000;VER: 1.08;STA
3A 31 30 3B 46 53 49 3A 30 33 3B 00 00 | :10;FSI: 03;..
Printer replies:
00 00 00 01 00 00 00 03 00 00 00 02 00 00 00 04 | ........ ........
00 00 00 00 80 9E 3B A0 | .....;.
etc
00 00 04 00 | ....
00 00 02 00 00 00 03 00 00 00 02 00 00 00 BB | ........ ........
00 00 00 00 80 9E 3B A0 | .....;.
00 BB 42 53 54 3A 30 34 3B 50 49 44 3A 30 30 2C | ..BST:04 ;PID:00,
30 30 2C 30 30 3B 54 52 42 3A 30 30 41 38 30 30 | 00,00;TR B:00A800and so on until the printer hangs and then they look like this:
Code:
[...lots of data elided...]
Macos X says (this is page data, I guess):
E8 EF 9E 97 CD 83 95 97 80 CE 00 00 01 FD 00 00 | ........ .......
01 A4 00 00 09 FE 00 00 1B F0 00 00 51 FB 00 07 | ........ ....Q...
01 00 1B 00 00 01 00 1B FE 00 09 1B 00 51 1B 00 | ........ .....Q..
00 03 00 1C 01 FE 00 0E 1B 03 00 00 09 5A 00 1C | ........ .....Z..
03 1B 01 03 1C 09 09 FC 00 4E 1B 00 51 00 1B 00 | ........ .N..Q...
Printer replies:
00 00 00 02 00 00 00 04 00 00 08 86 00 00 00 04 | ........ ........
00 00 00 00 80 9E 3B A0 | .....;.
MacOSX says:
00 00 10 00 | ....
no reply from printer!Now, my guess is that the printer has a race condition which is being exposed by the different timings between riousbprinting and the direct usb printing.
I want so much for my printer to work. I don't speak USB. Can any one help?
Bets wishes, Jon