Joined
·
10,744 Posts
QUOTE For some reason this is a requirement for consoles that read CV's. No doubt somebody will provide more information on this.
Before the advent of RailCom, the only way for base stations to get feedback from a decoder was for the decoder to make the motor "twitch" or in the case of Lenz move a tenth of an inch or so along the track. If the base station is fitted with sensing hardware, it can detect these twitches. Two types of twitch or twitch / no twitch without a set time period allows a decoder to send CV information one bit a time back to the base station. My educated guess is that the sensing hardware in the base station is restricted to the programming track outlet only for reasons of certainty and cost.
With RailCom equipped decoders the need to rely on the programming track to detect "twitches" will go away.
David
Before the advent of RailCom, the only way for base stations to get feedback from a decoder was for the decoder to make the motor "twitch" or in the case of Lenz move a tenth of an inch or so along the track. If the base station is fitted with sensing hardware, it can detect these twitches. Two types of twitch or twitch / no twitch without a set time period allows a decoder to send CV information one bit a time back to the base station. My educated guess is that the sensing hardware in the base station is restricted to the programming track outlet only for reasons of certainty and cost.
With RailCom equipped decoders the need to rely on the programming track to detect "twitches" will go away.
David