Multi-Drop Bus /
`Internal Communication Protocol
`MDB / ICP
`
`Supported by the Technical Members of:
`
`NAMA
`EVA
`
`EVMMA
`
`National Automatic Merchandising Association
`European Vending Association
`European Vending Machine Manufacturers Association
`
`Version 4.2
`February, 2011
`
`National Automatic Merchandising Association
`20 N. Wacker Drive, Suite 3500
`Chicago, Illinois 60606-3120 USA
`312-346-0370 FAX 312-704-4140
`www.vending.org
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 1
`
`

`

`(this page intentionally left blank)
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 2
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Multi-Drop Bus / Internal Communication Protocol
`
`
`
`
`
`
`
`
`
`
`
`
`
`Table of Contents
`
`Revisions
`Introduction
`Section 1
`General Information
`1. Introduction
`2. Operational and Application Notes
`3. Levels and Options
`Section 2
`Communication Format
`1. Byte Format
`2. Block Format
`3. Peripheral Addresses
`4. Software Operational Rules
`5. Typical Session Examples
`6. File Transport Layer
`Section 3
`Bus Timing
`1. Timing Definitions
`2. Timing Specifications
`3. Timing Diagram
`Section 4
`Hardware Specification
`1. Bus Power Supply Definition
`2. Bus Transmitter/Receiver Specification
`3. Connector Specification
`4. Example Schematic
`Section 5
`Coin Acceptor/Changer
`VMC/Peripheral Communication Specifications
`1. Introductions
`2. VMC Commands
`3. VMC Command Format
`4. Changer Non-Response Time
`5. Changer Power Requirements
`6. Coin Acceptor/Changer Examples
`
`MDB/ICP Version 4.2
`
` February, 2011
`
`i•1
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 3
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`
`
`
`
`
`
`
`
`
`
`
`
`Section 6
`Bill Validator
`VMC/Peripheral Communication Specifications
`1. Introductions
`2. VMC Commands
`3. VMC Command Format
`4. Bill Validator Non-Response Tome
`5. Bill Validator Power Requirements
`6. Bill Validator / Recycler Examples
`Section 7
`Cashless Device(s)
`VMC/Peripheral Communication Specifications
`1. Introduction
`2. State Definitions
`3. Command Protocol
`4. Cashless Device Command Response Formats
`5. Cashless Device Non-Response Time
`6. Cashless Device Power Requirements
`7. Example Vend Sessions
`Section 8
`Communications Gateway
`VMC/Peripheral Communication Specifications
`1. Introduction
`2. VMC Commands
`3. Communications Gateway Command Format
`4. Communications Gateway Non-Response Time
`5. Communications Gateway Power Requirements
`6. Communications Gateway Examples
`Section 9
`Universal Satellite Device
`VMC/Peripheral Communication Specifications
`1. Introduction
`2. USD Summary
`3. Command Protocol
`4. USD Power Requirements
`5. Examples - Mode 1 / 2 / 3 Sessions
`6. Examples - Data Block Transfers
`7. Examples - Communications
`
`MDB/ICP Version 4.2
`
` February, 2011
`
`i•2
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 4
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Section 10
`Coin Hopper or Tube – Dispenser
`VMC/Peripheral Communication Specifications
`1. Introduction
`2. VMC Commands
`3. VMC Command Format
`4. Dispenser Non-Response Time
`5. Dispenser Power Requirements
`
`Appendix 1
`Currency Codes
`
`Appendix 2
`Battery Operated Card Reader
`
`Appendix 3
`MDB Recommended “Best Practices”
`
`MDB/ICP Version 4.2
`
` February, 2011
`
`i•3
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 5
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Revisions
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•1
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 6
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`Version 4.2
`
`Version 4.1 of this specification is the sixth release of the international Multi-Drop Bus /
`Internal Communication Protocol (MDB / ICP). This specification is the continued
`effort put forth by technical members of NAMA and the EVA. The basis for this
`specification is the Version 4.1 international Multi-Drop Bus / Internal
`Communication Protocol (MDB / ICP) released in July, 2010.
`
`There is just one major change within cashless device(s) section, related to cashless
`devices commonly new in public (credit card) transactions. These devices, especially
`contactless operated, need an uninterrupted transaction starting with the actual correct
`vend price and therefore are not able to deliver a begin session in front of the
`transaction. Previous work arounds have been
`
`• Always starting a begin session by cashless with “unknown credit”, which of
`course interferes with cash payment (normally a VMC would disable
`coin/bill acceptance, while a session is active)
`
`• Forcing the customer to hold the payment media twice to the cashless
`device, once to start the session and second after pressing the selection to
`do the transaction.
`
`The new modification allows such cashless devices, to identify themselves with an
`option bit, telling the VMC, that they are capable of accepting vend request, negative
`vend request and, if possible, revalue request, while in the enabled state as well as in
`the idle state.
`
`If this option bit is set, a VMC will produce a vend request to the cashless whenever a
`selection is pressed and not sufficient cash credit is available. The cashless will
`proceed with this request like in the idle state. If in between, the customer will not
`present a valid cashless payment media and instead insert cash, the VMC will cancel
`the vend request with a vend cancel command and after this is accepted, a session
`complete to return to the enabled state.
`
`Section 1 – General Information
`Section 1.3.3
`• Added b5, “always idle session” option
`
`Section 7 – Cashless Device(s)
`Section 7.2.3
`• Added the “always idle session” option
`Section 7.3
`• Added the “always idle session” option
`Section 7.4.4
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•2
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 7
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`• Added b5, “always idle session” option in Ident response
`Section 7.7
`• Added example #11, vend session (always idle session option set)
`• Added example #12, vend session cancelled (always idle session option
`set)
`• Added example #13, vend session timeout (always idle session option set)
`
`Version 4.1
`
`Version 4.1 of this specification is the fifth release of the international Multi-Drop Bus /
`Internal Communication Protocol (MDB / ICP). This specification is the continued
`effort put forth by technical members of NAMA and the EVA. The basis for this
`specification is the Version 4.0 international Multi-Drop Bus / Internal
`Communication Protocol (MDB / ICP) released in April, 2009.
`
`Of special note are the two major changes that were made to the specification:
`
`• Changed the address of the second Coin Hopper / Tube Dispenser device
`peripheral in Section 10 from 68H to 70H.
`• Added the Age Verification Device peripheral (address 68H) in Section 11.
`
`The following lists the primary revisions to the Version 4.1 of the MDB / ICP.
`
`Section 2 – Communication Format
`Section 2.3
`• Changed the address for the second Coin Hopper or Tube – Dispenser to
`01110xxxB (70H).
`
`• Added address 01101xxxB (68H) for the Age Verification Device.
`
`Section 5 – Coin Changer
`•
`Corrected Page 5.14:
`Expansion command send diagnostic status (0F 05) response data:
`16 bytes: Z1-Z16 changed to 2 bytes: Z1-Z2
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•3
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 8
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`•
`
`Section 6 – Bill Validator / Recycler
`•
`Corrected Page 6.6:
`Notes: 1. Dispenser setup (3703) command replaced by recycler
`enabled (3704).
`Corrected Page 6.13:
`Under VMC Data: 19 bytes: Y1- Y19 replaced by Y1- Y18.
`Y3-Y19 replaced by Y3 – Y18 = 16 bytes
`Corrected Page 6.14:
`Y19 replaced by Y18
`Page 6.21, added after Expansion/ID:
`FEATURE ENABLE (cid:5)
` (cid:4) ACK
`
`•
`
`•
`
`Section 10 – Coin Hopper or Tube - Dispenser
`Section 10.1, 10.2, 10.3
`• Changed second device address to 01110xxxB (70H).
`
`Section 11 – Age Verification Device
`• Added entire section.
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•4
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 9
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`Version 4.0
`
`Version 4.0 of this specification is the fourth release of the international Multi-Drop Bus
`/ Internal Communication Protocol (MDB / ICP). This specification is the continued
`effort put forth by technical members of NAMA and the EVA. The basis for this
`specification is the Version 3.0 international Multi-Drop Bus / Internal
`Communication Protocol (MDB / ICP) released on March 26, 2003.
`
`Of special note are the three major changes that were made to the specification:
`
`• Added the Bill Recycler command set to the Bill Validator / Recycler device
`peripheral in Section 6.
`• Added a second address to the Coin Hopper / Tube Dispenser device
`peripheral in Section 10.
`• Added the MDB Recommended “Best Practices” as Appendix 3.
`
`The following lists the primary revisions to the Version 4.0 of the MDB / ICP.
`
`Section 2 – Communication Format
`Section 2.3
`• Added address 01101xxxB (68H) for the second Coin Hopper or Tube –
`Dispenser.
`
`Section 5 – Coin Acceptor / Changer
`Section 5.3
`• Added information regarding “Just Reset”.
`• Corrected typo for POLL command to 08h.
`• Added “Type activity” definitions in POLL Status section.
`• Added Section 5.6 Coin Acceptor/Changer Examples.
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•5
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 10
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Section 6 – Bill Validator
`Section 6.3
`• Added information regarding “Just Reset”.
`• Added “Type activity” definitions in POLL Status section
`• Added all new command/responses for the Bill Recycler.
`37H - 03H
`RECYCLER SETUP
`37H - 04H
`RECYCLER ENABLE
`37H - 05H
`BILL DISPENSE STATUS
`37H - 06H
`DISPENSE BILL
`37H - 07H
`DISPENSE VALUE
`37H - 08H
`PAYOUT STATUS
`37H - 09H
`PAYOUT VALUE POLL
`37H - 0AH
`PAYOUT CANCEL
`• Added Section 5.6 Bill Validator/Recycler Examples.
`
`Section 7 – Cashless
`Section 7.3
`• Added information regarding “allows selection without displaying balance”
`in the Begin Sessions (03H) – Funds Available response.
`
`Section 7.5
`• Added information regarding using the Non-Response time for commands
`that require data to be returned.
`
`Section 7.7
`• Added Controller “ACKs” to the end of the card reader session examples.
`
`Section 8 – Communication Gateway
`Section 8.2
`• Added 1FH/02H TIME/DATE REQUEST to VMC Command table.
`
`Section 8.3
`• Added option bit b2 : Expansion Time/Date Request command
`• Added 1FH/02H TIME/DATE REQUEST command/response.
`
`Section 9 – Universal Satellite Device (USD)
`Section 9.3
`• Corrected errors in 07H - Z3 to Z33 designations.
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•6
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 11
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Section 10 – Coin Hopper or Tube - Dispenser
`Section 10.1, 10.2, 10.3
`• Added a second devices as address 11001xxxB (68H).
`• Expanded on the "Coins Dispensed" section of the DISPENSER STATUS
`response.
`
`Appendix 3 – MDB Recommended “Best Practices”
`• Added entire appendix.
`
`
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•7
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 12
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`Version 3.0
`
`Version 3.0 of this specification is the third release of the international Multi-Drop Bus /
`Internal Communication Protocol (MDB / ICP). This specification is the continued
`effort put forth by technical members of NAMA and the EVA. The basis for this
`specification is the Version 2.0 international Multi-Drop Bus / Internal
`Communication Protocol (MDB / ICP) released on October 4, 2002.
`
`Of special note are the four major changes that were made to the specification:
`
`• Added a second Cashless Device peripheral address in Section 7
`• Replaced the Audit Unit with the Communications Gateway in Section 8
`• Added the Coin Hopper or Tube – Dispenser in Section 10 (new)
`• Assigned 2 addresses to be used for experimental peripherals
`
`The following lists the primary revisions to the Version 3.0 of the MDB / ICP.
`
`Section 1 – General Information
`Section 1.3
`• Changed the Level and Options chart for the Communications Gateway
`and the Coin Hopper or Tube – Dispenser
`
`Section 2 – Communication Format
`Section 2.2
`• Added headers for the Response Codes
`• Clarified non response processing for Master-to-Peripheral and Peripheral-
`to-Master communication.
`Section 2.3
`• Updated the Peripheral Address table for the Communications Gateway,
`Coin Hopper, Cashless Payment 1, and Experimental addresses
`• Defined the use of the experimental addresses
`Section 2.5
`• Added new RESET examples F & G.
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•8
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 13
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Section 5 – Coin Acceptor / Changer
`Section 5.2
`• Renamed the STATUS command to SETUP command
`• Added a new Possible Credited Coin Removal status code (0Dh)
`
`Section 6 – Bill Validator
`Section 6.2
`• Renamed the STATUS command to SETUP command
`• Added a new Possible Credited Bill Removal status code (0Ch)
`
`Section 7 – Cashless Device(s)
`
`
`
`
`
`(New Cashless Device #2)
`
`Changed name from Cashless Payment to Cashless Device
`
`Section 7.1
`• Added information regarding the dual addresses for two Cashless Device
`peripherals (10h and 60h)
`Section 7.3
`• Updated Command & Response table for dual addresses
`Section 7.4
`• Updated Command/Response Formats for dual addresses
`
`Section 8 – Communications Gateway
`Sections 8.1 through 8.6
`• Replaced former Audit Unit sections with new Communications Gateway
`Sections
`
`(New Peripheral)
`
`
`
`
`
`Section 9 –Universal Satellite Device (USDC)
`Section 9.3
`• Updated POLL table with proper number of bytes (FTL portion)
`• Changed “numeric row and column” to “Item Number”
`
`Section 10 – Coin Hopper or Tube – Dispenser
`
`Sections 10.1 through 10.5
`• Added complete new sections
`
`
`
`(New Peripheral)
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•9
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 14
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Version 2.0
`
`Version 2.0 of this specification is the second release of the international Multi-Drop
`Bus / Internal Communication Protocol (MDB / ICP). This specification is the
`culmination of effort put forth by technical members of NAMA, the EVMMA, and the
`EVA. The basis for this specification is the Version 1.0 international Multi-Drop Bus /
`Internal Communication Protocol (MDB / ICP) released on October 14, 1998.
`
`The following lists the primary revisions to the Version 2.0 of the MDB / ICP
`
`Introduction
`Foreword
`• Clarified that the Standard is a communication interface
`
`Section 1 - General Information
`Section 1.1
`• Added 3rd paragraph noting interface specification vs. system specification
`Section 1.3
`• Added entire Levels and Options section
`
`Section 2 - Communication Format
`Section 2.1
`• Changed Mode Bit Master-to-Peripheral text
`Section 2.2
`• Removed “command” from Master-to-Peripheral 4th paragraph
`• Changed RET description
`Section 2.3
`• Defined address 0000xxxB (00H) for VMC
`• Provided address information to show hexadecimal format
`Section 2.4
`• Changed format to 2.4.X sub-sections and added 2.4.4 on Levels
`Section 2.5
`• Changed RET description
`Section 2.6
`• Added complete File Transport Layer Section
`
`Section 3 - Bus Timing
`Section 3.1
`• Added 2nd sentence to tsetup
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•10
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 15
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Section 4 - Hardware Specification
`Section 4.3
`• Modified complete section and added AMP as alternate source to Molex
`Section 4.4
`• Added pin numbers to schematic
`
`Section 5 - Coin Acceptor / Changer
`Section 5.1
`•
`Provided additional address information
`Section 5.3
`•
`Added recommended RESET command sequence
`•
` Modified STATUS response to indicate Country / Currency Codes
`•
` Modified County / Currency Code to include ISO 4217 (Appendix A1)
`•
`Added Note 2 to DISPENSE (ODH) command
`•
`Added FTL POLLed responses
`•
`Added FTL “b3” option bit
`•
`Added FTL expansion commands
`•
`Cosmetic changes to all EXPANSION commands
`•
`Split ALTERNATIVE PAYOUT (0FH-02H) and PAYOUT STATUS (0FH-
`03H) command into two separate commands (cosmetic change only)
`•
`Added text to ALTERNATIVE PAYOUT (0FH-02H) Y1 description
`•
`Added Note 3 to ALTERNATIVE PAYOUT STATUS (0FH-03H)
`Section 5.5
`•
` Added “See Note 2 …” text
`•
` Added “If both peripherals supported” to Note
`
`Section 6 - Bill Validator
`Section 6.1
`•
`Provided additional address information
`Section 6.3
`•
`Added recommended RESET command sequence
`• Modified STATUS response to indicate Country / Currency Codes
`• Modified County / Currency Code to include ISO 4217 (Appendix A1)
`•
`Added Level 2 information
`•
`Added Level 2 option bytes w/ new EXPANSION COMMANDs:
`
`
`37H 01H
`Level 2 Option Bit Enable
`37H 02H
`Level 2 Identification
`•
`Added FTL POLLed responses
`•
`Added FTL “b0” option bit
`•
`Added FTL expansion commands
`• Modified last sentence in SECURITY command to link to Z9-Z10
` STATUS response
`Cosmetic changes to all EXPANSION commands
`
`•
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•11
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 16
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Section 6.5
`•
` Added “If both peripherals supported” to Note
`
`Section 7 - Cashless Payment
`Section 7.2 & 7.2.7
`•
`Added Level 03 Negative Vend Request
`Section 7.2.2
`•
`Changed 1st sentence to link Setup to 7.4.1 information
`Section 7.2.4
`•
`Added Negative Vend and Revalue
`Section 7.2.7
`•
`Added Level 03 Negative Vend Request
`Section 7.3
`•
`Added bold text regarding defining currency at the beginning of a session
`•
`Broke uninterruptable table into VMC Command and Reader Response
`•
`Added Level 03 NEGATIVE VEND REQUEST to VMC Command table
`•
`Added Level 03 DATA ENTRY REQUEST to Reader Response table
`•
`Highlighted command out of sequence hard resets from VMC
`• Moved Vend Failure Sequence to 7.4.8
`Section 7.3 – Table 1
`•
`Changed name to COMMANDS & RESPONSES
`•
`Changed Comment column to VMC / Reader Level Support
`•
`Linked all commands and responses to Levels
`•
`Added DATA ENTRY REQUEST POLLed responses
`•
`Added FTL POLLed responses
`•
`Added FTL commands
`•
`Added NEGATIVE VEND REQUEST responses
`•
`Defined 14H-1AH and 20H-FEH as “For Future Use”
`Section 7.4.1
`•
`Cosmetically modified RESET command sequence
`•
`Added 32 bit SETUP MAX/MIN PRICE
`•
`Changed text following Reader response
`Section 7.4.2
`•
`Clarified Level 01 information (reader has no revalue capability)
`•
`Added Level 03 information
`• Modified SETUP response to indicate Country / Currency Codes
`• Modified County / Currency Code to include ISO 4217 (Appendix A1)
`•
`Added bold Note in Z3-Z4 County / Currency Code
`•
`Added definition for Miscellaneous Options “b4 – b7”
`Section 7.4.3
`•
`Added Level 03 SETUP if Expanded Currency Mode
`Section 7.4.4
`•
`Added Level 03 BEGIN SESSION response if Expanded Currency Mode
`•
`Added Level 03 VEND APPROVED response if Expanded Currency Mode
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•12
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 17
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`•
`•
`•
`
`Added Level 03 PERIPHERAL ID response if Expanded Currency Mode
`Clarified COMMAND OUT OF SEQUENCE definition
`Added Level 03 REVALUE LIMIT AMOUNT response if Expanded Currency
`Mode
`•
`Added Level 03 DATA ENTRY REQUEST response if Data Entry Mode
`•
`Added Level 03 DATA ENTRY CANCEL response if Data Entry Mode
`•
`Added Level 03 FTL REQ TO RCV response if FTL Mode
`•
`Added Level 03 FTL RETRY / DENY response if FTL Mode
`•
`Added Level 03 FTL SEND BLOCK response if FTL Mode
`•
`Added Level 03 FTL OK TO SEND response if FTL Mode
`•
`Added Level 03 FTL REQ TO SEND response if FTL Mode
`Section 7.4.5
`•
`Added Level 03 VEND command if Expanded Currency Mode
`•
`Added Level 03 VEND APPROVED response if Expanded Currency Mode
`Section 7.4.8
`•
`Added Vend Failure (from 7.3)
`Section 7.4.10
`•
`Added Level 03 VEND command if Expanded Currency Mode
`Section 7.4.11 (new)
`•
`Added complete Level 03 NEGATIVE VEND Request section
`Section 7.4.15 (new)
`•
`Added complete Level 03 DATA ENTRY Request section
`Section 7.4.16
`•
`Added Level 03 REVALUE Request command if Expanded Currency Mode
`Section 7.4.17
`•
`Added Level 03 REVALUE Limit Request command if Expanded Currency
`Mode
`Section 7.4.18
`•
` Added Level 03 EXPANSION REQUEST ID response if Expanded
`Currency Mode
`Section 7.4.22
`•
`Added Level 03 EXPANSION ENABLE OPTIONS command
`Section 7.4.23
`•
`Added Level 03 FTL REQ TO RCV command & responses if FTL Mode
`Section 7.4.24
`•
`Added Level 03 FTL RETRY / DENY command if FTL Mode
`Section 7.4.25
`•
`Added Level 03 FTL SEND BLOCK command & response if FTL Mode
`Section 7.4.26
`•
`Added Level 03 FTL OK TO SEND command if FTL Mode
`Section 7.4.27
`•
`Added Level 03 FTL REQ TO SEND command & responses if FTL Mode
`Section 7.7
`•
`Added Example Vend Session #10 (Single Negative Vend)
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•13
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 18
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Section 8 - Audit Device
`Section 8.1
`•
`Provided additional address information
`Section 8.3
`•
`Added FTL POLLed responses
`•
`Added FTL “b3” option bit
`•
`Added FTL expansion commands
`
`Section 9 - Universal Satellite Device
`Section 9.1
`•
`Provided additional address information
`Section 9.3
`•
`Added FTL POLLed responses
`•
`Added FTL “b2” option bit
`•
`Added FTL expansion commands
`Document Revision History
`•
`Deleted
`
`Appendix 1 - Currency Codes
`• Added entire section (based on ISO 4217)
`
`Appendix 2 - Battery Operated Card Reader
`• Added entire section
`
`__________________________________________________________________
`Version 1.0
`
`Version 1.0 of this specification is the first release of the international Multi-Drop Bus /
`Internal Communication Protocol (MDB / ICP). This specification is the culmination
`of effort put forth by technical members of NAMA, the EVMMA, and the EVA. The
`basis for this specification is the International Multi-Drop Bus Interface Standard
`published by NAMA and the Internal Communication Protocol published by the
`EVMMA. The NAMA document was originally introduced on October 19, 1993 and later
`revised on August 19, 1994, June 20, 1997, and October 15, 1997. The EVMMA
`document was adopted in 1994 and later revised in 1995.
`
`The following lists the primary revisions to the original two documents which were
`“combined” to create Version 1.0 of the MDB / ICP. In actuality, the NAMA MDB was
`the basis of the MDB / ICP with the exception of Section 7 which came from the
`EVMMA ICP. Besides typographical corrections and actual feature changes (below),
`the entire document was edited to provide a more uniform appearance.
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•14
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 19
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`The following lists the primary revisions to the Version 1.0 of the MDB / ICP.
`
`Hardware Specification - Section 4.3
`•
`Added drawings of the MDB male and female connectors.
`
`Coin Acceptor / Changer - Section 5.3
`•
`Added Expansion commands:
`0F-05 Send Current Diagnostic Status
`0F-06 Send Controlled Manual Fill Report
`0F-07 Send Controlled Manual Payout Report
`
`Coin Acceptor / Changer - Section 5.5
`•
`Added coin acceptance and coin payout power requirements for coin
`changers using motorized payout mechanisms.
`Added note about simultaneously supplying bill validator transport power.
`
`•
`
`Bill Validator - Section 6.5
`•
`Added note about simultaneously supplying coin mechanism coin
`acceptance power.
`
`Cashless Payment - Section 7.2.6
`•
`Added Level 02 Revalue capability.
`
`Cashless Payment - Section 7.3
`•
`Added Level 02 REVALUE REQUEST.
`•
`Removed NAK (NCK) response from uninterruptable state and
`unexecutable command descriptions.
`•
`Eliminated the BUSY response to vend failure sequences.
`• Modified Table 1 per above.
`
`Cashless Payment - Section 7.4.1
`•
`Further defined the initializing sequence following a RESET command.
`
`Cashless Payment - Section 7.4.2
`•
`Further defined the Z7 Application Maximum Response Time.
`•
`Added Z8 – b3 for supporting the VEND/CASH SALE subcommand.
`
`Cashless Payment - Section 7.4.4
`•
`Begin Session (03h) - Added Level 02 Reader Z4-Z10 data.
`• Malfunction/Error (0Ah) - Added error code 1100 (refund error).
`•
`Command Out of Sequence (0Bh) - Added Z2 data.
`•
`Eliminated Busy (0Ch) response.
`•
`Added Level 02 Reader Revalue Approved (0Dh) response.
`•
`Added Level 02 Reader Revalue Denied (0Eh) response.
`•
`Added Level 02 Reader Revalue Limit Amount (0Fh) response.
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•15
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 20
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`•
`•
`
`Added Level 02 Reader User File Data (10h) response.
`Added Level 02 Reader Time/Date Request (11h) response.
`
`Cashless Payment - Section 7.4.10
`•
`Added Level 01 Reader CASH SALE (13h/05h) VMC command.
`
`Cashless Payment - Section 7.4.14
`•
`Added Level 02 Reader Revalue - Request (15h/00h) VMC command.
`
`Cashless Payment - Section 7.4.15
`•
`Added Level 02 Reader Revalue – Limit Request (15h/01h) VMC
`command.
`
`Cashless Payment - Section 7.4.17
`• Obsoleted EXPANSION – Read User File (17h/01h) VMC command.
`
`Cashless Payment - Section 7.4.18
`• Obsoleted EXPANSION – Write User File (17h/02h) VMC command.
`
`Cashless Payment - Section 7.4.19
`•
`Added Level 02 Reader Write Time/Date File (17h/03h) VMC command.
`
`Cashless Payment - Section 7.5
`•
`Further defined the non-response time with the “Application Maximum
`Response Time” Z7.
`
`Cashless Payment - Section 7.6 (original ICP Spec)
`• Moved this section (ICP Payment Media Return Button) to Section 7.3.2.
`
`Cashless Payment - Section 7.6 (MDB/ICP Spec)
`•
`Previously was the ICP 7.7 with no modifications.
`
`
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•16
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 21
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`
`
`(this page intentionally left blank)
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`r•17
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 22
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Introduction
`
`
`
`Foreword
`
`This voluntary Standard contains basic requirements for a vending machine
`communication interface within the limitations given below and in the General
`Information section of this Standard. These requirements are based on sound
`engineering principles, research, field experience, and an appreciation of the problems
`of manufacture, installation, and use derived from consultation with and information
`obtained from manufacturers, users, and others having specialized experience. These
`requirements are subject to revision as further experience and investigation may show it
`necessary or desired.
`
`NAMA, in performing its functions in accordance with its objectives, does not assume or
`undertake to discharge any responsibility of the manufacturer or any other party. The
`opinions and findings of NAMA represent its professional judgment given with due
`consideration to the necessary limitations of practical operation and state of the art at
`the time the NAMA Standard is processed. NAMA shall not be responsible to anyone
`for use or reliance upon Standard by anyone. NAMA shall not incur any obligation or
`liability for damages, including consequential damages, arising out of or in connection
`with the use, interpretation of, reliance upon this Standard.
`
`Standard Review
`
`A complete review of this standard shall be conducted at least every five years to keep
`requirements consistent with technology. These reviews shall be conducted by
`representatives from industry and user groups on the NAMA Vending Technology
`Standards Committee at that time.
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`I•1
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 23
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`(this page intentionally left blank)
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`I•2
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 24
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`Section 1
`
` General Information
`
`1.1 Introduction
`
`This document defines a serial bus interface for electronically controlled vending
`machines. The interface is a 9600 baud Master-Slave arrangement where all
`peripherals are Slaves to a Master controller.
`
`The intent of this document is to standardize vending machines that employ electronic
`control (traditionally known as vending mechanism controller - VMC) so that all vending
`and peripheral equipment communicates identically.
`
`It should be noted that this document is a vending machine interface / protocol
`specification and not a vending machine system specification. Each machine
`manufacturer should provide a specification on the overall operation of the machine.
`
`1.2 Operational and Application Notes
`
`The serial bus, or Multi-Drop Bus (MDB) is configured for Master-Slave operation.
`There is one Master with capability of communicating with up to thirty-two peripherals.
`The Master is defined as the Vending Machine Controller (VMC).
`
`Each peripheral is assigned a unique address and command set. The master will “poll”
`the Bus for peripheral activity. That is, each peripheral is asked for activity, and
`responds with either an acknowledge, negative acknowledgment, or specific data
`dependent on its current activity. If a peripheral does not respond within a predefined
`time, (t-non-response as defined in the peripheral sections) it is assumed that it is not
`present on the Bus.
`
`Bus interference, or “crashes” are prevented because each peripheral only responds
`upon being polled. Since there is only one master, and all communication is initiated by
`the Master, Bus “crashes” are easily precluded.
`
`All peripherals will recognize a disable command, or commands, sent by the Master.
`This allows for disabling of individual peripherals for various reasons, for example,
`power management techniques.
`
`Error checking and correction is accomplished by using checksums (CHK) and a
`retransmit command.
`
`MDB/ICP Version 4.2
`
`February, 2011
`
`1•1
`
`Petitioners Kiosoft Technologies, LLC, et al.
`Exhibit 1006
`Page 25
`
`

`

`Multi-Drop Bus / Internal Communication Protocol
`
`1.3 Levels and Options
`
`Since the introduction of the earliest Multi-Drop Bus specification, functional levels and
`operational options have been established for most of the peripherals on the MDB/ICP
`interface. These have provided the capability for new features to be implemented as
`new requirements and features were needed for the international vending industry.
`
`1.3.1 Levels
`Levels of peripheral functionality were established when a major change occurred in the
`peripheral that added extended commands and responses. Due to potential conflicts
`between a VMC level and a peripheral level, neither the VMC nor the peripheral should
`issue a command or reply with a response that is not supported by the other device.
`
`The VMC must initially determine (via the appropriate STATUS or SETUP command)
`the level of a peripheral before determining which commands it can issue to that device.
`A VMC must only send commands that are supported by the peripheral. For
`example, a Level 3 command may only be issued to a Level 3 or higher peripheral and
`must not be issued to a Level 1 or 2 peripheral.
`
`The Cashless Payment and the Universal Satellite Device can also learn the respective
`level of the VMC for that device. This information is sent via the SETUP command. It
`is the responsibility of the peripheral to only send responses that are supported
`by the VMC. For example,