stevech
October 13th, 2002, 12:55 PM
In my quest to get the TV set's remote in room A to be heard by irMAN which is in room B, I've reached an impass and seek help from someone who may have been there, done that...
-Can't hardwire cable from room A to B due to construction issues. So...
-First tried a Recoton 400MHz wireless remote extender. Random noise drove irMAN nuts and thus, Girder went nuts and crashed a lot.
-Now tried ezREMOTE. This converts IR to coded signals over the power like, kind of like X10.
When the direction is reversed, that is, the remote is in the opposite room from the TV, and the Recoton and ezREMOTE extenders are reversed, the TV does respond well.
With ezREMOTE, irMAN sends out two messages for each button-press. Can't see this in Girder very well. But with irMAN's standard IR SERVER history function, I see that with ezREMOTE, every button is prefixed by a constant message then the button-unique message comes out of irMAN. As if the IR code synch bits are changed by ezREMOTE in some manner which confuses irMAN into sending the prefix message.
A solution is to train Girder to ignore the 1st message and keep the 2nd message from ezREMOTE+irMAN. THis sort of works. However, this back-to-back scheme works only if the Girder SPEED option is at max; I guess SPEED is so it can catch the two successive messages. Howerver, with this in place, Girder is very crash prone - it does far too many ILLEGAL ADDRESS ACCESSED faults.
Maybe I'm the only fool in the world trying to use a remote extender with Girder.
I could write a program which itself receives data from irMAN and discards the bogus preamble message. Then pass the real message to Girder. Don't know how that program would interface to Girder; not schooled in developing plug-ins. Lotta work for such a dumb problem.
Ideas? (I know, I know. Run a wire and get rid of the extender. Easier said than done).
-Can't hardwire cable from room A to B due to construction issues. So...
-First tried a Recoton 400MHz wireless remote extender. Random noise drove irMAN nuts and thus, Girder went nuts and crashed a lot.
-Now tried ezREMOTE. This converts IR to coded signals over the power like, kind of like X10.
When the direction is reversed, that is, the remote is in the opposite room from the TV, and the Recoton and ezREMOTE extenders are reversed, the TV does respond well.
With ezREMOTE, irMAN sends out two messages for each button-press. Can't see this in Girder very well. But with irMAN's standard IR SERVER history function, I see that with ezREMOTE, every button is prefixed by a constant message then the button-unique message comes out of irMAN. As if the IR code synch bits are changed by ezREMOTE in some manner which confuses irMAN into sending the prefix message.
A solution is to train Girder to ignore the 1st message and keep the 2nd message from ezREMOTE+irMAN. THis sort of works. However, this back-to-back scheme works only if the Girder SPEED option is at max; I guess SPEED is so it can catch the two successive messages. Howerver, with this in place, Girder is very crash prone - it does far too many ILLEGAL ADDRESS ACCESSED faults.
Maybe I'm the only fool in the world trying to use a remote extender with Girder.
I could write a program which itself receives data from irMAN and discards the bogus preamble message. Then pass the real message to Girder. Don't know how that program would interface to Girder; not schooled in developing plug-ins. Lotta work for such a dumb problem.
Ideas? (I know, I know. Run a wire and get rid of the extender. Easier said than done).