CHDK Forum
Using CHDK => General Help and Assistance on using CHDK stable releases => Topic started by: stagdriver on 12 / May / 2014, 08:28:52
-
Hi all, hoping someone may have seen this before.
I have A800 running Ultimate Intervalometer that runs and operates fine until it reaches end of day (as set by geographical location, ucs and running dawn to dusk.
It simply stops on reaching dusk with lens still extended and totally powers off.
As a test i have altered the usc by 1 hour later and the camera shuts down 1 hour later too.
I have set chdk to record crash log but in every case nothing is recorded.
I am going to Misc Stuff, Debug Parameters, Save Rom crash log and i get an ok but does not record so i cannot post any logs here. (is my procedure correct for crash log?)
My PSU is tried and tested, (tried several) , all heavy gauge wires psu both ac types and regulator types all capable of 3 amps some even to 10 amps, battery powered 240 Ah), mains etc.
Totally convinced not a Psu issue but more something to do with the camera itself.
I will try tonight running from new AA batteries about 5 minutes before estimated shut down to see what happens.
All my other cameras are totally reliable, it's just this one. So any tips before i give it to my neighbors kids would be appreciated especially regarding the non recording of crash log.
??? does the lens try to retract at dusk, i have not noticed as yet???
Cheers.
-
I have A800 running Ultimate Intervalometer that runs and operates fine until it reaches end of day (as set by geographical location, ucs and running dawn to dusk. It simply stops on reaching dusk with lens still extended and totally powers off.
As there is no ROMLOG, it sounds more like something the script itself is doing wrong.
And IIRC, the A800 is very short of RAM so that might confound the problem.
All my other cameras are totally reliable, it's just this one. So any tips before i give it to my neighbors kids would be appreciated especially regarding the non recording of crash log.
Have you run the Ultimate Intervalometer successfully using the same settings (especially end of day shutdown) on any of your other cameras and does it work?
-
And IIRC, the A800 is very short of RAM so that might confound the problem.
We can try to load CHDK in ARAM.
@stagdriver What is the firmware version of your camera?
-
I am going to Misc Stuff, Debug Parameters, Save Rom crash log and i get an ok but does not record so i cannot post any logs here. (is my procedure correct for crash log?)
When you do this, a file called ROMLOG.LOG should be saved on the root of the SD card. This is a copy of the last crash recorded by the Camera on it's internal flash. The only case you don't get a ROMLOG.LOG should be if there are no crashes recorded.
-
Thank-you all for your advice, sorry for the delay in responding, been at work.
Waterwingz, yes i have run (am currently running exact same settings on A470. A530, A550, A810, A1200, A1300, A2300, A2400 and A4000. The only difference is the zoom factor. All have been good as gold some running for several (6) weeks now.
Nafraf, the camera firmware version is 100c.
Realp, have double checked and no Romlog recorded, its definitely as if the power plug is pulled.
Everything i have read about this particular camera suggests a bargain basement cut down to the bone so it may just be running on the ragged edge.
New info. I have been playing with this camera at lunch and i notice when using Ultimate Intervalometer that if a larger zoom setting is made say 3 or higher this camera goes through the start up procedure and sets the zoom then goes dead at the point where it should focus immediately after adjusting the zoom.
If setting the zoom to 1 or 2 it sometimes crashes, up to 1 in 5 times during start up.
By setting the zoom to '0' it achieves focus and proceeds to focus and run the script ok, i am going to run it with '0' zoom and otherwise identical settings to see if it restarts taking pictures at dawn. (seem to remember on my original tests i run for a few days with '0' zoom.
I have just tried larger zoom numbers with A1200, A1300, A470 and they work fine.
It may be possible I have a poorly camera here and something is shorting momentarily as the focus motor is adjusting along with the higher zooms as it has to generally move to a significantly different position when zoomed. ( But then it does not do this when in normal camera mode and setting zoom then gaining focus with 1/2 shutter press).
Confused, but intrigued to find the cause.
-
Could still be memory. We could try a loader script here to free up some memory if you would like to try that?
-
Test version A800 100c:
- Simpler loader
- CHDK loaded in ARAM
- movie_rec.c rewritten using code_gen
- Fix TurnOnMic/TurnOffMic function addresses
- #define CAM_MISSING_RAND 1
-
Waterwingz, i suspect a memory problem too, I would like to test this as i think there's something to be learnt from this excercise.
Nafraf, looking at the patch i'm thinking you have produced what Waterwingz has suggested. I will get this on test in the morning and report back
Thanks Guys.
-
What nafraf had done is different than what I proposed. A script loader lets you load a script such that it used a lot less memory. I'll post something later tonight.
-
Okay - attached here is a "loader" script for the ultimate intervalometer. Put this in the same directory as the ultimate.lua file and load / run it just like you would any other script. I should save enough memory to eliminate that as a possible source of your mysterious shut downs.
-
Thank you guys. I am going to test each method carefully for a couple of days each and will report back with the results.
Many thanks for your time and assistance.
-
I have extensively tested the test version from Reyalp and the loader from Waterwingz. The results i obtained were mostly identical with the original version and loading method where the camera appears to lose power after zooming and just at the point of focusing.
I have tried to emulate this problem with several other cameras and i can repeatedly replicate this phenomenon on two A1200's when using cheap non branded batteries.
It appears to be some kind of power issue where the internal voltage drops below a workable level and the camera simply shuts down instantly.
I have tried to replicate this without running a script, ie set a zoom, then 1/2 press to get focus but cannot manually replicate. I think the speed that i am able to perform the tasks if far inferior to the script.
I am thinking that the A800 is possibly so cut down that its own internal circuitry is barely adequate to run the camera and it does not take too much too soon, to just overload it...... Does still seem like it may be a memory issue but i am tending towards power.
I think i will repeat these tests tomorrow with an external display attached so i have no on camera live view (lcd and backlight) ti reduce the on-board power consumption. If this reduces the incidence rate of the problem then its most likely power related and it may be time to data log the voltage and current draws on this camera. (the Digital readout from my bench PSU is probably not fast acting enough to show any spikes).
Unfortunately on this camera you have to use a dummy battery to use external power as it does not have a DC in Jack which may be why the problem exists with both AC adapter or Batteries, and may point to the internal wiring or poorly made connections. (Hmmm, the A1200's use the same dummy battery method...)
-
I have tried to emulate this problem with several other cameras and i can repeatedly replicate this phenomenon on two A1200's when using cheap non branded batteries.
I have two A1200's as well. Most of the Ultimate Intervalometer script was built & tested (100's of times) on those using elcheapo NiCad rechargeable batteries. FWIW, I didn't see any shutdown issues until the batteries were good & ready for a recharge cycle.
I have tried to replicate this without running a script, ie set a zoom, then 1/2 press to get focus but cannot manually replicate. I think the speed that i am able to perform the tasks if far inferior to the script.
Should be pretty easy to write a short script that removes all the complexity of the Ultimate Intervalometer to test this out then. I'd like to validate that this is not an issue with the actual script.
-
Anything i can do to help with this, i would like to assist.
Can offer to test on A470, A800, A1200, A1300, A2300, A2400 and A4000 at present, my others are out in the field working away.
-
I have extensively tested the test version from Reyalp and the loader from Waterwingz. The results i obtained were mostly identical with the original version and loading method where the camera appears to lose power after zooming and just at the point of focusing.
I have tried to emulate this problem with several other cameras and i can repeatedly replicate this phenomenon on two A1200's when using cheap non branded batteries.
It appears to be some kind of power issue where the internal voltage drops below a workable level and the camera simply shuts down instantly.
This seems plausible to me. Zooming would draw extra current which could cause the battery to sag.
Most software issues (like running out of memory) should usually generate a ROMLOG.
FWIW some of the old AA cameras had problems with the battery contacts, where they would either get corroded or compressed to the point where they no longer make good contact. This resulted in short battery life even when the batteries were good, but would also make voltage sag worse.
-
Reyalp, i have just been looking under a 25x magnifier at the battery compartment contacts and the design does indeed lend itself to corrosion and poor contact. The contact points are approx 1mm wide at the widest point and are indented into the tin plated conductors from the rear forming a point, so the tin plate wears through real quick and you then have a thin oxidised layer giving the effect of used batteries due to voltage drop by reducing the current capacity.
Its a pity, but the dummy batteries for the external psu are of similar design. I may think about a mod with 3.5mm plug to bypass the battery compartment, should verify if this is the problem.
The A1200's are of the same design which is why i could probably replicate so easily. All my other cameras either use a 3.5mm power jack or use a dummy battery of the li-ion type so a completely different design.
I will post if i find a definite solution.
-
Small correction by the way.
I was able to replicate using two A1300's not a1200's as previously stated.
-
Well its taken some time, but i have managed to get a Romlog as the camera halted this time without powering off. Zoom was set to zero this time.
I have listed it below in the hope that it sheds some light on the problem. I have to confess that i personally cannot find anything useful but then i don't really understand it yet.
ASSERT!! DriverIC.c Line 48
Occured Time 2014:05:13 10:06:07
Task ID: 8716305
Task name: Nd
SP: 0x00280350
StackDump:
0x00000000
0xFFE06590
0x00000030
0x00000001
0x00000105
0x000061A8
0x0000010E
0x19980218
0x19980218
0x19980218
0x19980218
0xFFE06398
0x00008E08
0xFFE074E0
0x002725D0
0x19980218
0x19980218
0x19980218
0x19980218
0xFFC0717C
0x19980218
0x19980218
0x00000808
ShootConDump:
0f 0f 0f 0f 0f 0f 0f 0f 0f 0f
CameraConDump:
07 0a 02 0d 09 01 0f 0f 0f 0f
00018550: UI:ScreenUnLock
00018610: UI:AC:TstEVF:Ok
00018610: SS:ImgSys
00018610: SS:ToRec
00018610: SS:Lens1stP
00018620: SS: Evf=1
00018620: M:FIRST_S
00018620: M:SH_OPN_S
00018630: M:SH_OPN_E
00018630: M:ND_OFF_S
00018640: M:ND_OFF_E
00018640: M:ZM_RST_S
00018710: SS:InitPTM
00018710: SS: 0053->8004
00018710: SS: Asp 0001->0001
00018710: SS:ImgSys
00018710: UI:LogicalEvent:0x5004:adr:0,Para:0
00018710: UI:DisplayPhysicalScreenCBR
00018710: UI:DisplayPhysicalScreenCBR
00018710: UI:AC:ShwCaptI
00018710: UI:DSIC:53,0
00018710: UI:ScreenLock
00018710: UI:DSIC:49,1
00018720: UI:Display_CaptInfo
00018730: UI:DSIC:d4,0
00018750: UI:AC:DispSht
00018750: UI:DSIC:8c,0
00018830: M:ZM_RST
00018870: M:FC_RST_S
00019020: M:FC_RST_E
00019020: M:FC_STB_S
00019240: M:ZM_RST_E
00019270: M:FC_STB_E
00019270: M:FIRST_E
00019840: UI:ShootSeqToUI:0x202e:adr:0x3cb8,Para:15544
00019840: UI:ShootSeqToUI:0x201d:adr:0,Para:0
00019840: UI:DispSwCon_TurnOnBackLight
00019840: UI:DispSwCon_MuteOffPhysicalScreen
00019850: UI:AC:SUpShowI
00019850: UI:DSIC:54,0
00019850: UI:ScreenUnLock
00019900: UI:DSIC:53,0
00019900: UI:ScreenLock
00019900: UI:AC:EnryRecBt
00019900: UI:StartRecMode
00019900: UI:DispSwCon_MuteOffPhysicalScreen
00019900: UI:LogicalEvent:0x3110:adr:0,Para:0
00019900: UI:DispSwCon_TurnOnDisplayDevice
00019900: UI:UI_StrobeCon_Start
00019920: UI:LogicalEvent:0x3135:adr:0,Para:0
00019920: UI:_ManagePTMProperty
00019970: SS:ModChg
00019970: SS: Evf=0
00019970: SS: 0053->8004
00019970: SS: Asp 0001->0001
00019970: SS:ModChg*
00019970: UI:_DecideCaptureMode
00019970: UI:_StartStill
00019980: UI:DSIC:42,6
00019990: UI:DSIC:25,0
00020000: UI:ScreenUnLock
00020050: UI:TerminateDeliverToZoomController
00020050: UI:ScreenLock
00020060: UI:ScreenUnLock
00020100: UI:OPTICAL_ZOOM_POS
00020100: UI:UnpressZoomLever
00020100: UI:DispSwCon_TurnOnDisplayDevice
00020110: UI:LogicalEvent:0x313d:adr:0,Para:0
00020110: UI:_EnrySRec
00020110: UI:CaptModeChanger_CheckRTCRrepared
00020110: UI:DispSw: Unlock
00020110: UI:DispSwCon_MuteOffPhysicalScreen
00020110: UI:Window MuteOff
00020110: UI:MuteOffPhysicalScreen
00020110: UI:DisplayPhysicalScreenCBR
00020120: UI:DisplayPhysicalScreenCBR
00020120: UI:_DecideModeDial
00020120: UI:DSIC:14,0
00020120: UI:No Change Capture Mode
00020120: UI:LogiEvnt_NotPowerType:0x09a4:adr:0,Para:0
00020120: UI:LogiEvnt_NotPowerType:0x09a2:adr:0,Para:0
00020120: UI:DisplayPhysicalScreenCBR
00021560: UI:DSIC:58,0
00021600: UI:ScreenLock
00021600: UI:ScreenUnLock
00021660: UI:DisplayPhysicalScreenCBR
-
Its getting more interesting now, if i set the zoom to 3 and the camera crashes just after setting the zoom level, i can now save the Romlog.
listed below
ASSERT!! DriverIC.c Line 48
Occured Time 2014:05:13 10:06:07
Task ID: 8716305
Task name: Nd
SP: 0x00280350
StackDump:
0x00000000
0xFFE06590
0x00000030
0x00000001
0x00000105
0x000061A8
0x0000010E
0x19980218
0x19980218
0x19980218
0x19980218
0xFFE06398
0x00008E08
0xFFE074E0
0x002725D0
0x19980218
0x19980218
0x19980218
0x19980218
0xFFC0717C
0x19980218
0x19980218
0x00000808
ShootConDump:
0f 0f 0f 0f 0f 0f 0f 0f 0f 0f
CameraConDump:
07 0a 02 0d 09 01 0f 0f 0f 0f
00018550: UI:ScreenUnLock
00018610: UI:AC:TstEVF:Ok
00018610: SS:ImgSys
00018610: SS:ToRec
00018610: SS:Lens1stP
00018620: SS: Evf=1
00018620: M:FIRST_S
00018620: M:SH_OPN_S
00018630: M:SH_OPN_E
00018630: M:ND_OFF_S
00018640: M:ND_OFF_E
00018640: M:ZM_RST_S
00018710: SS:InitPTM
00018710: SS: 0053->8004
00018710: SS: Asp 0001->0001
00018710: SS:ImgSys
00018710: UI:LogicalEvent:0x5004:adr:0,Para:0
00018710: UI:DisplayPhysicalScreenCBR
00018710: UI:DisplayPhysicalScreenCBR
00018710: UI:AC:ShwCaptI
00018710: UI:DSIC:53,0
00018710: UI:ScreenLock
00018710: UI:DSIC:49,1
00018720: UI:Display_CaptInfo
00018730: UI:DSIC:d4,0
00018750: UI:AC:DispSht
00018750: UI:DSIC:8c,0
00018830: M:ZM_RST
00018870: M:FC_RST_S
00019020: M:FC_RST_E
00019020: M:FC_STB_S
00019240: M:ZM_RST_E
00019270: M:FC_STB_E
00019270: M:FIRST_E
00019840: UI:ShootSeqToUI:0x202e:adr:0x3cb8,Para:15544
00019840: UI:ShootSeqToUI:0x201d:adr:0,Para:0
00019840: UI:DispSwCon_TurnOnBackLight
00019840: UI:DispSwCon_MuteOffPhysicalScreen
00019850: UI:AC:SUpShowI
00019850: UI:DSIC:54,0
00019850: UI:ScreenUnLock
00019900: UI:DSIC:53,0
00019900: UI:ScreenLock
00019900: UI:AC:EnryRecBt
00019900: UI:StartRecMode
00019900: UI:DispSwCon_MuteOffPhysicalScreen
00019900: UI:LogicalEvent:0x3110:adr:0,Para:0
00019900: UI:DispSwCon_TurnOnDisplayDevice
00019900: UI:UI_StrobeCon_Start
00019920: UI:LogicalEvent:0x3135:adr:0,Para:0
00019920: UI:_ManagePTMProperty
00019970: SS:ModChg
00019970: SS: Evf=0
00019970: SS: 0053->8004
00019970: SS: Asp 0001->0001
00019970: SS:ModChg*
00019970: UI:_DecideCaptureMode
00019970: UI:_StartStill
00019980: UI:DSIC:42,6
00019990: UI:DSIC:25,0
00020000: UI:ScreenUnLock
00020050: UI:TerminateDeliverToZoomController
00020050: UI:ScreenLock
00020060: UI:ScreenUnLock
00020100: UI:OPTICAL_ZOOM_POS
00020100: UI:UnpressZoomLever
00020100: UI:DispSwCon_TurnOnDisplayDevice
00020110: UI:LogicalEvent:0x313d:adr:0,Para:0
00020110: UI:_EnrySRec
00020110: UI:CaptModeChanger_CheckRTCRrepared
00020110: UI:DispSw: Unlock
00020110: UI:DispSwCon_MuteOffPhysicalScreen
00020110: UI:Window MuteOff
00020110: UI:MuteOffPhysicalScreen
00020110: UI:DisplayPhysicalScreenCBR
00020120: UI:DisplayPhysicalScreenCBR
00020120: UI:_DecideModeDial
00020120: UI:DSIC:14,0
00020120: UI:No Change Capture Mode
00020120: UI:LogiEvnt_NotPowerType:0x09a4:adr:0,Para:0
00020120: UI:LogiEvnt_NotPowerType:0x09a2:adr:0,Para:0
00020120: UI:DisplayPhysicalScreenCBR
00021560: UI:DSIC:58,0
00021600: UI:ScreenLock
00021600: UI:ScreenUnLock
00021660: UI:DisplayPhysicalScreenCBR
-
I did a quick scroll through this thread but did not see the version of CHDK you are using. It would be good to know the release number & version ( e.g. 1.3.0 or 1.2.0, release 3343 ).
-
ASSERT!! DriverIC.c Line 48
Occured Time 2014:05:13 10:06:07
ASSERT!! DriverIC.c Line 48
Occured Time 2014:05:13 10:06:07
Your two logs are actually only one log, and it's not recent. That means, whatever is causing the symptoms, the camera fails to record a newer romlog at the time of crash/poweroff.
-
I did a quick scroll through this thread but did not see the version of CHDK you are using. It would be good to know the release number & version ( e.g. 1.3.0 or 1.2.0, release 3343 ).
In addition to an update on what CHDK version you are using, can you summarize where "we" are now?
Originally this seemed to be related to the script going from day to night mode. Then is seemed to be when the zoom lens moved. It was only the A800 but then later maybe the A1300? Power connections and battery types were mentioned? Were similar or different test conditions used for each problem mentioned?
Edit : What Display Blanking mode are you using? Does this happen if the script zoom position is set to 0? Can you enable logging to SDcard (or "both") in the script and attach the log file to a post in this forum (no need to cut and paste the whole thing into your message ;) )
-
using version 1.3.0 build 3440.
I am satisfied that battery terminals are not the issue as i have a direct connection made to the camera PCB bypassing battery terminals.
The A1300 was the only other camera i could force to crash when setting a zoom leve greater than 0 but only if using cheap non branded batteries. (i dont think the A1300 is relevant any more as it it always works with good batts or external psu, it does not fail if psu is good.
i have the script set to save to sd card, but as the camera completely powers off dead it does not log anything.
Orig problem was that camera crashed apparently at dusk (checked from last picture taken before crash)
I found however that i could make camera crash always, by setting a zoom of 3 or more in the script. Script would run, it would adjust the zoom, then a second later as it was adjusting the focus it turned off dead in an instant. Setting Zoom to 0 the camera does not crash (apart from today when it simply got stuck and the script halted....I think this is a red herring). Setting zoom to 1 or 2 and the camera then runs ok all day, but crashes at dusk.
This is why i deviated and investigated power connections.
-
I am using Bklite as dispkey does not work with this camera.
-
using version 1.3.0 build 3440.
Good enough !
I am satisfied that battery terminals are not the issue as i have a direct connection made to the camera PCB bypassing battery terminals.
That pretty much does it for battery terminals then.
The A1300 was the only other camera i could force to crash when setting a zoom leve greater than 0 but only if using cheap non branded batteries. (i dont think the A1300 is relevant any more as it it always works with good batts or external psu, it does not fail if psu is good.
Okay - back to the A800 only.
i have the script set to save to sd card, but as the camera completely powers off dead it does not log anything.
That does not seem right. The logging function opens & closes the log file ( A/ultimate.log ) each time it writes. What you see on the LCD console log should also be in the file.
Orig problem was that camera crashed apparently at dusk (checked from last picture taken before crash)
FWIW : I don't believe the transition from Day to Night updates the zoom position. However, if the Display blanking mode is set to PlayKey then the zoom position is updated each time the camera comes out of playback mode in order to shoot.
I found however that i could make camera crash always, by setting a zoom of 3 or more in the script. Script would run, it would adjust the zoom, then a second later as it was adjusting the focus it turned off dead in an instant. Setting Zoom to 0 the camera does not crash (apart from today when it simply got stuck and the script halted....I think this is a red herring). Setting zoom to 1 or 2 and the camera then runs ok all day, but crashes at dusk.
For reference, the ultimate.lua script does not use any focus related commands (i.e. no set_aflock(1), set_mf(), set_focus() etc) . The focus that stagdriver refers to here happens with the first half-press in the check_exposure() function. If there are problems with get_shooting() not returning true / false correctly on the shoot_half press / release then it's possible the script could "hang" at that point.
And the actual zoom code has a generous helping of sleep() applied around the actual set_zoom() command.
function update_zoom()
if ( zoom_setpoint > 0 ) then
zsteps=get_zoom_steps()
if(zoom_setpoint>zsteps) then zoom_setpoint=zsteps end
printf("set zoom to step %d of %d",zoom_setpoint,zsteps)
sleep(2000)
set_zoom(zoom_setpoint)
sleep(2000)
end
end
This is why i deviated and investigated power connections.
Understood - it was certainly worth a look.
Update : if this is just a zoom problem with the A800 it would not be the first time we have seen zoom issues. From one of my old threads / posts here's a test script you can try : http://chdk.setepontos.com/index.php?topic=7071.msg76172#msg76172 (http://chdk.setepontos.com/index.php?topic=7071.msg76172#msg76172)
-
The stand alone zoom script you have linked me to is going to be very useful as i have been trying to do this myself in order that i may record some power levels.
As this camera otherwise works it can become a general jobbing camera, but i will persevere with finding a root cause and post any results in case it helps others.
many thanks Waterwingz
-
The stand alone zoom script you have linked me to is going to be very useful as i have been trying to do this myself in order that i may record some power levels.
I cut the ultimate.lua script down to just the update_zoom() and check_exposure() functions and looped them. Every four iteration is actually takes a shot as well.
Let this run for a bit and see what it does ?
-
Well this is quite definitive. Most of the time it sets ok to Zoom 2 of 7 (irrespective of whether lens was in or out to start with, powers off about 1 in 10 times.
But when in the process of zooming 7 of 7 always loses power.
-
Well this is quite definitive. Most of the time it sets ok to Zoom 2 of 7 (irrespective of whether lens was in or out to start with, powers off about 1 in 10 times.
But when in the process of zooming 7 of 7 always loses power.
Does it do so when zooming or when it tries to focus?
Attached is a version of the script with longer delays between zooming and setting focus? See if that helps?
Edit : can you go to the debug menu and see if you can create a new ROMLOG ? If so, please attach it here.
-
With zoomer 2 its easy to see that is crashes at the end of the 7 of 7 zoom.
-
zoom crash was reported before, but definitions were not modified. http://chdk.setepontos.com/index.php?topic=7409.msg91826#msg91826 (http://chdk.setepontos.com/index.php?topic=7409.msg91826#msg91826)
Please test version in attachment.
-
zoom crash was reported before, but definitions were not modified. http://chdk.setepontos.com/index.php?topic=7409.msg91826#msg91826 (http://chdk.setepontos.com/index.php?topic=7409.msg91826#msg91826)
Please test version in attachment.
Ouch - missed that and it was my own post. How did you decide which of the three #defines to use?
-
I enabled three options, they were required by A810.
I think that it is possible to divide the problem in two and check if they are required:
in platform/generic/wrappers.c:
CAM_USE_ALT_PT_MoveOpticalZoomAt is used to correct lens distortion.
CAM_USE_ALT_PT_MoveOpticalZoomAt depends on CAM_USE_ALT_SET_ZOOM_POINT
In core/gui_osd.c
CAM_USE_OPTICAL_MAX_ZOOM_STATUS is used to fix bug related to change between optical and digital zoom.
#if defined(CAM_USE_OPTICAL_MAX_ZOOM_STATUS)
if (x==0) zoom_status=ZOOM_OPTICAL_MAX; //ERR99: No zoom back from digital to optical zoom possible if set to medium
#else
if (x==0) zoom_status=ZOOM_OPTICAL_MEDIUM;
#endif
Edit:
This was included too, probably the first to be tested :
#define CAM_NEED_SET_ZOOM_DELAY 300
core/shooting.c
void shooting_set_zoom(int v)
{
int dist;
if (!camera_info.state.mode_play)
{
dist = shooting_get_subject_distance();
lens_set_zoom_point(v);
#if defined(CAM_NEED_SET_ZOOM_DELAY)
msleep(CAM_NEED_SET_ZOOM_DELAY);
#endif
shooting_set_focus(dist, SET_NOW);
}
}
-
Hi, thanks for the responses,
I can report that under A800-100c-1.3.0.3443 the Zoomer2.lua has been working for 30 Minutes without error, i stopped at that point as things were getting a bit warm.
I have now set running Ultimate Intervalometer with the same script settings that were giving issues before and so far so good. (previously i was getting a total shutdown if setting a zoom level above 0). I will leave this script running overnight to see if the original problem recurs and report back.
I read through the post that was linked above regarding Zoom Crash, and i noticed a spreadsheet which suggested that the A800 and A1300 cameras require info from tests to be submitted. If this is still the case, i have A800 and 2A1300 that i can put to test if still required.
Best regards