Numerical Values, DCC, Flow Charts Or Tables

Over on another thread we've been discussing the complexities of DCC and the lack of easy to read flow charts or tables.

Would you be interested in helping me develop a simple, easy to read, easy to understand flow chart or table?

In the "OTHER" thread, MarkWR and Mark Watson hit on examples of what I'm looking for.
Objections - Complexity of DCC - TrainBoard.com See page 10, unless your paging has been set up differently.

Over there...We ended up with references to endless reading and tables that just don't get the job done. I blew it and mentioned my one and only locomotive and it turned into a discussion about it...which wasn't my intent. None the less appreciated.

This will be about identifying what the CV's are for, including brief but clear definitions. Establishing a mid-range for entering in numerical values. A indicator for which direction to move the numerical value, in relation to the action desired.

If you'd like to see an easy read... count yourself in and let's get started.

You can start by giving me examples of what works. Identify the decoder, a numbered CV, purpose or action desired, range, a numerical value that gives you said action.

Here is a hypothetical example: IE.,, Digitrax Decoder, CV 20, Momentum, has a range of 20-120, use the value of 10 to start out with and go higher if you need for the locomotive to take longer to get underway or go lower if you want it to start sooner and use the value of 0 if you want momentum shut off.

I may have used the wrong CV #, feel free to correct me in order to promote having the correct information. That would go for any entry or post in this thread.

Let's not turn this into a fist fight or an electrical engineers discussion. Keep it simple guys and gals. I don't need to know how it works...just that it does work. Fair enough?

.

 

I just use the charts that come with most/all decoder manuals. The only decoder to date that has been a chore/hassle has been the LokSound series. Their CV's don't match just about everyone else's in some cases, and the ranges of possible settings are often quite a bit shorter.

Just an observation, not meant to pick nits, but if the range of a CV setting is from 20-120, an initial trial value of 10 won't be possible.

I find that using the supplied charts works well, but the fact is that each engine requires its own few minutes of 'set-up'. You can have two Paragon Niagaras from BLI, and while one will need a CV2 setting of 1 (that being for V-Start, or the least voltage that will actually just get the drivers to rotate with their axles slightly), the one next to it will need an input value of 15, maybe 20. Because of this, and the tighter drive that forces this condition, the settings for CV's 3 and 4 (inertia and momentum respectively) will also be markedly different between the two engines.

Anyway, I hope you get the utility from this new initiative that you seek. I just have gotten used to memorizing the main CV's that I find I like to tweak across engines, and then I play with the settings until the engine behaves as I wish it to.

One final note: a warm engine and one not used for several hours or days will often behave differently. A CV2 setting meant to get a cold engine underway will be too aggressive a setting for a nicely warmed engine that has been running for 15 or twenty minutes.

 

Coverton,

As always, your thoughts are welcomed and appreciated. I just want to make it simpler and easier to comprehend. A quick start of sorts.

The idea that locomotives do act differently at different times needs to be a part of a disclaimer. I hope you won't mind if we quote you.

Rick,

Thanks for your supportive and kind words.

I have no problem adopting your ideas and additions.

What we don't want to do is make this complicated...if you get my drift.
.

 

Okay, I'm new to this, and I did read the "other" thread you started, but I was thinking that a good starting point might be the configuration files that are in the JMRI suite. I'm thinking that a lot of the CV's for given engines would already be in there, ranges would already be known, perhaps even default values. Once that was put into some sort of database, then the things that you want to note could be added - like what happens when you move a CV up or down. A little programming and DB work, and you could have a website simply spit out a "flow chart" if you will for your particular decoder.

 

CoolMoose,

No problem and you are appointed and elected to start the computer software. I think this is a great idea.


For all tuned in if you get a chance to check out the last pages: Objections - Complexity of DCC - Page 14 - TrainBoard.com

MarkWR and Dave aka DCESharkman have posted what I consider to be a start in the right direction.

I'm hoping administration can copy and move some of those same posts to this discussion.

 

Will this work?

Quoted from the other thread...

 

Mark Watson,

Does it ever. I'm glad you know how the tutorial works. Reference to an earlier directive from Mark to me self.

Looking good.

Thanks.