超过460,000+ 应用技术资源下载
pdf

MDB协议自动售货机非现金支付部分及串口测试方法

  • 1星
  • 日期: 2017-06-18
  • 大小: 3.65MB
  • 所需积分:0分
  • 下载次数:27
  • favicon收藏
  • rep举报
  • 分享
  • free评论
标签: MDB协议串口

自动售货机MDB标准协通信议V4-2版中的非现金支付部分,同时附加了一些非常有用的文档,比如能够通过串口连接MDB支付设备。通过串口如何连接自动售货设备的MDB支付接口实现移动支付。以及如果通过串口测试NAYAX的MDB非现金支付设备。

文档内容节选

MultiDrop Bus Internal Communication Protocol MDB ICP 无现金支付部分 MDB 协议文本阅读说明: 第 1 到第 68 页 MDB V42 标准协议无现金支付部分 第 69 到第 74 页 威佛 MDBRS232 快速使用串口连接 MDB 支付设别 第 75 页到 78 页 威佛 RS232MDB 快速使用串口连接售货机 MDB 接口 第 79 页 以色列 NAYAX 的 MDB 非现金支付设备串口测试讲解 MultiDrop Bus Internal Communication Protocol Section 7 Cashless Devices VMCPeripheral Communication Specifications 71 Introduction This section defines the communications bytes sent and received between the cashless devic......

