Warning

This is the dev documentation for an unreleased version of MPF!

This is the documentation for MPF 0.56, which is the “dev” (next) release of MPF that is a work-in-progress. Unless you’re specifically looking for this version, you probably want to use the version of documentation called “latest” which is for the latest released version of MPF. That documentation is at docs.missionpinball.org/en/latest.

bcp_server:

Config file section

Valid in machine config files NO
Valid in mode config files NO

The servers: setting in your bcp: section of your config is where you configure listeners for incoming BCP connections.

Required settings

The following sections are required in the bcp_server: section of your config:

type:

Single value, type: string.

The class to implement the transport. Use mpf.core.bcp.bcp_socket_client.BCPClientSocket to use the standard MPF BCP protocol.

Optional settings

The following sections are optional in the bcp_server: section of your config. (If you don’t include them, the default will be used).

ip:

Single value, type: string.

The IP to bind the server on. Starting in MPF 0.33, you can use ip: None and MPF will listen for incoming connections on all network interfaces.

port:

Single value, type: integer. Default: 5050

The port to listen for incoming connections.