Make an LED automatic light up when script is running.

  • 1 Replies
  • 553 Views
Make an LED automatic light up when script is running.
« on: 04 / January / 2014, 21:32:43 »
Advertisements
Hello, I have a question. I am running multiple cameras at the same time and I am using the blue LED that is integrated in the print button as an indicator wether a script runs or not. This way I immediately see when here or there a script did not terminate succesfully.

Since I am using CHDKPTP and for convenience reason I would like CHDK make the LED light up when a script starts to run and turn it off when a script shuts down succesfully. IS that possible with a normal build or CHDK or will I have to compile my own version?

If so: Could someone please give me a very short glance how to deal with it then? I had a look into the core files and I suppose I would have to change something in "script.c" But when I do that I will stick to the version I altered, so I won't be able to easily follof the new official releases.

I already it has to do something with SVN and patch files, but could one of you coders give me a very short workflow to deal with "trunks" and patches and so on? Or tell me where to read about it?

Thanks! Martin.

Re: Make an LED automatic light up when script is running.
« Reply #1 on: 04 / January / 2014, 21:54:50 »
Since I am using CHDKPTP and for convenience reason I would like CHDK make the LED light up when a script starts to run and turn it off when a script shuts down succesfully. IS that possible with a normal build or CHDK or will I have to compile my own version?
You can turn any or all of your camera's LED's on from your script.   Or at least you should be able to if the port was done correctly.    So,  if you turn on an LED when your script starts, it will (generally) stay on as long as the Canon f/w does not turn it off.    And if you only turn that LED off at the end of your script it will only be off if your script completed correctly.  No source code modifications needed.

Quote
But when I do that I will stick to the version I altered, so I won't be able to easily follof the new official releases.
If you make a patch file of your changes,  and are careful,  you can repatch each subsequent update and keep current with the svn updates.  But you really need to do it frequently as you might get too far out of sync to fix if you wait too long.

Quote
I already it has to do something with SVN and patch files, but could one of you coders give me a very short workflow to deal with "trunks" and patches and so on? Or tell me where to read about it?
http://svnbook.red-bean.com/en/1.7/svn-book.pdf
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics