LNERGE Posted January 27, 2021 Share Posted January 27, 2021 I now have two loco's with Loksound v4 decoders that are acting rather strange. They both pick and choose.when they are going to stop on abc sections. I watched one for 30 mins and it behaved. As soon as I wash looking it slipped past a section and caused chaos. Can anyone help with cv's to make them more reliable? Link to post Share on other sites More sharing options...
JST Posted January 28, 2021 Share Posted January 28, 2021 I don't think CVs are able to "adjust" sensitivity to ABC braking - more an on/off situation and then adjust the braking time/distance. However, I did experience a similar thing with one of my similarly equipped locos but cured it by the tried and trusted method of cleaning the track and wheels. How this solved the problem I have no idea but can only guess that dirty track was messing with the signal. Also, maybe there is an intermittent problem with the ABC unit itself. Link to post Share on other sites More sharing options...
Nigelcliffe Posted January 28, 2021 Share Posted January 28, 2021 12 minutes ago, JST said: I don't think CVs are able to "adjust" sensitivity to ABC braking - more an on/off situation and then adjust the braking time/distance. ........ ESU Loksound V4. Sensitivity threshold for ABC braking, CV134. Determines how much asymmetry in the DCC signal is needed to trigger the actions. Page 43 of ESU English language manual. The other question is the design of the braking circuits. If commercially bought ones, I assume they're done properly. If DIY, were they "fast recovery diodes" or just any old cheap rectifier diodes ? If the latter, may not be reliable. Link to post Share on other sites More sharing options...
LNERGE Posted January 28, 2021 Author Share Posted January 28, 2021 I use three types of diode unit. Two are commercial and then there are my home made lash ups. I watched one loco with v4 and it behaved everywhere. I got more trains running after a while and it started to misbehave. This morning it once again ran happily with the railway to itself stopping at signals keyed to danger. I have a Bachmann 101 with sound that follows the signalling perfectly no matter how many trains are on the move. Link to post Share on other sites More sharing options...
RMweb Premium Ray H Posted January 28, 2021 RMweb Premium Share Posted January 28, 2021 Is it possible that the other trains moving are causing a slight drop in the overall track voltage just enough that the decoder can't "see" enough of a difference between the two rails to know it needs to brake? Link to post Share on other sites More sharing options...
Nigelcliffe Posted January 28, 2021 Share Posted January 28, 2021 48 minutes ago, LNERGE said: I use three types of diode unit. Two are commercial and then there are my home made lash ups. I watched one loco with v4 and it behaved everywhere. I got more trains running after a while and it started to misbehave. This morning it once again ran happily with the railway to itself stopping at signals keyed to danger. I have a Bachmann 101 with sound that follows the signalling perfectly no matter how many trains are on the move. So, it sounds like the threshold in the problematic loco is "near the limit" for that particular decoder and loco combination. (It will be decoder plus loco plus layout - all can influence what goes on. ). So, if it remains a problem, you'll have to try adjusting the threshold CV to see if it improves, or gets worse: adjusting the value in a direction to make it worse will tell you to "adjust in other direction". Should be possible to adjust with ops-mode change whilst running loco on mainline to see how things behave. I've no idea what diodes were used in your home-brew units. - Nigel Link to post Share on other sites More sharing options...
LNERGE Posted January 28, 2021 Author Share Posted January 28, 2021 I had already encountered non fast recovery diodes in the early experiments with abc. The railway works really well most of the time with quite a number of trains running and me shunting and forming up trains etc. https://www.flickr.com/photos/32297024@N08/50870728768/in/dateposted/ Link to post Share on other sites More sharing options...
Prof Klyzlr Posted January 29, 2021 Share Posted January 29, 2021 Dear RMWebbers, I'm in the process of building my next exhibition layout, which is fundamentally reliant on Asym Braking with Lok Select (US outline) and an occasional V4 decoder. ( I standardised on Selects, but found myself a couple-short, and the V4s were going-cheap right when I needed them...) Literally using "common as mud" 1N4001 sillicon diodes, (No zeners, "High Spec", "Fast recover", or other excess $$$ options diodes here...) in 5-diode packs (4-in-series + 1-bypass config), with a bog-stock NCE Powercab FW1.65b + MiniPanel acting as a pseudo-"dumb timer/reverser", and "stop within 5mm of last-powered-axle crossing the gap" (using the "constant braking distance" CV set at absolute minimum, independent of the CV3/CV4 "Momentum"/Decel rates). is both reproducible, reliable, and confidence-inspiring... (exactly what an Exhibition layout demands...) Just a pity SoundTraxx don't support the NMRA-spec CV27 Asym Braking modes... Happy Modelling, Aim to Improve, Prof Klyzlr Link to post Share on other sites More sharing options...
RMweb Gold Phil Bullock Posted December 6, 2022 RMweb Gold Share Posted December 6, 2022 I have a problem with V5 Loksound decoders and ABC braking .... wonder if anyone has experience please? V4 are fine on my home brew ABC module V5s just will not obey ! Have set CVs as follows: CV4 = 0 - I want instant stop and no momentum when driving CV27 = 3 as I want loco to stop in both directions CV253, 254 and 255 = 0 CV123 = 0 Have posted on ESU forum but no solution from there ... Cheers Phil Link to post Share on other sites More sharing options...
Prof Klyzlr Posted December 18, 2022 Share Posted December 18, 2022 Hi Phil, Just checked my V5 DCC decoders which are setup for ABC, and confirmed against a "factory flat" V5 DCC project within the Lokprogrammmer software (Remember, the LP software can be used without the Hardware interface to check CV values, and then exported for reference using the "Tools > Show Changed CVs" menu... ;-) ). In short, I suspect the issue is that: - the lowest valid value for CV 253, 254, and 255 is "1", not "0". - the working default value for CV123 is "100" Try programming these values and retesting. Happy Modelling, Aim to Improve, Prof Klyzlr Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now