Stations & other LTN based designs

[Optera]

Heh. The previous signals still remain, though, so it hasn't actually broken anything past.

While adding the any vehicle type signals the naming schema for the auto generated position signals annoyed me, it used to be "LTN-<vehicle_name>" while all other signals are "ltn-<descriptive_name>".
So with 1.10.13 that naming schema was changed to "ltn-position-<vehicle_name>".

Sadly migration scripts don't support regex for migrating auto generated signals.
The only signals still working after upgrading to 1.10.13 are for base vehicles where I knew the exact names and could write a migration script.
All position signals for modded rolling stock vanish and have to be set again, including in blueprints.

[slippycheeze]

Heh. The previous signals still remain, though, so it hasn't actually broken anything past.

While adding the any vehicle type signals the naming schema for the auto generated position signals annoyed me, it used to be "LTN-<vehicle_name>" while all other signals are "ltn-<descriptive_name>".
So with 1.10.13 that naming schema was changed to "ltn-position-<vehicle_name>".

Sadly migration scripts don't support regex for migrating auto generated signals.
The only signals still working after upgrading to 1.10.13 are for base vehicles where I knew the exact names and could write a migration script.
All position signals for modded rolling stock vanish and have to be set again, including in blueprints.

Ah! Thank you, and I'm sorry if I missed that in the changelog et al. I'll file that away in my mental map of answers to deploy on discord, when people ask the same question.

Also, since this'll notify you, thank you again for LTN, and the rest of your mods. I very much appreciate what they bring to the game, for me.

[csduff]

Heh. The previous signals still remain, though, so it hasn't actually broken anything past.

Didn't break anything. Just been using LTN for months now, and when I finally got off my lazy ass around to making a refueling system using a dozen combinators, it's all just simplified.

Don't get me wrong, I love the mod and love the progress.

[NiteAngyl]

A provider station allowing all items from a logistic network being requested over long distances via LTN.

0eNrtXWuO2zYQvkqhn4WVkhSfCzQnaNKi6b8iMLQ2d1eoLbmSvO0i8AF6kF6sJylpef2gRImkHxvX/ZOFbOsTOd/McDjDUb5E97OlXJRZXkd3X6JsUuRVdPfrl6jKHvN0pj+rXxYyuouyWs6jUZSnc31VptksWo2iLJ/KP6M7uBoN31LcF4uirPduQ6vPo0jmdVZnsnns+uJlnC/n97JUuO27R9GiqNQNRa6fpEBiOope9B+Fq4Zfl8VsfC+f0uesKPVPJlk5WWb1eF5M5bh4GBcLWabN/aC5JZcTfV3pX0P9Tymn+6PJ1BUTq8+rlZ6mMUS0HWJaZvXTXNbZJJ4U8/ssT2s1gvZ4UTNe/I6ox0+zsnn6Gqlr/DvYsfp6mm2H+pCVVT1uSf05K+ul+mQ7ruYXsUwnT1r2ldQwGquqU017rKS8J5ToW3VrsawXS2/wlUWej6WUuSlRnoy23OhrpQzqdmSRf+vHo4Ov8eHX0EJWsh33VE6yqSydmEocmdpgnoamHT9AX8wXabke5V30PpgfDbR4UeNb5vX4oSzm4yxXMNHdQzqr5MrdGiBvy9vOHWoT3UUO9iMHvCMbQzokB986OcjHrpCNDbId5ax4zKq1V3uSVR2nagTPMl6UxbMWaJsZ+EqMtpsOZHo8Mu5GZjvJ1unktzjLK1nWXUhof4yHtt2By/1xsQuucMbFVlzagQuBP3DiBLxbkOWfi1JWVVyXaV7plTm+l7OO5TkZ4AyicEiLgsEkWMPI0Gjx8dC2URM//ycaNNji7QL+bxNDON/3oXFve37yn7/+Pr2nrMul1ypG+4MKyAaCDq9V0Py1icYdYxhIvSNO1qgKclSVs0ec4DDg/PHnk0ecXWwLn3VRW6MTGyyUDXhhNj6FGO5HfdM+V98FUPXBj6cBOyHoLDxyP+9L3tD7njb6/HjC0DMxhT3qNUE4QG2/QzXds5Va4W2i5H+H6bvJMxdTGxtoF5vO5TRbzmM5U4MpFSWLYiY7yNiGe7A7cELQiHYfspmKdXuC3hi+s9kv7k8ibekNYfdZli/1U5Y/9hvx9+uv7Vkr6LEVNJ0nojZakLcQ0a0IEfYnm2w7aBS+DdkpKLLofPg+ZMebDZv4qgK4FU2ghiYkwMY99TYncKvmhIhNiCxYycGQjvNw+xnEFr7c34onVeZi2E9iS9QDXxnezJJOTPOxVaYSGKzjQ0tEgo7P4dqgE1/m8a0wL0zr4TbmcSunuswVG4+l2uFNh7Kqza5nM/9mlxF1PYR4BvJDcXwSXhjAQ0rFfJWK3opL5mZwawtnE+4rQ3IrMkxMw2Q2GYpgFacDKo7B8ZUJG7T3BpvfCPO4VRKwxbLYe3/NbsV6mClDW+oIh2+o+ZCKh++n2RC093Za3Ir1WImmnqEFBAOxBQ7fSoohfrl3enlTugUXTi9/ONvxL88KD/FKLBPH40PCN7G81RrQzSwB3szyLd5XcbRPH644tnrnXTcgsL/KwxMf+k20VjnQltEm0K+iR72ou53jZNoKPOgCbtZKUFC9FVx/vfXTCQ+w8AFL4ycpoJLE+TjZtnBhc6nYHQoNQFlPKJby96X6219YaTTJ88C4R3BDzFoBtdUKCA2ZCLrYRMyEo7OJux/HHFqI3Q9gxkNQIkDY4FKypmaCnGKLcCkIURrwdkpjy1JT6H241kItRc5IA16KJgHCvZhBKp0wlMSWbqI4YB6X85BmPpvaqkGUHJHPBvvp7Gad7XoE9T4ybVMeFiB0fDHlMXOVzLbqU3enSwck4n7OnfQjsRCvRy8lW2bGX8yWDWQwYB7kYjpiZuSYLXRh7i6XDzDrHmOyAaQQp8cvpiPmwshszpuFxLfsYvMwIxVmi1SYu2cVA8yGeFZxMYlYBcAP2mbVkNMsjzf7xY4dyusCjFxaiFhHPFuX6wfUxSJu1rue1BcclMoxSeU0d0kpv9dfLyupHjUrymqzDXbfBVvkzkGvaDaV7R7ZuB7/bRL6lr7plmh++OVjPCuUAAqdeG4ks9RiEQPt1J1Ik7R8LOI/0kc1vh0U3WuxHu7Mzsoij4tyfyyIALDFSNZZBEc2uGO3J4d97HTS0pDiREkp02mTWVljNiqlokB9MdYPWEiPLohfolW4ANbqOdK+b5OE7Qo/uX8b+euShVb/2b7xLun2px85cEg2d6qjZ2s425P+mzUfw0s01fnmi9sOYHREPpm3a0Wj7vcJIEeicUhZ4I37fL5KorsKc15EdvNDQvhBb1u2QV+lIeKBhlOvF3BwWwKP09CGHvQaezrNxvp85t1Avq0CQEe1eRWTzNP7mRxPs0r/3VCyk+I66nhKm1WyVuOsXgOPvWB6/XnzU73h8NpjcPO0nrCGV9xfKuhapcIc+gg7hSSCm57QmXeT3CwfcdJvzQI0ceb+ZuR1O9ER6X/ueh0FCG6kO7s4zFyxSI6frv/LLMCVWohoaYvt1ITwfx1HDP4rfkPYHIVIgtu5zm0ZwtzxCHy8ZeDQDsCzz9YsXwh2/GyJt8pf60opzFVF2KIqQb2Fcq1BlTDLNsJWthEstCvt7HZh1oQFP94ueGgf49lnazpuCEDrE3S8AIS3DWCbDdCv3AZIS362YjwEIPiNXeetNgQdYTclfyjWLsEb3BwreW6VMwxssLMcVFcmEdpaeXaD5i31I0ebr1Jhb0Ul12q/oiVAbNUr7C0WeqVi0V7MlAuzyoWENjie2zz0YmZOg57APmhoV+z5J9xej8QJJuyfKmRXq/m4JUH7SuOfLORXK5dW7AitLw4DIrRp8/wGQlvTOD4BCCEI7fQ9/4RbKxxMTjBh/xyguFrNt9r/3jt4PfstbaEmTEKbXs+uSCexk/0EWZlmj091vP4vEToy5E2BEg8f5YKQuKNid1TqjorcUZk7KnBH5c6o3B1UOIO6c4WAM6g7VQdvMuwHdWfq4M1+vaDuPKHEFdNjnM425SFQZ4vyYN7ZntxVFDlbk4cxIWdj8rB75GxMHi5q721f6xOyw2djidPb6hMY3BJObK+WR6GnHayISWCaxwqIQ1fzNeLnUXM89G7vvwYaRbNURUP6zOnmrOY3P21emPDNp83BxlH0rJbTNSpLAGQEYYTwavUvtvXUYw==

Copy blueprint
2019-06-10 22_44_44-Clipboard.png

Why so complicated?
* Requester chests need to be cleaned out to avoid residual items clogging the station.
* While still cleaning residuals, they must not be loaded into an arriving train.
* Disabling the station (e.g. via red signal) while cleaning residuals would reduce efficiency.
* Stack Inserters only allow one type of item as a filter, this should always be an item that is still missing in the train, and already present at the station.
* Requester chests do not allow to read their contents when setting the filter.

Mechanisms:
* 4 Active Provider Chests: Removes everything that has been requested too much or cannot be loaded efficiently at the moment.
* 12 Active Provider Chests: Removes everything that has been requested too much.
* 12 Filter Stack Inserters: Clean out everything that is present and not needed anymore.
* 12 Requester Chests: Request items via bots.
* 12 Stack Inserters: Unpack the requester chests to allow the circuit to see what's currently inside.
* 12 Belts: Return their contents, allows to decide what should be loaded right now.
* 1 Belt in the middle: Allows the belts to empty while the majority of their contents is not to be loaded into the train (residuals or oversupply) -- or when there is no train
* 12 Filter Stack Inserters: Make sure nothing unintended get's into the train.

Combinators:
* 1x (*) at bottom left: Calculates what's missing in the train
* 3x (>=) at bottom right: Decides what to load right now -- it needs to be missing in the train, and it should be one of the items that are present on the belt the most
* 1x (/), 1x (>) at left: Divides the request by the number of chests, but makes sure at least one item per chest instead of none at all are requested, to avoid inability to load small amounts.
* 2x (|), 2x (>), 1x (/), 1x (>=), 1x (*) at left top: Returns only items on the belt whose quantity is above the average quantity per item. OR-Diodes are required for timing.
* 1x (*), 2x (>) at the top: Sets a filter to all items present on the belt, that are not allowed to be loaded, to clean them out of the boxes fast and keep them away from the belt (especially while loading). May do nothing while the majority of the belt is okay, and the bad items are only residuals on the belt -- with a second above average filter we could only improve our guess of the requester chests contents, but it will still be only a guess.
* Roboport: Tells the station which items can be provided. You might want to add a constant combinator and specify a lower request size minimum, if you want to load costly items (e.g. less than a thousand roboports)

EDIT: Blueprint was cropped, should be functional now.

PS:

Video

Hello phi1010,

The blueprint you've created is exactly what I've been looking for: a way to accurately request multiple items from my mall anywhere in my factory. However... it doesn't work for me like in the video you've posted.
I've connected a single constant combinator to the stop with the right configurations. I've placed a couple of passive provider chests with twice the requested amount of items in the logistic perimeter.
I can see on the Roboport that the signal switches on when I place items in the passive provider chest, but when a train arrives to pick up its order this provider station does not load any requested items.

Is there anything I may have overlooked? Thank you in advance.

[slippycheeze]

The blueprint you've created is exactly what I've been looking for: a way to accurately request multiple items from my mall anywhere in my factory. However... it doesn't work for me like in the video you've posted.
I've connected a single constant combinator to the stop with the right configurations. I've placed a couple of passive provider chests with twice the requested amount of items in the logistic perimeter.
I can see on the Roboport that the signal switches on when I place items in the passive provider chest, but when a train arrives to pick up its order this provider station does not load any requested items.

Is there anything I may have overlooked? Thank you in advance.

As Operta noted above, with the introduction of the unified wagon/locomotive presence signals, modded wagon/locomotive signals changed name, and could not be migrated. If the station is dependent on those signals, that might mess things up. I have not inspected it to determine if this is the case.

PS: I solved the residuals / overfetch problem by using an unfiltered inserter from requester chest to active providers, and disabling them via circuit when a train was present at the station. (I asked for the unified signals way back to simplify this, in fact.) Never found a problem with that: nothing got so much overload that I filled all the slots of the chest and blocked myself loading *something* the train wanted into it.

I finally just went with the Logistic Cargo Wagon, though, which uses scripted magic to make the wagon request and provide items like a chest based on the LTN collection / delivery status. Scripted, so not going to be the lowest UPS option, but on the other hand, only does anything during train collection or delivery, and event triggered, so ...

[sadris]

Basic Provider & Requester

This stop can supply/request any number of items.
To prevent timing issues (stop output is some ticks faster than the yellow combinator) it's waiting until train decoding signals are available before sending unloading signals.

2017-05-23-09-44-27-3173806.jpg

Pro:
- very versatile
- fast loading/unloading

Con:
- sorting multiple items from steel chests (I'm using merging chests and loaders)
- inserters will lock up if loading more than 40 items
- requires some tuning between stack size bonus and locked slots/wagon to prevent stuck inserters.

This doesn't seem to work. There isn't any combinator signal to define that the stop is either a provider nor a requester.

What are all those large numbers in the existing combinator for?

[slippycheeze]

What are all those large numbers in the existing combinator for?

Don't know, but they are usually either for filtering via integer rollover, or something similar. Unless they define request/provide sizes, in which case they are to make the station "not do that" if it accidentally advertises availability because, eg, transport delays or combinator math or whatever makes a value go negative when it should be positive, or vice-versa. (Also solved by a < or > filter, but *shrug*)

[phi1010]

A provider station allowing all items from a logistic network being requested over long distances via LTN.

The blueprint you've created is exactly what I've been looking for: a way to accurately request multiple items from my mall anywhere in my factory. However... it doesn't work for me like in the video you've posted.

Sorry, took a while -- apparently one wire from the constant LTN stop combinator to the output of the negating arithmetic combinator right next to it got lost at some point, so it simply does nothing, because it does not notice the request. The train signals are not used at any point, it only relies on the output of actual contents from the stop and requested contents from the combinator.

Patch to apply to existing station (I will update the blueprint later):

0eNqdltuOmzAQhl8l8mUFKw5JNpuLPkFVrdS9q1bIgQmMBDYyQ9oo4t1rm00ghQSSmwjH+JvDP+PhxHZ5DaVCQWx7YhhLUbHt7xOrMBU8N//RsQS2ZUhQMIcJXpiV4pizxmEoEvjLtn7jTB7JZSwLSXiA3sGg+XQYCEJCaA3bxTESdbEDpcmX8wUkWBcu5BCTwtgtZQ6aXspKH5bC2NVA13tZOeyoH8KXVWPc+g8YXMXgxhlH4X65PqT5Z5p+0F4nqLR1ux+MsMNesClWpL0kZfkkS1fWVNZ0z+WBkbXDtCKkZB7tIOMHlMoc2mNOoG4IdUBFtQ3m7AsJ92zS5eLoXisRy9qI70+IOY2NuUql+4en2vOOu+5p/Th3wtXwCeSUm8sZtYxKg6TqOxWGQcdYNZ92R4hWycqQfPOjIOmXOSatyKjiGskudUs0Y4W7vFtcKCZqK7C1NVZNZ+N6L7mc3aOqKJpObfuG0Z8yFGmbEFERNznxzKIoueJkTLHvZruuQJvKpalfUjWMxbq6F+swSu8rxFnNo4An0V7JIrLI1gmH2UVk+CUk8wP/YM3TSvtGaYfpZLUOMzaSivXFIldIWQEmGTqrOxQ2q4NkXK6s4IbeHaeTvHpCc+BxZgStwGCiTnZXN6gsQZ3D+qaPtpffo/AHctu2XHBjN7zRVK+dXVMAaUauHW3DRgpsUr3pIbCZi/TmEt/mEmf76HvXU3By/g0n0xj16WFt8OZLwN6y2943icNyvgNdMOzHx8/Fu5IHTEAtfrUts3jnFGe+fuugx6Hlvoaev3nzvOXGa5p/EwEAug==

Copy blueprint

[Humpfry]

In my playthru the constant combinator on the LTN train stop is not showing the requested item that is supposed to be delivered, leading to unwanted items being unloaded on my train stop. I am running the latest version of LTN 1.11.0 and Factorio version 0.17.69

I checked the demo map and the same situation is happening there too.

Factorio 0.17.69 2019-09-21 3_59_55 PM.png (3.62 MiB) Viewed 11703 times

The arithmetic combinator only shows the train car setup for the input and missing the requested cargo information (the output of the LTN train stop combinator). As you can see I have not changed the arithmetic combinator, the input is the train stop combinator and the train stop itself is connected to the output of the arithmetic combinator then to the filter inserters. The end result is the output of the train contents to the filter inserters and unloading all the train contents, the requested items AND unwanted items (if there is residue from a previous dispatch) - which is why the arithmetic combinator is SUPPOSE to stop the residue being dropped off.

You might as well not use the arithmetic combinator and connect the read train stop cargo directly to the filter inserters to unload. It is useless in helping stop unwanted items being dropped off. Obviously you can stop the train at the depot (by turning off the depot signal when there is left over cargo on the train).

[Optera]

You might as well not use the arithmetic combinator and connect the read train stop cargo directly to the filter inserters to unload. It is useless in helping stop unwanted items being dropped off. Obviously you can stop the train at the depot (by turning off the depot signal when there is left over cargo on the train).

Have you even tried it before writing this?
On a requester the stop combinator outputs items that should NOT be unloaded. Together with the arithmetic combinator it will prevent filter inserters from unloading those.

[Optera] Merged into design thread

[ztn]

i want to use same stations for receive and send items - so i want to check why this train come to station. what is the easy way to do it? the only difference is Logistic Train Stop Output have additional signals if train come to take goods. but it's hard for me to filter out these signals from alongside signals about train configuration. may be i miss something and there is another easy way to understand that i need load or unload train?

[xfir01]

Have you seen the Provider & Requester in the sample station thread?

viewtopic.php?f=214&t=51073#p297648

[ztn]

yes i see it. 2nd post connected with my question but author give exactly 0 explanation of these set of combinators half of that combitanors use overflow shenanigans that impossible to understand if you don't know exactly why you do this and how it works. i want simple answer for my simple question - i don't need solutions how to make "provider+requester" station in "right" way.

[Optera]

The simple answer: Learn how provider, requester and 1 combinator binary decoder work.
This is nothing more than all of those merged together.

merged into design thread

[torne]

i want to use same stations for receive and send items - so i want to check why this train come to station. what is the easy way to do it? the only difference is Logistic Train Stop Output have additional signals if train come to take goods. but it's hard for me to filter out these signals from alongside signals about train configuration. may be i miss something and there is another easy way to understand that i need load or unload train?

A couple of things that might help if you want to build your own design instead of using the one mentioned:

1) If your LTN setup makes sure that trains never leave the depot unless they are empty (which is generally a good idea), then any train which has any items on it when it arrives is to be unloaded, and any train that's empty when it arrives is to be loaded. LTN-generated routes are always intended to load an empty train at one station and then fully unload the train at another station; the same train is never used for loading and unloading at once.

