Author Topic: "Qualify" an engine  (Read 379 times)

0 Members and 1 Guest are viewing this topic.

daniel_leavitt2000

  • Crew
  • *
  • Posts: 6373
  • Respect: +1348
"Qualify" an engine
« on: March 01, 2024, 02:03:03 AM »
0
People talk about programing their engines, but don't often go into detail about it. What parameters do you use to standardize your fleet?

Here is what I do:
1. All functions on every engine must operate the same. This includes secondary effects. For example, if I sound the horn on a silent engine, the ditch lights will flash as they would if a horn was blowing.
2. Delayed start, momentum and braking are disabled. I've run into too many headaches trying to get different manufacturers settings to play well. If I want these affects, I just slowly turn the throttle dial.
3. All engines operate on 28 speed steps.
4. All freight engine decoders are programed to a 3 point speed curve. Position 1 will be the slowest I can make the engine operate after playing around with kick/depth settings. Usually about a tie every 10 seconds. Step 14 is 30 SMPH and step 28 is 60 SMPH. Tested going both directions.
5. Passenger engines are programed to 40 SMPH at step 14 and 80 at 28.
6. After an install, a small label is applied to the underside of the fuel tank noting the manufacturer.
7. After I'm satisfied with the programing, the engine is considered "qualified" to run. CVs are noted in a spreadsheet. A colored dot is added to the underside of the fuel tank. Red for a conventional decoder. Blue for sound equipped. Black for a decoder that is missing a feature or cannot comply with standards (BLI is the big offender here. I ended up purging all the MRC decoders that I had.)

I still run into some issues. I like to push visual functions up front as silent decoders make up the bulk of my fleet. Why block off 3/4 of the number pad for sound functions that I rarely use.

Another issue I'm trying to resolve is if the function number should activate a specific device, or a category? For example, if F4 activates strobes on my Amtrak F40PH, should it activate the gyra-light on my DRGW SD40T-2?
There's a shyness found in reason
Apprehensive influence swallow away
You seem to feel abysmal take it
Then you're careful grace for sure
Kinda like the way you're breathing
Kinda like the way you keep looking away

bigdawgks

  • Crew
  • *
  • Posts: 266
  • Respect: +252
Re: "Qualify" an engine
« Reply #1 on: March 01, 2024, 08:41:01 AM »
+1
For me the use of my JMRI roster is a must simply for the function labels. I can't do numbers because NA, Europe, and the UK all have different ideas of what functions should do what, so I rely on the descriptive names instead.

Honestly it's about time that more DCC systems start building this feature into their products as standard.

jagged ben

  • Crew
  • *
  • Posts: 3303
  • Respect: +522
Re: "Qualify" an engine
« Reply #2 on: March 01, 2024, 09:58:52 AM »
0
For me it's mostly just speed matching.  I usually do some work on the function map, too.  Momentum may come later.   The ditch lights will only flash where they have separate LEDs andthey flashed on the prototype.

Yeah, I don't have a spreadsheet, that's what JMRI is for.

jagged ben

  • Crew
  • *
  • Posts: 3303
  • Respect: +522
Re: "Qualify" an engine
« Reply #3 on: March 01, 2024, 10:01:51 AM »
0
... For example, if F4 activates strobes on my Amtrak F40PH, should it activate the gyra-light on my DRGW SD40T-2?

Yes.