[Csantucci]

Thanks to the support of Peter, (gpz) Distributed Power management is now available also in the Unstable release and should be available in the Testing release starting from next Saturday.

[edwardk]

It is great that this operation is now officially recognized. I remember combining his work on my own with one of the versions and enjoying it. Of course this was many, many years ago when this was done.


Edit: When it comes to the number of groups used, it pays off to watch many Virtual Railfan videos. A standard unit train such as coal as example will have locomotives at the front and the rear since they are not that long at least when compared to container trains. A container train on the other hand as far as I noticed will also have 2 groups. Depending on length, locomotives only on the front or front and rear. The super long container trains will have 3 to 4 locomotives on the front with 3 to 4 locomotives in the middle only. In this situation, it appears to be 2 trains in one.

[Genma Saotome]

railguy, on 14 November 2021 - 05:11 PM, said:

This brings up another issue that I've mentioned numerous times: With MU'ed locomotives in the "real world", all air compressors generally contribute to charging the train line. I don't believe that OR models this yet. The issue you mention about DPU units contributing/not contributing to charging the train line is valid, as well. Also, as I have mentioned before, currently OR only has the "inherited" TrainPipeLeakRate parameter, where, in fact, individual locomotive air tanks can leak in "real life." That should also modeled to achieve more realism. All of these things sort of inter-relate because they affect train line charging and air system behavior. Probably, on a broader front, this begs the discussion of whether OR should have a "gaming" mode for simplified (and less prototypical) options and behavior, and a "simulator" mode that tries, as much as possible, to simulate prototypical operation.

FWIW the problem is not limited to modern locomotives, this thread is about the same problem in 100 year old locomotives. In this case in the wagons dividing the powered units are actually just bogies in a set of 4 powered units. AFAIK, they were modeled that way because of how MSTS handled large locomotive models.

Any chance this matter of common air pump matters can be "elevated" to somebody-needs-to-deal-with-his-problem?

[Csantucci]

Feature now available in Testing release T1.4-100, as well as in ORNYMG 112.
Thanks to gpz and mbm_OR for having developed this.

[Csantucci]

In next days I foresee to release a new update of this functionalty, that manages a distributed power screen page and the related cabview controls.
Borislav kindly allowed me to modify and to make the modifications public for his excellent cabview for the SVTX ES44AC to test the feature.
Below the screen page in the cab

Using also the feature about the multiple screen pages, the page is recalled by pushing a button below the main screen.
The screen page layout is formed by a fixed background, and by the variable table part.
The variable table is recalled with following cabview control:

		ScreenDisplay (
            Type ( ORTS_DISTRIBUTED_POWER SCREEN_DISPLAY )
            Position (  164.4 286.5 136 52 )
			Parameters (
                FullTable True
			)
            Units ( KM_PER_HOUR )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
        )

