S110 Porting thread

Nikon

Re: S110 Porting thread

« Reply #30 on: 20 / January / 2013, 17:01:42 »

Advertisements

Quote from: waterwingz on 20 / January / 2013, 15:48:16

Quote from: Nikon on 20 / January / 2013, 15:16:12
BTW, USB remote trigger works. Yay!
Good news! IMHO, the ability to add a remote trigger to a $85 P&S camera is probably on of the best features of CHDK. But then it all comes down to which features actually interest you.

IMHO the fact that no P&S camera regardless of brand support remote trigger as a standard feature is really strange. It is a trivial feature to implement in the camera.

Even the S110 which has built in support for communicating with a smartphone... Being able to control the camera from the smartphone would be a obvious feature.

BTW, I just ran a port-scan on the camera. It has only two open ports: 8615 and 49152.
Telnet support would have been hoping for too much.
Both ports are probably related to the CameraWindow feature. I'd guess one port might be used to find the camera on the network, and the other for actual CameraWindow stuff.
I guess I could do some wireshark captures to figure out more, but the protocol implemented in the camera is likely limited to what the CameraWindow software already supports.

Logged

philmoz

3146

Re: S110 Porting thread

« Reply #31 on: 20 / January / 2013, 17:18:07 »

Quote from: Nikon on 20 / January / 2013, 17:01:42

IMHO the fact that no P&S camera regardless of brand support remote trigger as a standard feature is really strange. It is a trivial feature to implement in the camera.

Not true, the Canon G series have a remote socket for the RS-60E3 trigger (or equivalent).

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)

waterwingz

11953

Re: S110 Porting thread

« Reply #32 on: 20 / January / 2013, 17:23:54 »

Quote from: philmoz on 20 / January / 2013, 17:18:07

Not true, the Canon G series have a remote socket for the RS-60E3 trigger (or equivalent).

@philmoz : Hard to beat a $2 switch hooked up to a couple of $1 coin cells if you are into DIY stuff

Have you seen any CHDK hooks to the Gxx remote socket ?

Logged

Ported : A1200 SD940 G10 Powershot N G16

Nikon

Re: S110 Porting thread

« Reply #33 on: 21 / January / 2013, 06:30:54 »

Quote from: philmoz on 20 / January / 2013, 17:18:07

Quote from: Nikon on 20 / January / 2013, 17:01:42
IMHO the fact that no P&S camera regardless of brand support remote trigger as a standard feature is really strange. It is a trivial feature to implement in the camera.

Not true, the Canon G series have a remote socket for the RS-60E3 trigger (or equivalent).

Phil.

Did not know that.

Logged

c10ud

Re: S110 Porting thread

« Reply #34 on: 21 / January / 2013, 15:37:04 »

Quote from: Nikon on 20 / January / 2013, 17:01:42

Quote from: waterwingz on 20 / January / 2013, 15:48:16
Quote from: Nikon on 20 / January / 2013, 15:16:12
BTW, USB remote trigger works. Yay!
Good news! IMHO, the ability to add a remote trigger to a $85 P&S camera is probably on of the best features of CHDK. But then it all comes down to which features actually interest you.
IMHO the fact that no P&S camera regardless of brand support remote trigger as a standard feature is really strange. It is a trivial feature to implement in the camera.

Even the S110 which has built in support for communicating with a smartphone... Being able to control the camera from the smartphone would be a obvious feature.

BTW, I just ran a port-scan on the camera. It has only two open ports: 8615 and 49152.
Telnet support would have been hoping for too much.
Both ports are probably related to the CameraWindow feature. I'd guess one port might be used to find the camera on the network, and the other for actual CameraWindow stuff.
I guess I could do some wireshark captures to figure out more, but the protocol implemented in the camera is likely limited to what the CameraWindow software already supports.

I added your and srsa_4c hints to the source code, now most of the hard part is done.

Remains to be seen if this camera supports the old style hooks or requires the new RAM-patching code by ERR99. I guess that can be done only by trial and error..?