2) You don't necessarily need to even decide whether you are loading or unloading the train. The most basic version of this is pretty simple and doesn't require that you actually decide whether to load or unload the train, though it isn't always good:

- The LTN output tells you what items should be on the train, plus some extra signals about the train configuration.
- The train stop itself can tell you what is currently on the train.
- So: multiply the current contents of the train by -1 with an arithmetic combinator, and then connect the LTN output to the output of that combinator to add the signals together.
- This gives you positive numbers for everything that must be loaded onto the train, and negative numbers for everything that must be removed from the train.
- Connect that wire to the filter inserters you use to load the train, then multiply it by -1 again and connect *that* to the filter inserters you use to unload the train. Filter inserters in set filter mode ignore negative amounts, so that's "enough".

The issue with doing it that way is that if the inserters have a stack size greater than one, then they can get into a state where they load slightly too many of an item, then unload too many, then load too many, then unload too many, etc. There's a number of options to prevent this (including, but not limited to, just setting the inserter stack size to 1) with different tradeoffs in combinator complexity, speed, handling multi-item stations vs single-item stations, etc, many of which have been discussed in this subforum.

This basic version just ignores the train configuration signals, which is fine if all the trains that come to any given station are the same configuration. It's generally fine even when they're not - the one exception is when the station is capable of loading something that can be used as locomotive fuel, or unloading something that's left over from burning fuel, as in those cases you have to avoid accidentally interacting with locomotive fuel slots instead of the cargo.

[Zorku]

You might as well not use the arithmetic combinator and connect the read train stop cargo directly to the filter inserters to unload. It is useless in helping stop unwanted items being dropped off. Obviously you can stop the train at the depot (by turning off the depot signal when there is left over cargo on the train).

Have you even tried it before writing this?
On a requester the stop combinator outputs items that should NOT be unloaded. Together with the arithmetic combinator it will prevent filter inserters from unloading those.

[Optera] Merged into design thread

I was quite confused about this same issue, and I'm still confused about the part where it seems to be broken on the demo map, unless that's somehow meant to be an example of how to set up a station incorrectly?

Your nasty reaction did give me the insight to try my little bug test efforts in a different way, and I have a little bit better understanding of what conditions actually cause the LTN to change what signals will output at my drop off stations. It seemed difficult to catch the bad deliveries that were gumming up my factory when I was under the assumption that it was the wires that weren't working, rather than when and where I was putting dummy items into the cargo.

With the kind of "idiot that doesn't understand how these signals work" viewpoint that I'm much more familiar with, I'm gonna try and walk through this other post.

yes i see it. 2nd post connected with my question but author give exactly 0 explanation of these set of combinators half of that combitanors use overflow shenanigans that impossible to understand if you don't know exactly why you do this and how it works. i want simple answer for my simple question - i don't need solutions how to make "provider+requester" station in "right" way.

This is doing a few things that I bet you can follow, but for some reason when I try to paste in the blueprint string it's missing wires and even a few combinators. Dunno why that happens, but I fixed it by referencing the pic of Logistic Provider & Requester for LTN 1.10.13, since it has the same 5 combinators and those draft images are way more crisp than old school screen shops.

So, the first thing that's throwing you for a loop is exactly what you think it is. The 'any length depot' blueprint shows this thing simply enough. You've got a decider combinator that waits until the train is empty and then tells the station it's a depot, and then our two offending combinators are the constant combinator with all our encoding numbers and the arithmetic combinator that multiplies them all by the encoded position of (engines/wagons.) If you want your station to know which segments are engines/wagons then use this. If you only use one size of train then ditch this.

So, on to the blueprint you were actually looking at: The constant combinator on the left side of the power pole and the first arithmetic combinator are "overflow shenanigans" and that all runs through 2 more combinators now. Instead of sending that signal right to the inserters, it goes into a decider that passes each signal along as 1, if it was less that zero. So, negative numbers on those symbol-numbers are all 1s now. Since the output sometimes contains signals like "Load 7000 green circuits into me" it's best if we not multiply those by encoded numbers and then pass them to the inserters. I guess this was the most elegant way to deal with that.

Our 2nd decider combinator checks if anything is more than 0 to pass ALL values through, and accepts those encoded position numbers as well as the contents of the train. Since we already filtered out all of the regular things that come out of LTN output with that less than zero check, this should just trigger off of those overflow values where we've actually got wagons, so I guess this is a safeguard against trains that don't contain cargo wagons.

As far as you're concerned, so far this is a great deal of sound and fury, signifying nothing, but it used to be that if you rolled up in a short train you'd take all the fuel out of some of your engines, and then maybe the train would be stuck...

Now, finally, we're getting to those other two arithmetic combinators. The one closer to the LTN station accepts LTN output and multiplies it by -2. -2!? But everything was -1 so far! Why would it be different now!? Well, this is why I walked through all that encoded position stuff. It passed all the LTN outputs through, so if we added everything*1 to everything*-1 it would all be zero. We just want that -1 value so that we can stop the inserters from moving items they aren't supposed to, and we have to multiply by -2 in order to get it. As the basic blueprint notes, the combinator delays the signal a bit, so inserters don't filter out the crap if you hook them up directly; you need to slow down the train contents signal by also running it through a combinator. Could be anything, but in this case it's a check to make sure there are wagons.

And then the far arithmetic combinator. We dealt with requests, so this is our provider logic. We've got the familiar *-1 behavior here, where the LTN output tells your stop how many items were requested, and our *-1 reduces that signal to 0 when the train actually has that many items on board. Technically you could add another combinator to slow down the LTN output signal, but why would your train arrive with all the cargo it requested on the first tick?

And that's all of the pieces. I'm missing a tiny sliver of why it's done like this, but if you care about the requester and provider behavior then Requester v2 for LTN 1.10.13 and Provider show you what those three combinators do, and the little string of 5 combinators cuts out the redundant check for "is anything a cargo wagon?" because you get the same boolean "yup" when you're doing overflow positions.

And just in case that was hard to follow:

so i want to check why this train come to station. what is the easy way to do it?

The LTN output and the contents of the train are the two pieces of data that you put together to figure out what the train is doing at this station. LTN output always gives those encoded position values, but as for the items, it says what is in the cargo condition for the stop it is at, as well as what was already on the train (other than what was requested.)

If you subtract the LTN output signal from the station signal then unexpected items will be 0, and the requested items will give you a positive number until the train is empty.
If you subtract the station signal from the LTN output signal then items meant for pickup will be positive until the train contains this many items.

So positive or negative numbers tell you if the train arrived for a request or provide order, based on which way you connect the wires to the arithmetic combinator. If your station is configured for both provide and request orders then you could also check based on which arithmetic combinator provides positive values.

Do you need to know why the train is arriving for purposes other than controlling which set of inserters activates?

e: Seems I wasn't even right about some of it. Oh well, the new design is much easier to walk through anyway.

[Optera]

Updated Basic Provider and Requester blueprint viewtopic.php?f=214&t=51073&p=297648#p297648
Removed unused position decoding and overload trickery required for for logistics version.

Updated Demo Map to use more recent designs.

[mrvn]

i want to use same stations for receive and send items - so i want to check why this train come to station. what is the easy way to do it? the only difference is Logistic Train Stop Output have additional signals if train come to take goods. but it's hard for me to filter out these signals from alongside signals about train configuration. may be i miss something and there is another easy way to understand that i need load or unload train?

The yellow constant combinator shows two things:

1) the train configuration
2) the items that should be on the train

For a provider stations that means items you have to load. For a requester stations that means items not to unload.

So program your inserters to load missing items and unload excess items and make it count perfect or you end up with 6 items loaded over the count and then 12 items added /removed in a ping-pong.

[Cadde]

I've been doodling a bit with a "perfect" provider that would NEVER overfill a cargo wagon and thus eliminate the "stuck inserter" issue once and for all.

Before you go "uuhh locked slots per wagon" there's a number of problems with that.

1. I am using bob's inserters and i am "cheating" with them picking up like this:

