another rare bug - page 5 - General Help and Assistance on using CHDK stable releases - CHDK Forum supplierdeeply

another rare bug

  • 48 Replies
  • 13380 Views
*

Offline reyalp

  • ******
  • 13456
Re: another rare bug
« Reply #40 on: 28 / July / 2016, 15:49:28 »
Advertisements
cool :) I didn't know about this feature.
Always good to check  http://chdk.wikia.com/wiki/CHDK_Scripting_Cross_Reference_Page :)
Quote
What is difference between this two functions electronically and physically in terms of power consumption/dissipation?
set_backlight() only controls the backlight.
set_lcd_display should turn off a bit more of the hardware, but I wouldn't expect the difference in power consumption / heat generation to be very significant.

With set_backlight, the backlight may come back on after shooting, so your script needs to call it after each shot. This doesn't usually happen with set_lcd_display, but it can if review is enabled.
Quote
Will it affect CHDK motion detection function in any way?
set_backlight definitely shouldn't. AFAIK set_lcd_display normally doesn't either, but you should test your specific cameras to be sure.
Don't forget what the H stands for.

*

Offline timgor

  • ***
  • 150
Re: another rare bug
« Reply #41 on: 28 / July / 2016, 16:19:48 »
Thanks for explanation, may be it will solve my problem. I will do tests and post results here about power consumption and temperature behavior.
In general I have created many different functions for my project with more reliability compared to scripts/functions published in this forum. I'm sure they can be helpful. 
Unfortunately, I don't have possibility to review this forum periodically and I would appreciate if moderators and permanent members would send me personal message and ask me to help and publish my version. those function are related to almost everything, shooting, video, zooming, motion detector, write/delete files, night shooting, day shooting...

*

Offline reyalp

  • ******
  • 13456
Re: another rare bug
« Reply #42 on: 28 / July / 2016, 20:41:28 »
In general I have created many different functions for my project with more reliability compared to scripts/functions published in this forum. I'm sure they can be helpful. 
Do you mean changes in CHDK C code, or script?
Quote
Unfortunately, I don't have possibility to review this forum periodically and I would appreciate if moderators and permanent members would send me personal message and ask me to help and publish my version. those function are related to almost everything, shooting, video, zooming, motion detector, write/delete files, night shooting, day shooting...
I'm not sure why you want someone to PM you. If you want to post something, you can just post it in the forum. In general, I prefer to have all development discussion out in the open.

If you would like to propose code changes in CHDK itself, please post in the development section: https://chdk.setepontos.com/index.php?board=6.0

If the change is straightforward, you can post it directly in the code submission thread https://chdk.setepontos.com/index.php?topic=650.1460

For anything that's complicated or likely to trigger discussion, I'd suggest starting a new thread.
Don't forget what the H stands for.

Re: another rare bug
« Reply #43 on: 29 / July / 2016, 00:26:43 »
Unfortunately, I don't have possibility to review this forum periodically and I would appreciate if moderators and permanent members would send me personal message and ask me to help and publish my version.
IIRC,  we have already suggested that you post your script as an attachment.

Please post your complete script. It is very hard to help debug a script fragment.
It's very hard to post whole script because it's 30 kB in size
Attach it?
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline timgor

  • ***
  • 150
Re: another rare bug
« Reply #44 on: 29 / July / 2016, 11:12:31 »
Ok,

*

Offline timgor

  • ***
  • 150
Re: another rare bug
« Reply #45 on: 29 / July / 2016, 11:33:23 »
Ok, I will publish the whole script. It's open as well as CHDK and I will not hide it.
I attached, the script and it's interface in .txt format. the description can be read and downloaded from here  (sorry if did something wrong).
The script itself doesn't make any sense on the following reasons.
1. This is hybrid CHDK + firmware settings script that performs standard scripting functions and firmware functions using "click", "left", "right" functions.
2. It needs some firmware and CHDK settings without of which it's not gonna work correctly.
3. The most important thing that I talked about - more than half of the script code and functions have some physical meaning that doesn't make any sense from programming point of view and must be explained. If I start to explain physical meaning of everything then I would need to write big paper, may be much bigger than user description that I published.
The only thing that I can do is to explain particular function one by one if somebody will ask me. But I suspect that nobody will even look at the script and will not ask me without a reason.
In this case I can propose to do the following: I can briefly itemize my functions and explain - what kind of problem I had and what kind of solution I implemented. Based on this summary somebody can ask me questions and I can publish more detailed explanation.

