LTN can't find station but delivers goods ...

[Heikooo]

Hey,

I set up a kinda big network so far. Crazy about the network is that nearly every station (beside some for fluids) are set up the same, but, some of them are not working properly.

I have 4 dropoff stations for uranium ore. Those are the only stations with messages from the logs like "[LTN] Requester station uranium dropoff not available in network 0x1"
Some seconds later the system 'can find the station' and prepares an order. So it gets uranium ore delivered. But all 4 stations get listed as not available like all 5 minutes and then get uranium ore delivered. So it kinda works, but the messages are really crazy.

All other requester stations for like plates and stuff are setup the same just with different items requesting. I can't find the problem.

Can someone help?

[DarkShadow44]

Well I can't give you a direct solution, only tips how to analyze this. First step would be to try and simplify the situation to the fewest components possible. Just switch to the editor and delete unrelated stations while making sure the issue still appears. Then it should be easier to analyze. If it suddenly begins to work, you know what you removed is related and can undo and take a closer look.

[Optera]

I have 4 dropoff stations for uranium ore. Those are the only stations with messages from the logs like "[LTN] Requester station uranium dropoff not available in network 0x1"

That message means LTN doesn't see it as valid station for creating deliveries.
If it's an requester like the name implies the most likely reason is more trains are scheduled for that stop than "limit trains" signal allows.
Apart from that dynamically changing control signals like NetworkId, Thresholds, Train Sizes, etc. can also result in such behavior.