Looks like I beat Vanzy to the punch, here's a shot from above Fortune's Rocks, Me taken on Sunday. The shot shows most of Biddeford Pool, Me.
http://img354.imageshack.us/my.php?image=d2ml.jpg
The camera went into the drink on Monday. I'm hoping a freshwater rinse and blow dry will at least let me extract some shots.
radarman- 08-29-2005
I remember talking to an old sailor (vietnam era), and he mentioned one time how the Navy deals with waterlogged equipment.
You stick the affected bit in fresh water for a few hours to get the salt out of it - then let it air dry in the sun for a few days. Of course, back then, most things were still built with discrete transistors and single function DIP chips - no idea if it would work with modern electronics.
mattcam3- 10-09-2005
Ok, try this. I don't have a 6510 handy, but one of the other patches will work there. (you'll have to figure out which)
Step 1
To change "auto turn-off" into take-a-pic on 6410 and 6430:
Scan for "05 e0 0e". there should only be one instance. Change to "05 e0 0a"
To change "auto turn-off" into take-a-pic on 6520 and 6550:
Scan for "25 e0 0e". there should only be one instance. Change to "25 e0 0a"Step 2
To change the in-between pics time, measured ~ as decaseconds on 6410 and 6430:
Scan for "98 21 e2 18 e3 00". there should be 5 instances. Change to "98 21 e2 XX e3 00", where XX is the time you want
To change the in-between pics time, measured ~ as decaseconds on 6550:
Scan for "98 21 e2 15 e3 00". there should be 5 instances. Change to "98 21 e2 XX e3 00", where XX is the time you want
Note to all - I haven't had time to check the manual patch with the 6550, only with the 6410 red and 6430 red. If it doesn't work, it may sieze the camera up. You'll have to recover with a flash short and run+upload the previous good firmware.
Any or all people attempting this - please report your success or lack thereof to this thread, along with the firmware rev you applied it to.
ok, i found all the valuses just fine, but when i replace XX is 98 21 e2 XX e3 00 what if it is longer then just the XX.
i want it to take a picture every 5 seconds, and thats .05 decaseconds, but in hex .05 is 2e 30 35 i think, so will it work if it's that meny long or is 100 sec (01 in hex maby?) the shor-*test*-('")?
BillW- 10-09-2005
It's an integer value, not a float, so you can't do fractions. Without a lot more extensive changes to the firmware, the time you use must be a multiple of 10 seconds.
ZeroGwafa- 10-10-2005
i cannot seem to find the newest version (0.3.2) the only one listed is the 0.3.1 version
BillW- 10-10-2005
I "recalled" that version after the time lapse patch misapplied itself to some different firmware revisions and temporarily bricked the cams.
A follow-up and probably final release with the fixed version of these patches is in my TODO list.
pulsar- 10-17-2005
Hi, I'm new to this board, but have been following it for some time. Thanks to this board I've managed to unlock my 6550 2B. I'm trying to apply BillW's interval timer patch, but I'm confused as to the value I put in for XX.
I initally assumed that if I want the interval between successive shots to be 60 seconds, I would enter 06 for XX because 60 seconds are 6 decaseconds, but after reading some of the posts to this thread I'm not so sure.
06 in hex is the same as 06 in decimal, isn't it?
Also the original (factory) value for XX for the 6550 is 15 which would be 150 seconds. That just doesn't make sense to me.
Please can someone help me with this since I don't want to screw this final mod up.
Thanks
Pulsar
BillW- 10-17-2005
You would indeed use 06 for 60 seconds. And yes, 06_decimal=06_hexidecimal
The stock time for a 6550 is 210 seconds (0x15=21) - this patch turns the "inactivity timer" into the take-a-pic timer. A 6550 turns off after ~210 seconds of inactivity. (sidenote: earlier firmwares use 12 for this value. Wonder why Pure Digital adjusted the timeout)
Good luck with the mod!
pulsar- 10-17-2005
Thank you for the quick reply BillW.
I patched the one "auto turn-off appearence and the five timing interval appearences in the firmware.bin file but when I used PV2 Tool to upload the image file back into the camera the loading stopped at 96% and gave me a "bulkwrite failed" message. The camera was dead providing only two beeps when turned -on. I then tried to use the Resurrector and initially it wouldn't load the firmware.pv2 when I pressed Run PV2 Code. I took the batteries out and tried the Resurrector again, but no luck. Then I tried the Run PV2 Code using the PV2 Tool (batteries still out) and it loaded the firmware.bin and allowed me to upload the original image file using the Resurrector. The camera worked normally again. I then tried the timer patch again. This time the modified image uploaded ok, but the camera is dead again giving 2 beeps when turned on.
Any idea what the problem is. I suspect it has to do with the checksum of the patched image file, but have no idea how to fix it.
Pulsar
BillW- 10-17-2005
2 beeps is definitely a bad firmware checksum.
Do the "run pv2 code" thing from pv2tool. Don't bother with Resurrector - it has some issues that ironically make it less efficient at resurrection than the recent pv2tool
If you're using a recent pv2tool and the firmware has a bad checksum, it will offer to adjust the checksum for you. Be sure to accept this offer and you should be set.
pulsar- 10-19-2005
I tried to upload the patched .img file several times using PV2 Tool, but it never offered to adjust the checksum resulting in a dead camera and the two beeps. Then I tried to upload just the patched firmware.bin file to the camera using PV2 Tool and that's when I received the popup offering to adjust the checksum. My PV2 now snaps a photo every minute which is just perfect for kite photos.
Thanks so much for your help BillW.
Pulsar
sadhack- 05-12-2006
BillW, thanks for this man! I used your original instructions on a 6550 30 and it worked fine the first time! Now the cam will sit there and automatically take pics every 60 seconds...what fun!...now what am I going to do with it??
...guess I better go buy a kite...
BillW- 05-12-2006
You're totally welcome!
I'm in the same boat - I want to try it out but haven't bought a kite yet. I was also considering going with some helium balloons and a lot of string.
sadhack- 05-12-2006
I had the balloon idea too! Was thinking about how many balloons (or at least how much helium) to lift the cam AND all the string high enough to be fun...then I started wondering what I'd do with the pics anyway??...
...and then I thought it might just be easier to make the auto repeat shot cam a dishwasher cam or such and use the peanut butter jar case idea to take 25 pics of the inside of my dishwasher at work or something...
BillW- 05-12-2006
Dishwasher shots... I like your thinking!
You could also ensure that the light really does goes out when the fridge is closed. Or change the timeout to 0 decaseconds and see how many shots you can get when you toss the cam up into the air. Or maybe you could construct a bungee cam...
So much important investigation to be done, so little time! :P
Forumer™ is Voted #1 Free Forum Hosting provider
Build your own community today with the largest message board hosting company.