Vuescan only scans 6 frames from roll

[vanstinator]

I've converted an SA-21 to an SA-30 via the pin trick, and flashed the latest firmware release. Vuescan only ever scans up to 6 photos before spitting the roll back out.

Here's a memory dump. Happy to help in any way I can.

***************************************
* Nikon Memory Dumper by Kosma Moczek *
***************************************
Connecting to scanner \\.\usbscan0...
...connected.
Checking model: 0x04b0, product: 0x4001, version: 2.01
...model: DF17811
Checking scanner...
cmd: 12 00 00 00 24 00
...scanner says it's a Nikon   LS-50 ED        2.02
Reading memory at 0xffffc0 to 0xffffdf...
cmd: 3c 02 00 ff ff c0 00 00 20 00
I/O Registers:
0000: ff ff 00 00 ff ff 01 00
0008: ff ff 00 ff ff ff ff eb
0010: ff ff fd 3f ff ff 00 d7
0018: 00 ff 00 00 00 00 1f ff

Finished.
Press any key to continue...

[vanstinator]

My understanding is the rear door sensor doesn't exist on the LS-50, but the sensor value is still present. Wonder if there is maybe a hardware revision difference at play here.

[kosma]

That's my understanding as well - the phantom sensor is on PC6/MSW18. The purpose of I/O register dump was to check if there are any differences in the input port values seen by the scanner - but so far I have not determined anything useful. I am still waiting for a friend to send me a second LS-50 board, just to compare.

[vanstinator]

Having a board in person is obviously best, but if that doesn't work out I'd be happy to give you remote access to a Windows box connected to this unit if there's any value to that at all. This kind of RE is a little outside my wheelhouse but I'll help any way I can!

[remigrousset]

Hey there,
I did the same, I've converted an SA-21 to an SA-30 via the pin trick, flashed my coolscan LS-50 with the Version 2.02 and got the same result...
With vuescan I can scan up to 6 images, same with NikonScan...

Sharing 2 memory dump, I got on error the first time :

***************************************
 * Nikon Memory Dumper by Kosma Moczek *
***************************************
Connecting to scanner \\.\usbscan0...
 ...connected.
 Checking model: 0x04b0, product: 0x4001, version: 2.02
...model: DF17811
Checking scanner...
cmd: 12 00 00 00 24 00
...scanner says it's a Nikon   LS-50 ED        2.02
Reading memory at 0xffffc0 to 0xffffdf...
cmd: 3c 02 00 ff ff c0 00 00 20 00
sense: 02 06 29 00 00 00 00 00
Error: sense_buffer data indicates failure
Press any key to continue... 


 ***************************************
* Nikon Memory Dumper by Kosma Moczek *
***************************************
Connecting to scanner \\.\usbscan0...
...connected.
Checking model: 0x04b0, product: 0x4001, version: 2.02
...model: DF17811
Checking scanner...
cmd: 12 00 00 00 24 00
...scanner says it's a Nikon   LS-50 ED        2.02
Reading memory at 0xffffc0 to 0xffffdf...
cmd: 3c 02 00 ff ff c0 00 00 20 00
I/O Registers:
0000: ff ff 00 00 ff ff 01 00
0008: ff ff 00 ff ff ff ff eb
0010: ff ff fc 3f ff ff 00 d7
0018: 00 ff 00 00 00 00 1f ff
 
Finished.
Press any key to continue...

Let me know if I can help anyhow.
And thanks again for putting all the work together!

[sloaneross]

Hey there, I did the same, I've converted an SA-21 to an SA-30 via the pin trick, flashed my coolscan LS-50 with the Version 2.02 and got the same result... With vuescan I can scan up to 6 images, same with NikonScan...

I can't get nikonscan to work at all with the SA-30 pin trick, but vuecan does. @kosma, right now my LS-50 is just sitting. I'd post it over to you to fiddle with if that would help (assuming you'll send it back at some point if you get this working)

[snowphish]

Dang mine is doing the same, cut the hole, shorted the pins, flashed the firmware, scans 6 then ejects the film
Thanks for the mod! if there's anything I can do to help to get to the bottom of this, let me know.

[hohaha045]

Same issue with mine, I think A-30 is identified correctly (there are 40 frames showing in Vuescan) but eject after frame 6)

***************************************
* Nikon Memory Dumper by Kosma Moczek *
***************************************
Connecting to scanner \\.\usbscan0...
...connected.
Checking model: 0x04b0, product: 0x4000, version: 2.02
...model: PT17035
Checking scanner...
cmd: 12 00 00 00 24 00
...scanner says it's a Nikon   LS-40 ED        2.02
Reading memory at 0xffffc0 to 0xffffdf...
cmd: 3c 02 00 ff ff c0 00 00 20 00
I/O Registers:
0000: ff ff 00 00 ff ff d1 00
0008: ff ff 00 fb ff ff 7f eb
0010: ff ff fc 3f ff ff 01 d5
0018: 00 ff 00 00 00 00 1f ff


Finished.
Press any key to continue...

[snowphish]

Yeah, I've tried a few things on the hardware side also.

Assuming it might be a sensor issue as the 4/5000 models have an extra sensor for the back door - I tried messing with PC6 on the H8 ic ... didn't do anything

seems there is also a photosensor on the other models, tried playing around with that pin as well but I imagine it would be looking for a signal and not just a simple pull-up pull-down on that pin...

out of ideas, if anyone has leads - I'm down to experiment

[Toesoe]

@snowphish lmk if you want to take a deeper look at this, I tried patching out the checks on PC6 in the firmware (see the other open issue) but didn't get anywhere. who knows there's something else to figure out here, maybe if someone's got a 4000 to mess around with to compare signals?

[hohaha045]

Anyone tried with the real "SA-30"?

[arahowerya]

Hey everyone, been doing this mod to my LS-50 today and having the same issue.

If PC6 is the rear door input pin, how come the data direction register for port C (PCDDR) is set to 0xFF on all the above examples?

that would indicate it's set as an output... So surely it would need to be set as an input first? Or am I missing something?

@kosma what does your (working!) LS-50 say? Do you have a register dump handy?

p.s. this repo is excellent, very impressive work so far

[arahowerya]

... nevermind - read the datasheet Kilian 😅

[arahowerya]

I just put a bit of magnet wire to short PC6 (pin 17) to GND - and it wouldn't initiate USB at all. Nothing detected on two computers.

Removed the short and it came back to life. Weird. It definitely wasn't shorting on any other pins either

[arahowerya]

Also fwiw

***************************************
* Nikon Memory Dumper by Kosma Moczek *
***************************************
Connecting to scanner \\.\usbscan0...
...connected.
Checking model: 0x04b0, product: 0x4001, version: 2.02
...model: DF17811
Checking scanner...
cmd: 12 00 00 00 24 00
...scanner says it's a Nikon   LS-50 ED        2.02
Reading memory at 0xffffc0 to 0xffffdf...
cmd: 3c 02 00 ff ff c0 00 00 20 00
I/O Registers:
0000: ff ff 00 00 ff ff 01 00
0008: ff ff 00 ff ff ff ff eb
0010: ff ff fc 3f ff ff 01 d7
0018: 00 ff 00 00 00 00 1f ff

[arahowerya]

I realised I got the pin1 marking incorrect earlier so re-did the modification to pull PC6 down (with the right pin this time)!

You can see it in the registers - d7 goes to 97

0000: ff ff 00 00 ff ff 01 00
0008: ff ff 00 ff ff ff ff eb
0010: ff ff fc 3f ff ff 02 97
0018: 00 ff 00 00 00 00 1f ff

but it still only scans 6 frames in the roll unfortunately