Multi-Drop Bus / Internal Communication Protocol MDB / ICP (无现金支付部分) MDB 协议文本阅读说明: 第 1 到第 68 页 MDB V4.2 标准协议无现金支付部分 第 69 到第 74 页 威佛 MDB-RS232 快速使用(串口连接 MDB 支付设别) 第 75 页到 78 页 威佛 RS232-MDB 快速使用(串口连接售货机 MDB 接口) 第 79 页 以色列 NAYAX 的 MDB 非现金支付设备串口测试讲解 Multi-Drop Bus / Internal Communication Protocol Section 7 Cashless Device(s) VMC/Peripheral Communication Specifications 7.1 Introduction This section defines the communications bytes sent and received between the cashless device(s) and the Vending Machine Controller (VMC). As defined in Section 2.3, there are two cashless device addresses; Cashless #1, 00010xxxB (10H) and Cashless #2, 11000xxxB (60H). The second address has been assigned to allow for two unique forms of cashless devices to be resident in the vending machine simultaneously. An example would be a card based system as Cashless Device #1 (10H) and a mobile phone based system as Cashless Device #2 (60H). Everything defined in this section will be common to the two cashless devices – only the addresses will be different. Unless otherwise stated, all monetary values used by the cashless devices and the VMC will be sixteen bit (Level 01 & 02) or thirty-two bit (Level 03 if 32 bit option enabled), unsigned binary numbers. The numbers will be sent most significant byte first and scaled using the parameters provided by the cashless device’s READER CONFIGURATION DATA response. 7.2 State Definitions MDB cashless devices may be viewed as state machines. These states are as follows: 1) Inactive 2) Disabled 3) Enabled 4) Session Idle 5) Vend 6) Revalue (Level 02/03 cashless devices) 7) Negative Vend (Level 03 cashless devices) 7.2.1 Inactive This is the state of the cashless device at power up or after a reset. While in the Inactive state, cashless devices will NOT be accepted for vending purposes. The cashless device cannot leave this state until all Setup information is received from the VMC. 7.2.2 Disabled The cashless device automatically enters this state from the Inactive state when it has received the Setup information specified in 7.4.1. It will also enter the Disabled state from the Enabled state when it receives the READER DISABLE command. While in the Disabled state, payment medias will NOT be accepted for vending purposes. The cashless device will remain in this state until either a READER ENABLE command is received (when it will enter the Enabled state) or a RESET is received (when it will enter the Inactive state). For power MDB/ICP Version 4.0 April, 2009 7•1 Multi-Drop Bus / Internal Communication Protocol management purposes, current consumption will not exceed idle mode specification during disabled state. 7.2.3 Enabled In this state, cashless devices may be used for MDB transactions. The cashless device will remain in this state until a valid payment media is read (when it will enter the Session Idle state), a READER DISABLE command is received (when it will return to the Disabled state) or a RESET is received (when it will enter the Inactive state). 7.2.4 Session Idle In the Enabled state, when a valid payment media is processed, the cashless device will issue a BEGIN SESSION response to a VMC POLL and enter the Session Idle state. This indicates that the cashless device is available for vending activities. The only structured exit from the Session Idle state is through the SESSION COMPLETE message from the VMC. The SESSION COMPLETE command will cause the cashless device to respond with an END SESSION message and enable/disable itself appropriately. Vend / Negative Vend / Revalue commands will cause the cashless device to leave the Session Idle state and enter the Vend / Negative Vend / Revalue state when products are selected and purchased. 7.2.5 Vend This state is entered from the Session Idle state upon reception of a VEND REQUEST message from the VMC. The entire Vend state is an uninterruptable command/response sequence. The cashless device will return to the Session Idle state upon completion of this sequence. (Level 02 / 03 Cashless Devices) 7.2.6 Revalue This state is entered from the Session Idle state upon reception of a REVALUE REQUEST message from the VMC. The entire Revalue state is an uninterruptable command/response sequence. The cashless device will return to the Session Idle state upon completion of this sequence. 7.2.7 Negative Vend Request (Level 03 Cashless Devices) This state is entered from the Session Idle state upon reception of a NEGATIVE VEND REQUEST message from the VMC. The entire Negative Vend Request state is an uninterruptable command/response sequence. The cashless device will return to the Session Idle state upon completion of this sequence. 7.3 Command Protocol After the VMC has issued a command, no new commands may be issued until all data generated in response to that command has been received from the cashless device. The complete response may be an ACK only (e.g. the READER ENABLE command). Alternatively, it may consist of an informational response (e.g. READER CONFIGURATION DATA). MDB/ICP Version 4.0 April, 2009 7•2 Multi-Drop Bus / Internal Communication Protocol The cashless device may provide an informational response in two ways. It may respond immediately with the requested data, or the cashless device may ACK the VMC command. If ACKed, the VMC must issue POLLs until the cashless device responds with the requested data, or until the Application Maximum Response Time (defined in READER CONFIGURATION response) has elapsed. The cashless device will define the currency type at the beginning of each session. The currency type will be used for all following transactions in that session. If the VMC does not support this currency type, it will end the session. Below are the uninterruptable VMC commands which require an informational cashless device response and their associated result: VMC Command SETUP/CONFIGURATlON DATA => Cashless Device Response Result READER CONFIGURATION DATA PERIPHERAL ID CANCELLED EXPANSION/REQUEST ID => READER CANCEL => VEND REQUEST... VEND CANCEL => VEND DENIED* VEND DENIED* VEND REQUEST => VEND APPROVED => VEND REQUEST => VEND APPROVED => VEND REQUEST => NEGATIVE VEND REQUEST => NEGATIVE VEND DENIED* NEGATIVE VEND NEGATIVE VEND REQUEST => APPROVED => NEGATIVE VEND APPROVED => REVALUE APPROVED/DENIED* END SESSION NEGATIVE VEND REQUEST => REVALUE REQUEST=> VEND SUCCESS* VEND FAILURE* NEGATIVE VEND SUCCESS* NEGATIVE VEND FAILURE* SESSION COMPLETE => *These VEND / NEGATIVE VEND / REVALUE REQUEST response sequences constitute the Vend / Negative Vend / Revalue Request states. Below are the uninterruptable POLLed cashless device which require an informational response from the VMC: VMC Command & Data POLL => Cashless Device Response Result DATA ENTRY REQUEST + DISPLAY REQUEST (optional) DATA ENTRY CANCEL Cancelled Cancelled POLL => DATA ENTRY RESPONSE w/ FFs => Any command may be issued by the VMC at anytime providing the above command protocol is observed. There are four exceptions to this rule: 1) VEND REQUEST, REVALUE REQUEST, and NEGATIVE VEND REQUEST response sequences may only be initiated in the Session Idle state. MDB/ICP Version 4.0 April, 2009 7•3 Multi-Drop Bus / Internal Communication Protocol 2) The VMC may issue a VEND CANCEL command after issuing a VEND REQUEST, but before receiving a VEND APPROVED/DENIED response. In this case the cashless device will issue a VEND DENIED response to satisfy the original VEND REQUEST response requirement. 3) The cashless device may issue DISPLAY REQUESTs in response to POLLs at any time, if the VMC’s display is available for use. 4) The RESET command is allowed at any time, it is not subject to any restrictions. If a VMC command is received by the cashless device while it is in one of the preceding uninterruptable states, the following will occur: The cashless device will ACK the offending command (no data response will be forthcoming). The cashless device will respond to the next poll with the “COMMAND OUT OF SEQUENCE” response (0BH). It should be pointed out to cashless device developers that a command out of sequence will always cause the VMC to issue a RESET command to the cashless device. 7.3.1 Multi-Message Response Format The multi-message response format permits the cashless device to send multiple messages in response to a single command or POLL. Because all messages are of a fixed length, there is no confusion determining where one message ends and the next message begins. (The total message length is subject to the 36 byte limit imposed by Section 2 of this standard.) For example, if a cashless device fails to correctly write a payment media after a VEND REQUEST, it may need to report: 1) VEND DENIED 2) MALFUNCTION/ERROR subcode 07h 3) SESSION CANCEL REQUEST The multi-message response (hex) would look like this: 06 0A 07 04 1B* 1 2 3 4 The first byte above (marked 1) is the VEND DENIED message. The next two bytes (marked 2) are the MALFUNCTION/ERROR message. The third and final message is the CANCEL SESSION REQUEST (marked 3). An eight bit checksum with the mode bit set (marked 4) finishes the message. It is important to note that the controller must service the messages in the order in which they are received. This is necessary to ensure that command protocol is maintained. MDB/ICP Version 4.0 April, 2009 7•4
更多简介内容

