PC Universal Freight Calculator For German Content

As teased previously in the thread about calculating correct characteristics of freight trains, I was trying to create a calculator that would keep all the necessary values on one place, and made possible to generate timetables within few seconds.

Now I have a first version ready to present, it is not perfect and it neglects some calculations for sake of simplicity, but it should be well enough to give you a quick guide on:

• What PZB mode you should use
• What brake selectors you should change
• What is maximum speed of your train so you safely stop on red

Before I get to the details, here is the link for the calculator:
> https://docs.google.com/spreadsheets/d/1nkUl7kI-k3EOyEfFVhL3lQlEKw7fJ_ytps16HBLDpjY/edit?usp=sharing <
You need to make an own copy of the document to your Google Drive to be able to edit it, that way people don't overwrite each other's data when using it.

How to use it:

1. Make a copy

First, make a copy of the document, to gain edit rights and not conflict with other users. You can do this by going to File - Make a Copy. Document has a version number, so when your local copy is older than the upstream, simply delete it from your Drive and make a copy of the original one again.

2. Select locos

Then, you can get to the data. First, select a loco that you will be driving. This is simple, just put "1" next to one that you want and ensure that there "0" next to all others. The calculator eats also higher numbers for multi-headed trains, but I have not tested if the resulting values are correct.



3. Build consist

Now comes the tricky part, building a consist. Find the wagons that your train contains, and insert respective amounts into "empty" or "loaded" columns. For covered wagons without visible load, just try either state and check if tonnage of train corresponds to game or not, and adjust accordingly.
Due to "lange lok" concept, we need to insert first five wagons separately, as they may have different brake settings than the rest. So if you have 20 loaded coal wagons, insert 5 to "1-5 loaded" and 15 to "6+ loaded" columns. Again, ensure that all other wagons are zeroed.



3.1. Articulated wagons

Articulated wagons (container and car wagons currently) count as a single unit, but game treats them separately. So if pause menu shows container train with 41 parts, it means you have 1 loco and 20 articulated units. Because both halves of articulated wagons must have same brake setting, for lange lok, we have to consider first six halves (three articulated units) instead of five wagons. In this case you need to enter 1 loco, 3 container wagons in "1-5" column and 17 in the "6+" column. It sounds complicated, but if you think about it, it makes sense.

Mixed trains are supported, order of various wagons does not matter, but still insert separately the first five and the rest.

4. Configure route

In the last step, insert maximum descent on your route. Some more direct route selector is planned there for future, but gathering the data is lengthy, so for now, there is just a raw permille configurator. If you don't know what to put in, you can roughly use 11 for flat-ish routes like Nahverkehr Dresden or Münich-Augsburg, 17 for hilly routes, and 25 for very hilly routes where trains struggle, like Dresden-Chemnitz or Wuppertal-Hagen.



5. Pick up timetables

After you finish entering the data, you will be presented with two timetable options - Timetable R/P usually offers better speed, Timetable G is an alternative if R/P for some reason cannot be used. Usually dispatcher would decide which timetable you should drive to, but you can pick what is more fun. Each timetable will prescribe you with PZB mode, maximum speed and brake settings. Especially with brake settings, you will most likely have to do the respective changes on wagons yourselves, check tygerways's youtube tutorial for how to do that correctly.



Sometimes it happens that the total train weight and length does not match what is shown in the game's pause menu, length should differ just by few meters, but weight can differ greatly. If that's the case, first check if your train is correctly entered as empty/loaded and if the other option does not get you closer. Even then it may vary; it looks like some newer wagons have randomly generated load, I couldn't determine how exactly. If that's the case, you can use "Train data override" section which will override the values for calculation of PZB and brake modes, but does not ruin the remaining consist data about braked weights and so on. When you don't need it, put zero there to return to calculated values.



6. Have fun

Treat this as a first version and I am looking for feedback especially from other expert content creators, if everything is correct and I did not forget anything, but I play with using it for few weeks and the outputs make a good sense to me.

I will not hide that during building this, I was working with a lot of materials provided by people in the thread linked in the first paragraph, so be sure to show some love to them as well.

Two known issues are in the first version. First, Uacns data are completely missing. This wagon is from the old and unsupported MSB 363 addon that I don't have and I don't plan to buy it. If somebody has it and is willing to complete the data, I can add them in next version. Second, Falns ingame data are absurd. The wagons in the game are loaded with 160 tons of coal while their real capacity is only 65 tons, so the calculation doesn't make much sense. It still works, but your brake percents will be so horrible that you will be restricted to 35-40 km/h maximum speed. You can ask DTG to fix this.

 

I will be checking this out! Thanks for your efforts

 

This will get lost quickly, I've reported it to be moved to the Guides section.

Great job!

 

The guides section of the forum is so hidden that nobody goes there, really. Rest of the guides are here as well.

 

It's easier to find there, as the General Discussion gets flooded with threads of all sorts and this one will drown quickly unless someone constantly bumps it.

 

Please leave it here, this forum gets much more traffic and much more people can see it here.

Getting the formulas right was not as much of a problem, as OpenMinded, cwf.green, Lamplight, tygerways and some other users already made a great effort in the Dresden-Riesa topic to explain the process and how are all the things related. I always liked driving german freight trains, but only reading how to calculate everything was not easily memorable, in this way I actually wrote everything myself and finally got grasp of all the concepts behind it. Getting all the data took me about a week of poking around with god mode and later TSW4 free roam, and since that, it was multiple weeks of testing by actively playing and cross-checking every train, if the game agrees with my results and the numbers make sense

 

Great work
As someone who appreciates German freight, it's often a headache to calculate this type of value.
Thank you very much, a very useful file.

 

Great work and this is useful on KWG DRA too

 

Regarding steepest descend.

Drove every german route from end(s) to end(s) the last few weeks and collected the gradients as shown in ingame hud. Here are the maximum values that occured:

• SKW 13 Kassel-Würzburg
• DCZ 27 Dresden-Chemnitz
• RRO 26 Rhein-Ruhr Osten
• BRO 8 Bremen-Oldenburg
• HHL 25 Hamburg-Lübeck
• HMA 15 München-Augsburg
• HRR 15 Hauptstrecke Rhein-Ruhr
• MSB 21 Main-Spessart Bahn
• DRA 16 Dresden-Riesa
• RSN 20 Ruhr-Sieg Nord
• SKA 10 Schnellfahrstrecke Köln
• LFR 9 Linke Rheinstrecke: Mainz-Koblenz
• RT 40 Rapid Transit
• NID 16 Niddertalbahn
• VBRG 14 S-Bahn Vorarlberg

Hope that helps

 

One thing that could come in some future versions.

 

Coincidentally, tygerways#2596 and myself are in the process of incorporating exactly this plus a „Wagenliste“ into his calculation tool as well. I would not have thought that there is actually anybody out there who is also interested in this in the first place… obviously I was wrong

 

This is genius. Now I don't have to spend an hour trying to calculate it by paper.

 

Just what I needed. Thank you!

 

Brilliant! Man, what a useful tool!

One oddity, though: it seems that running light on a flat route, even the fast locos (101, 146.2, 182) come out limited to 135 km/h. Surely that can't be right? Or is it because the calculator doen't make provision for R brakes?

 

Excellent!

Do you have numbers for Voralberg, Maintal or Rosenheim?

 

Thanks for the bump. It’s a year old thread and I never saw it to be honest. I don’t know why it’s not pinned yet… Thanks to the author for this useful tool.

 

Wikipedia claims Maintalbahn is 5 ‰ max, Rosenheim-Salzburg 11 ‰. Wikipedia doesn't have data for all the branches of S-Bahn Vorarlberg, but I want to cross-check with https://geovdbn.deutschebahn.com/isr later anyway

 

Yup, the calculator uses only P+E value to generate the timetable.

This tool is not forgotten, by the way, I am working on a new version. Not much will change on the frontend, but I would like to completely rewrite the logic behind it to better support dynamic load level that seems to be present in some newer wagons. Using the "override weight" should then better distribute the (usually additional) load across wagons and have bigger impact on brake percent overall.

 

Shouldn’t it use P (or R) but not the +E values for light locos?

 

Using this to compute light locos was not an intended scenario

 