This means they load wagons really fast.
2. With bobs inserters i can have 24 inserters per cargo wagon. This gives me around 288 items in 12 ticks (and that's 12 ticks because of my synchronizing design) which means 1440 item's per second transferred from chest to wagon.
3. Stack size matters... For the sake of argument, let's say my train wants 1100 items of coal AND 1200 items of stone. There's 40 slots in a wagon, one cycle of the inserters loads 288 items so 4 cycles will load 1152 items of coal... 52 too many.
And then it will load 1440 items of stone, 240 too many! Overall, i would have to have 6 locked slots per wagon which is 15% loss in capacity. I would be better off nerfing my loading routine.

At which point you may go "so don't use so many inserters / set their stack size to 1-2"

4. I am looking for maximum throughput in a single station that is to be served by several trains of different lengths. With different stack sizes of cargo and with mixed cargo possibly being loaded onto the train. In other words, i will NOT nerf anything in any way or even accept "locked slots per wagon".
5. Because it's mixed cargo, most "simple" designs simply doesn't work. That or i simply can't imagine a way to do it simply. Circuit network madness ahoy!

---------------------------------------------------

SO!



Imagine for a moment that the merged chests in the center is the train wagon. This is after all my 4th or 5th attempt at getting this one right. At this point i went "/editor" and checked the circuits in tick step to ensure everything was working as i expected it to. So it's not actually a station yet.
I am merely showing off the crazy stuff one has to go through to meet the above demands.

Along the "dirt" path on the left side at the far bottom is two constants and a medium pole. That is the "LTN train stop", Thus i can change the values in it easier than changing a trains orders.

The combinators that snake about above that is dedicated to ensuring the "wagon" isn't loaded with more items than requested.
One part clock sending a pulse every 12 ticks. One part inversion X * -1 to count down the loaded items from the requested. One part wagon balancing which means if you request 500 items of something using a train that has 2 wagons, each wagon will get 250 items of that request.

NOTE: All of this is of course assuming the inputs (warehouses or logistics requester chests which is what i intend to use either side the loading platform) have enough items, otherwise other platforms will load whatever is missing into whatever wagons they can.

On the right side of the dirt sits another set of combinators which filters signals (removes position of loco/wagons signals etc), counts the number of cargo wagons (for balanced wagon loading) and filters the remaining request signals so only ONE is active at any given time.
The latter part is the part i am not so happy about at the moment. Perhaps i should just refire my old "Signal splitter combinator" mod which would simplify matters something immense.
Either way, it's a bunch of circuit network voodoo that took me quite a lot of thinking to come up with.

The way it works is i multiply each "possible" cargo with a constant value like so...

steel * <0> = <Info>
iron gear * <1> = <Info>
iron pipe * <2> = <Info>
firearms magazine * <3> = <Info>
etc etc

And the signals 0-9A-V are assigned 2^N values such as 1, 2, 4, 8, 16, 32 etc... Thus the <Info> signal is a binary encoded selector value that the next column of arithmetic combinators deals with by doing...

<Info> AND 1 = <Info>
<Info> AND 3 = <Info>
<Info> AND 5 = <Info>
<Info> AND 7 = <Info>
<Info> AND 15 = <Info>
<Info> AND 31 = <Info>
<Info> AND 63 = <Info>
etc etc

So say the train requests steel and magazines. Info would equal 1 + 8 = 9.
The next column of decider combinators then picks a unique cargo by doing...

<Info> == 1 = steel
<Info> == 2 = iron gear
<Info> == 4 = iron pipe
<Info> == 8 = firearms magazine
<Info> == 16 = ...
<Info> == 32 = ...
etc etc

On the output of that column is ONLY ONE of the possible cargoes. And that feeds into the combinators on the left of the track.
The final column of combinators just transform the cargo into an <S> signal which i use to limit stack size on the inserters, which i will explain next.

So, we are requesting 451 units of steel plate. How do we ensure that it loads only that many?
Well... All the inserters are wired up to the circuit network on their own "channels" from the arithmetic combinators on the sides of the platform.
Each and every one of these take...

EACH - <number> = EACH

So the inserters get the cargo (steel) and the virtual signal <S> (as well as some garbage like <C> and <W> because i couldn't be arsed to filter those) which set their filter and stack size respectively.

The numbers i used in the combinators, which i alternated from left to right, are...

0 <left side>
12 <right side>
24 <left side>
36 <right side>
48 ...
60 ...
72
84
etc etc

Obviously i've maxed the inserter capacity research so each inserter can move 12 items tops.
What this means is, if the request is for say 23 items then an inserter on the left side will pick up 12 items and another inserter on the right side will pick 11 items. Request satisfied.
Or if the request is for 1100 items...

1) All 24 inserters will move 12 items each for a total of 288 items... 812 items remain to move.
2) All 24 inserters will move 12 items each for a total of 288 items... 524 items remain to move.
3) All 24 inserters will move 12 items each for a total of 288 items... 236 items remain to move.
4) 19 inserters will move 12 items each. And ONE inserter will move 8 items for a total of 236 items this round.
...
5) PROFIT!


If you wanna fiddle with it yourself then here you go!
Mods: bobinserters_0.17.10, WideChests_2.2.2, LogisticTrainNetwork_1.11.6, OpteraLib_0.1.8

