*Apr. 28+ Port Manager FB

A mechanism is needed to avoid:

• multiple sensors types used on the same port
• to encourage application developers to only use 1 FB for 1 physical sensor / motor.

Related notes will collected here and formatted as the ideas become better formulated.

Open Questions:

• Can Port assignment / use be required / enforced using FBs?

Simple Mgr can check if the port is taken and reserve the port#,  but no check if its used.

• Should input ports (sensors) &output ports (motors) be managed together or separate?

In other words should there be an Lego Brick FB or 2 port managers? Leaning toward 2 port managers at the moment.

• Port / sensor Initialization at start-up or when first used?

If the leds are initialized when the AVR is, then no need when the led FB is used.
Extra work to initialize all 4 leds even if they are not used.

Or should initialization be moved into FBs or allowed as an option?