package mpf.vpe

Get desktop application:
View/edit binary Protocol Buffers messages

• rpc Start (MachineState, stream Commands)

  platform.proto:6

  message MachineState

  platform.proto:16

  • map<string, bool> initial_switch_states = 1

  message Commands

  platform.proto:86

  • oneof command

    • FadeLightRequest fade_light = 1

    • PulseCoilRequest pulse_coil = 2

    • EnableCoilRequest enable_coil = 3

    • DisableCoilRequest disable_coil = 4

    • ConfigureHardwareRuleRequest configure_hardware_rule = 5

    • RemoveHardwareRuleRequest remove_hardware_rule = 6

    • SetDmdFrameRequest dmd_frame_request = 7

    • SetSegmentDisplayFrameRequest segment_display_frame_request = 8

• rpc GetMachineDescription (EmptyRequest, MachineDescription)

  platform.proto:7

  message EmptyRequest

  platform.proto:12

  (message has no fields)

  message MachineDescription

  platform.proto:54

  • repeated SwitchDescription switches = 1

  • repeated CoilDescription coils = 2

  • repeated LightDescription lights = 3

  • repeated DmdDescription dmds = 4

  • repeated SegmentDisplayDescription segment_displays = 5

• rpc SendSwitchChanges (stream SwitchChanges, EmptyResponse)

  platform.proto:8

  message SwitchChanges

  platform.proto:63

  Platform streams switch changes to MPF

  • string switch_number = 1

  • bool switch_state = 2

  • uint64 change_time = 3

• rpc Quit (QuitRequest, EmptyResponse)

  platform.proto:9

  message QuitRequest

  platform.proto:14

  (message has no fields)

Used in: MachineDescription

• string name = 1

• string hardware_number = 2

Configure a minimal hardware rule to hide latency from pops/slings/flippers Dual-wound, EOS, cut-off rules and more are ignored here Not sure if hold_power is simulated in VPE or if we should remove it

Used in: Commands

• string coil_number = 1

• string switch_number = 2

• uint32 pulse_ms = 3

• float pulse_power = 4

• float hold_power = 5

  Probably not important for VPE because knocking down a flipper will probably not happen there

Disable a coil

Used in: Commands

• string coil_number = 1

Used in: MachineDescription

• string name = 1

• DmdDescription.ColorMapping color_mapping = 2

• uint32 width = 3

• uint32 height = 4

Used in: DmdDescription

• BW = 0

• RGB = 1

Used as response type in: MpfHardwareService.Quit, MpfHardwareService.SendSwitchChanges

(message has no fields)

Enable a coil Not sure if hold_power is simulated in VPE or if we should remove it

Used in: Commands

• string coil_number = 1

• uint32 pulse_ms = 2

• float pulse_power = 3

• float hold_power = 4

  Probably not important for VPE. Can a ball be knocked off from a magnet?

Used in: Commands

• uint32 common_fade_ms = 1

• repeated FadeLightRequest.ChannelFade fades = 2

This is up to discussion

Used in: FadeLightRequest

• string light_number = 1

• float target_brightness = 2

Used in: MachineDescription

• string name = 1

• string hardware_channel_number = 2

• string hardware_channel_color = 3

Pulse a coil If it has been enabled before disable it afterwards

Used in: Commands

• string coil_number = 1

• uint32 pulse_ms = 2

• float pulse_power = 3

Remove a rule between switch and coil

Used in: Commands

• string coil_number = 1

• string switch_number = 2

Used in: MachineDescription

• string name = 1

• uint32 width = 2

Used in: Commands

• string name = 1

• bytes frame = 2

• float brightness = 3

Used in: Commands

• string name = 1

• bytes frame = 2

• repeated SetSegmentDisplayFrameRequest.SegmentDisplayColor colors = 3

Used in: SetSegmentDisplayFrameRequest

• float r = 1

• float g = 2

• float b = 3

Used in: MachineDescription

• string name = 1

• string hardware_number = 2

• string switch_type = 3

  NO or NC