Trouble w/ RC4 transponders w/ KO Propo Receivers?
#1
Trouble w/ RC4 transponders w/ KO Propo Receivers?
Had a a frustrating day at the track today. I recently "upgraded" my transponders to MyLaps RC4's because the tracks I run moved to the new RC4 system.
Four of my brand new RC4's didn't work. They powered up and blinked normally but the timing system would not count laps from these four transponders, which are the "normal" RC4's, not the Hybrids.
--- Three RC4's plugged into the "B" terminal of KO Propo KR-211FH receivers.
--- One RC4 plugged into the "B" terminal of a KO Propo KR-411FH receiver.
The four cars are outfitted with various ESCs, servos and motors.
The common theme to my issue was the "B" terminal of KO Propo receivers.
Has anyone else had this problem?
Is there some sort of non-cooperation problem between KO receivers and RC4transonders?
Is there some sort of non-cooperation problem between the "B" terminal in KO receivers and RC4 transponders?
PS. I was also using an RC4 plugged into the channel 3 port of a Spektrum SR3500. That transponder logged laps properly. So, I'm fairly sure it was not operator error on behalf of the Race Director operating the timing software.
Four of my brand new RC4's didn't work. They powered up and blinked normally but the timing system would not count laps from these four transponders, which are the "normal" RC4's, not the Hybrids.
--- Three RC4's plugged into the "B" terminal of KO Propo KR-211FH receivers.
--- One RC4 plugged into the "B" terminal of a KO Propo KR-411FH receiver.
The four cars are outfitted with various ESCs, servos and motors.
The common theme to my issue was the "B" terminal of KO Propo receivers.
Has anyone else had this problem?
Is there some sort of non-cooperation problem between KO receivers and RC4transonders?
Is there some sort of non-cooperation problem between the "B" terminal in KO receivers and RC4 transponders?
PS. I was also using an RC4 plugged into the channel 3 port of a Spektrum SR3500. That transponder logged laps properly. So, I'm fairly sure it was not operator error on behalf of the Race Director operating the timing software.
#2
Tech Master
iTrader: (49)
Had a a frustrating day at the track today. I recently "upgraded" my transponders to MyLaps RC4's because the tracks I run moved to the new RC4 system.
Four of my brand new RC4's didn't work. They powered up and blinked normally but the timing system would not count laps from these four transponders, which are the "normal" RC4's, not the Hybrids.
--- Three RC4's plugged into the "B" terminal of KO Propo KR-211FH receivers.
--- One RC4 plugged into the "B" terminal of a KO Propo KR-411FH receiver.
The four cars are outfitted with various ESCs, servos and motors.
The common theme to my issue was the "B" terminal of KO Propo receivers.
Has anyone else had this problem?
Is there some sort of non-cooperation problem between KO receivers and RC4transonders?
Is there some sort of non-cooperation problem between the "B" terminal in KO receivers and RC4 transponders?
PS. I was also using an RC4 plugged into the channel 3 port of a Spektrum SR3500. That transponder logged laps properly. So, I'm fairly sure it was not operator error on behalf of the Race Director operating the timing software.
Four of my brand new RC4's didn't work. They powered up and blinked normally but the timing system would not count laps from these four transponders, which are the "normal" RC4's, not the Hybrids.
--- Three RC4's plugged into the "B" terminal of KO Propo KR-211FH receivers.
--- One RC4 plugged into the "B" terminal of a KO Propo KR-411FH receiver.
The four cars are outfitted with various ESCs, servos and motors.
The common theme to my issue was the "B" terminal of KO Propo receivers.
Has anyone else had this problem?
Is there some sort of non-cooperation problem between KO receivers and RC4transonders?
Is there some sort of non-cooperation problem between the "B" terminal in KO receivers and RC4 transponders?
PS. I was also using an RC4 plugged into the channel 3 port of a Spektrum SR3500. That transponder logged laps properly. So, I'm fairly sure it was not operator error on behalf of the Race Director operating the timing software.
Last edited by Jerz616; 05-20-2013 at 11:55 AM.