CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD - page 9 - Creative Uses of CHDK - CHDK Forum
« previous next »
Pages: 1 ... 4 5 6 7 8 [9] 10 11 12 13 14 ... 71   Go Down

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

  • 704 Replies
  • 204413 Views
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #80 on: 03 / November / 2012, 23:17:09 »
Advertisements
@casrap
To me all is of value and I appreciate your input.  PI(D) systems I have worked with were in the negative feedback loops of TEC controllers.  I don't see any evidence for that here.  Stepper motors I use run open loop, like in this camera.  By setting a defined phase difference between the two windings you can reposition the armature to exactly any rotational position none of which requires feedback (error differences etc), so long as its rated shaft N.m resistance is not exceeded.  For example, the S90 focus stepper turns at 1/12th revolution per manual focus index.  A more detailed explanation is somewhere in this thread.  Standard (larger) motors step at 1/200th revolution per index.  Given what I've seen, I'd side with srsa_4c in that it may mean "photointerrupter."  An insight into the meanings of these semi-cryptic commands is always helpful.
« Last Edit: 03 / November / 2012, 23:22:43 by SticK »
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #81 on: 03 / November / 2012, 23:58:08 »
Some results from the new event procs.  These were analyzed in REC mode with IRIS fully operational.

"ResetIris"  - puts IRIS in stowed position
"MoveIrisToStandbyPosition" - puts IRIS in stowed position // I think I had a shutdown after this one.
"MoveIrisToTerminatePosition" - puts IRIS in stowed position
"MoveIrisToFullOpen" - puts IRIS in stowed position
"MoveIrisToFullClose" - puts IRIS in f8
"EnableIris" - no measurable effect
"DisableIris" - no measurable effect // activated with shoot normally and also activated with "MoveIrisToFullClose" (as if not disabled)

I also tried "DisableIris" while in PLAY, and then when I set REC, the IRIS activated anyway (stowed -> f2).  So whatever it is disabling is not obvious.  I think that even though some of these procs respond none I expect will do anything to inhibit error when disconnected.

I think FOCUS and ZOOM will likely respond similarly.  Before going there, I rather get a handle on (circumvent if possible) IRIS first.  I am open to try other ideas/suggestions.
Logged
*

Offline ahull

  • *****
  • 634
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #82 on: 04 / November / 2012, 07:13:12 »
I may be wrong here, but it seems to me the shutdown following any error is probably controlled by the watchdog task.

My assumption is this, in the event of *any* error, the watchdog timer interrupt is masked, so further interrupts cant take place and the watchdog eventually times out,  and kills the camera. I suspect if we can un-mask this interrupt (or control the watchdog process, perhaps simply kill it), then we can cause as many errors as we like without the camera taking any action. Obviously the state of the camera, after error would be unpredictable, but in this case, we are probably safe.
   
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #83 on: 04 / November / 2012, 07:58:15 »
@ahull
Yes, your thinking is along the same line as the objective and I welcome your input.  Because I do not know the firmware, it is something the other fellas might like to comment on further.  That could be worth a try if it exists and can be located.
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #84 on: 04 / November / 2012, 09:40:28 »
Stopping the watchdog alone won't solve the problems. Anyway, "System.Create" registers event procedures named "StartWDT" and "StopWDT". There is a good chance that calling these will have the same effect (i.e. nothing) as calling most of the Disable[some hardware] eventprocs.
I suspect that many of these event procedures require some special mode (factory mode for example). Factory mode makes the camera look and act like a brick, and I think even the USB is switched to "twain" mode.

@SticK
Try to store 0 to the address 0x7938. This may divert IrisError. It's possible that the system will overwrite that value though. The Lua command is poke(0x7938, 0).
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #85 on: 04 / November / 2012, 09:54:00 »
@srsa_4c
Perhaps you missed my result for your recommendation on the IS override code earlier.  It's the only one that actually works so far and is why I have had my hopes up.  For example, if I jam the IS lens and then PUP, one minute later I get the E32.  But if within that one minute I issue:
  =return call_event_proc("Mecha.Create")
  =return call_event_proc("StartImStEventProc")
  =return call_event_proc("DisableISDriveError")
That works: there is no E32 and the camera keeps on running and working perfectly.  My last test was 20 minutes taking shots terminated by me and no problem.

edit:
Would your poking suggestion have any added benefit or difference over the code above?
« Last Edit: 04 / November / 2012, 09:56:12 by SticK »
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #86 on: 04 / November / 2012, 10:14:51 »
Quote from: SticK on 04 / November / 2012, 09:54:00
Perhaps you missed my result for your recommendation on the IS override code earlier.  It's the only one that actually works so far and is why I have had my hopes up.
No, I haven't missed that. I also saw the error list of your camera, therefore I know that it's still only ISDriveError that can be disabled by DisableISDriveError. This (DisableISDriveError) eventproc is special, the only similar one is DisableLensError which is not present in your cam's firmware.
Because of this, disabling other kind of errors is non-trivial. I found this (0x7938) specific memory location while searching for the other error that is present in your error list.
Quote
Would your poking suggestion have any added benefit or difference over the code above?
It may prevent shutdown in presence of "IrisError".
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #87 on: 04 / November / 2012, 10:33:39 »
I see ... a true cable disconnect perhaps .. so it is worth trying, correct?  Because the cable also carries the shutter signal, there may be a side-effect in which disconnecting the shutter may cause an error on its own, it may be inclusive if shutdown occurs.  Thus I suppose we'd have to inspect paramdmp to validate ??

edit:
syntax?  =return poke(0x7938, 0) ??
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #88 on: 04 / November / 2012, 10:42:19 »
Quote from: SticK on 04 / November / 2012, 10:33:39
I see ... a true cable disconnect perhaps .. so it is worth trying, correct?  Because the cable also carries the shutter signal, there may be a side-effect in which disconnecting the shutter may cause an error on its own, it may be inclusive if shutdown occurs.
Disabling an error may lead to another. If you get some shutter related error instead, that's a sign.
Quote
  Thus I suppose we'd have to inspect paramdmp to validate ??
Use the firminfo script instead.

poke() is simple enough that its return value can be ignored.
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #89 on: 04 / November / 2012, 10:56:29 »
The reason for my syntax question is that I want to be absolutely sure the camera receives the cargo.  Thus, at the CHDKPTP command line, I can say this:

   poke(0x7938, 0), without special preceding characters?

I intend to do this in 2 steps:
  a) first keep the IS connected and wedge the toothpick, and if this passes,
  b) disconnect the IS+SHUTTER and test.
Logged
Pages: 1 ... 4 5 6 7 8 [9] 10 11 12 13 14 ... 71   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal