With protocol 57, it was very eratic. I couldn't really control if
there was a 2 second delay, or immediate picture. And it probably
worked once every fifty to one hundred tries or so when I was button
mashing.

I wasn't able to get it to work with the protocols mentioned by you
(67, 10, 35) with the given OBCs (1, 170, 255).


I am trying to follow the protocols brough up when Universal Remotes
are mentioned. I picked 57 from here, but will get around to trying
the other codes mentioned in this page:

http://www2.camerahacker.com/CH_Exec/Comments/DisplayComments.tcl?.file=Hacks/un\
iversal_remote_with_Canon_cameras.html


The "intersting" OBCs that I found so far are 009, 024 + 026, 50, 52,
87, 83?, 89, 94. They're only interesting because when I was going
through them, I was able to trip the shutter at times. But when I go
back and try to build something with them it doesn't work well...


Here is the complete HEX representation of the databases in the
OmniRemote (Pro) memory for these two actions. Pipe || symbols around
the name, and the astriks ** around a byte I can drop that still
works. I can't drop the preceding bytes for some reason though.

SHOOT
00 32 00 54 00 3C 00 3C
|53 68 6F 6F 74|
00 BC 00 00 00 00 00 2B
07 00 00 01 00 01 32 40
01 F0 00 00 00 00 00 00
1F 00 *00*

2 SEC
00 32 00 18 00 3C 00 3C
|32 73 65 63|
00 00 00 00 00 00 07 00
04 00 00 00 01 00 01 32
40 01 F0 00 00 00 00 0F
80 00


Thanks for your time. Hopefully we can figure this out.

-Cliff


--- In RMCEnhancer@yahoogroups.com, "Jason Olsen" <jasonolsen@m...> wrote:
>
> I found some info in the JP1 forum. Their solution actually involved
> writing a new protocol (if JP1 devices don't have the protocol built
> in, it must be a proprietary one to Canon). But this is the info I was
> able to glean:
>
> Frequency 36363
> Click: +714 -5330 +576 -130494
> Delay: +714 -5330 + 582 -31892
>
> Where immediate click is Click, 1 second delay is Delay + Click, two
> second delay is Delay + Delay + Click, etc. I didn't find any other
> mapped buttons.
>
> You said it is working with Protocol 57? According to my notes,
> protocol 57 is a sony 20 variant
> Frequency: 40000
> Zero: +600 -600
> One: 1200 -600
>
> That doesn't map really well, so if it is working, it is probably very
> erratic.
>
> What controls did you get to activate with each of the OBCs you listed ?
>
> See if this works -- it's not exact, but it's a little closer to your
> specs:
>
> Protocol 67
> Device/Subdevice = 0
> OBC = 1, 170, or 255
>
> Also try protocols 10 and 35 with same settings. See if any of those
> produce more consistent results.
>
> I was not able to make heads or tails out of the Omniremote signal you
> gave. It doesn't appear to be an actual capture. But hopefully this
> other information I found will negate that need.
>
> --- In RMCEnhancer@yahoogroups.com, "Cliff" <tim_axe@y...> wrote:
> >
> >
> > For the most part, I have skinned everything needed to put together a
> > definition file for RMC to work with the Digital Rebel. I know what
> > the signal I need to reproduce is from OmniRemote. The problem is I
> > only have 1 PDA, so I can't quite guess & check the OBC/Command Table
> > to match the signal I need to produce. I need someone to help me with
> > this stuff below:
> >
> >
> > OmniRemote Signals To Match:
> > 1) 00 BC 00 00 00 00 00 2B 07 00 00 01 00 01 32 40 01
> > F0 00 00 00 00 00 00 1F 00 00
> >
> > 2) 00 00 00 00 00 00 07 00 04 00 00 00 01 00 01 32 40
> > 01 F0 00 00 00 00 0F 80 00
> >
> >
> > Current Settings in RMC Enhancer's Command Table Editor:
> > Protocol: 57
> > Device Sub Device: 0 . 0
> > Command Size: 1 ( 1,1 )
> > Device Type: 18
> >
> >
> > I've gone through a lot of OBC's, and sometimes I can get 009, 024 +
> > 026, 050, 052 to work with my camera's IR remote. I'm still working
> > my way through 200 more OBC's, but I don't even know if the Command
> > Size is right, because I can't look at the signal being produced.
> >
> > If someone knows a way to compute the signal being produced so I can
> > derive the OBC to supply to RMC Enhancer to produce the correct
> > signal, I'd appreciate it. Thanks in advance, and I'll continue
> > working on this to hopefully get something working to provide to both
> > users of this camera, and of clie's...