So with only a call the whole table is displayed.
The cabview controls to control the various DP commands are linked to the buttons below the display, and are active only if the DP screen page is displayed. Here the self-explaining code for them in the .cvf file:

		TwoState (
			Type ( ORTS_DP_MOVE_TO_FRONT TWO_STATE )
			Position ( 163.2 378.4 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_MOVE_TO_BACK TWO_STATE )
			Position ( 179.9 379 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_IDLE TWO_STATE )
			Position ( 214.325 379.5 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_TRACTION TWO_STATE )
			Position ( 196.9 379.25 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_BRAKE TWO_STATE )
			Position ( 231 380.6 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_MORE TWO_STATE )
			Position ( 248.5 379.6 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_LESS TWO_STATE )
			Position ( 247 390.625 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey2trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)

I'm planning to make available the whole customization kit, so that the ugraded cab may be used and can be used as reference for content developers.

[ATW]

Amazing 👏 I look forward to this feature an to add to the existing cabiviews including mine in development.

[ATW]

railguy, on 07 December 2021 - 06:49 AM, said:

Not to derail the thread, but the "revised" regular SD70s would be a real treat. Thanks again for all your contributions.

Oh they will be icing on the cake to run with the other SD70s in store. Still some more Notch noses will follow including some ones in real life that have had their computer screens removed an analog guages added to them. Gotta yet think of revised NS ones.

But that will be till some time an interest gets into them.

Yea back on topic I await adding the DPU cab instruments to the Tier 4.

[akioyamamura]

Csantucci, on 24 December 2021 - 02:48 AM, said:

In next days I foresee to release a new update of this functionalty, that manages a distributed power screen page and the related cabview controls.
Borislav kindly allowed me to modify and to make the modifications public for his excellent cabview for the SVTX ES44AC to test the feature.

Awesome Carlo. This feature will be available fot 3D cab too?

[Csantucci]

That should work in 3D cabs too.

[akioyamamura]

Csantucci, on 25 December 2021 - 02:04 AM, said:

That should work in 3D cabs too.

Nice! One thing that i noticed that still wrong in the Shift+F9 and in your printscreen is the flow and the load display.

The flow is not the fuel flow, but the BP air flow feeding the Brake Pipe. This parameter we don't have yet in OR/MSTS, so in my opinion this parameter shouldn't exist

Another point is the load display, this should diplay the tractive effort or the amps. To simplify I would suggest to show the "LOAD_METER DIGITAL" value that is a command that already exist.

[Borislav]

Csantucci, on 24 December 2021 - 02:48 AM, said:

In next days I foresee to release a new update of this functionalty, that manages a distributed power screen page and the related cabview controls.
Borislav kindly allowed me to modify and to make the modifications public for his excellent cabview for the SVTX ES44AC to test the feature.
Below the screen page in the cab
DPscreenpage.jpg
Using also the feature about the multiple screen pages, the page is recalled by pushing a button below the main screen.
The screen page layout is formed by a fixed background, and by the variable table part.
The variable table is recalled with following cabview control:

		ScreenDisplay (
            Type ( ORTS_DISTRIBUTED_POWER SCREEN_DISPLAY )
            Position (  164.4 286.5 136 52 )
			Parameters (
                FullTable True
			)
            Units ( KM_PER_HOUR )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
        )

So with only a call the whole table is displayed.
The cabview controls to control the various DP commands are linked to the buttons below the display, and are active only if the DP screen page is displayed. Here the self-explaining code for them in the .cvf file:

		TwoState (
			Type ( ORTS_DP_MOVE_TO_FRONT TWO_STATE )
			Position ( 163.2 378.4 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_MOVE_TO_BACK TWO_STATE )
			Position ( 179.9 379 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_IDLE TWO_STATE )
			Position ( 214.325 379.5 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_TRACTION TWO_STATE )
			Position ( 196.9 379.25 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_BRAKE TWO_STATE )
			Position ( 231 380.6 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_MORE TWO_STATE )
			Position ( 248.5 379.6 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey1trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)
		TwoState (
			Type ( ORTS_DP_LESS TWO_STATE )
			Position ( 247 390.625 13.75 10 )
			Graphic ( "..\\..\\Common.Cab\\ES44v3\\softkey2trans.ace" )
			NumFrames ( 2 2 1 )
			Style ( WHILE_PRESSED )
			MouseControl ( 1 )
			ORTSDisplay ( 1 )
			ORTSScreenPage ( "2300-0" )
		)

I'm planning to make available the whole customization kit, so that the ugraded cab may be used and can be used as reference for content developers.

This is an excellent addition! I will start working on implementing it in all of my cabs.

[railguy]

These new cabs are fantastic. The DPU capability will be just more icing on the cake. One note that I will make--that I also believe existed in some of the earlier ES44 cabs--the indexing of the throttle and dynamic brake displays are not indexing correctly for many SLI and other locos. I've been tweaking mine to fix the issue on the throttle--it's not difficult, and I'll be checking the dynamic brake indexing issue to tweak those. This is not a big deal and there is no "one-size-fits-all" for this because many .eng files themselves have different throttle notch values. A huge thanks to Borislav for making these wonderful cabs--they are another big step forward for OR.

[Csantucci]

The DPU features described here http://www.elvastowe...post__p__279652 (cabview controls for display of DPU table and for DPU commands) are now available in ORNYMG 113 and in Unstable release U2021.12.28-0906.

[akioyamamura]

First of all, thank you Carlo and everyone that contribute to the progress of DPU. It's a fantastic feature for heavy haul operantions.

Carlo, it's already working for 3d cab? I'm trying name the new screen as "ORTS_DISTRIBUTED_POWER:0:0" in the hierarchy. Tried also "ORTS_DISTRIBUTED_POWER:0:6:SPEEDB" but didn't work here.

[Csantucci]

Hi, please suspend your efforts to try to have this working in 3D cabs, to avoid wasting time. I'll consult another developer. 2D cabs instead are OK, because I could test them.