Hi, I took delivery of my MX-700 today and have been playing with it most of the day. I've come across a problem that I can't find an answer to. Basically, the remote won't send the same signal two or more times in a row. My "power on" macro requires me to transmit the AV signal 3 times to get from the default startup RGB to S-vid. I've played around with different delays between signals, relearnt the signal, imported from my ccf files etc but still no luck. I've found that if I hit the AV button , then hit another button, then return to AV, it works OK... My Pronto has no probs like this - I'm sure that there's a simple answer out there, but I can't find it.

Apart from that, I love the feel of real buttons.

thanks

Scott

This message was edited by Wallaby on 08/27/04 05:49 ET.

What components are you using?

It's possible that this is a Parity Bit issue. If your components use parity bits, the MX-700 would respond in this manner and the Pronto would not.

Eakf, the TV is an Orion WS (I try not to tell too many people that!!)

Refusing to give in to the luxury for sleep, I went through the pre-programmed MX-700 database files one by one and found that the controls for a Loewe actually worked. The AV input buttons worked fine and I was able to add them to my startup macro which now works perfectly. Funny thing is though, I can't remap the working AV input signals (or 16:9 screen mode IR either I found out later) to other buttons on other components, so I've still got some playing around to do.

I thought I'd read up on the MX-700 pretty widely and I hadn't come across the "parity" issue. Is this a hardware handicap, or do you believe that a future firmware revision will sort it out?

thanks

Scott

Learning parity bit commands are a problem for most learning remotes. If there's a code in the IR database for a component (like you found), then the MX-700 will work fine. Philips products often use parity bit commands, but there are others as well.

Scott,

It's likely a hardware limitation. A few MX-700/800 owners have asked HTM for a firmware fix that will allow them to learn RC5 and other IR protocols with toggle (aka parity) bits for quite some time to no avail. These remotes can generate toggle bits using codes in their database but are unable to learn them properly.

HTM has addressed this learning limitation in their new URC (consumer) series and in the MX-3000 but owners of the older MX remotes are stuck or have to resort to imperfect work-arounds.

Greg