0eNrtXdtuI8cR/ZUFgbwkotNdfV8gAey1nbvj2En8EBgCJY12B6ZIYkSuvTb2A/IX+bZ8SYbkShyR01NdxUsP5Tz4IomsmalT1V11qrrmp8HVeFHMqnIyH7z8aVBeTyf3g5f/+mlwX76ejMbL383fzYrBy0E5L+4GF4PJ6G7506gq52/uinl5Pbye3l2Vk9F8Wg3eXwzKyU3xw+ClfP/txaCYzMt5WawFrn54dzlZ3F0VVf2BR1F3xU25uBsW4+J6XtXyZtNxUV9oNr2vvzydLG+hFji0F4N39X+kev/+YkcaEKWpLmEKecrdewsfmQ8CZa2Cm7KqL776c31ftUbn1XR8eVW8Gb0t66/X39nIvaz/fLOSdb/8w21Z3c8vd3T/tqzmi/o3jze2/sSwGF2/WSr9vliKWcq6n4+WSIIWF4PprKhG6/sYDOvvThfz2YIsvdbQ8hkm60da3aVc/qsqbpq4lvVPuv5kWV0vyvnqR9nQ7fJnUNt//7aWDRFhvv5rGzp6D3SgJ+hYnQEdkvZDRPuGrH3XN+1LyOEblqJ9KSPqt3uovydLU7AZtG+QlUmT0BERdNzjfX4/qoo308V9MYQfbAsq5gGVem1qk+Q3TzwfXX83vC3H86IalpP7oqr/p0WibqDchuvD491Nb4rL6e1lAwK5efj7ov5necUaix/ry8+rRXGxvofLB6nlhITV1wP+GgVLRddWW01nl1sPDB+BUBLWalQffqg/Oyuvv1vsfHoI68+16TqwdQ1nrWudQddSkJWtnoVh2xzKlmxln7dlmxzKhuTFXzYX/+SH8rGYQCoqzKI9ItDnjLkMyaAPt1CXIYD0Lo57F+yaq3x4Tsr3eZRvUn0OkHhLWiqM8hn60DIxygGj4yr/OfkQyDzK99SUUscSepsroVeQIaXc3nCQnFHHdu/A17/sif6Fz6F/353TK1pOryL4gKDiY/uGD5gc/rG9nu3g40j42Bg+ko9PT9YvcDkose3NHtG/i+kf+Hx86AkhHLL4h0L8g7S/QNQ/9qlmiZ7US2QWBwEEIBI+Uf/Re1D6PcHHQR8KKluUviHBE6t3wR4Fr54sbzpHdAZILViTdh+IFYPBcsn7cNYM5/balEpxDhOSxQ8s57C90cKxqyXivDWeozQFnsvgn7l5m1zmHdglkzM37xzVQCWY5Hl4RryfMkzeb4jqvsvSleQWLsRzUr7OQroqYDLez8rwbR7DV9xqw7MyfJfH8DWf7Rb9YOu87kWx4aJzE+lOp1SslUAZNjyhH+jYHL2dCkl2DSnZVbH2QmXZVHdP0AGRpfHZIfCQmDwFMXgcvxLRk7UNIAdXpDAqj+Y+sUqe8nwm3PWkUqGz+A+y+WhJwUdH/Sfw8fE9wcdm8R+kEr5byOjEJ+Y/WvCpcN+XY1E5qHBzUPcxMXgkH56eLG9ZzqwJJLJGnMvYrV/YlrS2A85YX5AGLtHuzvsEiM9E/WrFVbg/b4WHXArXXK79vC1cy1wKN1yFn7eFa5FL4ZbJsbtnxDQamYXm1Y6pe/+cdC/y6N4zKfZnZfeQR/eBqftnZfcqi+6NYNPnvh8EoMrRaKmQBNnQEuRYp6WRbHRcTw5a5OizNEiCbJA2WYskwLHGZQNsOr0vcJksoy7kIasdOtZ5aRQbnp6sddLn4Jswd1GkQTE6OqeH3lbuH/AxJ8XnVeRM31NsfsHA5lUcmNdVUUx2oDFR5q7187blBFMrFpu8+6a4Lm/qaKwTCEsD4oPM/VD4arDW1IP6lz/czUbV6hZfDn7DU/9SyuxdfWeLyfzytpreraO+dUBIcZodZLbWNLccN9cOqqfQsWa3jyImVyeCb5mD7iyfUWrdgltvbpMkP2DfbZokw1xnHpFxgojVLD5Y4WacIN9aotB4ml+qDH45mrybvyknr5+6p9hyz98y3POrDve8HY3vKf5pVbd/2vhZz6SVOIpgICEoIgDCEQF8CD8OC95GKh2/9r0MOY1ow9YvQvdCakUagpacMgMNRGqY8nTM6f28KMbD2Xg0LxphSjJMYvmlZhjzSwbW5eR2SgsxQ7c3Opm6yTmBf7XLCJB9ybVRw21Gws/czUkr22uo2sLZp2bw8RefnsIQrEAMgZQKWpXo0sxhvPaAOW6MVLCKtGHYDBvGgw3xgvHO5eswwbjd9dpYjIw0jjlS17JBOjGspv0dkLuJrkbk1Nrn37KiTTa/YixEX9NWISQ4dH6fVQiTFkWRmJQ/TmxVpwv+d2PHQ+TlSOxIXQ0cJb9ua45qRYc+6PgRIJ2TXkz+3jfboeGvTzI0waWu3UGT2tgwBiJ1bXXMlFyfzitfbbkkHMIn3xZVM9E/CGnmuVwWzYcxrKNxoqeRT6J1/YUDck8iwj1dEGTIhgx4lAEkGdCQoR9lKJIM1ZDhH2Vokgzd1Id9FGJIQkxDiNpoxJKE2IYQu1GJIwlxzceBjVI8SYpvAmw2WgkkKaEhxciNWqQgifm4+UgCNpqRNKv9pPlQQm90I2mW22RvtQgb7Uia9X7atN7VfK4HOTQL/uyJBSvfUBDNij9/YsXONjREs+TfNS3ZGNVQEc2af998NCWFayjJU+jyHZInGAI/FFnbA2tt10dY28fzyfDhaks6fTie1ncynZdvi4YGhyC1017Zpu2n4fHkAsnCgSF8effXo+r1dPj96HWtoO4rKMYV0qVr5v3fjhflTdIVDOMK6dIt8/5H1bwcj+toLekqjnMV0hXirp5IyUReZSJoDiyPHpz9oblFWVgdhWRFaH9sbr2gwXtmmPanJ5uv9sZZZrD25yfbb3DSADNk+0tzA5ZBK6GZcdsXzS1YeW+FZwZvf32yCTvnoBFM0ja9L5vbsDJG60ZISYvj/tbciJ0U9RNqZjD31ZOtWIOsH9FzQ7qvn9i518roRpRJjOv+3rR1Zb0ToRls0uz9H0/s3SmnpW+GnDSb/ye2+2pKEGN9NEixfjtBTaxNOsmuTeoTEL1lVW8Wr4tRNfz+TVGMOSSUzFKftEhHqYPU+JMhiVCzBkRajMRywLYbdQK7mZUzVjEbshiLQ5hFr5OTFbqkDmPZrV13S4sai2LXtnU/atsqT20b6y2goZnIWTr+/CrVD7RcFrQc0l7kSV3PziaiZXjVfp2z2g/san9LQHCYSoJTqVUjrI3M2YPWehOric7y7EDltAPNtoOHDf5A4OtU8B1yjsv7fZZkQKRFwXfsdo0M0VjGPg2H9NcEUu/fbh9Gt7QofJ4NX94kLGfHDdIJ5Uiv3kH7plwikoHf09GTN/UM5f4ZELlnw2Pd8iGmcU+f2KX+r/GOV616ST3M8/DyA8Ko152NDiM5Eil9T6YlHs9LnOjV8V2lqMNaRvxKpFMTHglQA6nBNSQ2SXnFBhJ6COQ+2yMdxza9Ywc9PSR6mGYTf3CCWKX+UB2o3A3vRq9HP5YTFgmo8pCAyKFpn96xQJfUFeQCkqOkerRhG448geHUmpyMblj2orPYi0cC4GBT7YUhqcNePBJKh0RCw1s2DQk9ORBl8vCQCJyelBm1ERqtcDn+Ww96wvHnOcDmkVbjQGKUfGqg7Hl0IeSkCz2bLmwLCw5DHXqbTB0iQPuwT30AEGnRZTbwDEFmPS1o2ZbQ2OcPZADJx008Qj5KIfZZmQETFzOBINj0Y57ILCPtGCSGIem8cZAYhioRQ8nGMHNalrMagLw0JZD8cZcj7pYWhRKIA2vW/Js4wryatL5yuVc3ebzh2+7VSI7c6uE6x7E2VuS4+rqN1UikhTUlnlm3jC7PJTz2sBLaC71KPksXaGxt1NIVazTTtqW3SdasoTmyTzNz/vvv/zBWwG8OOPIoUIfFJfasBMMld7O+DH6/1WL/1JJ+EjreMOxJXaMe4QBD4qC4YLkc4J7AUyk9k4fSQ5pLgkum9OiSuuBH2lRCYnU8OC788ucAf7BYbpFM6XJEdaUpFktTEknd4LksoegHSWjzdAJ7LFMhcUetREMrXIELl/xZwxVQpsfT8JJpeK2AZbB5IieZp9q6gQ/DzQWfzM0FDDG5Dw0PmDiIIipZiMrnimhIRbRlkdvCQIq9Fk3A5MUxBS5Zd5g4KCPl1sKPbmsRaKgoDBVIRUVxURHnjkrAXEWQQAmYp4hkTBrvz1tc1epZqSRKD6iPTLsYdu+JOm3i4bIkHi3ZwLYTJZ9AZMnqdHAs95A61ZjY7AOc1gpsnvTTYYtAcgcaR1TXeuKw9cSkmgC7S6UnRxvB5GkqaslYtt3Q0tw6pKY0bMqgL21gkOc8akBTGhIJ2BoutyPGaynJehJxNSvvSDnLjqI7khaJJi1+L9AAkxddOiWPWsjaMGb1EUH16Zko2jQS9qKDAJMXB5XdNqLOPhOVSJu8BBo/IJEi2Y68OCpsfgDOnx/AUJGS5isYKjKViZOKmz6Y06YPIU8SKTXmT8kzj1iyOn1TY76ZykhI9vknfVor8JmoBIP5r0qnEhiyOtcCg60FKtUKDDcp6cvLegTkKY215Inbrkjjh2TiGypXF+Zh1pMhVEbKTLk/RudIQ4PMp0LmWDlH1jcZGXm86teOorsySYywAbsXaIDJiy+evLNHeSdWGXtEVG16KomROtLtRcMBJi+OauAmLebskxbAWBugsTaAsTaQytoA+2yPPv8EH6NdJI12kRjtIlNpF2BP3XWnTSI+yZNEAEYCKJGcRHBkdfomRiioVJoH2DN07Wmt4ONMhALWKgIynVBgyOpcC7C2E0illYA9HNf1Iy3RImSqSQLGEikaSwSJE3JXF+ZhZntSRhbaZUr/MU4HaJwO2FTMeINyXdasY/WaqmOlHZA88rZFy9uepvdCDTB58eWTN/fWZi02r95idjRYdTpHgBE7YPbi4gCTF4eVPdHWnX82iTE3isbcAMbcqFTmBtiDau35Z5MY8wLEdhqMeYFU5gUCN48Ip80jPs2TRyiMnVHJb5FlyeqyAoUxPSqV6VGCawX+tFbwKhOngLFBENI5BYaszhUaY5YglVlSkpuZhJ4UJq3ymSqTCmOKNI0pUioxNVHABc33AzQvQ6bSJGC8jqLxOkqnYqZYeUfIOj9v9ZbhY+UdSibnHQojbjTshRpg8uLrp2bB6rO+RWX1EuqjwQrpLAHG7Si1Fx8HmLw4rIabuISzT1wUxt1oGnejMO5Gp3I3ynJR8eef5GPUi6JRL4BRLyqVelH8KS0nHtPyeaZ8EuNntEnPJxmyOp0T43p0shl4thmceFjTZ5kSSowQUi49oWTI6lwNMHJJpZJLij8Cpi8zYIxRmQqUGmOLNI3J1alzYLRgo9aTQUsKnM1UolQYu6No7I6GVNSYs14yD3tx9ohFSpU+8EWj/I3bCzfA5EUXUQ08YEXeIevKH7FMqUU6XYCRPFruRcwBJi8OLHtmjDz/UT4aZXFotRCNsjiptRCt2bCI88/3MRZG01gYhbEwOpWF0ewxPPLEE1h+lymzTM8YiAlBcryv2aekZF/mbSgpXKZyBDUyTD27pnkHoWTe6Qt14nVEYlqnn5ohxgfp2z+7H0ae/0l94jbSvkvUkK3ebPBycDVeFLOqrJ/lYjAeXRX1HQ++rKbz6fKuX+gX0+qFeTG9fTGrpm+X1vpiMw3ubVHdrx7bKSGDhXq1s+/f/w+3bjL1

