my support-train setup:
Filter inserters set to check train content and then load missing items, but cause high-tech trains stops so fast,items are being loaded even before train fully stops, breaking the amount every time train stop at this train-stop.
Support train overload
Re: Support train overload
Thanks for the report,
Can you provide a savegame so we can easily reproduce the exact problem?
Can you provide a savegame so we can easily reproduce the exact problem?
Re: [Pending] Support train overload
It is not possible for inserter to access the inventory before the train stops, so it must be something else.
Re: [Pending] Support train overload
Sorry for delay, this one.
In this save i stand near this support train. Launch this train and send it back to load station.
In this save i stand near this support train. Launch this train and send it back to load station.
- Attachments
-
- support_train.zip
- (10.69 MiB) Downloaded 92 times
Re: Support train overload
From the screenshot, it looks like it could be the signal delay between stopping and reading the cargo.
I wonder if it would be beneficial to have the station get the cargo info when the train enters the block or gets closer, but before it stops.
I wonder if it would be beneficial to have the station get the cargo info when the train enters the block or gets closer, but before it stops.
Re: Support train overload
Hello, so now I understand what is going on.
It is related to very similar bug report: 46234
The good news is, that there is a way around this, by using the "read stop train" signal in the train stop.
I changed your setup to only use one chest and one inserter, and still do what you want, here is the blueprint string:
The idea behind this is, that you setup the things you want in the train in the constant combinator, they are summed with the values in the train (multiplied by -1), so all values bigger than 1 are the ones that are needed.
All this is then only sent to the inserter ONLY if the T signal is present, so the inserter won't be active when the signal is not processed yet.
It is related to very similar bug report: 46234
The good news is, that there is a way around this, by using the "read stop train" signal in the train stop.
I changed your setup to only use one chest and one inserter, and still do what you want, here is the blueprint string:
Code: Select all
0eNqlV21ymzAQvYt+dlAGbOy4TI/Rf50MI8Pa1gQkqo+kboYD9BY9W0/SlXBs2QFHTv4YC7FPj923H7yQdWOhU1wYUrwQXkmhSfHjhWi+Faxx98y+A1IQbqAlCRGsdSujGBdUG9mRPiFc1PCLFFmfvGuooKbPXEFgNosw2yoAcWk4jzBkiptdC4ZXtJLtmgtmpAow8v4hISAMNxyGN/eLfSlsuwaFL3WE0u6ltztD8dLgCZ3UaCWFOxuRaJ6QPV7wdUiNRKthz7/dBeYsGnMWjTmPxUyjIfNYyHiWi1jIeGcuA0hWPdINbwwoyoUGhX9GnDq/Wwzo6d3iHB9PxQwwSjblGnbsiaNW0KjiqrLclLhXH5E2XGlTviO/joOquNhSJa2oNW3Zlv3mwqvY5ZphLvFSt2g7prw4C/LNbx8ObWUNpdyUsgPc94dng7UYaGt3euZ+fJaEIuY1KVb9Q9+P+O3+SLKRW659huxAY0Dgp8XrVdcNnrvmqxtoY024JJ0tJlivjqxbqLltKTQIp5B8JxsYYZydBzvabcvgcLf+eoqIW84m+H098quh4jUKMSg7I+wCbwY6XI779gB50qG+IsQnroxlzUmLwxP0+3Xt/fvzF02kNZ29ARSeQO3NDpU+oHd7JGmFKTdKtiUXCEYKoyz0t8QgSy+dnrxVSUJmN2vfAV9tEFNVMzZSJ9TPBQtYtTuPl5NMkFPky0ei5VFvC0X+jqsv8iOb8nzQT1vWNLRhbTfSUcKsHYM5tdANw5o1Xe2z6WI/hjv/QFXMzori4cFy6EPDTPE6IJ3GIFk9gqEbCy46PlWcKp2P33LKx8auiY6ZXjTMcXlqEHVpZOnxSLFhjQbHnNVDwh7uu4Q93HZndlCf7/jFceuWCvSZKjAprdNw8Zou14tveohbFpnUYUQ/1fd9tFdpeuPk3DGuaIczToAyD1BiBumjqpVcSxMAzQKgmMEaoy6APmMKByCLACSPAPFxUta7/SqjRcw3ghXUWKVgCmTpS1jkBHLvPgziKx0+7NkUwQdVQrAr6kFReT5bZvn9Kk/7/j+yppGl
All this is then only sent to the inserter ONLY if the T signal is present, so the inserter won't be active when the signal is not processed yet.