Comment 3 for bug 426826

I don't know about the driver's internals
but as it looks to me it seems there is
a common root cause for all those issues:

It seems the driver does not work in full
compliance to what is specified in the PPD
but has some values (which should actually
be specified in the PPD) as hardcoded "secrets"
inside the driver, compare the related issue
https://bugs.launchpad.net/hplip/+bug/237342

If I am right, I would prefer to have the root cause fixed
instead of fixing each individual issue separately.

I.e. move all hardcoded values from the driver
to the PPD.

Have in mind that one can specify values in the PPD
which are meant to be changed by the user
(i.e. which are not in a "*OpenUI ... *CloseUI" section)
so that it is really possible to have all model-specific values
for the driver in the PPD.