Reading contents of space platform hub is wonky - Schmitt trigger doesn't work

[Eddie the Jedi]

I set up a Schmitt trigger on my space science platform to regulate the assemblers. The assemblers should be deactivated when there's lots of space science packs and not reactivated until they run low. What happens instead is that, when the number of space science packs in the hub reaches the high mark, the whole thing starts oscillating on/off every tick.

I copy/pasted the two combinators that comprise the trigger (with their connections) to another place on the same space platform, and connected a constant combinator and a lamp to the copy. It works just like a Schmitt trigger should. But when I connect the space platform hub to the copy, the copy does the same bizarre oscillation.

I can only guess that the "read contents" function of the space platform hub outputs signals differently somehow, compared to constant combinators/chests/storage/tanks/everything else in the game. Surely this can't be the intended behavior?

Here's a picture of the original Schmitt trigger in situ. I could put together a blueprint but this should be enough to reproduce the issue, it's a widely used design:


And a picture of the copy:

[eugenekay]

Factorio is not a true-to-life Electrical Engineering Simuator. You have not included a Blueprint string, so we cannot test your Setup or see the Combinator specifics.....


You can implement a Latch with a single combinator, by wiring the "Output" to the "Input", and adding some Conditions:

Screenshot 2024-12-15 223518.png (611.85 KiB) Viewed 760 times

0eNq9VMFyozAM/RedRQcIZCf8SifjMSBSz4LN2KJtNsO/r0xKN7uhPeSwN1uW3nuSHlyg7icavbEM1QVM42yA6vkCwZys7mPM6oGggpYa05JPGjfUxmp2HmYEY1t6hyqbjwhk2bCha/1yOSs7DTV5ScAVp9OBE/bahtF5TmrqGRBGF6TW2UgoeMn+qUQ4yyF7KucZ7/DyR/HSbbwdftPnPdyNOITWeGqurwWCTJC961VNL/rVSLWUfGAqeWsXnBCjtzeZWGd8YHU3dwmT9kMy6JP+ZSzFqcctsY4ry9MU/6pUlvjN+Z8Lg6cWKvYTIZw8kQjsdB9oGcBDdOX/oPsef4H8JIhsi8Jh1J4Un8eIqm0L0ZFu4nHiLwy93el4li1NllXn3aCMlfq1jeO85ZziQSd+YezyQbh0seKW+Rrjm8mwkm5b9SKjiTZkoQ3rstaMNX5NHVwrMvItkftPkb2zpySCUpsYG8gzbX0vxU3T/34wUyDVmV4KPwTFzb1JStzb8w4zLDE7opxy3GGxnArcY36UPMM0iIw/PzGEVwFasMt9figOh7JMy8OPrJjn37hCsoY=

Copy blueprint

This simple circuit is used to keep between 200 - 500 Magazines on the Belt.

Good luck!

[Eddie the Jedi]

The same arrangement of combinators that works as a Schmitt trigger should when the input is a constant combinator, does not work when reading the hub's contents. That is what I'm reporting as a bug. I'm not asking how to make a nicer Schmitt trigger.

[Muche]

I tried to reproduce it on v2.0.25 (using this Schmitt trigger implementation), and did not manage it; output was stable when connected to a constant combinator or a hub.
But the hub contents was stable, I was not requesting it on the planet or anything.

Could you try to go into editor mode and stepping it tick by tick and evaluating wires signals?

[eugenekay]

You have not included a Blueprint string, so we cannot test your Setup or see the Combinator specifics.....

Reading the Contents of a Space Platform Hub (and refilling with Science Packs as-needed) works just fine here (exact same Combinator setup):

Screenshot 2024-12-15 231103.png (1.43 MiB) Viewed 742 times

0eNrtWsuO4jgU/ZeskxakgapC6t7M/MFIsymhyCQ3YJVjp/2gGrX497l2IHEgPELSs2rVhryOfZ/n2K5fwZoZKCXlOlj+CmgquAqW778CRTecMHuPkwKCZaBKkkJUMqJzIYtoa9bBIQwoz+BnsJweVmEAXFNNofreXewTboo1SHwhPOHkROlIS8JVKaSO1sB0EAalUPit4HZAxPv6ZR4G+2AZLb7McZSMSkirx6+H8AI8rsEzSGkGMkpFsaacaCEvsac1NiKjvVoKlqxhS3YUX8d3jiAJPsvch8re9a/QvpxKpZMrXlIpBW69RdKPoBpFaWJdHE8mYevbhIP+FPLDjSEhC5ZaGgiDjQTAGeeEKThYm58ccP5/DViURDqHL4Pvwb0h3Sj1mHYCNQYkel/agQjPAptWwujS6JtZeTmbco/hM1wnuRRFQjkinGxbHQ4dOfT1yQSdP5Kgsxp8bdhHRLkCqUHegJ052K7sTKlMDUXXAhpHGcKo2oP1NbrqVJnhDVeFwQ9DGM4UH3OsanTtWSi/uRAYBedjXdg4D290igtDJ87MyRUbJZAsKcSO8o0L4ClH/ftatO6qEppcdhde6h4zakelNs7G00zdG9G/NmccSkYKssEMJB+nvMTYevcex9wCkTo4OOAfBpQXLEzjKlnagbI+Pf6O74VSCw7RJ2HsoRDaG8Y2g+lkMmkP0x2yHF/PiAvXEPympjaGR9pICboFaDgiFW6UG5AeYlNIjGANdWE+MkkPsUlbgyVPDRpvgEUpPOFbD3ZRw0ooCZWP19sVwJcaENsTSEEzJDnGMJEcx/Xy6dwHfquB9VYaVbWlXnCxDzed1Hgpwm3P4B6w2ge7Jxuez81p3IbGhAe5kTbxnwP3sc/IRJWIo/t7ooU5a2N6HPI8ZpP8TPBNtEXKhWwc6MVVynses6mB0hRlP6hWzk9fGyRaQqRFVIV+0PTeWqD9oOJ2Y574rV4i/USo5j56W7yyEkuYEh/8ZdYQ/WNKTEVU6GFAkIF2cNJErZ59k3oK0Eg7Rm5o2l9L3Ccixzxy39d5naSDkmyfsr45F3fzTUpYSjX0DcGkFYR3ZFjUwt84MTuqVn9LUYo8vxGN2Z1ooHhKkQBhJO8zsaFKY2SlWAs9oMC++jNUqKOc3hkM64WD0TyP4GfJUFfuXEb3cwAuXQvLJEd9GVQhCbqilRu2wSJ8IFzzO+Gy9ttBB7hgnGBNJ78nWtfUWuWwqJSo3d36fIuKeIAXGuIqiVKjQi8uWu9QxBePCvN8hCm+ei3OrS1GwGzISwlGrF7lMEgBe0KwgMwKa7BqVWLCloLBEPZuCgrLUW2FxPD3FgTxFTU4iHA7NeBIKwBPAbr1bVSIzDCI4iGzbAoJ8pw6Pt+PAtyUEVZmZjvKDnFGgW7q6QgxCuqrt7TkGbZxNkTBeWKQpKkpDCPnC7We4fc04WDy62K5DYP1Ixy3uMNxT5sbXxElJNsRVJm43q12vvqhzq4wHZXIcHbDA4bgzfwsTwGpCJdRhvedZHxlSwIxP0C7HYkhgAtPM3xGGXBli6YieiMHrVRexlTbTQmugaR9N5/ibjqrWEdw5J2nEiie/E5au8JrIwhFj9J+m1jupLvTPlpKOMcaU9uBW2ke70mSETkO3Y221PGYboS1Tkdj3hmGrjTXl4srb4/ZnnZUKrM5FTg9LKjrT4k/zaTADigp4hxfRzCFWtLyadXgmcDpCu3yZvk+955XO/WpkNnxcEZXW8Z1foTBJ6E6OTs56zjmCU+76YSx5DhdlSiEUzmFzCXarc+awq7HspM7P8G6s2VfnUa1T88uTrYO9+aiaWG7AKaWPe+avlZsi4aJT5UYzgTJMAgerzZuOy40//jt5Le2e5xC+eOcbuecusQf/9T+WR1s5X1S6TrXexxOw3k4XYX4y/7N3K8Z/sUrfI9qsNTW/DtEGOywizqr5ov4bfb2Np9P5m8v09nh8B9nNx2Q

Copy blueprint

[Eddie the Jedi]

Alright, I've found something. My two-combinator latch goes wonky when its input is the space platform hub contents, only if the space platform is also configured to transition from a non-unloading to an unloading state at the same high mark. eugenekay's one-combinator latch works fine, and my latch also works when I have the space platform transitioning to unload based on the latch's output signal instead of the cargo count.

I still think this is a bug, because I don't see any way for my latch to go into an oscillating state like it does, unless the space platform hub becomes... uncomputable??... for a tick during the state transition. I'll try running it in editor mode to see what happens.

Here's a blueprint if anyone wants to test:

0eNrlmm1u2zgQhu/Cnwu6oKgv21j0IoEh0BJdEytRKkk5DQIfYA+yF9uT7FD+jJ20bt8/CxQBElLiDDnvPByTcF7Zuh314IwNbPnKTN1bz5ZPr8ybL1a18ZlVnWZL5gdV69nQqrDpXTfbjmu258zYRn9jy2S/4kzbYILRB/up81LZsVtrRwP4yY/yXnfr1tgvs07VW2P1LGWcDb0n497GGcnhTH7KOXuhRvEpp3loXcH1bbXWW7UzvYvDauPq0YRKW7VudcOWwY2anx+TSXN2uTHOh+oSVHgZ4mJ2xoWRnpxXdxgxq7e6/osd5vVBRXFE7HSDcirE6dlntqf3TtdmuMjja6NtlEmR+elt9ZWmIDFolCXpaLo9vxNI/qRA4jfTJ/1JfdLfTJ/svARjvXaBnt1vquQkSkaivOMkf8DJj3wUD/iQP/BRnn00pECj3YykWxs7SXfnLTt7+yDRRyeXjPop/Ve9p/sMvyl7b/LyJq1SiFj7+jEMY7gtnY9TMrzQ6kYbqo3ru8pYcsaWG9V6vV/t35NoftkPzoRtp4OpH1NJfqDSxc+NUL/KvtfRT3XRajYXtAv6QdMemBbG/mAn6R5T/l0pFvw7n1H3hXNSQUx77+uoKbKNaYnSKVRa8oWI82cbP7epSisasdPn5Fy5iZlbj5vN5CvWkqs5OuM9VayDGG6cZqk6RfMa8nMcTs48qdeM7fFDtO0po32cL/YXV+/jYqk69K45MhdOklo17oynuJ/VdRE7DDtUIF0dU6hsQwOPHRN0d4CQcfbd4vfg1kiEuC16//79DyWR4lBt2z/7arRtrxoS5qQn/3+GIu8i+TPGEfcmBfNs3JSgp4TL+LPiT/FvOrXoNy95Rq2SJ3zO06mVUSu+pT5f8GRFXoI5pf22bGeHjTvffwT6hkJtDqpFBW/tU9BegvYJZi8wc3B2MHhQezT1R/sSRKcE0SlBdEoMnRJDp8TQKTF0SgydEkSnANEpQHQKEJ0CQ6fA0CkwdAoMnQJDpwDRyUF0chCdHEQnx9DJMXRyDJ0cQyfH0MlBdDIQnQxEJwPRyTB0MgydDEMnw9DJMHQyEJ0URCcF0UlBdFIMnRRDJ8XQSTF0UgydFERHguhIEB0JoiMxdCSGjsTQkRg6EkNHgugkIDoJiE4CopNg6CQYOgmGToKhk2DoJBg6AiNHYOAIjBsBYSMgagQEjYCYERAyAiMGrDVgqQErDVZosDqDlRmsymBFBqwx4MEGPNeAxxrsVIMdarAzDXakwU404IEGvEWBlyjwDoVdobAbFHaBwu5P2PXpMesVn75eo0GX/xzibKedn/zlhVxki0WeLeS8yMR+/x+RB1v3

Copy blueprint

[Eddie the Jedi]

In editor mode, I can see that on the tick when the input of the decider combinator in my Schmitt trigger is 200, the science pack count is not 1000 (which would produce that result) but much lower, because the space platform has already transitioned to the unload state and decremented its cargo count by the amount to be unloaded. This leads to the oscillating behavior.

This seems like a bug, in that the unload happens in the same tick as the transition, but is not reflected on the circuit network output for that tick. However, fixing this bug by correctly reporting the cargo count, when the unload happens in the same tick, wouldn't help my use case, because my two-combinator Schmitt trigger (EDIT: or a one-combinator latch, come to think of it) will never stop production.

What I need for this whole setup to work properly for me is for the cargo unload to happen at least one tick after the science pack count reaches the high mark. I found I can make this happen by having the space platform transition to another non-unloading state for zero seconds before unloading.

[eugenekay]

This seems like a bug, in that the unload happens in the same tick as the transition, but is not reflected on the circuit network output for that tick

How would this work? If the Circuit Network has finished calculations for a given Tick, and the Unload logic has processed, then how would the Circuit Network re-calculate before the next Tick?

This is why Factorio is “not an electrical engineering simulator”. It’s a tick based game, and deadlocked or infinitely oscillating circuits happen all the time.

What if you try adjusting your Setpoints such that “extra” Science packs are stockpiled, more than what is being Requested by the Landing Pad? Assuming that the point of this circuit is to reduce the rate at which Drop Pods that are sent, please be aware that Release 2.0.25 (currently marked experimental) includes a change to address this.

[Muche]

I've stepped through it as well and platform hub contents reporting works fine.
Yes, it transitions from not unloading into unloading state and launches cargo in the same tick, but that is not the issue here.

The issue is it reports as having cargo of 1000 for one tick only, the next tick it has, e.g. 990, and used Schmitt trigger implementation doesn't seem to handle one-tick inputs correctly.

Not a bug.

[Eddie the Jedi]

The behavior of my Schmitt trigger is definitely not a bug (BTW thanks for the helpful tips on that), but the behavior of the space platform hub on the circuit network definitely is. Here are two screenshots from the tick when space science packs are inserted into the hub:

after-1-hub.jpg (1.68 MiB) Viewed 562 times

after-2-pole.jpg (1.63 MiB) Viewed 562 times

And from the tick immediately before that one:

before-1-hub.jpg (1.68 MiB) Viewed 562 times

before-2-pole.jpg (1.63 MiB) Viewed 562 times

The hub outputs a value of 1000 space science packs when it has only 592 after unloading. There was no tick in which the hub actually had 1000 science packs, because the unload happened during the same tick as the insertion.

@eugenekay: Once again I'm grateful for your combinator tips, but before you tell me again that I'm expecting too much from the game, I'd ask that you carefully read every entry in the 1.1 release changelogs here: https://wiki.factorio.com/Version_history/1.1.0. Then come back here and tell me why it should be beneath Wube to fix this bug.

[Muche]

I don't see any issues in your screenshots.

There are 991 packs in the hub, 991 reported on the wire.
Inserters put in 9. There are now 1000 in the hub. Platform immediately transitions into unloading state and launches 408 packs down. Reports 1000 on the wire.
Yes, you can't see the 1000 in the hub, they have been already launched.

The most important tick is the next one. I would guess that the hub would report 592 on the wire in this one.
This is the situation your Schmitt does not handle - one tick the measured amount is higher than the upper limit, the next one is in the middle region.
As there is one tick propagation delay, combinators decide upon conflicting information and keep switching between the two states.

[eugenekay]

[Koub] Removed by request of the author.