I recently found out that someone can issue commands through the serial port of these projectors..either with python scripts or simply by creating plain text files with the desired commands and "copying" these texts over the serial port of the projector.Question is , can we use some way and issue these commands (with any way i dont really care which one) through chdkptp ?
QuoteRegarding your problem with burst shooting:I'm still thinking about it, I just had some stuff come up that doesn't leave me with much time for CHDK. Maybe after the weekend I'll have something to test.Any input on it will be much appreciated and useful.
Regarding your problem with burst shooting:I'm still thinking about it, I just had some stuff come up that doesn't leave me with much time for CHDK. Maybe after the weekend I'll have something to test.
Right now i have 2 x ixus 160 in my home and i can test it. Theoritically under the same setup , A2500 should perfom more or less the same since they have the same specs (0.8 shoots per second).
So if i get this right.. a rig of x ixus can go as low as ~1.7-1.8 secs between shots regardless the number of them ?(of the cameras)Always in theory...
I can say that 2000msecs is a safe interval.How sure we are that this interval will work the same way with more cameras (with the same configuration apparently)?Theoritically it should work..right?
1. Address of the function i need to change.2. The actual command to do the change.
Quote from: mphx on 27 / June / 2016, 04:14:41I can say that 2000msecs is a safe interval.How sure we are that this interval will work the same way with more cameras (with the same configuration apparently)?Theoritically it should work..right?In theory.Quote1. Address of the function i need to change.2. The actual command to do the change.You need the ID of the UI property, and the values. To change it, you can use the eventprocs mentioned in the forum thread.To find the ID and valuesIn the debug menu, set the "ALT +/- debug action" to CmpUIPenter alt and press the debug keyleave alt and change the settingenter alt and press the debug key againThe differences in UI prop values will be displayedThe debug key is port specific. It should be shown in the alt help screen.However, on D10, review time doesn't appear to be a UI prop. It does appear to be one (ID 129) on ixus140_elph130, which was released much closer to a2500.
call_event_proc("PTM_SetCurrentItem",0x800c,0) didn't work with the 2 ixus at home (where 0x800c and value i put the correct ones ofc).Unless the syntax is different than the above and i don't know it (And by "didn't work" i mean the command produced error , it didnt get through to the cameras , i can copy/paste the error when i get back home and repeat it)
it seems i am losing something as far as A2500 is concerned.I dont find any reference about "debug key" in alt help menu.Check the photo below (not the best but u can see what it displays )
I changed manually the settings of 8x A2500s to "play" with the intervals.
At 2000msecs 1-2 double shots were synced , the rest not.At 2500msecs , same result.Some synced , some not.
I would suggest starting with just one or two. As I've said before, there really shouldn't be a difference, and it will be easier to keep track of the results.
Were you using the most recent multicam.lua?What were the status values?Have you run fixedint.lua on one of these cameras?
Started by mrgreen4242
General Discussion and Assistance
Started by gcgc
General Help and Assistance on using CHDK stable releases
Started by waterwingz
General Discussion and Assistance
Started by simtek
Started by reyalp
Creative Uses of CHDK