primax: Thread: Can not identify this scanner. code: 0e

Some weeks ago, I desperately tried to get my Colorado D600 (30Bit)
workingwith primax_scan-0.93. However, all my attempts were in vain, 
because my parport driver refused to recognize EPP mode for some reason.

In the meantime, I have replaced the mainboard and I thought it's time 
to have another go. So I used my old primax_scan-0.93 binaries
and the parport EPP mode seems to be recognized now.
But "primax_scan --lamp=on" exits even though after spitting out the
following messages:

| root@anna > ./primax_scan --lamp=on
| parse_options:
|   lamp:                 on
|   dimension:        425x585 pixel
| parse_options:       switching lamp
|
| Can not identify this scanner. code: 0e

I tried primax_scan-0.93-Beta2 as well, but got the same result.
Has anybody had that experience or can give me some advice?

Thank you in advance.

Juergen.

>
> Some weeks ago, I desperately tried to get my Colorado D600 (30Bit)
> workingwith primax_scan-0.93. However, all my attempts were in vain,
> because my parport driver refused to recognize EPP mode for some reason.
>
> In the meantime, I have replaced the mainboard and I thought it's time
> to have another go. So I used my old primax_scan-0.93 binaries
> and the parport EPP mode seems to be recognized now.
> But "primax_scan --lamp=on" exits even though after spitting out the
> following messages:
>
> | root@anna > ./primax_scan --lamp=on
> | parse_options:
> |   lamp:                 on
> |   dimension:        425x585 pixel
> | parse_options:       switching lamp
> |
> | Can not identify this scanner. code: 0e
>

Add some lines to primax_scan.c
(some where you should find three lines like this
case 0x02
            printf('looks like a primax .......etc.etc

add these two line and re-configure. At least your scanner could now be
identified, but if it works I don't know. I still have trouble with the
output of the scans (black images)

case 0x0E
            printf("\Looks like a Primax Colorado D600");
            break;

Succes Joshua

On Thu, 30 Mar 2000, J. v. Santen wrote:

> >
> > | root@anna > ./primax_scan --lamp=on
> > | parse_options:
> > |   lamp:                 on
> > |   dimension:        425x585 pixel
> > | parse_options:       switching lamp
> > |
> > | Can not identify this scanner. code: 0e
> >
> 
> Add some lines to primax_scan.c
> (some where you should find three lines like this
> case 0x02
>             printf('looks like a primax .......etc.etc
> 
> add these two line and re-configure. At least your scanner could now be
> identified, but if it works I don't know. I still have trouble with the
> output of the scans (black images)
> 

I have added the following lines:

case 0x0E:
    printf("\nLooks like a Primax Colorado D600\n");
    break;

Now, on "./primax_scan -l on" the scanner is identified (of course), but
unfortunately the lamp does *not* turn on.

After one minute, I have fired off a "./primax_scan -d5x5 -p3x0 -r150",
just to see what happens: Nothing but the following message ...

| parse_options:
|  dimension:   X= 5.0 x Y= 5.0 inch
|  position:    X= 3.0 x Y= 0.0 inch
|  resolution:           150 dpi
|  dimension:        750x750 pixel 

... and the process seemed to run forever ...

So I killed and restarted it with a debugger, where it turned out
that the process gets trapped in an endless loop in function 
read_calibration_data, when y equals 1:

   for (y = 0; y < height ; y++){
        do {
            back = epp_read_one(&pa, 0x06);
            back = epp_read_one(&pb, 0x05);
        } while ((( i = pa * 0x100 + pb) < total_width -1 ));
        
        ...

Does anybody has any idea, what's going on here?

Regards - Juergen.

Juergen Salk schrieb:
.... 
> So I killed and restarted it with a debugger, where it turned out
> that the process gets trapped in an endless loop in function
> read_calibration_data, when y equals 1:
> 
>    for (y = 0; y < height ; y++){
>         do {
>             back = epp_read_one(&pa, 0x06);
>             back = epp_read_one(&pb, 0x05);
>         } while ((( i = pa * 0x100 + pb) < total_width -1 ));
> 
>         ...
> 
> Does anybody has any idea, what's going on here?

Of course does someone know what's going on there. Someone has written
the code -- and that's me. 

Your and the problem of all the others their scanner does not work with
the program is: This scanners are not compatible!
The first problem you can see the incompatibility is that the lamp does
not switch on!
 
This means that the scanner uses an other protokoll to comunicate with
the PC. The different protocols can be fixed by the different ASICs.
There is only one ASIC the code is written for! To find out what you
have to change you can contact Christian Ordig, Marco Foglia or Primax
or do your own reengenering. 

Sorry, I can't help you. :-<

Thomas

P.S. The loop is for waiting until the scan of a line is completed. The
registers 5 and 6 together are a counter that counts the Bytes in the
output buffer of the scanner. In your case: the counter is not at this
position (other registers -> other protocol) or the scan wasn't
started.

>Hi Joshua,
>
>thanks a lot for your replies. In the meantime I had some
>private e-mails with Th. Schano and Chr. Ording.
>
>It turned out that my EICI 091000 ASIC and WM 8143-12 ADC is
>not supported by the primax_scan software.
>
>If your problem persists, it may be worth opening the
>scanner and have a look at the PCB. If you find an
>EICI 072100 or EICI 085900 with LM9811 ADC you have
>good chances that your scanner is supported. If not,
>you are in no-support land.
-----------------------------------------------------------

Hai Juergen,

I'm sorry to hear that for you.
Yes, my problem still persists, and I already had a look in my scanner
before and the part#'s are:

EICI 085900 (f98120177, ASYM 087680m / y1832000145080)
LM9811 (s9806ba)
EICI 080300 (9811)
74HC244A
62003F TD810
only a different memory chip:
ISSI IS 61C1024-15J E175 6700L 9808
and a small one: 74HC04D

As compared to the partnumber page on the diver site they are identical to
the original, so I don't know where to look for my problem and probably
nobody else does, because I still have not received any comments. So I guess
I have si and wait for some support of Primax or buy a new one.
Thanks for your replies too.


Joshua