The Type 1b standard was used shortly after the GBC standard was created, when we included a small GBC in a train layout. It easily allows for design of a non-ad-hoc layout.
I kind of laugh at the suggestion of a "best practice" for builders to not follow rule #2, and make the in baskets lower than 10 bricks tall. I've always thought the best practice would be to make your OUTPUT HIGHER than 10 bricks (or 10 1/4 bricks) so you can feed into a 10-brick-high basket.
It does cause problems if the input basket is too low, and balls bounce. Why encourage people to vary the height?
And, if the 1/4 brick height difference of the output causes a problem for your output, I'll bet there are going to be other problems with your module.
If your module can not output 1bps, the biggest problem is not the fact that downstream modules will be starved. The problem is that your module will be flooded as balls build up in it.
And if a module is given an out-of-spec batch (more than 30 balls, as "often happens in the aftermath of clearing a jam") it should be 100% OK for the module to flood and fail. (see "Following the Spec") It doesn't matter if that batch passes through a module that is "running fast".
I don't understand why a module running "too fast" would ever be a problem.
|Posted by 220.127.116.11 on 7 July 2015 at 18:58.|