Copy blueprint

NOTE: I haven't tested the design LIVE yet. I am certain it will work though.
Except for one little thing... Certain requests on 2, 3, 4 or more wagons MIGHT load more than requested still. This because of not being able to divide items evenly and thus inserters that are further up the chain can overload by one or two or three items etc.

Let's put it this way... If you clone the platforms without changing anything, you are guaranteed to have overloaded items and possibly stuck inserters.
Remember the "per inserter" combinators?

0 <left side>
12 <right side>
24 <left side>
36 <right side>
48 ...
60 ...
72
84
etc etc

Well, for each platform you add, you'd do well to change the 0 (zero) to 1, 2, 3, 4 etc so as to not overload the train.
This will mean the wagons further back will have less items than the ones in front (space allowing) but i see no other way of solving this.

BTW, i didn't mention one little combinator. This one:

This ensures the division over several wagons doesn't get the whole platform stuck at 122 out of 123 items requested over two wagons.
123 divided by two is 61 leaving one rest units. This is what that combinator deals with.
So keep that in mind as well if you just clone platforms.

... (dot dot dot)

And yes, i know. If you wanna use this you would have to actually build your own station through it and re-connect wires. I am not here to hold your hands but i might return with a fully live blueprint if requested.

[Optera]

I like it.
That's one hell of an over engineered solution if I ever saw one.

To be fair though having one stop per item and using a dumber loading system might be smaller and easier to troubleshoot.