Hi all,
Sorry for the delayed reply.... didn't realize until just now that someone responded to the original thread from March as late as the end of September.
I did indeed have a slight problem with the DCS52, but that's long resolved. I don't even recall what the issue was, but I think a factory reset and updating the firmware fixed whatever it was.
As for speed-matching, it's been on hold since March... work got busy, been on archaeological survey across the Dakotas until just recently, but I have a pile of TCS decoders waiting on my workbench for when I get the time to work on them. The winter slump is nearly here, though, so hopefully will dive in before the end of the year.
Thanks,
Jason
-Jason
I have 2 Bachmann locomotives with the "Sound Value" decoders. They run fine and sound good, once I replaced the worthless Bachmann couplers. However, both engines, a small Mikado and a GG1, originally were subject to jackrabbit starts because the decoders wouldn't allow me to set momentum. I fixed that by setting Vhi to about half its original value, making the engine run slower so it wouldn't jump at speed step one. I think both of these engines run too fast anyway, so it's a good compromise.
It takes an iron man to play with a toy iron horse.
jkovacs5Mental check 2: So for the Sound Value unit, I'd have to adjust CV2 for starting speed, activate the speed tables in CV29, and build my own speed table via CV67-94 to establish the running characteristics I want?
If you don't already have it, adding Decoder Pro might be very usefull to you. You will need something like a Digitrax PR4 to connect a programming track to your computer, but the software is a free download from JMRI.
For example, instead of having to program 28 separate CVs one at a time to set the speed curve, you can do them all by adjusting sliders and then saving the result. Much quicker and easier. It also reads all the available settings for each decoder, so you can see at a glance what the decoder's options are.
https://www.youtube.com/watch?v=fKc8W6_M-vU
(You can skip to about 1:25 for the tables.)
I must be missing something. I saw nothing about problems with the DCC system.
I'm not sure about the Digitrax decoders having BEMF. I have found that having BEMF helps tremendously in slow speed MU consists. I've used TCS decoders for decades. Have run consists of steam and diesel locomotives together and even rear end helpers. There will always be some slack action no matter what you do. You just don't want to drag a locomotive or have one spinning it's wheels.
Don't waste time trying to get the Sound value locomotive to run like the silent ones. Work on getting the silent ones to play nice with the sound one.
Pete.
jkovacs5 Hi all, This is mostly a baseline sanity check before I start tinkering. Finding all the documentation from either Bachmann or Soundtraxx has not been the most straight forward, and most of the posts I've seen on the topic are 10-15 years old. I just want to make sure I'm barking up the right tree here. Recently, I picked up a few older but new in box HO Bachmann FT units. Specifically, an FT-A and two B units with just the basic DCC-on-board decoders, and an FT-A with the Sound Value decoder (not the one that was released in 2021). The idea being to create an A-B-B-A set once they're all repainted and decaled, with just the lead unit having sound. As it had been a long time since I bought any low end Bachmann DCC locomotives (and that last one was in N scale), I had completely forgotten how utterly primitive their decoders were. These DCC-on-Board decoders can't utilize CV5 or CV6 or speed tables, for instance, so unless they run close enough out of the box, MUing them together could quickly become problematic. And, indeed, I'm not super happy in my early trials doing so. On level track it was close enough, but my sole gradient section clearly exposed some different running characteristics between the three non-sound locos which should be easy to iron out if I could properly speed match them. Mental check 1: Easy-peasy; for the non-sound DCC-on-Board locos, I'll pick up some NCE Bach-DSL drop-in replacement boards, and speed match like normal. Or is there something a bit newer that folks might recommend? Older posts from 10ish years ago mentioned Digitrax DH123, which I think has been replaced by the DH126 now. Anyone have a review of these? Next, the other real concern is the Sound Value lead FT-A unit. These decoders are slightly more versatile than the basic DCC-on-Board decoder in that speed tables are functional, but CV5 and CV6 aren't utilized, right? Mental check 2: So for the Sound Value unit, I'd have to adjust CV2 for starting speed, activate the speed tables in CV29, and build my own speed table via CV67-94 to establish the running characteristics I want? Thanks in advance. I've lots of practice speed matching and consisting locos, just not with dissimilar decoders or with such minimally functional decoders. Want to make sure I'm thinking through what I'll need to do to build the ABBA consist I envision. -Jason
This is mostly a baseline sanity check before I start tinkering. Finding all the documentation from either Bachmann or Soundtraxx has not been the most straight forward, and most of the posts I've seen on the topic are 10-15 years old. I just want to make sure I'm barking up the right tree here.
Recently, I picked up a few older but new in box HO Bachmann FT units. Specifically, an FT-A and two B units with just the basic DCC-on-board decoders, and an FT-A with the Sound Value decoder (not the one that was released in 2021). The idea being to create an A-B-B-A set once they're all repainted and decaled, with just the lead unit having sound.
As it had been a long time since I bought any low end Bachmann DCC locomotives (and that last one was in N scale), I had completely forgotten how utterly primitive their decoders were. These DCC-on-Board decoders can't utilize CV5 or CV6 or speed tables, for instance, so unless they run close enough out of the box, MUing them together could quickly become problematic. And, indeed, I'm not super happy in my early trials doing so. On level track it was close enough, but my sole gradient section clearly exposed some different running characteristics between the three non-sound locos which should be easy to iron out if I could properly speed match them.
Mental check 1: Easy-peasy; for the non-sound DCC-on-Board locos, I'll pick up some NCE Bach-DSL drop-in replacement boards, and speed match like normal. Or is there something a bit newer that folks might recommend? Older posts from 10ish years ago mentioned Digitrax DH123, which I think has been replaced by the DH126 now. Anyone have a review of these?
Next, the other real concern is the Sound Value lead FT-A unit. These decoders are slightly more versatile than the basic DCC-on-Board decoder in that speed tables are functional, but CV5 and CV6 aren't utilized, right?
Mental check 2: So for the Sound Value unit, I'd have to adjust CV2 for starting speed, activate the speed tables in CV29, and build my own speed table via CV67-94 to establish the running characteristics I want?
Thanks in advance. I've lots of practice speed matching and consisting locos, just not with dissimilar decoders or with such minimally functional decoders. Want to make sure I'm thinking through what I'll need to do to build the ABBA consist I envision.
It sounds like you've done some troubleshooting already, but since you're still experiencing issues with your new DCS52 command station, here are some additional steps and considerations you can take:
Firmware Update: Check if there's a firmware update available for your DCS52. Sometimes, updating the firmware can resolve compatibility or performance issues.
Inspect Track and Wiring: Even though you've checked your track wiring, it's worth another inspection to ensure there are no loose connections, short circuits, or damaged wires.
Verify Power Supply: Ensure that the power supply you're using for the DCS52 is delivering the correct voltage and amperage as specified in the DCS52's manual. An inadequate power supply can cause issues.
Check Locomotive Addresses: Verify that the addresses you're using for your locomotives are unique and not conflicting with any other devices on your layout.
Reset the DCS52 to Factory Defaults: Try performing a complete factory reset on the DCS52. Consult the manual for the exact procedure, as it might involve more than just option switch 40.
Test with Different Locomotives: Try using a different locomotive on the DCS52 to see if the issue persists. This can help determine if the problem is specific to the locomotive or the DCS52.
Contact Digitrax Support: If you continue to experience issues after trying these steps, it may be a hardware or compatibility problem with the DCS52. In that case, contacting Digitrax's customer support or warranty services would be a good next step.
Check for Interference: Sometimes, electromagnetic interference from other devices or electronics can affect DCC systems. Ensure there are no strong sources of interference nearby.
Update Documentation: Make sure you have the most up-to-date manuals and documentation for your DCS52 and Zephyr. Sometimes, new features or troubleshooting tips are included in updated manuals.
Community Forums: Consider checking online model railroading forums or communities where other model railroaders may have encountered similar issues and have shared their solutions.
If none of these steps resolves the issue, it's a good idea to reach out to Digitrax's customer support for further assistance or warranty service if your product is still under warranty. They can provide specific guidance tailored to your situation and may be able to help you diagnose and fix the problem.
jjdamnit Most of my Bachmann diesel motive power has been converted to either Digitrax DH126- or DH166-series decoders, depending on lighting needs. Some installations use the 8-pin NMRA to 9-pin harness while others are hardwired (soldered).
Most of my Bachmann diesel motive power has been converted to either Digitrax DH126- or DH166-series decoders, depending on lighting needs.
Some installations use the 8-pin NMRA to 9-pin harness while others are hardwired (soldered).
Hi there, thanks for the input.
I believe all 3 of the non-sound FTs I picked up were from the latter DCC-ready runs, so using the plugged harness would be pretty easy. I'll likely take the time to wire up new LED headlights, though... the stock bulbs (uncertain their voltage) are pretty weak. I've only popped one shell off at this point, but hardwiring if needed is easy enough as well.
jjdamnit Digitrax decoders support both CVs 5 (V Max) & 6 (V Mid) or a 28-step speed table for ease of speed matching along with CV2 (V Start). With the Digitrax decoders speed matching is done with either CVs 2, 5 & 6 OR the speed table, not both.
Digitrax decoders support both CVs 5 (V Max) & 6 (V Mid) or a 28-step speed table for ease of speed matching along with CV2 (V Start).
With the Digitrax decoders speed matching is done with either CVs 2, 5 & 6 OR the speed table, not both.
Yep, pretty standard I believe, either use custom speed tables or use the linear curves with CVs 2, 5 and 6, but not both. I've spent hours speed matching on my primary N scale layout over the years. The difference there was all my locomotives (well, the ones I planned on MUing at any rate) all had full decoders with the full suite of CVs to play with. Some speed matched best with simple linear curves and tweaks to trim and momentum, others needed the finer control of using the 28-step speed tables. What was nice was having all those options available to the end user, unlike with the minimally functional basic Bachmann decoders.
That sounds like a lot of work for that GP40 set! I bet they run like a champ, though.
rrebell the other day mentioned running in these NiB Bachmanns, and I'm pleased to say I have done so now. Golden spike moment was yesterday afternoon, finished connecting the final feeders to the buss before dinner, and first test runs a little later in the evening after cleaning the track. This morning I've had the non-sound FTs up and working for a few hours, ostensibly to more thoroughly test the trackwork and look for trouble spots, but with the added bonus of logging some scale miles.
The three non-sound Bachmanns run well together on level ground without any issue. On 2% inclines/declines, there is definitely some oscillation in the coupler tension, particularly with one of the B units. This one lags on the inclines, and races on the declines. Not enough to break the train at my relatively sedate running speeds of 20-30 scale mph, fortunately, but noticeable.
Unlike the SoundValue FT-A, these non-sound Bachmanns have no momentum programmed from the factory (or if they do, its so minimal I can't see it in action). I kind of want to play with the momentum on these non-sound FTs, increasing it to something closer to the momentum of the SoundValue FT, and see what happens with the coupler tension on the inclines. I don't know if tweaking the momentum will have any affect on the inclines; as the throttle position generally doesn't change while running the layout I suspect it won't have any noticeable affect, but it seems like a good test for the moment.
I may hold off on that test though. At the moment, the SoundValue FT has a distinct and appreciable different speed curve than the non-sound FTs, so the first step will be adjusting the SoundValue FT to more closely match the performance of the unchangeable non-sound FTs. Then I see how the full A-B-B-A set performs as a whole, and can play with the momentum to see if it makes a difference on coupler tension on inclines or not.
Of course, messing with the stock decoders in at least the non-sound FTs is kind of a pointless exercise, as I have some DH126s on order. In the end, I just want to have all the options available for speed matching properly. So I guess this exercise is mostly just to see how close I can get things matched using only the default factory decoders, so if I want to I can hold off on the decoder upgrade until I'm actually ready to repaint the shells.
Hello All,
I feel your pain when it comes to the simplicity of the Bachmann decoders.
With the GP40 consist of four (4) units (A-A-A-A) I even went so far as to re-motor all the units, along with hardwiring the DH 166 decoders and adding PX108-2 Power Xtneder Energy Storage Devices and LED lighting.
For the GP30 three (3) unit consist (A-B-A) I used the 126-series decoders with the 8-pin NMRA to 9-pin medium harness. These uses the existing Original Equipment Manufacturers Printed Circuit boards and factory-installed LEDs.
A TR2 Cow & Calf unit (NW2s) has also been re-motored and hardwired with DH126 decoders and LEDs.
The only units I have with sound are a Class G 2000 BB Vossloh locomotive and an EDK 750 Slewing Crane both with factory-installed sound.
I am currently installing a Digitrax SDXH166D sound decoder in a single H10-44, which might fit the needs of your single sound A unit in your consist.
Unfortunately, I don't have any experience with the Bachmann Sound Value decoders so I can't comment on their programming.
Hope this helps.
"Uhh...I didn’t know it was 'impossible' I just made it work...sorry"
rrebell You said they were brand new, did you run them in yet, that may fix part of the proublem.
You said they were brand new, did you run them in yet, that may fix part of the proublem.
That's one of the reasons I've held off on ordering replacement upgraded decoders, since I've not yet fully run them in. My 75-ft loop project is only about 80 percent complete, so they've been limited to 40-50 ft runs forward and backwards maybe three or four times each. At least with my N scale equipment, I always like to set up my new locos to run an hour or so nonstop around the layout, both forward then backwards, before I even attempt speed matching. I'm not *quite* there with the benchwork on this HO project to do that, but hopefully by the weekend I will be.
Although truth be told, for the cost of the Bach-DSL or the Digitrax DH126 and the funtionality upgrade they'll offer me, I might as well pick some up. I can get the three I'll need for under $60... comparatively nothing in the grand scheme of things. After running them in properly, if I can then get away with running the factory-installed decoders for a while and run them as a unit as planned, great; the replacement decoders can sit here on the workbench for a rainy day project whenever.
Basically, just tweak them as best as you can with what settings are available. In the old DC days, we used to mu engines together without the advantage of ANY fine tuning and they worked ok for the most part. If you don't like the limited options of tuning these basic decoders, then an upgrade is obviously the next best approach.
Mark.
¡ uʍop ǝpısdn sı ǝɹnʇɐuƃıs ʎɯ 'dlǝɥ