Also, I think the camera might support PTP/IP? ( http://gphoto.sourceforge.net/doc/ptpip.php ).. however I'm not sure if it would be easier to hook into it or just write a simple http server (the camera seems to have some posix-y network api) for interpreting scripts and whatnot

Logged

Nikon

Re: S110 Porting thread

« Reply #35 on: 21 / January / 2013, 16:54:55 »

Quote from: c10ud on 21 / January / 2013, 15:37:04

Quote from: Nikon on 20 / January / 2013, 17:01:42
Quote from: waterwingz on 20 / January / 2013, 15:48:16
Quote from: Nikon on 20 / January / 2013, 15:16:12
BTW, USB remote trigger works. Yay!
Good news! IMHO, the ability to add a remote trigger to a $85 P&S camera is probably on of the best features of CHDK. But then it all comes down to which features actually interest you.
IMHO the fact that no P&S camera regardless of brand support remote trigger as a standard feature is really strange. It is a trivial feature to implement in the camera.

Even the S110 which has built in support for communicating with a smartphone... Being able to control the camera from the smartphone would be a obvious feature.

BTW, I just ran a port-scan on the camera. It has only two open ports: 8615 and 49152.
Telnet support would have been hoping for too much.
Both ports are probably related to the CameraWindow feature. I'd guess one port might be used to find the camera on the network, and the other for actual CameraWindow stuff.
I guess I could do some wireshark captures to figure out more, but the protocol implemented in the camera is likely limited to what the CameraWindow software already supports.

I added your and srsa_4c hints to the source code, now most of the hard part is done.

The latest changes works fine!
There is some commented-out LED-code in loader/s110/main.c which is still incorrect. Don't kow if it is important?

Quote

Remains to be seen if this camera supports the old style hooks or requires the new RAM-patching code by ERR99. I guess that can be done only by trial and error..?

I'll see what I can figure out.
How do I know if the hooks actually starts working? Is there any particular CHDK feature which uses them?

Quote

Also, I think the camera might support PTP/IP? ( http://gphoto.sourceforge.net/doc/ptpip.php ).. however I'm not sure if it would be easier to hook into it or just write a simple http server (the camera seems to have some posix-y network api) for interpreting scripts and whatnot

If it supports PTP/IP then it is on a non-standard port.

I have also noticed the posix style TCP/IP socket strings in the firmware dump. Should not be totally impossible to figure out the socket API..

Logged

c10ud

Re: S110 Porting thread

« Reply #36 on: 21 / January / 2013, 17:57:18 »

Quote from: Nikon on 21 / January / 2013, 16:54:55

Quote from: c10ud on 21 / January / 2013, 15:37:04
Quote from: Nikon on 20 / January / 2013, 17:01:42
Quote from: waterwingz on 20 / January / 2013, 15:48:16
Quote from: Nikon on 20 / January / 2013, 15:16:12
BTW, USB remote trigger works. Yay!
Good news! IMHO, the ability to add a remote trigger to a $85 P&S camera is probably on of the best features of CHDK. But then it all comes down to which features actually interest you.
IMHO the fact that no P&S camera regardless of brand support remote trigger as a standard feature is really strange. It is a trivial feature to implement in the camera.

Even the S110 which has built in support for communicating with a smartphone... Being able to control the camera from the smartphone would be a obvious feature.

BTW, I just ran a port-scan on the camera. It has only two open ports: 8615 and 49152.
Telnet support would have been hoping for too much.
Both ports are probably related to the CameraWindow feature. I'd guess one port might be used to find the camera on the network, and the other for actual CameraWindow stuff.
I guess I could do some wireshark captures to figure out more, but the protocol implemented in the camera is likely limited to what the CameraWindow software already supports.

I added your and srsa_4c hints to the source code, now most of the hard part is done.
The latest changes works fine!
There is some commented-out LED-code in loader/s110/main.c which is still incorrect. Don't kow if it is important?

Quote
Remains to be seen if this camera supports the old style hooks or requires the new RAM-patching code by ERR99. I guess that can be done only by trial and error..?

I'll see what I can figure out.
How do I know if the hooks actually starts working? Is there any particular CHDK feature which uses them?

Quote
Also, I think the camera might support PTP/IP? ( http://gphoto.sourceforge.net/doc/ptpip.php ).. however I'm not sure if it would be easier to hook into it or just write a simple http server (the camera seems to have some posix-y network api) for interpreting scripts and whatnot
If it supports PTP/IP then it is on a non-standard port.

I have also noticed the posix style TCP/IP socket strings in the firmware dump. Should not be totally impossible to figure out the socket API..

Now that's booting, LED blinking functions are not important anymore. Still it's important to update them with working code for educational purposes.

Well i guess once the captseq task is ported you can add remote, raw and parameter override hooks (example: https://github.com/c10ud/CHDK/blob/master/platform/s100/sub/100d/capt_seq.c#L80 and https://github.com/c10ud/CHDK/blob/master/platform/s100/sub/100d/capt_seq.c#L291) and see if you can get DNGs/correct USB Remote shots/correct parameter overrides.
(Please note that in order to get a correct DNG RAW some values still need to be sorted out in platform_camera.h https://github.com/c10ud/CHDK/blob/s110_port/platform/s110/platform_camera.h#L67 )

Example of "old" hooks: https://github.com/c10ud/CHDK/blob/master/platform/s100/sub/100d/boot.c#L172
Discussion about this new issue: http://chdk.setepontos.com/index.php?topic=8932.msg93205#msg93205

I added the "new" code to the boot.c file, but since it's crashing i guess it might be a consequence of either:
- some address being wrong (even if after giving it a brief look the ram addresses seemed the same as sx50..)
- s110 being different (this whole F8 vs FF thing might have some over caveat?) thus requiring "old" hooks (with probably new addresses as ERR99 says about DryOS r51?)
-

however first step is writing capt_seq.c, I can try and help you in the next days

Logged

Nikon

Re: S110 Porting thread

« Reply #37 on: 21 / January / 2013, 18:17:52 »

Ok.

USB remote seems to work already?

Logged

Nikon

Re: S110 Porting thread

« Reply #38 on: 22 / January / 2013, 02:20:32 »

A big problem with hacking the wifi of this camera is that the Canon firmware does not keep the wifi active in shooting mode.
You need to enter a special wifi mode where the wifi is activcated and image transfers via wifi is possible. As soon as you leve this mode, the wifi is disabled.

So even if the socket api is reverse-engineered, which should be completely doable, we would have to figure our how to activate the wifi in shooting mode as well, which is probably much more difficult.

Logged

waterwingz

11953

Re: S110 Porting thread

« Reply #39 on: 25 / February / 2013, 21:07:00 »

@Nikon :
@c10ud :

Its been a few weeks. Do either of you plan to submit this as a patch file to add to the svn site and (someday) the autobuild?

I suppose I could extract it from the github myself and make the patch but I have no idea about the completeness of the code posted there.

Logged

Ported : A1200 SD940 G10 Powershot N G16