Support for Epson Expression series (XP-610, XP-620, XP-630, XP-820, XP-830, etc) #1
Comments
|
Thanks for the report! Could you please provide me with approximate level of inks, that were in the printer during these reports being generated? Is it a new printer or an old one? I'm trying to estimate how much of it's waste ink tanker/counter should be filled for this time. Couple of new reports for the same printer would be also helpful. Please make two reports consequently (without printing) and then third report after printing one page with black-only text. |
|
It's a brand new printer so the waste ink should be relatively low. Another utility says that one waste ink counter is about 6% full (which I thought was unusually high for such a new printer) and the other is less than 1%. I think one counter is referring to the main pad that absorbs ink during head cleaning and charging, and the other is the pad that runs the length of the printer to absorb the edges off borderless photo prints. Not sure which one is which. I have attached three new reports, the first two taken about a minute apart without printing, and the third after printing a page of black text. Also, the ink level is from the printer's LCD right after printing the text. I haven't printed a lot since the first two reports so the level would be only slightly higher for the first two reports. |
|
If I can find a copy of the official Epson waste pad reset utility that works with this printer I can attach a Wireshark capture of the USB traffic. |
|
Yep, USB traffic dump would be helpful too. |
|
I think I have identified addresses of all ink counters and one waste ink counter. I was unable to differentiate between cyan and magenta because they have almost same ink level. I was also unable to found second waste ink counter. I have one candidate, but it's located not in sequential addresses, which is weird. Are you sure this printer have two waste ink counters? In any case, we can start testing what I've found. I created a branch https://github.com/lion-simba/reink/tree/xp630 with added support for XP-630. Let's try the following: Let's also do the same procedure for black ink: Then repeat for for other colors: -z2 (cyan), -z3 (magenta), -z4 (yellow), -z7 (photo black). In any case, attach all the dumps you get. |
|
I managed to obtain a copy of the official reset utility for the XP-620 (not the 630). I will post reports of this printer before and after resetting the counters and also a Wireshark USB traffic dump. |
|
I do also want to verify that we have the correct addresses with Wireshark before writing to the printer's EEPROM. |
|
I tried to do a dump of the eeprom, and I get "Fail to read EEPROM data from address 0." Setting debug mode gives: |
|
I also created a test report for the XP-620. This created a very large log file (about 12MB uncompressed) and ran for a long time until I interrupted it. I don't know if this log file is very useful but since I have the official reset utility for the XP-620 I can do a wireshark dump of the USB traffic when reading the counters and resetting. |
|
Here is a Wireshark capture of the USB traffic to/from the printer while reading and resetting both waste ink counters of the XP-620 using the official Epson utility. I think I did this capture correctly but it might not be correct. This was done with the Epson utility on Windows 10 64-bit in VirtualBox as guest, with Wireshark running on the host system (Ubuntu 16.04). Part of the reset procedure requires turning the printer off and back on (although I think this happens after the reset actually happens), which disconnected the printer from VirtualBox for a moment until I reconnected it manually. |
|
Regarding failed EEPROM dump, it seems like my mistake. I have missed that this printer is using two-byte addresses. I just corrected this in xp630 branch. Please get the changes and try again. Also, given that this is two-byte addresses printer, we might actually have seen only part of it's eeprom... Let's try to do a full dump: 0x0000-0xFFFF. Please replace 0x00-0xFF in all commands from my previous comment to 0x0000-0xFFFF. Test report from XP-620 seems good, although it was not completed (just as you stated). It has checked only 0x2e89 of 0xFFFF possible model codes. And it seems that it was running with enabled debug (REINK_DEBUG). Enabled debug will drastically increase time needed for checking all the model codes. I suggest to re-run the report with disabled debug. Thanks for the USB traffic log. I'll check it later. |
|
I have analysed XP-620's USB traffic log. It revealed the following:
So, if the utility first enquire current values of ink counters prior to resetting them, it must be that the first waste ink counter is at 0x0010-0x0013 and the second is at 0x0006. The question remains: what are all others address utility is writing to? |
|
The mass storage is probably from the printer's SD card slot, but there was not an SD card in the slot when I made that log. The computer might still see it as an empty drive though. Not sure what the other addresses are. I noticed after running the Epson utility that the printer took a long time to print the first time, and moved the print carriage back and forth several times, similar to what it does during a head cleaning. The LCD display on the printer read "Printing" and not "cleaning" though, but it still could have been a head cleaning. The other addresses might have something to do with this. |
|
I've added waste ink counter reset for XP-620 in a new xp620 branch. Currently it writes zeroes to 0x0010-0x0013 and 0x0006. Probably it's enough. Could you please test it? Let's also get the dumps before and after reset. |
|
Dumping the eeprom appears to work but the result is different from the official utility. It could just be that the official utility formats the data differently. === printer_model === |
|
Later I will attach a Wireshark capture of the official utility dumping the EEPROM. |
|
Here are three Wireshark dumps, one is the official utility reading the EEPROM, the other is the official utility reading and resetting the waste ink counters (again, just to verify that it does the same thing each time and that there isn't some kind of checksum byte that it's writing to), and the last one is a capture of what ReInk is doing during the failed reset. Just to be safe I would suggest doing the same thing that the official utility does during resetting, because if it's writing to those other bytes there must be a reason. |
|
Here is also a test report from the XP-620. |
|
Here are the ink levels from the XP-620. |
|
Just realized that waste1.dump is an empty file. My bad. I will do a full dump of the eeprom tomorrow. |
|
Hi, I encountered the problem of a full ink-waste on my Epson XP-760 when I found this tool and your discussion. Did the reset of the ink-waste work in the end? Would this also work on the XP-760? I did the testreport, which look in my case like: |
|
Hi, Here's a testreport for the Epson XP-700. It has 4 cartridges:
For some reason, the yellow cartridge is not recognized. I hope that this doesn't affect the test results.
|
|
XP-830 here. Model code is 0x28 0x09. The printer was blocked with "end of life" message a first time; then received a waste ink counter reset with "WIC reset utility" (and ink cartridges were taken off); finally got blocked with EOL message for second time (which Epson says requires a service by them). Below are EEPROM dumps of non-null bytes. Cols 3,5 marks which bytes changed in-between. Found no non-null bytes in 0x282-0xffff. It seems at least bytes 0x08, 0x10-0x15, 0x34 are involved (and 0x1ed? -- higher bytes were not dumped between the two EOL states). The second but not least issue is that writing to EEPROM fails. With current reink the response is "||:42:NA;". Maybe this would work as long as the printer is not in the (second/last) EOL state? (It also fails when writing to "protection" byte 0x01ed. @sinopsysHK, have you had any success with PR11?) EEPROM dumps: |
|
Hello,
Actually I couldn’t test it because I couldn’t figure out what bytes were to rest before finally using WICReset tool (paying for a key).
But then I could find where the counters are and recorded it here for next time.
… On 7 May 2019, at 9:08 PM, Daniel Gerber ***@***.***> wrote:
XP-830 here. Model code is 0x28 0x09.
The printer was blocked with "end of life" message a first time; then received a waste ink counter reset with "WIC reset utility" (and ink cartridges were taken off); finally got blocked with EOL message for second time (which Epson says requires a service by them). Below are EEPROM dumps of non-null bytes. Cols 3,5 marks which bytes changed in-between. Found no non-null bytes in 0x282-0xffff.
It seems at least bytes 0x08, 0x10-0x15, 0x34 are involved (and 0x1ed? -- higher bytes were not dumped between the two EOL states).
The second but not least issue is that writing to EEPROM fails. With current reink the response is "||:42:NA;".
When mimicking traffic from @blenheimears's dumps above, the device does answer with "||:42:OK;", but subsequent reads still return the original value:
Sending...:
>> 02 02 00 1A 01 00 7C 7C 10 00 28 09 42 BD 21 34 00 5E 42 6D 75 69 62 66 62 2F
>> ° ° | | ° ( Ť B ! 4 ° ^ B m u i b f b /
Received 16B:
<< 02 02 00 10 00 01 7C 7C 3A 34 32 3A 4F 4B 3B 0C
<< ° ° | | : 4 2 : O K ;
Sending...:
>> 02 02 00 11 01 00 7C 7C 07 00 28 09 41 BE A0 34 00
>> ° ° | | ° ( Ť A 4 °
Received 26B:
<< 02 02 00 1A 00 01 40 42 44 43 20 50 53 0D 0A 45 45 3A 30 30 33 34 36 38 3B 0C
<< ° ° @ B D C P S Ř E E : 0 0 3 4 6 8 ;
Maybe this would work as long as the printer is not in the (second/last) EOL state?
(It also fails when writing to "protection" byte 0x01ed. @sinopsysHK, have you had any success with PR11?)
EEPROM dumps:
addr,waste_dead1,wicreset,afterwic_wo_cartridges,use,waste_dead2
0000,,,,,
0001,,,,,
0002,02,,02,,02
0003,,,,,
0004,68,,68,,68
0005,08,,08,,08
0006,,,,,
0007,,,,,
0008,9D,X,D0,X,9D
0009,,,,,
000A,E4,,E4,X,3B
000B,6C,,6C,X,71
000C,14,,14,X,36
000D,69,,69,X,6D
000E,E6,X,E7,X,3F
000F,6C,,6C,X,71
0010,05,X,B5,X,13
0011,21,X,1D,X,21
0012,,X,D9,,D9
0013,,X,0B,,0B
0014,02,X,,X,5F
0015,25,X,,X,03
0016,58,,58,X,2C
0017,CC,,CC,X,12
0018,16,,16,X,C4
0019,06,,06,X,
001A,C0,,C0,X,E7
001B,9F,,9F,X,8C
001C,85,,85,X,5B
001D,04,,04,X,06
001E,70,,70,X,20
001F,23,,23,X,E1
0020,34,,34,X,FF
0021,02,,02,X,03
0022,AC,,AC,X,CC
0023,7A,,7A,X,F4
0024,06,,06,X,CB
0025,02,,02,X,03
0026,79,,79,X,58
0027,01,,01,X,5E
0028,21,,21,X,52
0029,02,,02,X,06
002A,,,,,
002B,,,,,
002C,,,,,
002D,,,,,
002E,A0,,A0,,A0
002F,73,,73,,73
0030,05,,05,X,03
0031,,,,,
0032,73,,73,X,5F
0033,17,,17,,17
0034,68,X,5E,X,68
0035,5E,,5E,,5E
0036,,X,01,X,
0037,,,,,
0038,,,,,
0039,,,,,
003A,,,,X,01
003B,,,,,
003C,,,,,
003D,,,,,
003E,,,,,
003F,,,,,
0040,36,,36,,36
0041,FF,,FF,,FF
0042,48,,48,X,2B
0043,F9,,F9,X,F1
0044,FF,,FF,,FF
0045,35,,35,X,BA
0046,F6,,F6,X,F8
0047,FF,,FF,,FF
0048,07,,07,X,7E
0049,F3,,F3,X,F5
004A,FF,,FF,,FF
004B,C8,,C8,X,36
004C,F2,,F2,X,F5
004D,FF,,FF,,FF
004E,4A,,4A,X,CB
004F,F2,,F2,X,F6
0050,FF,,FF,,FF
0051,FF,,FF,,FF
0052,FF,,FF,,FF
0053,,,,,
0054,F4,,F4,,F4
0055,02,,02,,02
0056,9C,X,B5,X,14
0057,67,,67,X,6D
0058,22,X,38,X,23
0059,0E,,0E,X,32
005A,3C,X,7E,X,97
005B,79,X,D0,X,5A
005C,DF,X,E0,X,2C
005D,07,,07,X,08
005E,,,,,
005F,,,,,
0060,36,,36,X,FC
0061,CD,,CD,X,D3
0062,,,,,
0063,,,,,
0064,,,,,
0065,,,,,
0066,FF,,FF,,FF
0067,FF,,FF,,FF
0068,,,,,
0069,,,,,
006A,40,,40,,40
006B,01,,01,,01
006C,0B,,0B,,0B
006D,,,,,
006E,05,,05,,05
006F,18,,18,X,19
0070,03,,03,,03
0071,30,,30,X,23
0072,54,,54,X,6A
0073,05,,05,X,06
0074,,,,,
0075,82,,82,X,85
0076,A8,X,A9,X,12
0077,0D,,0D,X,0E
0078,08,,08,,08
0079,1C,,1C,,1C
007A,1E,,1E,,1E
007B,08,,08,,08
007C,B3,,B3,,B3
007D,,,,,
007E,8E,,8E,,8E
007F,26,,26,,26
0080,FF,,FF,,FF
0081,D0,,D0,,D0
0082,01,,01,,01
0083,,,,,
0084,23,,23,,23
0085,05,,05,,05
0086,07,,07,,07
0087,FD,,FD,,FD
0088,04,,04,,04
0089,FD,,FD,,FD
008A,02,,02,,02
008B,FB,,FB,,FB
008C,FE,,FE,,FE
008D,FB,,FB,,FB
008E,09,,09,,09
008F,FB,,FB,,FB
0090,,,,,
0091,02,,02,,02
0092,05,,05,,05
0093,,,,,
0094,,,,,
0095,FD,,FD,,FD
0096,FA,,FA,,FA
0097,,,,,
0098,A8,X,A9,X,12
0099,0D,,0D,X,0E
009A,,,,,
009B,,,,,
009C,,,,,
009D,,,,,
009E,,,,,
009F,,,,,
00A0,82,,82,,82
00A1,01,,01,,01
00A2,D1,,D1,,D1
00A3,0B,,0B,,0B
00A4,A9,,A9,,A9
00A5,01,,01,,01
00A6,37,,37,,37
00A7,05,,05,,05
00A8,67,,67,X,96
00A9,26,,26,,26
00AA,,,,,
00AB,,,,,
00AC,,,,,
00AD,,,,,
00AE,,,,,
00AF,,,,,
00B0,,,,,
00B1,,,,,
00B2,,,,,
00B3,,,,,
00B4,01,,01,,01
00B5,,,,,
00B6,,,,,
00B7,,,,,
00B8,67,,67,,67
00B9,68,,68,,68
00BA,5D,,5D,,5D
00BB,64,,64,,64
00BC,61,,61,,61
00BD,6B,,6B,,6B
00BE,64,,64,,64
00BF,68,,68,,68
00C0,5C,,5C,,5C
00C1,65,,65,,65
00C2,64,,64,,64
00C3,64,,64,,64
00C4,65,,65,,65
00C5,66,,66,,66
00C6,62,,62,,62
00C7,63,,63,,63
00C8,01,,01,,01
00C9,68,,68,,68
00CA,55,,55,,55
00CB,4D,,4D,,4D
00CC,A3,,A3,,A3
00CD,72,,72,,72
00CE,14,,14,,14
00CF,68,,68,,68
00D0,,,,,
00D1,,,,,
00D2,4F,,4F,,4F
00D3,,,,,
00D4,01,,01,,01
00D5,,,,,
00D6,,,,,
00D7,,,,,
00D8,57,,57,,57
00D9,35,,35,,35
00DA,39,,39,,39
00DB,59,,59,,59
00DC,30,,30,,30
00DD,30,,30,,30
00DE,35,,35,,35
00DF,35,,35,,35
00E0,38,,38,,38
00E1,30,,30,,30
00E2,,,,,
00E3,,,,,
00E4,,,,,
00E5,,,,,
00E6,,,,,
00E7,,,,,
00E8,,,,,
00E9,,,,,
00EA,44,,44,,44
00EB,D2,,D2,,D2
00EC,44,,44,,44
00ED,58,,58,,58
00EE,14,,14,,14
00EF,DB,,DB,,DB
00F0,03,,03,,03
00F1,,,,,
00F2,,,,,
00F3,,,,,
00F4,41,,41,,41
00F5,03,,03,,03
00F6,4F,,4F,,4F
00F7,4F,,4F,,4F
00F8,3F,,3F,X,17
00F9,3F,,3F,,3F
00FA,26,,26,,26
00FB,3F,,3F,,3F
00FC,17,,17,,17
00FD,,,,,
00FE,,,,,
00FF,,,,,
0100,,,,,
0101,04,,,,04
0102,21,,,,21
0103,,,,,
0104,,,,,
0105,,,,,
0106,20,,,,20
0107,,,,,
0108,,,,,
0109,,,,,
010A,,,,,
010B,,,,,
010C,AE,,,,AE
010D,01,,,,01
010E,88,,,,88
010F,04,,,,04
0110,,,,,
0111,,,,,
0112,,,,,
0113,0A,,,,0A
0114,,,,,
0115,AE,,,,AE
0116,01,,,,01
0117,88,,,,88
0118,04,,,,04
0119,31,,,,31
011A,,,,,
011B,,,,,
011C,,,,,
011D,04,,,,04
011E,06,,,,06
011F,66,,,,66
0120,,,,,
0121,66,,,,66
0122,,,,,
0123,,,,,
0124,58,,,,58
0125,02,,,,02
0126,,,,,
0127,,,,,
0128,,,,,
0129,,,,,
012A,,,,,
012B,,,,,
012C,,,,,
012D,,,,,
012E,21,,,,21
012F,11,,,,11
0130,,,,,
0131,,,,,
0132,AB,,,,AB
0133,92,,,,92
0134,01,,,,01
0135,,,,,
0136,,,,,
0137,20,,,,20
0138,,,,,
0139,,,,,
013A,,,,,
013B,,,,,
013C,,,,,
013D,,,,,
013E,20,,,,20
013F,,,,,
0140,,,,,
0141,,,,,
0142,,,,,
0143,AE,,,,AE
0144,01,,,,01
0145,88,,,,88
0146,04,,,,04
0147,20,,,,20
0148,,,,,
0149,,,,,
014A,,,,,
014B,03,,,,03
014C,64,,,,64
014D,,,,,
014E,,,,,
014F,,,,,
0150,CC,,,,CC
0151,01,,,,01
0152,74,,,,74
0153,04,,,,04
0154,05,,,,05
0155,06,,,,06
0156,03,,,,03
0157,,,,,
0158,05,,,,05
0159,06,,,,06
015A,01,,,,01
015B,10,,,,10
015C,,,,,
015D,,,,,
015E,21,,,,21
015F,D0,,,,D0
0160,,,,,
0161,,,,,
0162,10,,,,10
0163,03,,,,03
0164,,,,,
0165,,,,,
0166,,,,,
0167,,,,,
0168,,,,,
0169,,,,,
016A,05,,,,05
016B,06,,,,06
016C,,,,,
016D,,,,,
016E,05,,,,05
016F,06,,,,06
0170,01,,,,01
0171,10,,,,10
0172,05,,,,05
0173,06,,,,06
0174,01,,,,01
0175,31,,,,31
0176,,,,,
0177,03,,,,03
0178,,,,,
0179,03,,,,03
017A,22,,,,22
017B,99,,,,99
017C,,,,,
017D,,,,,
017E,,,,,
017F,70,,,,70
0180,99,,,,99
0181,,,,,
0182,05,,,,05
0183,06,,,,06
0184,,,,,
0185,,,,,
0186,,,,,
0187,,,,,
0188,,,,,
0189,,,,,
018A,22,,,,22
018B,30,,,,30
018C,30,,,,30
018D,30,,,,30
018E,30,,,,30
018F,,,,,
0190,02,,,,02
0191,,,,,
0192,,,,,
0193,22,,,,22
0194,69,,,,69
0195,01,,,,01
0196,8D,,,,8D
0197,02,,,,02
0198,66,,,,66
0199,0E,,,,0E
019A,D3,,,,D3
019B,02,,,,02
019C,5B,,,,5B
019D,01,,,,01
019E,F1,,,,F1
019F,0C,,,,0C
01A0,55,,,,55
01A1,0E,,,,0E
01A2,F7,,,,F7
01A3,0C,,,,0C
01A4,,,,,
01A5,,,,,
01A6,,,,,
01A7,,,,,
01A8,,,,,
01A9,,,,,
01AA,,,,,
01AB,,,,,
01AC,01,,,,01
01AD,,,,,
01AE,,,,,
01AF,,,,,
01B0,,,,,
01B1,,,,,
01B2,64,,,,65
01B3,01,,,,01
01B4,AC,,,,AC
01B5,,,,,
01B6,7E,,,,7E
01B7,03,,,,03
01B8,91,,,,91
01B9,,,,,
01BA,B0,,,,B0
01BB,06,,,,06
01BC,56,,,,51
01BD,02,,,,02
01BE,CF,,,,D6
01BF,01,,,,01
01C0,CD,,,,D3
01C1,01,,,,01
01C2,71,,,,76
01C3,01,,,,01
01C4,,,,,
01C5,,,,,
01C6,80,,,,82
01C7,,,,,
01C8,,,,,
01C9,,,,,
01CA,1D,,,,1D
01CB,1C,,,,1C
01CC,,,,,
01CD,,,,,
01CE,,,,,
01CF,,,,,
01D0,,,,,
01D1,,,,,
01D2,,,,,
01D3,,,,,
01D4,,,,,
01D5,,,,,
01D6,,,,,
01D7,,,,,
01D8,,,,,
01D9,,,,,
01DA,,,,,
01DB,,,,,
01DC,,,,,
01DD,,,,,
01DE,,,,,
01DF,,,,,
01E0,,,,,
01E1,,,,,
01E2,,,,,
01E3,,,,,
01E4,,,,,
01E5,,,,,
01E6,,,,,
01E7,,,,,
01E8,,,,,
01E9,,,,,
01EA,,,,,
01EB,,,,,
01EC,02,,,,02
01ED,,,,,
01EE,,,,,
01EF,,,,,
01F0,,,,,
01F1,80,,,,80
01F2,,,,,
01F3,,,,,
01F4,,,,,
01F5,80,,,,80
01F6,02,,,,02
01F7,04,,,,04
01F8,,,,,
01F9,,,,,
01FA,,,,,
01FB,,,,,
01FC,,,,,
01FD,,,,,
01FE,,,,,
01FF,,,,,
0200,F8,,,,FA
0201,EB,,,,ED
0202,,,,,
0203,,,,,
0204,CC,,,,D0
0205,01,,,,01
0206,,,,,
0207,,,,,
0208,,,,,
0209,,,,,
020A,0F,,,,32
020B,,,,,
020C,,,,,
020D,,,,,
020E,,,,,
020F,,,,,
0210,,,,,
0211,,,,,
0212,0A,,,,0A
0213,0B,,,,0B
0214,,,,,
0215,34,,,,34
0216,08,,,,08
0217,,,,,
0218,,,,,
0219,9A,,,,9A
021A,0B,,,,0B
021B,,,,,
021C,,,,,
021D,01,,,,01
021E,,,,,
021F,,,,,
0220,,,,,
0221,,,,,
0222,,,,,
0223,,,,,
0224,,,,,
0225,,,,,
0226,,,,,
0227,,,,,
0228,,,,,
0229,,,,,
022A,,,,,
022B,,,,,
022C,,,,,
022D,,,,,
022E,,,,,
022F,,,,,
0230,,,,,
0231,,,,,
0232,,,,,
0233,,,,,
0234,,,,,
0235,,,,,
0236,,,,,
0237,,,,,
0238,,,,,
0239,,,,,
023A,,,,,
023B,,,,,
023C,,,,,
023D,,,,,
023E,,,,,
023F,01,,,,01
0240,,,,,
0241,,,,,
0242,,,,,
0243,,,,,
0244,,,,,
0245,,,,,
0246,,,,,
0247,0B,,,,0B
0248,,,,,
0249,0B,,,,0B
024A,0B,,,,0B
024B,,,,,
024C,,,,,
024D,25,,,,25
024E,25,,,,25
024F,25,,,,25
0250,25,,,,25
0251,25,,,,25
0252,0B,,,,0B
0253,25,,,,25
0254,25,,,,25
0255,25,,,,25
0256,0B,,,,0B
0257,,,,,
0258,,,,,
0259,0B,,,,0B
025A,0B,,,,0B
025B,,,,,
025C,0B,,,,0B
025D,0B,,,,0B
025E,,,,,
025F,,,,,
0260,,,,,
0261,,,,,
0262,,,,,
0263,,,,,
0264,,,,,
0265,,,,,
0266,,,,,
0267,,,,,
0268,,,,,
0269,,,,,
026A,,,,,
026B,,,,,
026C,,,,,
026D,,,,,
026E,,,,,
026F,,,,,
0270,,,,,
0271,,,,,
0272,,,,,
0273,,,,,
0274,,,,,
0275,,,,,
0276,,,,,
0277,,,,,
0278,,,,,
0279,,,,,
027A,,,,,
027B,,,,,
027C,,,,,
027D,,,,,
027E,,,,,
027F,,,,,
0280,3D,,,,3D
0281,0A,,,,0A
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
So, the suffix in write commands seems to be a (model specific?) opaque key... |
|
So it means reink in current version do not enable the reset as this command suffix isn't supported hence the failure on XP-620 I guess. Obviously my proposed PR will not work neither for XP-821 neither as I didn't add this suffix (I thought it could have been par of the USB protocol) But reviewing the code and the trace it is clear that this 8 bytes suffix is fully part of the command but I have no clue it it is dynamically computed (kind of checksum) or if it is static kind of internal key. I couldn't find any reference on that matter :( |
|
Hi, thank you!! |
|
Hi, by searching how to reset the waste ink counter on my XP-510 I found a blog using an snmpget command to reset the waste ink counter.
It's actually working, but I don't know if the snmp packets are useful to support this model in reink. |
|
Hi, just to add a hint I found the OID for the XP-540: |
|
Hi all, thanks to this thread I was able to finally reset my Epson XP-850 that was sitting getting dust for four years. It should be obvious, but: if you want to replicate it, do it at your own risk. Just one note in case you only use the WIC utility with the "trial" key: be aware that if your printer has two WICs, it will reset both to 80% and, in my case, only the first one was above 100%, the second was at 12%. @Earnestly if you want, you can update the table: |
Hello, i've tried this on my XP-325 (identical to XP-315) but it does not work. snmpget report always this when i send commands: "00 7C 7C 3A 34 32 3A 4E 41 3B 0C " |
|
Thanks @3BIUM, updated. @axel-1267 Those bytes, I'm not sure how accurate the wicreset tools are (it seems like it "sprays" a bunch of bytes in certain ranges), or how they're even determining the counter values. I've isolated from examples that it reads 2 or 3 addresses (oid ~24..34) which are used to produce the percent levels for both ink counters. E.g. The two ink counters here appear to consist of three addresses: And from this, it determines: I have not yet found no way to correlate this. The bit patterns interpreted as IEEE, various fixed-point formats, integer types, etc. don't seem to produce anything that could correspond to the percentages the tool prints. More The next step might be trying to map the EEPROM to note where values are stored, e.g. ~192..201 appears to be the serial ID. |
@Earnestly, instead of Great investigation, will soon have a look at the XP-610 I got from my parents-in-law. |
|
Good insight, updated to |
|
It seems like the ink counter calculation can be figured out, given the log above: Here the values Interpreting For the second counter, the factor appears to be The address locations may be model specific though, so I'm not sure how useful this is. |
|
@Earnestly, looking at my logs, I think you figured it out correctly. I saw a Youtube video where someone used the official (but cracked) Epson utility and it showed the counters in "point" units (with also the percentages) and there were also indicated "max" values for both counters, which were respectively 8450 and 2903; if I recall correctly, the printer model in the video was the XP-750 (edit: in another video the values were the same also for the XP-600/XP-605). From my logs, calculating the read percentages, I can tell they match also the maximum values for my model (XP-850). It remains to understand what the other addresses (in my case 20.0, 21.0, 52.0 and 53.0) are for. As someone has already pointed out they could be a way to flag that the "trial" key has alredy been used on a printer. In my case the values were 13, 00, 68, 5E and were changed to 00, 00, 5E, 5E when resetting to 80%. |
|
That is interesting; soon I might have a spare XP-625 with which I can try various experiments. I may have already written to certain locations and unknowingly changed internal colour settings so that blue now prints as yellow. It would be nice to believe that these locations can be determined from the content of the eepom itself. Perhaps even the key as the key needs to exist somewhere, in some form, to be compared, but I doubt this is in the eeprom. |
|
I tried the same than you to convert values to percentage on my printer, you were quicker than me to figure that out. 😉 I believe it would not be so easy to find those from eeprom only, wicreset uses a dedicated database. |
|
Another one for the table above: XP-610 Determined from ~/.wicreset/application.log using the TRIAL key. Printer selection in wicreset is named "EPSON XP-610/611/615", so the key (and model no.?) might work for XP-611 and XP-615 as well. The two waste ink counters could be cleared with these commands then: The wicreset tool wrote bytes to addresses as follows in this order: This matches #1 (comment) above describing the XP-850 amongst others, also the max counter values of 8450 and 2903 do fit. However, I don't know all of my EEPROM values before the reset. |
|
The table seems to suffer a bit from dec/hex confusion. In #1 (comment) for XP-620 there is written 0x57 0x05, the table contains .57.5. In 34bc702 of the |
|
I piped
For my XP-610, reading from 0x0200 and higher returned all 0, so it seems 512 bytes of memory are accessible. However, I only checked up to 0x3FF. |
|
Added the XP-610 model, thanks. The OID is in decimal, so the Srecord seems interesting, I'll have to keep that in mind. |
Sure, but your table contains
Will have a look at. |
|
That would mean both the 620 and 625 have the same model number which is curious. Regardless, I'll just update it anyway as the whole thing can change as things are learned. |
Which was the case before with 700+850, 630+830 and newly 510+610. Having a look at the table now, same model number also means same write key. That's consistent. The table could be adapted to reduce redundancy, only the first XP-* column is different for several rows. Would lose alphabetical order of the printer names of course, but might help recognize other patterns. |
|
I'd prefer to name By the way, what's this |
|
It's from their escpr linux drivers, see |
|
@axel-1267 You could identify your model number from wicreset's application.log. If it exists in the table above, then it seems the same key is valid for your printer. |
I used the same write key on my XP-315 and XP-313 , Used snmp commands with Linux its throw this "00 7C 7C 3A 34 32 3A 4F 4B 3B 0C" :42:OK; instead of "00 7C 7C 3A 34 32 3A 4E 41 3B 0C " that you got and i was able to reset both wastink counters on my printers. |
Using -Oa I already got the format to easily convert to hex dump, I didn't convert the hex myself, just split the hex part into Compare these outputs: |
Thanks, I will give a try and dive the logs. @Dj33as Thanks for your report. I thought about mine and will give it another shot. It could be a network problem on my lan (SNMP traffic restricted) and not the key. |
|
@Earnestly thanks for noting the naming usage! After trying a few taxons... |
|
Ha, that's wonderful |
|
Hello, I just discover this project and I want to contribute and add support for my printer. I got an XP-245. |
|
@Jocabin, the process would be: find model code and secret suffix key,
then look for similar models whose eeprom layout is known. Else you
have to try memory addresses guessed from traffic logs or from
inspecting eeprom values...
(Maybe my python utility linked above will be easier to use for this.)
But what is it you want to achieve? I think ink levels in your printer
will be managed by the cartridges and cannot (?) be changed with
reink. The only use here is to get rid of the waste ink pads warning.
|
|
Had the "ink pad full issue" with my Expression XP-820. I initially thought that all I need to is replace the tank - $10 and 5 min with screws. But then it turned out to be a stupid counter, and the old tank was nowhere full anyway. After wasting N hours trying to reset the counter (and being rather displeased with Epson), I can confirm that the write code for XP-820 is the same as XP-850 "Ijcjtdvt". The reset sequence that worked for me goes over 16 through 21, use at your own risk: for xx in 16 17 18 19 20 21 ; do snmpget -Ov -OQ -v1 -c public $printer_ip_address 1.3.6.1.4.1.1248.1.2.2.44.1.1.2.1.124.124.16.0.40.0.66.189.33.$xx.0.0.73.106.99.106.116.100.118.116 ; done One more thing - before I got this working I did upgrade the firmware, this might or might not be needed. I was hoping firmware upgrade will reset the counters, but this did not happen. To Epson folks - this should be a button on the menu. You can warn customers that not replacing tank will make ink spill, but ultimately it is their choice, just like what cartridges to use. XHFKF! And if you are planning to brick the printer after N pages, this should be in bold letters on the box, so we can avoid buying it, and not have a problem when we need to print something by tomorrow. |
|
At the risk of having the gray market Epson reset cabal on my ass, here's a dump of the database WicReset uses. It has a ton of printer models, and the file format isn't super hard to parse. I might write a parser for it sometime soon. I'd be super grateful if anyone else wants to help. P.S. I'm also looking into the chipless firmware thing. If anyone has anything relating to that, please chime in. |
|
I stumbled upon a Python project based on Reink which contains some keys for printers. One of them is for the XP-2150. I have an XP-2100, but thanks to the file from wicreset, I found out that the XP-2100 and XP-2150 share the same behaviors. Here is the key: 67.106.101.98.101.98.115.106 I wonder if it is possible to reset the counter for the ink cartridge. I'm trying to find the OID code for it but haven't managed to get it...
|
|
Hi, I'm trying to reset the inkpad on my XP-960, could you help me? Is it possible? |
and others
These are units that have both a printer and scanner in one. I don't think the cartridge level can be reset, but the waste ink counter should be able to be reset. These printers have Cyan, Yellow, Magenta, Black, and Photo Black cartridges. There are no light cyan or light magenta cartridges, except on the XP-860 and XP-950 (which also don't have the photo black cartridge). These test reports are from an Epson XP-630. I also have an XP-620 (which uses a different cartridge) but I don't have any cartridges for it yet. I can run a test on it once my cartridges arrive.
testreport-epson-xp-630.zip
The text was updated successfully, but these errors were encountered: