[darwins]

I have a brake controller that looks like this...

Comment ( Davies & Metcalfe E70 brake controller )
Comment ( overcharge should be by a separate button )

Brake_Train ( 0 1.0 0.01 0.2
NumNotches ( 9
Notch ( 0	0 TrainBrakesControllerOverchargeStart ) Comment ( RELS )
Notch ( 0.01 0 TrainBrakesControllerReleaseStart ) Comment ( RUN )
Notch ( 0.02 0 TrainBrakesControllerEPApplyStart ) Comment ( 1 INI )
Notch ( 0.16 0 TrainBrakesControllerEPApplyStart ) Comment ( 2 )
Notch ( 0.40 0 TrainBrakesControllerEPApplyStart ) Comment ( 3 )
Notch ( 0.65 0 TrainBrakesControllerEPApplyStart ) Comment ( 4 )
Notch ( 0.80 0 TrainBrakesControllerEPApplyStart ) Comment ( 5 )
Notch ( 0.99 0 TrainBrakesControllerEPApplyStart ) Comment ( 6 FULL SERV )
Notch ( 1.00 0 TrainBrakesControllerEmergencyStart ))) Comment ( EMGY )

Brake_Engine ( 0 1 0.3 0
NumNotches ( 3
Notch ( 0	0 EngineBrakesControllerReleaseStart )
Notch ( 0.3  0 EngineBrakesControllerHoldStart )
Notch ( 0.6  0 EngineBrakesControllerFullServiceStart )))

I would like to use a brake controller that looks like this...

[b]**** ORTS OVERCHARGE BUTTON ****[/b]

Brake_Train ( 0 1.0 0.01 0.2
NumNotches ( 8
Notch ( 0.00 0 TrainBrakesControllerReleaseStart ) Comment ( RUN )
Notch ( 0.02 0 TrainBrakesControllerEPApplyStart ) Comment ( 1 INI )
Notch ( 0.18 0 TrainBrakesControllerEPApplyStart ) Comment ( 2 )
Notch ( 0.36 0 TrainBrakesControllerEPApplyStart ) Comment ( 3 )
Notch ( 0.55 0 TrainBrakesControllerEPApplyStart ) Comment ( 4 )
Notch ( 0.70 0 TrainBrakesControllerEPApplyStart ) Comment ( 5 )
Notch ( 0.85 0 TrainBrakesControllerEPApplyStart ) Comment ( 6 FULL SERV )
Notch ( 1.00 0 TrainBrakesControllerEmergencyStart ) Comment ( EMGY ) ) )

Brake_Engine ( 0 1 0.3 0
NumNotches ( 3
Notch ( 0	0 EngineBrakesControllerReleaseStart )
Notch ( 0.3  0 EngineBrakesControllerHoldStart )
Notch ( 0.6  0 EngineBrakesControllerFullServiceStart )))

How do I do it? The manual says you can add overcharge buttons to a cabview but it doesn't say how to make them work in an eng file!

http://www.elvastowe...post__p__282830

[cesarbl]

It should work without any .eng configuration, just adding it to the cvf. The EngineControllers() section is only partially used in OR at the moment.

[Laci1959]

Hello.

Oh, it's simple. Two lines were left out of the Engine section.

ORTSTrainBrakesControllerMaxOverchargePressure (6.3bar) Comment (Maximum overcharge)
ORTSTrainBrakesControllerOverchargeEliminationRate (0,0025bar / s) Comment (The leakage rate that drops to 5 bar in the RUN position.)

This has yet to be entered with the appropriate values and will work. I've been using it for a long time.
The only downside is that it is not a spring-loaded position that must be taken back by hand. It would be good to be in this position as long as I hold down the button.

Cabview would need an entry, according to the code below.

TwoState (
	Type ( ORTS_OVERCHARGE TWO_STATE )
                  Position ( 120 425 30 21 )
                  Graphic ( Overcharge.ace )
                  NumFrames ( 2 2 1 )		Comment ( First number: the control consists of two frames, second number: two columns, third number: one row. )
                  Style ( PRESSED )
                  MouseControl ( 1 )
)

In the CabViewControls row, increase the value of CabViewControls (X by the number of entries added.
I haven't tried it yet, but logically I should.

Sincerely, Laci 1959

[darwins]

Does it have a keyboard shortcut for outside of the cab view?

If not can I suggest that it uses the "J" key. This key is used for vacuum exhauster fast speed with vacuum brakes, which is the equivalent of overcharge with air brakes. For dual braked locos it was often the same position on the brake controller.

It would definitely be good as a spring loaded control. On older locos you held down the train brake handle against a spring to do this.

On modern locos you just push the button once and it overcharges to the predifined amount - very simple to use.

Perhaps we should have some way to choose between the two!

[Weter]

Same as a bailoff sprung first position of engine brake lever, by the way (very first position of 254 valve is "while pressed" - spring returns a handle to second notch(release/running), as soon as you stop pushing handle forward)
As I recall, Darwin said that time about some complexity in making such behavior mouse-controlled, as well as keyboard does that (latter seems to me elementary)

[darwins]

Yes. Previous attempts at making sprung brake notches did not work. Hopefully the coders will try again at some stage.

[Aldarion]

I have tried Laci 1959's solution and it works great. I have used it mousew clicking the button on the cab so that leaves me with a more pressing :pleasantry: question: is there a key for activating it?

[Aldarion]

I have sugested to cesarbl to use ctrl+'-' for oversharge activation.

[Keilen]

Hello to all enthusiasts!
I have the request to clarify or even help me in the following problem:
But to better understand my misunderstanding, let me explain what exactly I wanted to achieve.
Like Darwins (post #1), I wanted to visualize on the cab board the overcharge situation including the brake controller animation and the pressure gauges indication. This I have achieved by combining double blocks of the Lever - Train_Brake control, but after discovering this topic I wanted to have , this functionality separate from the controller animation.
As per post #3, by Laci1959, who presented a solution for adding the overcharge button, I followed the steps described for implementing this button. Here I have some doubts because, compared to what Laci1959 said, using the mouse activates the ON-OFF command type (i.e. the equivalent of a spring-loaded button) but does not activate the animation corresponding to the graphic in the .cvf code. Basically the dedicated button in the cab for this command remains static. I specify, (maybe I repeat myself) that the simulator reads the OVERCHARGE command, on the screen appears the control confirmation (On and Off) but the button does not animate. I have read that Aldarion managed to apply the solution presented by Laci1959 but I did not understand if the dissatisfaction is related to the non-existence of a dedicated control in the cab or to the fact that the animation does not take place on the command given with the mouse? Am I misunderstanding the method described?
Two more things, I use OR stable version 1.4 and the cab is for a diesel-electric locomotive.
I apologize for the inconvenience on Sunday but maybe someone has time to clarify.
Thanks in advance.
With consideration,

Florian

[Weter]

Hello, Florian.
On-Off style, IIRC, will give not self-returning control.
WhilePressed or Pressed (please see documents for exact syntax - I can't recall correctiy)
Is what is needed.

WRT animation absence, it can be tied with errors in *.cvf syntax too.
Particularly, ORTS understands NumFrames in very odd way - not so consistent, as MSTS did.
Some statements should be inverted (2:1 to 1:2), for some reasons, other don't work atall (tri-states are looking hard-coded to accept only 1:3)

Try to shift Your graphic's coordinates: is *.ace displayed anyway then? (or You've seen static image of CabFront only)

It's better to look log-file for possible cab errors reports, then *.cvf-file, then *.ace file of that control.

Good luck and keep on writing, when needed.

[Laci1959]

Hello.

What I forgot to write is that the code is in the eng file and it adds the possibility of overcharging with the necessary settings.
I confess that I drive with a keyboard to this day. I'm kind of used to it. That's why I never dealt with the part of the cvf file.
Not my solution, I just read the manual and applied it.
KNORR D2, D12 brakes have fixed notches, each notch has a specific pressure value. From the Run position ( ReleaseStart ), exactly the sixth press is the Row 5 position, which means exactly 3.5 bar main line ( BP ?? ) pressure.

Sincerely, Laci1959

[Weter]

And the third setting should be added to Wagon() section for referring brakes insensitivity (softness). It's triple valve's property actually.
Otherwise, overcharge elimination would cause unwanted brake application (it's rate should be slower, than softness value, for preventing that effect)

[Keilen]

Hello.

First of all thank you for responding so quickly.

Now, to summarize or recap:
In the .eng file in the engine subsection I insert the block with the two references to "Maximum overcharge" and "The leakage rate..." which I have done (I attach photo extract). Then in the .cvf file I insert the command block with the corresponding button (also attached photo).
Apart from the fact that it doesn't execute my button animation ( attached photo with cab and command given with the mouse) this entered parameter - OVERCHARGE - should be displayed on the gauges or not ?
Going back to what I wrote this morning, I checked the .cvf and Log.txt files and found nothing that would lead me to discover any mistake. I attach everything in photo format ( the forum does not allow me to upload .txt files ) I also attached the .ace image of the button. I even reversed the .ace file with the sanding one and the function was reversed. The original button for overcharge, is now animated but from the sanding command while the sanding button, now assigned to the overcharge command is stationary.
The same thing happens with the ORTS_QUICKRELEASE functionality for which I opened another topic a few months ago and the problem remained unresolved.

So, it remains to wait from Aldarion if he wants to share his experience with us.

Note: Disregard the absence of the brake controller; during testing I deliberately removed it from the .cvf

Thank you.

Attached thumbnail(s)

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

[Weter]

I like Your method: it's more perfect, than that, which I offered.
Since You only assign to button in question, the guaranteed-working function - it's more informative to see.
Now we sure, that animation, graphic and position are all good, but function (overcharge) causes the button to freeze.
***
Overcharge elimination is slower, than leak rate?
Doubtful, because they both have to be ignored by triple valves of the train.
Elimination have to eliminate overcharge in defined amount of time (say, couple of minutes) but 0,0025bar/s IMHO is good.
See real brakes documentation for true valuse, if possible.
Did You entered the rate of brake insensitivity to Wagon() section?

WHILE_PRESSED ?

Are You actually have 38 ACTIVE cab controls now?
No missing/excessive brackets?

Quote

this entered parameter - OVERCHARGE - should be displayed on the gauges or not ?

Which of? Manometers? If You enter the limit beyond 6.3 bar - then yes.

[cesarbl]

You should try with a more recent (testing or unstable) version