jabdoa2

@stlehmann: Nope. I implemented a workaround using polling on windows (see above). Works but it ain't a great solution

@rob-smallshire i guess that they are right in https://bugs.python.org/issue32396. We could probably just use `loop.sock_send()`/`loop.sock_recv()`. Do you think we should implement it this way?

@small-round-object feel free to solve the issue. Afaik this could be done using the methods mentioned in my previous post. If you want to volunteer to do it go ahead!

We could asynchronously initialize all posts and only wait for NET. Or maybe add timeouts for the ports to respond but that would increase the start up time if you...

I guess this could become a separate command in MPF: https://github.com/missionpinball/mpf/tree/dev/mpf/commands. We can then later refactor code into other parts. Does that make sense?

For certain hardware (i.e. FAST or Multimorphic) we show the headers for their node boards. Based on that we could generate wire harnesses. I guess we should start simple and...

Yeah exactly. We would have to discover the type of node boards for FAST (code exists for that) and then store a mapping for connectors to inputs/outputs. Based on the...

Sweet. I guess we can think about separating exports later. This is better than what most makers got initially

We can add a warning. This should only be a starting point. In production machines you will probably also have some additional connectors and you would want to edit the...

Yeah FAST and P3-Roc make the most sense. Demo man is not optimal but it might be easy to modify it for those platforms. I mean just start the command...