CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD - page 63 - Creative Uses of CHDK - CHDK Forum
« previous next »
Pages: 1 ... 58 59 60 61 62 [63] 64 65 66 67 68 ... 71   Go Down

CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD

  • 704 Replies
  • 195593 Views
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #620 on: 07 / September / 2013, 15:04:07 »
Advertisements
Quote from: SticK on 07 / September / 2013, 14:57:55
@srsa_4c

The bin in the zip has a date of 08-14-2013.  I don't think it's the right one ??
https://subversion.assembla.com/svn/chdk-s1.bin/files/s90-101a-1.1.0-2729_disableisdriveerror_nodistcorr_isofix_novigncorr_0deg.zip
Logged
*

Offline reyalp

  • ******
  • 14128
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #621 on: 07 / September / 2013, 15:04:53 »
Quote
Wow .. you've got some memory!  I tried =post_levent_to_ui(4484) with H/W OFF and still in date screen loop.
Umm... I'm not clear what you did.

The idea is that sending that levent would unlock the keyboard and allow you to set the date in the startup screen, rather than switching to rec mode. Did you successfully do this?

The chdkptp shutdown buttons uses the shut_down() chdk script function. You could try shutting down with
Code: [Select]
.post_levent_to_ui('PressPowerButton')
This may be more similar to pressing the physical power button, so it may cause more state to be saved than shut_down.

Note also that you could set the date over PTP using eventprocs. I have no idea how this interacts with the RTC being updated, but see this thread: http://chdk.setepontos.com/index.php?topic=7280.msg78087#msg78087

I bring this up mostly because it seems like having the camera clock synchronized with the host might be desirable in your situation anyway.
Logged
Don't forget what the H stands for.
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #622 on: 07 / September / 2013, 15:21:58 »
Quote from: reyalp on 07 / September / 2013, 15:04:53

Umm... I'm not clear what you did.  The idea is that sending that levent would unlock the keyboard and allow you to set the date in the startup screen, rather than switching to rec mode. Did you successfully do this?
Yes, that is what I did:
   PUP
  ->date_screen
  ->levent
  ->set date
  ->SET button (into PLAY)
  ->REC (clock OK)
  ->PLAY
  ->H/W OFF
  ->PUP
  =date screen 0-0-0 ??

Quote
The chdkptp shutdown buttons uses the shut_down() chdk script function. You could try shutting down with .post_levent_to_ui('PressPowerButton') This may be more similar to pressing the physical power button, so it may cause more state to be saved than shut_down.
Oh that is *very* interesting for future use.  In any case I can use the H/W POWER button to shutdown.

Quote
Note also that you could set the date over PTP using eventprocs. I bring this up mostly because it seems like having the camera clock synchronized with the host might be desirable in your situation anyway.
Exactly!  Nice ... I was going to ask you about that, but for now I'd like to get the 101a back to normal behavior ... still waiting for srsa's possibly misplaced BIN.
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #623 on: 07 / September / 2013, 15:31:17 »
Quote from: SticK on 07 / September / 2013, 15:21:58
... still waiting for srsa's possibly misplaced BIN.
See direct link in reply #620 above. File date is correct (09-07-2013). Assembla's html index pages tend to get cached, a page reload helps.
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #624 on: 07 / September / 2013, 16:12:22 »
OK -- I HAVE RESULTS

@srsa_4c

Now this is quite interesting ...the new BIN in #620 has revived clock operation back to normal, thanks!!!. 

However ... big however .. recovery from POWER FAILURE during REC is erratic with #620 BIN ... I have to keep pressing the POWER SW several times and eventually FW will/might zero in and accept MECHA SIM response.  So the two BINs are mutually exclusive in that sense ... hence if I have to recover the clock from a battery fail .. I load in #620 .. and then if I want clean recovery after power fail, then I have to use the current BIN.  So it *does* look like what you did with the RTC in the current BIN has a beneficial effect on normal PFP101a usage, and is the preferred operational BIN if I were to choose between the two.

Can you offer a bit of technical insight what could be responsible?  Is there a way to combine the two into one solution?  Can you give this some thought ??  It would not be the end-of-the-world if not possible .. as the #620 BIN is a way out of the set date loop.

edit: I think it's the "nostartuplenscheck" that gives clean performance overall, because I noted that with #620 even changing between REC->PLAY etc gave some erratic behavior.
« Last Edit: 07 / September / 2013, 16:23:12 by SticK »
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #625 on: 07 / September / 2013, 16:26:31 »
Quote from: SticK on 07 / September / 2013, 16:12:22
Now this is quite interesting ...the new BIN in #620 has revived clock operation back to normal, thanks!!!.
OK, its mission is accomplished then.