Those who want to help me fill in all the missing route data, I am using the value shown in the new minimal HUD. To keep consistency in measurement: just drive the full route and watch for maximum descend and maximum ascend (ie. descend in other direction) values. Ignore extremes that are only present for short time and not representative of the whole route (ie. multilevel junctions around Köln or Dresden, as you don't go through them at maximum speed anyways), it should stay at that maximum value for at least few seconds at higher speeds to have any effect on your needed braking distance.

It is important to write down numbers for ascend and descend (descend in each direction) separately, because uphill routes will be very different in each direction.

(These numbers are permilles, I think the HUD shows percents)

 

So, for example, the ramps to the city tunnel on RT are quite steep...up to 4% I think, this values I don't take in account?

 

Correct. The issue is preventing the possibility of a runaway, and being able to stop in time at line speed or close to it; short little elevation changes, especially around low-speed yards, don't factor in. Think rather coming down the Tharandter Rampe. The term used in the US is "ruling grade."

 

going now through all these freight threads and my brain is ready to go nuclear lol... I usually look at the train with "3" camera and together with train length and weight data given by the game I decide between M and U and hope the game gives me pts

dont get me wrong, I would love to drive more realistically, but all these calculations make my head spin just going through them

still kudos for the spreadsheet... might use it from time to time until someone or you comes up with an actual utility ah, sweet passenger runs lol

 

My spreadsheet only asks you to pick a loco and wagons and then hands you all the data, it will not get more accessible than that

Yep. You are basically interested in average descend in rolling 1000 m (braking distance). But as that is almost impossible to calculate unless you plot the whole route with all elevation changes, I just take an educated guess based on how the HUD changes and slightly polish the extremes in that.

It's been years since I drove on RT, but if the ramp has 100 meters we ignore it, if it has 700 meters, we take it into account. For example Hamburg - Lübeck is flat as Hungary, but the multilevel junction at Wandsbek takes you down in 2,5%. But it only has like 300 meters and you go 60 to it, so no need to "ruin" the 0,8% profile of the rest, because it will not have that large effect on your braking distance.

 

IIRC, RL Buchfahrpläne break the run into segments, with different Vmax based on the ruling grade in that segment. If you're taking a freight from Hamburg to Innsbruck, you shouldn't have to cross Lower Saxony at a speed calculated for the Alps!

 

hay I've noticed that calculator c7 should be
=floor((if(C9="P";sum(X20:X34);sum(Z20:Z34))*D9+sum(X38:X50)*D10+sum(AA38:AA50)*D11)/C5*100) instead of =floor((if(C9="P";sum(X20:X34);sum(Z20:Z34))*D9+sum(X38:X50)*D10+sum(AA38:AA50)*D11)/sum(W20:W34;W38:W50;Z38:Z50)*100)
so that it can use the overrided weight value to calculate BrH R/P and PZB mode

same for F7 should be
=floor((sum(Z20:Z34)*G9+sum(X38:X50)*G10+sum(AA38:AA50)*G11)/C5*100) instead of =floor((sum(Z20:Z34)*G9+sum(X38:X50)*G10+sum(AA38:AA50)*G11)/sum(W20:W34;W38:W50;Z38:Z50)*100)
so that the BrH G can be calculated with the overrided weight value

I noticed this issue when drive on vorarlburg int he vectron with service 63235 where originally the calculator gave me PZB mode M and a max speed of 100km/h for R/P timetable witch caused a PZB emergancy stop as the train wouldnt slow down fast enough. After my changes it gave PZB mode U with a max speed of 90km/h tomorrow I will test this as I am now headding to bed

 

Alright update time,

• using the default calculations using a steepest desend % of 11 you get PZB mode M and a max speed of 100km/h this will result in an emegancy stop
• using the default calculations using a steepest desend % of 17 you get PZB mode M and a max speed of 90km/h this will result in being able to slow down just in time
• using the changed calculations using a steepest desend % of 11 you get PZB mode U and a max speed of 90km/h this will result in an emegancy stop
• using the changed calculations using a steepest desend % of 17 you get PZB mode U and a max speed of 80km/h this will result in being able to slow down just in time

Personally I would assume the game calculates accelation, deaccelation as well as inclines and declines bassed on what the games says the weight of the train is and not what the calculator thinks the weight of train is. So, I think it would be a good idea to do calculations bassed on the weight override if there has been an overrided weight put in

 

What level of braking are you using, to outrun the braking curve like that?

 

I was using the what the calculator said loco G first 5 G rest of the consist P I was also putting the brake straight to full application in all 4 tests

 

In the UK we call it the "ruling gradient", just to be different!

 

You are correct! Thank you, I updated the formulas.

Upstream spreadsheet was now upgraded to version 1.1. Includes updated formulas for correct weight override and data for BR 111*.
Simply delete your copy, visit the upstream spreadsheet link and do File - Make a copy again.

* BR111 data are not tested as I don't have the addon yet, I used data written on the loco, basically the same as with 110, just with increased speed – I don't know if that is correct or if that is the behavior in the game. But it's not really a freight loco anyway, so eh.

Yeah, the brake distance should not be fitting exactly for centimeters, you should still have I think 10% reserve or something? Usually I am not really hugging the permitted speed unless I know I have green wave, and brake level 1-2 is often enough to easily make the 1000 Hz check. For 500 Hz maybe level 4, but I don't really use full brake at all.

To all drivers, do not forget that almost all locos are equipped with dynamic brake that can be unlinked from air brake. It's useful thing for freights, as you can go into full dynamic braking (and back) very quickly without risking the two minute release time of air!

 

I love this calculator. Thanks!

Permille grades on BSR:
Rosen - Salzb 11
Salzb - Rosen 11

 

Upstream spreadsheet was upgraded to version 1.2. Link stays the same.

I finally collected all the necessary data for all german and austrian routes in TSW (including Semmeringbahn), so I could make the route switch simpler to use. Now you can simply pick the route and direction from the select box, and appropriate downslope speed limit will be applied automatically.



If you found the prefilled slope (visible in timetable) not to your liking or you needed some route that is not provided in the list, override field is present as usual.



This selector makes it much faster in everyday use, as you no longer need to cross-reference other places to find the correct number.

You can safely delete your own old copy of the document from your Google Drive. Then, go to the upstream spreadsheet, and click on File - Make a copy to create your own editable copy once again, so you don't conflict with other users.

 

Why was this excellent and useful thread unpinned? Mods? This one should be permanently affixed to the top of the subforum.

 

Probably because the place became too cluttered. A personal user-curated threads index (with questionable importance of some entries) which needed permanent updating, what people do in Freeroam (not really interesting for everyone) and such. I see they want the forum structure to be more clean.

It's what it is - a fantastic but content-specific guide that belongs to the section that was created for it, and where all the other fine in-depth guides are happily gathering without wanting "special treatment" - in the Guides subforum.

Noir apparently did not want it to be there though, fearing it would not be seen. But if I'm looking for a guide, I go to "Guides". If people can't read or use a forum, it's their problem.

DTG don't want it on the opening page of their game (as it is not a general thing) - so the only option left was to unpin it.

Another issue is people tend to spam the General Discussion with all sorts of things unfortunately, many bug reports are not seen because they're in the wrong place or have meaningless thread titles. Mods have to move stuff to the Troubleshooting section manually.

 

Randomly got onto RSN with the 187. saw it wasn't in the calculator. was that loco overlooked or is there a problem with it why it can't be in there?

 

Whilst this brilliant tool works superbly for me in Google Docs, I have an issue when downloaded to Excel, which is I don't get a Max Allowed Speed showing:

(I'm using the defaults unaltered, so this should be showing 75kmh in R/P, 65kmh in G.)
Working through the formulae, I am getting Invalid Name Errors in four cells on the Calculator tab:


Do others get this too? Is there an easy way of resolving it, or is it just one of those things?!

 

As the error is in the route speed calculation, excel probably does not support the IFS function. That's how this table is encoded. I don't have a solution for you, I don't work with excel. You can just use it natively in Google Drive.

 

yeah I got the same issue porting it to excel. the easiest way to resolve it is to bookmark it and use it in your browser in google drive. that's the quickest and easiest for me

 

Thanks for the reply. I had another delve into the formulae and think I've solved my issue.

The errors were occuring in Excel because it didn't like the formuale on the Calculator tab being lower-case. Doing a case-sensitive Find+Replace to change all the instances of ifs to IFS sorted everything out

 

Just a mild touch, there is a -60% sale on the old red 363 addon and as many recently praised this very old DLC, I decided to finally grab it. With it come rarely used Uacns wagons, so I completed the wagon data for them as well. This makes the calculator finally complete with all the current rolling stock implemented.

If you own this DLC, you may want to upgrade to version 1.2.1 of my spreadsheet, but if you don't own it, you don't need to bother, as there is nothing new otherwise.

 

Just started playing TSW and coming from flight sim I love these kind of tools, they really add to the immersion knowing everything is set like it should, massive thanks!

 

So this is a fun trip. uphill I'll try to keep at 80 but wow DTG put some heavy trains in the system

Edit: it's the DGS 47480 at 7 AM from Salzburg

Second edit: Wow I'm tired and read the Brake Percent as max speed.

 

If you're departing from Salzburg, you've got the 'Route and direction' the wrong way around. Might not make a difference here, but it can sometimes.

 

ah. wasn't aware there is a salzburg to rosenheim one.

 

So I was wondering about these rare services. sadly not seen ingame anymore on any route. a loco haul with a 185 taking five 143's and two 185's somewhere. of course all panto's but the towing loco should be down, suppose the game can't do that for a service start.

I wonder how to calculate speed and PZB for those. Ingame it was set to PZB U. but my logic says take the one loco and full weight and length of the consist as override and pick a container wagon empty to get the higher speed limit but since carrying unpowered loco you are freight so PZB M or U? or do you fill in all the loco's and put PZB on O?

 

When you pull locos it basically follows the exact same rules that define this spreadsheet. The way you have to set up the loco that you pull is dependent on type and varies a lot. In reality only people that have a rating for this type of loco are allowed to do this. Modern locos, for example, don’t have a mechanical possibility to change the brake type. If the battery is switched off you need to know what it is doing.

In case of 5 143s you would be way below 800t, hence, you would set all locos to brake type „P“. You now calculate BrH (rough estimate: braked weight 515, weight 495) = 104. As per definition this will be PZB mode „M“. As the 143 limits this consist to 120kph anyway, this will be your max speed.

 

There seems to be a variance between the way the spreadsheet calculates freight car weights, and the way the game does. I have to use the override box just about every time, because the in-game weight is heavier than the spreadsheet output.