[darwins]

Quote

Hi Peter,

You've certainly championed this cause more than anyone I know - your site is an absolute gem - there is so much useful information there (not to mention all the specific value calculators) - I don't know how I would create a physics file without it... I've only been hitting it heavy for the last year or so - after I realized how much it contained - but I still find something new every time I visit... Thanks for doing it - seriously...

Got to agree with that.

Also think that more of the stuff that Peter has put together should find its way into the official OR User's Manual - unless there is a thought to split that up more for different kinds of users and have a more detailed manual for physics, another for timetables and activities and another for route building.

[R H Steele]

scottb613, on 19 November 2019 - 03:49 AM, said:

I was hoping you would pipe in here Gerry - I know you've made a herculean effort on getting the diesel physics worked out - and that's an area where I know very little...
Regards,
Scott

Thank you, but I'm obliged to add...Maybe i get some credit for the work of wrangling all the data into the proper formats, but without the patience, knowledge, experience, and assistance of people like Bob Boudoin, Derek Morton, Dave Nelson, Peter Newell, Joe Realmuto, and sooo many others, I would not have been able to do any of it. By the way, I consider it fun, and am enjoying every minute of it.
We are all working towards the same goal.
...and about Peter's web site....a gem, a treasure, and invaluable resource.

[Genma Saotome]

