[Lamplighter]

Laci1959, on 22 November 2020 - 02:55 PM, said:

I think it works, you just need to set it up in the Wagon section.
AuxilaryLeakRate ( 0.1bar/s )
This is set for a bit strong leakage for testing.

The AuxilaryLeakRate parameter would be useful because cars also suffer from leaks. However, it only works in MSTS.
Unfortunately, OR only accepts the TrainPipeLeakRate parameter for the Engine section.
Leaks are therefore only counted for traction vehicles.

[Weter]

http://www.elvastowe...post__p__265197
Obviously, this is better to be fixed back.

[Lamplighter]

That would be nice, but the AuxilaryLeakRate parameter is obviously not on the Open Rails feature lists.
Respectively, the parameter is listed as MSTS only.

[darwins]

A quick experiment can determine that the parameter makes no difference.


TrainPipeLeakRate ( 0.01inHg/s ) - in eng file

AuxilaryLeakRate ( 0 ) - wag files

9 hours for vacuum to fall from 21 in to 10 in.




TrainPipeLeakRate ( 0.01inHg/s ) - in eng file

AuxilaryLeakRate ( 100 ) - wag files

9 hours for vacuum to fall from 21 in to 10 in.

[Laci1959]

It may not be listed, but it works. I tried it right before writing the comment, but I don’t have to believe it because I don’t have a name. Sorry, but I deleted the post after that because I find it meaningless. I thought I'd make a wewgy video of it, but after that ...

[Traindude]

Sorry to dig up this old thread, but I have just remembered some things I want to add to the braking improvement wishlist:

1. I've done some experimenting with equipping a loco with a Westinghouse 6 ET-style brake controller system:

Brake_Engine ( 0 1 0.08 1
            NumNotches ( 5
            Notch ( 0 0 EngineBrakesControllerReleaseStart )
		    Notch ( 0.35 0 EngineBrakesControllerRunningStart )
		    Notch ( 0.60 0 EngineBrakesControllerSelfLapStart )
		    Notch ( 0.75 0 EngineBrakesControllerApplyStart )
            Notch ( 1 0 EngineBrakesControllerEmergencyStart )	
                )
            )
	    Brake_Train ( 0 1 0.08 0
                NumNotches( 6
                    Notch ( 0     0 TrainBrakesControllerReleaseStart )
                    Notch ( 0.32   0 TrainBrakesControllerRunningStart )
                    Notch ( 0.44   0 TrainBrakesControllerHoldStart )
                    Notch ( 0.62   0 TrainBrakesControllerSelfLapStart )
                    Notch ( 0.76   0 TrainBrakesControllerApplyStart )
                    Notch ( 1   0 TrainBrakesControllerEmergencyStart )
                )
            )

Here's what I discovered:
a. ) Currently, the "Running" and "Hold" states on the Train Brake are essentially the same as "Self Lap"--used for holding the brake pressure after an application. In reality, the "Running" state is supposed to maintain full brake pipe pressure and release the loco brake (I believe someone already mentioned this), and "Holding" is used to hold the loco brake applied while charging the Auxiliary and EQ reservoirs and pressure chamber to brake pipe pressure (without charging the brake pipe). Additionally, the "Release" position charges the brake pipe to release the brakes on the cars but leave the loco brake applied.

b. ) The "Self Lap" position on the Engine Brake essentially has the same effect as "Apply"--it slowly increases the brake cylinder pressure, when in reality it's used to hold the brake cylinder pressure at a specified amount. As with the Train Brake, "Running" seems to maintain brake pressure rather than releasing the loco brakes when the Train Brake is in Running. ("Release" is used whto release the brakes when the Train Brake handle is NOT in Running.) "Apply" and "Emergency" are what I've chosen to use for the "Slow Application" and "Fast Application" positions, respectively.

2. The term "Self Lap" is IMHO a misnomer since its function is to manually lap the brakes.

3. The Bail Off function has no effect whatsoever on steam tender brakes.

That's all I can think of for now...

[Weter]

@Traindude, no sorry, please, as the brake-implementation's now just far from, not say "perfect" but even acceptance-grade :)
As DarwinS discovered, Running in sims(not IRL, certainly) is relared to vacuum systems. For air the token for Running state is ReleaseStart

Yes, there is a bit mess among token-names.

[Weter]

So, here is my proposal:

Kuju modelled brake systems in "somehow" way;
Content-developers had to follow that "odd rules" for more, than a decade, having no alternative:
ORTS was wrote "from blank sheet", but with reverce-MSTS-compatibility as a strategy.

We have ambigous names for many of tokens, as far as "Service" "Running" and "Continious" words can be interprted in different ways.

The idea itself:

1.use of MSTS tokens, which names are inambigous further
2.introduce new ORTS-tokens with correct names for rest brake-handle positions.
3.add ORTS_Display_name () parameter for giving to each of tokens desired names, that will be visible on HUD and as a tooltips

[Traindude]

Weter, on 09 January 2021 - 01:19 PM, said:

So, here is my proposal:

Kuju modelled brake systems in "somehow" way;
Content-developers had to follow that "odd rules" for more, than a decade, having no alternative:
ORTS was wrote "from blank sheet", but with reverce-MSTS-compatibility as a strategy.

We have ambigous names for many of tokens, as far as "Service" "Running" and "Continious" words can be interprted in different ways.

The idea itself:

1.use of MSTS tokens, which names are inambigous further
2.introduce new ORTS-tokens with correct names for rest brake-handle positions.
3.add ORTS_Display_name () parameter for giving to each of tokens desired names, that will be visible on HUD and as a tooltips

Thanks Weter! That is a nice idea!

I've also been doing some braking research and experimentation and one feature I'd love to see is separate MaxBrakeForce and BrakeCylinderPressureForMaxBrakeForce parameters for Service and Emergency Braking. This is why:



This is from ICS textbook 516b Section 2071a: Foundation Brake Rigging Part 1. As you can see, the net braking ratios are more than twice as high for emergency braking as for service braking. But since OR currently uses one MaxBrakeForce parameter for all braking conditions, this makes things complicated. I can use the "Emergency" net braking ratio for the Coals to Newcastle calculator, then use the appropriate value for the BrakeCylinderPressureForMaxBrakeForce paratemer from the table (example: NBR: 1.5; BrakeCylinderPressureForMaxBrakeForce: 100 psi), but this makes the associated loco or car slow down way too fast.

Does anyone catch my drift?

[darwins]

Several air brake systems and some EP brake systems work in that way. It seems like a good idea to add those parameters.

I would suggest that

MaxBrakeForce and BrakeCylinderPressureForMaxBrakeForce

remain the values for all service braking, and that where no other value is specified (vacuum brakes, some air brakes, many EP brakes) would also be used for emergency braking.

Then for those systems like those you have listed perhaps new parameters could be added

ORTSMaxEmergencyBrakeForce and ORTSBrakeCylinderPressureForMaxEmergencyBrakeForce