Stumbling along a rocky path... first an error message about variables - maybe they have to be done differently for v 1.3 ? I set fixed values instead.
I corrected this and attached a new script (below). The problem was a 1.3 vs 1.4 issue as expected.
Then other issues that I could not identify properly. Possibly something went wrong with testing card space? Possibly lcd disable/enable behaves differently on D10?
Another 1.3 vs 1.4 issue. While 1.3 scripts will run on 1.4, the converse is not necessarily true. In this case, I believe the issue was passing "true" rather than "1" to the set_lcd_display() function. I reverted to 1.3 conventions in the attached script.
Also wondering whether there's any way to have a button-press to turn off autostart while the script is running? Might need this in order to get view screen to stay on long enough for another check. I will be unable to delete the config file after the camera is in position in its mounting box. Perhaps something like 'menu' press that will safely stop Ultimate Intervalometer - I'm thinking maybe it could disable autostart before safely stopping - could that be feasible?
Done.
Note that you could have just pressed the camera's shutter button right after the script autostarts to abort instantly. But now you have the option of pressing the MENU button after the shot as well.
I need photos at 5 minute intervals for this project. Need to measure script run-duration when it's working right. Aiming to have external controller turn power on, leave it on for 10sec plus script run-duration. Leave it off for (5 min minus (10s+run dur)). Repeat. Does that sound reasonable?
Well, the script turn the camera off on its own. So you can let your external controller leave the power on for four minutes if you like - no precision measurements needed.
Try the new script? If it acts up, please post the log file that was created (by default now).
