Menu
▾
▴
gimp-print-devel
|
From: Andrew X <68...@gm...> - 2022-03-31 21:57:51
|
Im working with epson L805 and half opaque film and have some troubles when PW sensor in standard mode (not borderless) trying to check film. With usual white paper everything works good. I know in other RIP software for epsons present option to disable PW check. May be i can add some command to init sequence to disable PW check? |
|
From: Walker B. <fo...@wa...> - 2022-03-31 22:30:18
|
There’s a few ways to fix this. One way could simply be to put OHP Ultra Premium film in there because it’s slightly milky white. The other thing could simply be that the film needs a white paper behind it when the printer loads the film part (not both film and paper just the paper behind the film so the printer know’s there’s something to load). The XP-15000 printer needs that for film. You can also put white tape on left and right of film. Best regards -Walker > On Mar 31, 2022, at 5:57 PM, Andrew X <68...@gm...> wrote: > > Im working with epson L805 and half opaque film and have some troubles when PW sensor in standard mode (not borderless) trying to check film. With usual white paper everything works good. I know in other RIP software for epsons present option to disable PW check. May be i can add some command to init sequence to disable PW check? > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel |
|
From: Robert K. <rl...@al...> - 2022-04-03 16:03:36
|
On 4/3/22 10:28, Solomon Peachy wrote: > On Sun, Apr 03, 2022 at 10:24:21AM -0400, Solomon Peachy wrote: >> You just want it extracted, right? > > This capture doesn't seem to have any printer data -- just a USB HID > device and a USB-attached bluetooth device. > > I think the capture was attached to the wrong logical bus.. It looks to me like it is the right one. I found this in packet #634. This is a response from the printer. 1.3.0 looks like the right device; I'm just not sure how to extract the data from the host to the printer. jæÓ ÿÿ©©MFG:EPSON;CMD:ESCPL2,BDC,D4,D4PX,ESCPR1,END4;MDL:L805 Series;CLS:PRINTER;DES:EPSON L805 Series;CID:EpsonRGB;FID:FXN,DPN,WFA,ETN,AFN,DAN,WRN;RID:00;DDS:022500;ELG:0F61; |
|
From: Solomon P. <pi...@sh...> - 2022-04-03 16:59:53
Attachments:
signature.asc
|
On Sun, Apr 03, 2022 at 11:30:56AM -0400, Robert Krawitz wrote:
> It looks to me like it is the right one. I found this in packet #634. This is a response from the
> printer. 1.3.0 looks like the right device; I'm just not sure how to extract the data from the host
> to the printer.
Oh yuck. Wireshark thinks the packets are Bluetooth HCI, for some reason.
There's only a handful of OUT packets. #639 is the @EJL header:
0010 00 00 00 1b 01 ................
0020 40 45 4a 4c 20 31 32 38 34 2e 34 0a 40 45 4a 4c @EJL 1284.4.@EJL
0030 0a 40 45 4a 4c 0a .@EJL.
0000001b0140454a4c20313238342e340a40454a4c0a40454a4c0a
But starting at #663 things get more interesting, with the REMOTE command:
0010 40 40 00 49 00 .......I...@@.I.
0020 00 1b 28 52 08 00 00 52 45 4d 4f 54 45 31 53 4e ..(R...REMOTE1SN
0030 2e 00 00 13 0b 00 de 0a d8 04 18 01 1b 02 f0 00 ................
0040 00 00 00 00 e8 05 00 00 00 00 00 00 01 01 01 01 ................
0050 01 01 01 01 01 01 00 02 01 00 00 00 00 02 f1 03 ................
0060 1b 00 00 00 ....
0010 40 40 00 0c 00 ...........@@...
0020 00 0d 0a 0d 0a 0d 0a .......
4040004900001b285208000052454d4f544531534e2e0000130b00de0ad80418011b02f00000000000e805000000000000010101010101010101010002010000000002f1031b000000
4040000c00000d0a0d0a0d0a
The rest of the packets are a series of command-responses, presumably querying printer parameters.
(Now I'm idly wondering if it wouldn't make sense to try and write an
ESC/P dissector for Wireshark..)
- Solomon
--
Solomon Peachy pizza at shaftnet dot org (email&xmpp)
@pizza:shaftnet dot org (matrix)
High Springs, FL speachy (libra.chat)
|
|
From: Robert K. <rl...@al...> - 2022-04-04 00:12:09
|
On 4/3/22 12:59, Solomon Peachy wrote: > On Sun, Apr 03, 2022 at 11:30:56AM -0400, Robert Krawitz wrote: > But starting at #663 things get more interesting, with the REMOTE command: > > 0010 40 40 00 49 00 .......I...@@.I. > 0020 00 1b 28 52 08 00 00 52 45 4d 4f 54 45 31 53 4e ..(R...REMOTE1SN > 0030 2e 00 00 13 0b 00 de 0a d8 04 18 01 1b 02 f0 00 ................ > 0040 00 00 00 00 e8 05 00 00 00 00 00 00 01 01 01 01 ................ > 0050 01 01 01 01 01 01 00 02 01 00 00 00 00 02 f1 03 ................ > 0060 1b 00 00 00 .... > > 0010 40 40 00 0c 00 ...........@@... > 0020 00 0d 0a 0d 0a 0d 0a ....... > > 4040004900001b285208000052454d4f544531534e2e0000130b00de0ad80418011b02f00000000000e805000000000000010101010101010101010002010000000002f1031b000000 > 4040000c00000d0a0d0a0d0a > > The rest of the packets are a series of command-responses, presumably querying printer parameters. > > (Now I'm idly wondering if it wouldn't make sense to try and write an > ESC/P dissector for Wireshark..) Remote mode commands are of the form XX (2 ASCII bytes) ll hh (little endian short, how many bytes) data So in this case, SN is the command (which is described as "select mechanism sequence"). It's then followed by 0x2e bytes of data. For the "SN" command, the first two bytes are the subcommand, which is 00 0x13. Unfortunately, I don't know what the subcommand 0x13 means, so the rest of the data doesn't mean too much to me. One possibility would be to extract that literal command, put it in the print stream at the right place, and see if it solves the problem. I believe those would be the bytes from 0x32 to 0x5f; the sequence starting at 0x60 (ESC 0 0 0) is the exit from remote mode, so that makes sense. |
|
From: Andrew X <68...@gm...> - 2022-04-04 06:19:09
|
I can put it into raw print file or into xml to test if you tell me what and were I need to insert пн, 4 апр. 2022 г., 03:13 Robert Krawitz <rl...@al...>: > On 4/3/22 12:59, Solomon Peachy wrote: > > On Sun, Apr 03, 2022 at 11:30:56AM -0400, Robert Krawitz wrote: > > But starting at #663 things get more interesting, with the REMOTE > command: > > > > 0010 40 40 00 49 00 .......I...@ > @.I. > > 0020 00 1b 28 52 08 00 00 52 45 4d 4f 54 45 31 53 4e ..(R...REMOTE1SN > > 0030 2e 00 00 13 0b 00 de 0a d8 04 18 01 1b 02 f0 00 ................ > > 0040 00 00 00 00 e8 05 00 00 00 00 00 00 01 01 01 01 ................ > > 0050 01 01 01 01 01 01 00 02 01 00 00 00 00 02 f1 03 ................ > > 0060 1b 00 00 00 .... > > > > 0010 40 40 00 0c 00 ...........@@... > > 0020 00 0d 0a 0d 0a 0d 0a ....... > > > > > 4040004900001b285208000052454d4f544531534e2e0000130b00de0ad80418011b02f00000000000e805000000000000010101010101010101010002010000000002f1031b000000 > > 4040000c00000d0a0d0a0d0a > > > > The rest of the packets are a series of command-responses, presumably > querying printer parameters. > > > > (Now I'm idly wondering if it wouldn't make sense to try and write an > > ESC/P dissector for Wireshark..) > > Remote mode commands are of the form > > XX (2 ASCII bytes) > ll hh (little endian short, how many bytes) > data > > So in this case, SN is the command (which is described as "select > mechanism sequence"). It's then > followed by 0x2e bytes of data. > > For the "SN" command, the first two bytes are the subcommand, which is 00 > 0x13. Unfortunately, I > don't know what the subcommand 0x13 means, so the rest of the data doesn't > mean too much to me. > > One possibility would be to extract that literal command, put it in the > print stream at the right > place, and see if it solves the problem. I believe those would be the > bytes from 0x32 to 0x5f; the > sequence starting at 0x60 (ESC 0 0 0) is the exit from remote mode, so > that makes sense. > > > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > |
|
From: Andrew X <68...@gm...> - 2022-03-31 22:34:14
|
I know this tricks, but much more easy to rewrite sequence in printer xml if somebody know what sequence can disable PW пт, 1 апр. 2022 г. в 01:31, Walker Blackwell <fo...@wa...>: > There’s a few ways to fix this. > > One way could simply be to put OHP Ultra Premium film in there because > it’s slightly milky white. > > The other thing could simply be that the film needs a white paper behind > it when the printer loads the film part (not both film and paper just the > paper behind the film so the printer know’s there’s something to load). The > XP-15000 printer needs that for film. > > You can also put white tape on left and right of film. > > Best regards > -Walker > > > > On Mar 31, 2022, at 5:57 PM, Andrew X <68...@gm...> wrote: > > > > Im working with epson L805 and half opaque film and have some troubles > when PW sensor in standard mode (not borderless) trying to check film. With > usual white paper everything works good. I know in other RIP software for > epsons present option to disable PW check. May be i can add some command to > init sequence to disable PW check? > > _______________________________________________ > > Gimp-print-devel mailing list > > Gim...@li... > > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > > > > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > |
|
From: Robert K. <rl...@al...> - 2022-04-01 01:19:33
|
On 3/31/22 18:33, Andrew X wrote: > I know this tricks, but much more easy to rewrite sequence in printer xml if somebody know what > sequence can disable PW If someone can discover this by decoding the print data (it would probably be in the remote mode block), I'd be happy to add it. > пт, 1 апр. 2022 г. в 01:31, Walker Blackwell <fo...@wa... > <mailto:fo...@wa...>>: > > There’s a few ways to fix this. > > One way could simply be to put OHP Ultra Premium film in there because it’s slightly milky white. > > The other thing could simply be that the film needs a white paper behind it when the printer > loads the film part (not both film and paper just the paper behind the film so the printer > know’s there’s something to load). The XP-15000 printer needs that for film. > > You can also put white tape on left and right of film. > > Best regards > -Walker > > > > On Mar 31, 2022, at 5:57 PM, Andrew X <68...@gm... <mailto:68...@gm...>> wrote: > > > > Im working with epson L805 and half opaque film and have some troubles when PW sensor in > standard mode (not borderless) trying to check film. With usual white paper everything works > good. I know in other RIP software for epsons present option to disable PW check. May be i can > add some command to init sequence to disable PW check? |
|
From: Andrew X <68...@gm...> - 2022-04-01 14:45:58
Attachments:
PaperLoad.html
initsequence.png
|
In attacment html file captured command "load paper" from epson service utility. with this command printer load film without any troubles and not checking with pw sensor can you tell me what sequences i need to test? Im not sure i can find right part of sequence by myself [image: initsequence.png] пт, 1 апр. 2022 г. в 04:20, Robert Krawitz <rl...@al...>: > On 3/31/22 18:33, Andrew X wrote: > > I know this tricks, but much more easy to rewrite sequence in printer > xml if somebody know what > > sequence can disable PW > > If someone can discover this by decoding the print data (it would probably > be in the remote mode > block), I'd be happy to add it. > > > пт, 1 апр. 2022 г. в 01:31, Walker Blackwell <fo...@wa... > > <mailto:fo...@wa...>>: > > > > There’s a few ways to fix this. > > > > One way could simply be to put OHP Ultra Premium film in there > because it’s slightly milky white. > > > > The other thing could simply be that the film needs a white paper > behind it when the printer > > loads the film part (not both film and paper just the paper behind > the film so the printer > > know’s there’s something to load). The XP-15000 printer needs that > for film. > > > > You can also put white tape on left and right of film. > > > > Best regards > > -Walker > > > > > > > On Mar 31, 2022, at 5:57 PM, Andrew X <68...@gm... <mailto: > 68...@gm...>> wrote: > > > > > > Im working with epson L805 and half opaque film and have some > troubles when PW sensor in > > standard mode (not borderless) trying to check film. With usual > white paper everything works > > good. I know in other RIP software for epsons present option to > disable PW check. May be i can > > add some command to init sequence to disable PW check? > > > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > |
|
From: Robert K. <rl...@al...> - 2022-04-01 23:47:33
|
On 4/1/22 10:45, Andrew X wrote: > In attacment html file captured command "load paper" from epson service utility. > with this command printer load film without any troubles and not checking with pw sensor > can you tell me what sequences i need to test? Im not sure i can find right part of sequence by myself Can you capture the first 16KB or so of the output and send that? It will be easier for me to try to interpret (I have tools to inspect the byte stream). Thanks! |
|
From: Robert K. <rl...@al...> - 2022-04-03 14:06:10
Attachments:
WireShark_load_sequence.pcapng
|
On 4/3/22 06:06, Andrew X wrote: > I grub All usb pockets with wireshark. in attachment. Is it ok to analyze? (Resent to list -- prefer that you reply-all rather than individual reply) Solomon, you have experience with wireshark, IIRC? I'd like to reconstruct the data stream from the host to the printer. > сб, 2 апр. 2022 г. в 02:47, Robert Krawitz <rl...@al... <mailto:rl...@al...>>: > > On 4/1/22 10:45, Andrew X wrote: > > In attacment html file captured command "load paper" from epson service utility. > > with this command printer load film without any troubles and not checking with pw sensor > > can you tell me what sequences i need to test? Im not sure i can find right part of sequence > by myself > > Can you capture the first 16KB or so of the output and send that? It will be easier for me to try > to interpret (I have tools to inspect the byte stream). Thanks! > |
|
From: Solomon P. <pi...@sh...> - 2022-04-03 14:24:37
Attachments:
signature.asc
|
On Sun, Apr 03, 2022 at 09:50:05AM -0400, Robert Krawitz wrote:
> Solomon, you have experience with wireshark, IIRC? I'd like to reconstruct the data stream from the
> host to the printer.
You just want it extracted, right?
- Solomon
--
Solomon Peachy pizza at shaftnet dot org (email&xmpp)
@pizza:shaftnet dot org (matrix)
High Springs, FL speachy (libra.chat)
|
|
From: Solomon P. <pi...@sh...> - 2022-04-03 14:28:21
Attachments:
signature.asc
|
On Sun, Apr 03, 2022 at 10:24:21AM -0400, Solomon Peachy wrote:
> You just want it extracted, right?
This capture doesn't seem to have any printer data -- just a USB HID
device and a USB-attached bluetooth device.
I think the capture was attached to the wrong logical bus..
- Solomon
--
Solomon Peachy pizza at shaftnet dot org (email&xmpp)
@pizza:shaftnet dot org (matrix)
High Springs, FL speachy (libra.chat)
|
Thanks for helping keep SourceForge clean.
X