Since the RTC hack is early in the boot process, it's not possible to make it optional. If the hack is necessary - looks like it is - then simply don't let the battery lose its charge. If you ever need to change it, make things normal with the RTC-hack-less diskboot, then switch back to the other one.

Am I missing something, and "s90-101a-1.1.0-2729_disableisdriveerror_nodistcorr_no_startup_lens_check_isofix_novigncorr_0deg" doesn't work now that you set the RTC date back to normal?

edit:
"RTC hack" == "no_startup_lens_check"
« Last Edit: 07 / September / 2013, 16:29:01 by srsa_4c »
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #626 on: 07 / September / 2013, 16:47:07 »
@srsa_4c

Everything you say above is another way of saying what I said in my previous post to yours.

Quote
Am I missing something, and "s90-101a-1.1.0-2729_disableisdriveerror_nodistcorr_no_startup_lens_check_isofix_novigncorr_0deg" doesn't work now that you set the RTC date back to normal?
What I tried to say was the converse (ie it's OK!).   After getting the clock back with the #620 BIN you posted earlier, I go back to this *very long* one, and yes all's good again.  So I can recover from a clock battery fail and go back to a working system, via the #620 BIN.

Quote
"RTC hack" == "no_startup_lens_check"
Yes, it's what I conjectured too, in my previous post.

Quote
Since the RTC hack is early in the boot process, it's not possible to make it optional.
You've answered my question.

Quote
If you ever need to change it, make things normal with the RTC-hack-less diskboot, then switch back to the other one.
Yes indeed, that is what I described, and if have to do it this way which now I know I do, I did say "it's not the end of the world."

Quote
OK, its mission is accomplished then.
Absolutely.  :)

edit: What's next ... now comes the tricky risky part hardware-wise.  I have to take out the main board from the metal camera frame (or what little is left of it ... hence the reason for the battery removal today) and apply a conformal coat to prepare the board for a thermal heastsinking solution.
« Last Edit: 07 / September / 2013, 16:51:38 by SticK »
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #627 on: 13 / September / 2013, 11:24:57 »
S90_101a IMAGER REASSEMBLED and BACK INTO WORKING CONDITION

After doing the thermal upgrade, the RTC has been recovered is operational again.  No other settings were lost and that is very good news too.

Although not yet installed, I am beginning to use the hardware as a regular user.  I am confident I won't find any show stoppers, but some regular usage caveats are bound to pop up.

For now ...

CAVEAT #1  -  PLAY MODE MENU jaggies.

Figure.  I always use the REC menu (right panel) and that menu is OK.  I don't recall using the MENU in PLAY mode for quite a while, but I think the last time I used it was many months ago and it was fine.  When I scroll down into the menu selections, they appear correctly as in REC mode.

edit: viewing PLAY MODE images is OK, it's just the menu that has the problem.

CAVEAT #2 - DATE STAMP  1 hr PLUS

This has always been there.  The stamp on the images is always +1 hr from the CHDK OSD clock.  Even if I set Daylight Savings on or off, Canon menu clock always agrees with CHDK OSD clock, that's OK, but images continue to be stamped (as they appear in the Win File Explorer) +1hr.  Any ideas?
« Last Edit: 13 / September / 2013, 12:27:48 by SticK »
Logged
*

Offline ahull

  • *****
  • 634
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #628 on: 13 / September / 2013, 15:24:02 »
Quote from: SticK on 13 / September / 2013, 11:24:57
CAVEAT #2 - DATE STAMP  1 hr PLUS

This has always been there.  The stamp on the images is always +1 hr from the CHDK OSD clock.  Even if I set Daylight Savings on or off, Canon menu clock always agrees with CHDK OSD clock, that's OK, but images continue to be stamped (as they appear in the Win File Explorer) +1hr.  Any ideas?

Does the camera have a Timezone setting, and does this agree with the timezone on the PC? This sounds the most likely cause.  For example if the camera is set to CEST and the PC is set to GMT/BST, then while both cameras may apparently show the same time, the UTC timestamps will be an hour apart.
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #629 on: 13 / September / 2013, 15:38:50 »
Quote from: ahull on 13 / September / 2013, 15:24:02
Does the camera have a Timezone setting, and does this agree with the timezone on the PC? This sounds the most likely cause.  For example if the camera is set to CEST and the PC is set to GMT/BST, then while both cameras may apparently show the same time, the UTC timestamps will be an hour apart.
That's a good point.  However, they agree, both are set to Eastern (NY on camera).  In fact, changing the time zone on the camera does not affect the +1 hr time stamp .. could be a clue.
Logged
Pages: 1 ... 58 59 60 61 62 [63] 64 65 66 67 68 ... 71   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal