PDA

View Full Version : Global cache IR repeat issue...



shaun5
September 1st, 2010, 10:14 PM
I have a global cache wf2ir and having a bit of trouble. I have built a list of ccf commands (all from the makehex program) for my projector and most work (with a repeat value around 10), but I can't get the commands taht require repeat to work (stuff like lens zoom or shift). I raised the repeat to 15 (I think that is the highest value allowed), but I don't get much more than a small step in movement. Setting repeat to 0 (for continuos) for any command does not illuminate the led, so I don't think it is sending anything. I have tried sending the command every 100ms (I tried a few different values), but they all cause the led to flash vs. staying on. The lens doesn't move until the last flash and then only moves a bit... This makes me think the ir signal is being chopped verse continuos, but the API documentation says the command should continue to repeat if a identical command is sent before the end. The projector is a Sony vpl-vw50...

Barf
September 2nd, 2010, 06:25 AM
... and most work (with a repeat value around 10), ...

(boldfacing mine) This indicates that somehow your signals are of low quality; (no sane signal takes 10 repetitions) probably you should tackle that problem first.

shaun5
September 4th, 2010, 05:01 PM
Since the codes were generated with makehex, I don't understand how they would be low quality.

I learned from global cache that the repeat until stopped command has been removed on the wf2ir units because of the wireless interface. That doesn't make sense to me, because according to the API documentation: the command only repeats 15 times and then stops if a followup command isn't sent (this prevents a volume up command from continuing to repeat without control...). Anyway this is something I have to work around.

Global Cache suggested that I break out the pulse information from my CCF and repeat it in the CCF (effectively building a much longer command that I in theory should be able to stop at any point). Does anyone know where the pulse information is located in a given CCF. I also have the makehex irl file used to generate the CCF's.

0000 0068 0000 0010 0060 0018 0030 0018 0030 0018 0030 0018 0018 0018 0030 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0030 0018 0018 0018 0030 0018 0018 02FD

If I could get the wf2ir to learn a command (built in functionality that I can't get to work), I could use it, but that seems to be something that is difficult for a lot of people to get working...

shaun5
September 8th, 2010, 10:33 PM
The CCF's are good the emitter was not stuck on in a good place (only 2 repeats now required for all commands - except the ones that must be repeated lens focus/shift/zoom and the arrow keys). As suggested by Global Cache, I repeated the pulse information in the CCF's but the projector only accepts doubling the pulse within the CCF, so the command is now ~1/5th of what is required.

According to Global Cache, I need to repeat the identical command before the first ends to the wf2ir for it to reset the repeat counter and send a continuous command until repeat ends or a stop is received. Stop works fine. My problem is that the identical command must be 'identical' which includes the same ID. According to the API documentation the ID is an ASCII number generated by the sender. It appears Girder changes the number...because:
GC:SendIR(row.ccf,15,1,1)
win.Sleep(250);
GC:SendIR(row.ccf,15,1,1)
causes the emitter to flash between IR's (my single IR repeated 15 times is over 500ms). So....How do I force Girder to use the same ID?