L3250 resetting waste ink issue

[klifinpol]

Hello, I've tried using your tool to reset the ink levels on one of my L3250 and I have ran into multiple errors.

When I try to ''Reset Waste Ink Levels'' it pops up with an error saying ''cannot readd EEPROM values for ''Raw waste rest'': invalid printer model selected. So I saw that somone had a simmilar issue and it was suggested to use the ''Detect Access Keys'' which I tried and it crashed the program, similarly when I tired using Detect configuration it also spit out an error saying ''int() can't convert non-string with explicit base''

Due to the crashes I attempted to use the the comand-line tool, however similarly after the process was completed it poped up with and error saying ''Cannot found Read_key''

I'm not a coder so apologise if I do not know what these error codes mean exactly however I hopefully have provided enough data to be able to solve this issue... I hope.

[Ircama]

Thanks this helped correct something.

Please try running the command line tool with the -d option and upload the output.

Example:

python3 epson_print_conf.py --detect-key -a 192.168.178.29 -m L3250 -d >trace.log 2>&1

You should get a file named trace.log that you can browse and upload.

[klifinpol]

Sorry about my previous comment I used the incorrect adress (mine ends with .32) here are the correct .log files.
I took the liberty of trying two other commands aswell. One was the --reset_waste_ink and -i (i was unable to locate the ''detect configuration'' equivalent in the command line). I truely hope this helps you find and solve the issue as my printer is currently an expensive paperweight...

(I had to add the bruteforce attempt in two parts as the log file on its own was too large)

trace_BruteForce_Part1.txt
trace_Bruteforce_Part2.log
trace_info.log
trace_wasteRest.log

[Ircama]

It fails to read values from the EEPROM. From your logs, the following is strange:

  ADDRESS: 1.3.6.1.4.1.1248.1.2.2.44.1.1.2.1.124.124.7.0.74.54.65.190.160.0.0
  OID: 0=0x0
  TAG: OctetString
  RESPONSE: b'\x00||:41:NA;\x0c'

Same issue as #26 (comment).

If you have a Linux system (or Windows Subsystem for Linux), you might run the following commands and paste the outputs:

snmpget -v1 -d -c public 192.168.178.32 1.3.6.1.4.1.1248.1.2.2.44.1.1.2.1.124.124.7.0.74.54.65.190.160.0.0
snmpget -v1 -d -c public 192.168.178.32 1.3.6.1.4.1.1248.1.2.2.44.1.1.2.1.124.124.7.0.74.54.65.190.160.48.0
snmpget -v1 -d -c public 192.168.178.32 1.3.6.1.4.1.1248.1.2.2.44.1.1.2.1.124.124.7.0.74.54.65.190.160.48.1
snmpget -v1 -d -c public 192.168.178.32 1.3.6.1.4.1.1248.1.2.2.44.1.1.2.1.124.124.7.0.74.54.65.190.160.255.0

There are also binaries for Windows which include snmpget.exe, that runs with the same arguments.

The answer should include these two strings @BDC PS and EE:

[klifinpol]

Here hope this helps, I'm not sure however if what I did was correct....

[Ircama]

Please also try these:

snmpget -v1 -d -c public 192.168.178.32 1.3.6.1.4.1.1248.1.2.2.44.1.1.2.1.124.124.7.0.74.54.65.190.160.1.0
snmpget -v1 -d -c public 192.168.178.32 1.3.6.1.4.1.1248.1.2.2.44.1.1.2.1.124.124.7.0.74.54.65.190.160.0.1

[klifinpol]

Here you go. If you'd like I'd be willing to hop on discord or somthing similar to try and help resolve this issue.

[Ircama]

Thanks. Unfortunately, there is no way to manage this printer model at the moment; the only thing which can be done is temporarily removing this model from the configuration. I will ask you for more tests as soon as I have other ideas.

[klifinpol]

I called a few of my programmer friends to help fix my printer... We are trying a few ideas; aporximatley 65k*6 ideas

[klifinpol]

... we ran out of ideas... (our attempt didn't work)