Wooooohooo! Million thanks to you, guys, especially ahull and waterwingz! Got it working here for the first time. I have "remote" enabled and also the sync option. I changed the 10k resistor to 2.2k, now the GetAdChValue(5) shows a value ~100. Tomorrow I'll start building ten dummies and then will do some sync testing.
But there is one thing. Until now when having the camera to USB I switched it on and some autostart.lua ran. Know the camera stucks in the ALT-Mode, the autostart script does not run anymore. I suppose the camera is in the play mode?
Changing this back to the original mode - before dealing with both PTP and Remote at the same time - makes it work as expected.
Okay - I've done some more testing and I now see the problem.
With my latest patch, the camera USB port can communicate via PTP without interference from the Remote functionality. And A/D channel 5 is used for all the shooting & sync stuff.
However normal USB communications (CHDK loaded or not) puts the camera into playback mode when the USB cable is connected. This means the A/D channel 5 code performs the default USB remote playback action (photo advance) and does not take a picture. If you are using CHDKPTP or a CHDK script, you can issue a
switch_mode_usb(1) command to go into shooting mode and the A/D channel 5 code should work at that point. But if you want to do this without a script or ptp message (i.e. camera buttons only) then the usual method of pressing the half pressing the shutter button to switch to shooting mode will not work.
In Karmaschinkens' case, he is using a startup script and so should be able to add a
switch_mode_usb(1) statement to the script and be in business. As long as his USB hubs are powered before he turns on his cameras. However, a better solution for this is needed. I have some crude ideas about adding
switch_mode_usb(1) to a remote input device mode that supports A/D triggering (added to the existing OnePush, TwoPush, CA-1 modes) but I hope other will have better ideas?