Closed skissane closed 8 months ago
Thank you very much! :tada:
I published a new version (0.6.0), which sends a request with the old XML (because it worked before for some models) and if it fails, if applies the modifications that you mentioned. With this changes, I could successfully download the firmware for MFC-L3750CDW.
As described in https://github.com/sedrubal/brother_printer_fwupd/issues/20#issuecomment-2078379285, this hack was also necessary for my HL-L2360DW printer.
- In
<MODELINFO>
, your tool sends<SERIALNO></SERIALNO>
, that other tool sends<SELIALNO>
(yes terrible spelling is necessary) with the actual printer serial as contents- Your tools sends
, theirs sends EWS
At least for my printer, the "SELIALNO" misspelling isn't necessary to be able to fetch its firmware files, only the <DRIVER>EWS</DRIVER>
change is needed.
Given that https://github.com/sedrubal/brother_printer_fwupd/commit/565ef037ea8fd9ccc6bd0b03dd7c18120f7f17e6 didn't actually implement sending the printer's serial number as the tag contents, and that some of Brother's own tools send it and others don't, it's a pretty good indication that the SERIALNO/SELIALNO bit is not necessary.
Thanks @dlenski for this hint. I'll have a look 😉
This tool doesn't work with MFC-L3750CDW – but https://github.com/CauldronDevelopmentLLC/oh-brother does
The difference seems to be in the XML request being sent:
<MODELINFO>
, your tool sends<SERIALNO></SERIALNO>
, that other tool sends<SELIALNO>
(yes terrible spelling is necessary) with the actual printer serial as contents<DRIVER></DRIVER>
, theirs sends<DRIVER>EWS</DRIVER>
Your tool doesn't get back a response, that other tool gets something like this: