0 Members and 1 Guest are viewing this topic.
Given the dual motor situation, would it be better to go with two decoders or just one? I guess with two you'd have a shot at speed-matching the two cabs if it turns out that the motors don't run quite the same.Cheers,-Mark
The whole thing can be insulated with "liquid insulation", "liquid rubber", or a good thick coat of paint, as there's little danger of the short stub being bent.
Two identical decoders is the way to go IMO, but don't give them the same address. Consist them so you can adjust the CV's to get them to run as exactly the same as possible.
All good suggestions.Now, I don't do a whole lot of consisting on my layout and thus have not fiddled with speed tables before.So Peteski, if I understand you correctly, you're saying that I should give the two Cabs, say addresses as 5 (say for loco number E5) and 100. Program individual speed table to get them to run the same.Then take #100 and (by itself on the programming track) change its address to 5.Now I have two locos with the address of 5---- but they have different speed tables.Have I got it?
Have I got it?
You got it!However I'm with Max. I don't see a need for 2 decoders in this situation. Both mechanism will ready be pretty much fine tuned in DC model. I would use the KISS principal (which to me is minimal amount of electronics and tweaking the electronics).I have been running multiple loco lash-ups for ages (lots of them in in DC days) on N Trak layouts. They ran fine, even with sightly mismatched speed. They pulled some long trains without problems. I thing this quest for speed-matching perfection might be bordering on obsessive, in the end, without much gain.
Y'know, Peteski and Max are correct. I've run multiple units many many times on DC, totally non-speed matched and although one might be grinding away, or another might be being pulled along, they DID work together and pull that long train.