Re: another rare bug
« Reply #46 on: 29 / July / 2016, 11:52:59 »
Ok, I will publish the whole script.
Thank you.

Quote
The script itself doesn't make any sense on the following reasons.
Actually, having read through the script, I find it quite understandable.  But then I have a little experience with making complex scripts work with CHDK and Canon's camera limitations  8)

Quote
The only thing that I can do is to explain particular function one by one if somebody will ask me. But I suspect that nobody will even look at the script and will not ask me without a reason. In this case I can propose to do the following: I can briefly itemize my functions and explain - what kind of problem I had and what kind of solution I implemented. Based on this summary somebody can ask me questions and I can publish more detailed explanation.
Your code is clear and well organized, IMHO.  There are even a few concepts that I will look at adding to some of my scripts.  Thank you for that.

My only immediate suggestion might be to convert all the commented out
Code: [Select]
--fout = io.open .... debugging statements into a function that you can enable / disable at run-time so that you don't have to hand edit the code to enable debugging after any script update? Yes - it takes up more space when the script loads but as of release 1.4 of CHDK that should not be an issue (and in earlier versions the commented out text took up space anyway).
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline c_joerg

  • *****
  • 1157
Re: another rare bug
« Reply #47 on: 30 / July / 2016, 01:28:16 »
I would appreciate if somebody would give me idea (not precise instruction) how to bypass this feature or how to to overload or block temperature measurement.
In my project I also try to use external fan but still don't have an answer how it cools down the sensor temperature. I also don't know if there is any variation from camera to camera.

In my first time-lapse script I have the sensor temperature limited to 60 degrees.
Currently I use rawopint for time-lapse. There are no adjustments for temperature.
My G1x I operate in a waterproof case. Since it is already very hot. The highest measured temperature was 68 degrees. And since I had a guilty conscience ....

https://www.flickr.com/photos/136329431@N06/27964969200/
« Last Edit: 30 / July / 2016, 01:30:31 by c_joerg »
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd


*

Offline timgor

  • ***
  • 150
Re: another rare bug
« Reply #48 on: 19 / August / 2016, 11:42:26 »
I did some temperature measurements.
I made 4 tests with the following script:


Code: [Select]

sleep(3000)
set_lcd_display(0)
set_record(1)
sleep (3000)

for i = 0,1800 do
fout = io.open("A/out.txt", "a") fout:write(tostring(get_temperature(0)),"    ",tostring(get_temperature(1)),"    ",tostring(get_temperature(2)),"    ",os.date("%X"),"\n")  fout:close()
sleep(1000)
end

press("video")
sleep(3000)
release("video")
 
sleep(1700000)

press("video")
sleep(1000)
release("video")
sleep(1000)


for i = 0,1800 do
fout = io.open("A/out.txt", "a") fout:write(tostring(get_temperature(0)),"    ",tostring(get_temperature(1)),"    ",tostring(get_temperature(2)),"    ",os.date("%X"),"\n")  fout:close()
sleep(1000)
end

set_record(0)
sleep (6000)

It does nothing, just takes temperature measurement with and without video recording.
I took 2 cameras and tested 4 times.

  • camera 1,  set_lcd_display(0)
  • camera 1, --set_lcd_display(0)
  • camera 2, set_lcd_display(0)
  • camera 2, --set_lcd_display(0)
I tested everything in my home with ambient temperature 74F. I attached 4 output files:
Conclusion: difference for get_temperature(1) is 4 degrees when video is working
LCD  screen gives extra 2 degrees when it's working.

 

Related Topics