lovetofly
10-30-2007, 11:28 PM
Not sure if anyone else has seen this, but I just got my X9303, and the first thing I tried to do was bind my "old" AR9000 to it. The AR9000 was previously bound to a DX7 and was working perfectly. So I did the normal binding procedure which seemed to work fine, but when I powered everything up again after binding, the AR9000 was all messed up with the channels mixed up and some not working. I re-bound it to the X9303 several times with the same results. To double check, I re-bound it to the DX7 and all worked fine. Then I again bound it to the X9303 and it was all messed up again. The R921 that came with the X9303 worked fine (and I didn't bind it to anything else).
I was about to ship the AR9000 back to Horizon when I thought to try binding it in smart safe mode instead of fail safe mode (where you pull the bind plug off after powering the receiver up). To my surprise, it bound correctly and worked perfectly after that. Then I was able to bind it in normal mode where you leave the bind plug on as well.
After this, I thought I'd see if I could reproduce the issue, and it is 100% reproducible. Bind to a DX7, then try to bind to an X9303 and it won't work unless you bind in smart safe mode first.
The Horizon tech said they had not heard of this before, but clearly there is an issue after being bound to a DX7. Looks like someone didn't do their backward compatibility testing very well...sure hope there aren't any other major bugs that were missed...
I was about to ship the AR9000 back to Horizon when I thought to try binding it in smart safe mode instead of fail safe mode (where you pull the bind plug off after powering the receiver up). To my surprise, it bound correctly and worked perfectly after that. Then I was able to bind it in normal mode where you leave the bind plug on as well.
After this, I thought I'd see if I could reproduce the issue, and it is 100% reproducible. Bind to a DX7, then try to bind to an X9303 and it won't work unless you bind in smart safe mode first.
The Horizon tech said they had not heard of this before, but clearly there is an issue after being bound to a DX7. Looks like someone didn't do their backward compatibility testing very well...sure hope there aren't any other major bugs that were missed...