Re: [Gimp-print-devel] Init sequence to disable PW sensor on EPSON

[Solomon P. <pi...@sh...>]

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)