推荐帖子

自动售货机的前世今生
自动售货机被称为 24小时营业的微型自助超市,又称自动贩卖机,它的售货领域非常广泛,是绝大多数发达国家商品零售的主流零售模式。      自动售货机(自动贩卖机)最早是1888年出现的“投币式口香糖自动售货机”,至今已经历了130年的历史。自20世纪70年代,自动售货机(自动贩卖机)在日本、欧美等发达国家呈现爆发式发展,逐渐成为一种主流的销售和消费方式。       1999年,自动售货机(自动
lct2000 工控电子
串口测试
各位大神,本人刚学习嵌入式,在测试串口程序时,想通过无线模块来接收和发送数据,模块的波特率是19200,固定的了,不知道以下这个程序怎么修改波特率?改来改去都没效果。    # include # include # include # include # include # include # include # include # include stat
林晓松 【Linux与安卓】
Z-Stack协议栈串口打印乱码问题的可能性及解决办法
在通过串口打印的时候,经常出现乱码现象,分析可能的原因 ​1.配置有误 这个是最低级,最不应该发生的错误了,如果你调试了半天,结果发现是自己波特率设置或者是其他串口相关配置不正确,是不是有种想抽自己几个耳光的冲动。 ​ 2.串口助手的问题 这是可能发生的。我在用一个串口助手调试了大半天后,发现怎么调试都是乱码,无奈抱着试试看的心理换了一个串口助手,奇迹出现了,竟然不再乱码了 ​ 3.
fshchh 【Zigbee 部落】
关于解读串口设备返回的数据问题,请帮忙看看,如何把根据协议把A9 03解析为937……
通讯是RS485协议,其中关于返回数据的格式如下: SM 返回: DATAINFO(9字节):                 桶底BOTTOM(2字节);                 下一次新记录存放指针 SAVEP(2字节);                 下一次读取记录位置指针 LOADP(2字节)                                SM已修改L
jesfei 嵌入式系统编程
SenSorTile串口测试实验
  昨天在测试官网提供的DataLog程序时因为驱动问题,所以官方程序我就无法直接测试使用了,所以我决定全部推翻自己编写程序,自己测试。所以今天的第一步就是在自己最初的LED点灯案例上添加了串口,对于板子上面的串口我的理解为有以下两个方案。 1、使用USART5,所使用的两个引脚也就是与USB的两个引脚相同,只需要进行相应的设置久好了。不过需要对SB11、SB21、SB10,、S20进行相应的焊
李炳1991 【意法半导体SensorTile专区】
串口
if(ReceiveBuf==0x55) { SBUF= SendBuf[0]; //若接收到的是0x55,则将SendBuf[0]中的0xaa发送出去 while(!TI); //等待发送 TI=0; //若发送完毕,将TI清0 P2=0x00; BEEP=0; Delay_ms(500);  BEEP=1; }   请问各位大哥,这个程序能实现吗。当输入0x55,
lpfzhx 嵌入式系统编程

评论


个人中心

意见反馈

求资源

回顶部

下载专区


TI最新应用解决方案

工业电子 汽车电子 个人电子

搜索下次设计所需的
TI 器件

● 目前在售器件有45,000款
● 6.99美元标准运费,不受时间和地点限制
● 无最低起订量要求

About Us 关于我们 客户服务 联系方式 器件索引 网站地图 最新更新 手机版

EEWorld电子技术资料下载——分享有价值的资料

北京市海淀区知春路23号集成电路设计园量子银座1305 电话:(010)82350740 邮编:100191

电子工程世界版权所有 京ICP证060456号 京ICP备10001474号 电信业务审批[2006]字第258号函 京公海网安备110108001534 Copyright © 2005-2018 EEWORLD.com.cn, Inc. All rights reserved
$(function(){ var appid = $(".select li a").data("channel"); $(".select li a").click(function(){ var appid = $(this).data("channel"); $('.select dt').html($(this).html()); $('#channel').val(appid); }) })