I've implemented all of the suggestions posted above as syntax in my editor (Emeditor pro) for .con and .inc files. Note, my eye's have been "failing" (I'll probably have corneal transplant surgery in December) and so as my own visual aid I've set the font to be pretty "loud".

A .con file:


I see that the reserved word "Flip" isn't in the list.


My empty_car,inc for Tim Muir's USRA SS boxcars:


As you can see I've chosen to apply specific colors to different strings - purple for MSTS parameters, blue for OR, brown for parameters not in OR which probably should be. What remains in black is a parameter name not in either list. That might be an omission for the posted list in this thread... or it could signify an old MSTS parameter that is no longer in use. THAT is useful.

I could have set the display to color code the whole line following the keyword, or defined the keyword to include the left parenthesis but I think it is better to leave the data values in black. I could assign a color to both parenthesis and I will give that a trial.

Thanks Scott for showing the way forward on this, I think it will be a big help to me.

[conductorchris]

For collaboration: maybe google docs? (sheets)

[scottb613]

Hi Dave,

Hah - EXACTLY...

Happy to help...

Sorry about your eyes and yes - that's certainly a high visibility color scheme you have there...

I've been going through various ENG/WAG files and it's interesting to note what stands out...

It might actually help for people in the know to do similar - to help us separate the wheat from the chaff on our current mission...

So - I'm not familiar with your editor - but if folks want to try a Free Open Source editor - Notepad++ is practically an industry standard for editing text files...

Download Here:
Notepad++


Updated Spreadsheet and Notepad++ Config Files:
 ORTS Params.zip (101.98K)
Number of downloads: 123


So in my attachment I included two files for "Notepad++" - the ORTS Syntax Language [SCO_ORTS_LANG.xml] - a work in progress - and a matching Style [SCO_ORTS.xml]…

After you load Notepad++ - simply copy [SCO_ORTS.xml] into your "AppData" directory (might be hidden by default) for Notepad++ themes… You should see bunch of other themes in XML format residing there....


Example AppData: C:\Users\[your user name here]\AppData\Roaming\Notepad++\themes


Next - you can place [SCO_ORTS_LANG.xml] anywhere - as we need to "Import" it - just put it somewhere easy to find...

• Start Notepad++
  
• Click on the menu item for [Language] [Define Your Language]
  
• Click on the [Import] button and then find the file [SCO_ORTS_LANG.xml] to import it
  
• That should complete import - now anytime you open an ENG/WAG/INC file - it should use that language file

One final step...

• Select [Settings] [Style Configurator]
  
• There's a dropdown called [Select Theme] - click on that
  
• Now if you placed [SCO_ORTS.xml] in the correct location - you should see [SCO_ORTS] as a style listed - just select that

Done...


Now when you open an ENG/WAG/INC - it should look like the following - green is MSTS - yellow is ORTS - magenta is valid keyword arguments... If the line of text is white - there's a chance it is no longer used - such as the white lines in my example...

NOTE - WARNING - DANGER - our lists are not complete and we have much more work to do - DANGER - WARNING - NOTE







Regards,
Scott

[steamer_ctn]

While you are talking about ENG/WAG files, I would strongly recommend that you also consider formatting in a consistent way with section headings as described on this page.

This will make the files more readable and easier to check by others, and also act as check list to identify any "missing" items. The order in which some parameters are read can also be important.

[Genma Saotome]

Here are several that are not in the above lists. I would imagine most are still in use and original to MSTS, but are there any that are obsolete? Which ones were added by the OR Team?

About brakes:
EmergencyBrakeResMaxPressure( 90 )
DerailRailForce ( 109.0903kN )
DerailBufferForce ( 380.1582kN )

About couplers:
Stiffness ( 0 5e6N/m )
Damping ( 2e6N/m/s 2e6N/m/s )
Centre()
Velocity ( 0.2m/s )

About the car or locomotive itself:
InertiaTensor ( Box ( 3.1m 4.6m 13.15m ) )
Adheasion ( 0.17 0.35 1.8 0 )
DieselEngineSpeedOfMaxTractiveEffort( 11mph )
EngineVariables( 1200 )


Most everything about diesel locomotive braking.

EngineBrakesControllerEmergencyApplicationRate( 8 )
EngineBrakesControllerEmergencyBrakeTimePenalty( 60 )
EngineBrakesControllerFullServicePressureDrop( 26 )
EngineBrakesControllerHasProportionalBrake( 1 )
EngineBrakesControllerMaxApplicationRate( 6 )
EngineBrakesControllerMaxReleaseRate( 14 )
EngineBrakesControllerMaxSystemPressure( 90 )
EngineBrakesControllerMinPressureReduction( 6 )
EngineBrakesControllerMinSystemPressure( 15 )
EngineBrakesProportionalBrakeLag( 0.9 )
DynamicBrakeHasAutoBailOff ( 0 )
DynamicBrakesCutInSpeed( 5 )
DynamicBrakesDelayTimeBeforeEngaging ( 10 )
DynamicBrakesEffectAtMaximumFadeOut( 0 )
DynamicBrakesFadingSpeed( 17 )
DynamicBrakesHigherSpeedCurveExponent( 9.2 )
DynamicBrakesLowerSpeedCurveExponent( 1.55 )
DynamicBrakesMaxAirBrakePressure ( 50 )
DynamicBrakesMaximumEffectiveSpeed( 23 )
DynamicBrakesMaximumForce( 115.5kN )
DynamicBrakesMaximumSpeedForFadeOut ( 325 )
DynamicBrakesMinUsableSpeed( 3.0 )
DynamicBrakesNumberOfControllerNotches( 1 )
DynamicBrakesResistorCurrentLimit ( 600 )
TrainBrakesControllerEmergencyBrakeTimePenalty( 60 )
TrainBrakesControllerMinSystemPressure( 15 )
BrakesEngineBrakeType ( "Air_single_pipe" )
BrakesTrainBrakeType ( "Air_single_pipe" )
BrakesEngineControllers( "Independent, Train, Dynamic" )
EngineBrakesControllerDirectControlExponent( 1 )
AirBrakesAirCompressorPowerRating( 3.85 )
AirBrakesAirCompressorWattage( 12000 )
AirBrakesAirUsedPerPoundsOfBrakePipePressure( 1.4 )
AirBrakesIsCompressorElectricOrMechanical( 1 )
AirBrakesMainMinResAirPressure( 14.7 )
Brake_Dynamic
AWS
DoesHornTriggerBell( 0 )

Monitors

EmergencyStopMonitor(
MonitoringDeviceMonitorTimeLimit( 0 )
MonitoringDeviceAlarmTimeLimit( 0 )
MonitoringDevicePenaltyTimeLimit( 0 )
MonitoringDeviceCriticalLevel( 0 )
MonitoringDeviceResetLevel( 0 )
MonitoringDeviceAppliesFullBrake( 0 )
MonitoringDeviceAppliesEmergencyBrake( 1 )
MonitoringDeviceAppliesCutsPower( 0 )
MonitoringDeviceAppliesShutsDownEngine( 0 )
)

AWSMonitor(
MonitoringDeviceMonitorTimeLimit( -1 )
MonitoringDeviceAlarmTimeLimit( 5 )
MonitoringDevicePenaltyTimeLimit( 0 )
MonitoringDeviceCriticalLevel( 0 )
MonitoringDeviceResetLevel( 0 )
MonitoringDeviceAppliesFullBrake( 0 )
MonitoringDeviceAppliesEmergencyBrake( 1 )
MonitoringDeviceAppliesCutsPower( 0 )
MonitoringDeviceAppliesShutsDownEngine( 0 )
)

[scottb613]

Hi Dave,

Thanks...

Exactly what we need - yeah - and here is where we can illustrate the "hocus pocus" part of the problem....

I didn't think any of the derail values applied in ORTS

• DerailRailForce ( 109.0903kN )
  
• DerailBufferForce ( 380.1582kN )

Same for these values for couplers (important to note only one set of couplers are used in ORTS):

• Stiffness ( 0 5e6N/m )
  
• Damping ( 2e6N/m/s 2e6N/m/s )
  
• Centre()
  
• Velocity ( 0.2m/s )

And the Inertia Tensor:

• InertiaTensor ( Box ( 3.1m 4.6m 13.15m ) )

I know Peter updated Basic Couplers to Advanced Couplers - but I'm really not sure how they differ that much from Basic Couplers - the "Size" of the shape controlled the car spacing and the "r0" controlled the slack in "Basic"...

Regards,
Scott

[Lamplighter]

Hi everyone,
I took a job and commented on the parameters. Comments describe how to get values.
I also have examples of values ​​there.
So far only the "Wagon" section
Unfortunately I wrote it for the Czech OR community and it is in Czech language.
The tutorial is part of my website where I offer settings for .wag and .eng for OR.

[scottb613]

Lamplighter, on 22 November 2019 - 04:32 AM, said:

Hi everyone,
I took a job and commented on the parameters. Comments describe how to get values.
I also have examples of values ​​there.
So far only the "Wagon" section
Unfortunately I wrote it for the Czech OR community and it is in Czech language.
The tutorial is part of my website where I offer settings for .wag and .eng for OR.

Hi...

Thanks - I'll take a look as soon as I am able...

Regards,
Scott