Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Please explain to us in more detail what you actually did and what you are trying to do.
Buffer chest items goes to your passive requester then provider, dunno not enough info to solve your problem.
Your description...seems like it's mingling the "my setup is SUPPOSED to do X" along side "my setup is DOING X".
Unless you want this to work a specific way just for the sake of it, or are in some heavily modded factorio such as pycoal or angelbobs, I find it unlikely you actually NEED to get this fancy with your buffer chests.
You seem to be trying to use a set/reset latch to control the chests for some reason?
That's what I'm making out of the OP's post, as well.
It looks like the standard SR latch setup you would use to hook up backup power generation to your solar power setup.
My other thought is to consider altering your controls to include the downstream process results: why are you only refilling the buffer periodically? For example, if you are prioritizing modules 1 to go towards science rather than filling a buffer box en route to module upgrades you'd want to fill that buffer whenever science is "keeping up" and not necessarily when it is empty. Or is this a problem that can be solved by simply expanding/fixing bottlenecks?
This is the rlatch : 0eNqNk0FugzAQRe8yy8qpgBLSsOiup6giZMwkGSnYyDZRUeS7dwxtmrYk6QZhe+b7z/vyCepDj50l7aE8ASmjHZRvJ3C00/IQ9/zQIZRAHlsQoGUbV9KS37foSS2UaWvS0hsLQQDpBt+hTIO4q9GgogbtvEAWNgJQe/KEk6NxMVS6b2u0fMMdLwI647jb6GiAFRdZkeSPSwFD/M/XCV/G43prDlWNe3kk7uLSb7mKj5tRwsWDLVnnqz9DHcn6nnfOfqaKxWucxmHUiELOy8j4KUkSAaZDKydv8MCdpvddP6P9E5gyfBjC5FujOjtL42dnEfUlKWoYI9eSVT35aRk23J3FcovNneKUi0PM8Rf57FaCs9iX/8D+qfU/5nNcRtkvyutImW110o62Sni5gflmhMp0A7vqta+21rQVadaAcisPDq9lMQM3vZrEbHDpXBb8JMbJy4tXK+CI1o28s+c0X+XrVbFKk2JZhPABpupQJw==
Bigger picture: you must choose between setting requests and reading the contents of a buffer chest therefore you will end up needing two chests or two separate networks. If you are determined to not have a static request, I am still thinking your best alternative is to try regulating the requests of your buffer chest not by it's current contents but by your downstream needs. It will be easier to setup.