beavercreek
Travel, Art, Theatre, Music, Photography, Trains

After some embarrassing lack of function with my new C19/QSI Quntum combo at the local Essex meet. I managed to untangle why the MTSII (with LGB handset and Massoth Navigator) was having problems as it was set to serial, not parallel. So the MTS III and the loco then was fine and Dandy when the MTS III was changed to parallel..
BUT..
Although the loco was demonstrating very fine low speed control when run from the laptop with either the QSI Programmer or 'Sprog' with Decoder Pro3, it would only jump to a trot when then controlled by the 55016/MTS III or Navigator/MTS III systems.
Speed steps were set to 28 on the decoder and on the Navigator. Even at setting '1' speed on both controllers the speed would jump to a brisk pace. control after that is fine. It is just the initial start that is so 'crude'.
As I say it is fine with the laptop control systems. you set the speed to '1' and after a nice pause while the sounds of steam etc it gradually moves the wheels very slowly then to '2' a little faster etc. Very realistic starts can be achieved. The MTS ssytem configurations seem to miss all the slow start and jump to the equivalent of speed '4' on the laptop control configurations even though the MTS or Navigator handset is only at '1'
The decoder was reset to factory default settings and the same behaviour was displayed.Also another QSI decoder was tried with the same effect.
Am I missing something...can the MTS III only do 14 speed steps even if the Navigator handset is set to 28?
Or is there a compatibility problem between the QSI decoder (with all of its possible extensive CV c ontrol of how the motion can be configured) and MTS III?
The MTS III unit is fine with a Climax fitted with a Tsunami DCC board or a factory fitted DCC LGB loco.
BUT..
Although the loco was demonstrating very fine low speed control when run from the laptop with either the QSI Programmer or 'Sprog' with Decoder Pro3, it would only jump to a trot when then controlled by the 55016/MTS III or Navigator/MTS III systems.
Speed steps were set to 28 on the decoder and on the Navigator. Even at setting '1' speed on both controllers the speed would jump to a brisk pace. control after that is fine. It is just the initial start that is so 'crude'.
As I say it is fine with the laptop control systems. you set the speed to '1' and after a nice pause while the sounds of steam etc it gradually moves the wheels very slowly then to '2' a little faster etc. Very realistic starts can be achieved. The MTS ssytem configurations seem to miss all the slow start and jump to the equivalent of speed '4' on the laptop control configurations even though the MTS or Navigator handset is only at '1'
The decoder was reset to factory default settings and the same behaviour was displayed.Also another QSI decoder was tried with the same effect.
Am I missing something...can the MTS III only do 14 speed steps even if the Navigator handset is set to 28?
Or is there a compatibility problem between the QSI decoder (with all of its possible extensive CV c ontrol of how the motion can be configured) and MTS III?
The MTS III unit is fine with a Climax fitted with a Tsunami DCC board or a factory fitted DCC LGB loco.