![IDTECH Vivopay Neo 2 Developer'S Manual Download Page 308](http://html.mh-extra.com/html/idtech/vivopay-neo-2/vivopay-neo-2_developers-manual_618786308.webp)
NEO 2 Interface Developer’s Guide
Copyright © 2019, International Technologies & Systems Corporation. All rights reserved.
308
Mifare Write Block Data Field
Data Field
Length
(bytes)
Description
Card & Block Count
1
Card Type: [Bit 7..4]
This can only indicate the following cards
Mifare Type A (Standard)
Mifare Type A (Ultralight)
The values for these card types are defined in the “Poll for Token” command
(consider only the lower 4 bits).
Block Count: [Bit 3..0]
This is the number of blocks that are written. The Block Count cannot be
greater than 15. This count does not include the skipped blocks if the card is a
Mifare Standard card.
Start Block
1
This is the card block number from which the reader starts writing.
Data to Write
Variable
(multiple of
block size)
Data to write to the Card.
The length of the data to be written to the card depends on the number of
blocks to be written and the card type.
After receiving the
Command Frame
the ViVOpay reader verifies the parameters. If the
parameters are valid, it writes the data to the card. If this operation is successful, the ViVOpay
reader sends a
Response Frame
with a Status of OK.
If the
Command Frame
is invalid or the write operation fails then the reader sends a
Response
Frame
with an appropriate Status.
Response Frame
Byte 0-9
Byte 10
Byte 11
Byte 12
Byte 13
Byte 14
Byte 15
Header Tag &
Protocol Version
Command
Status Code
Data Length
(MSB)
Data Length
(LSB)
CRC (MSB)
CRC (LSB)
ViVOtech2\0
2Ch
See
00h
00h
8.16.4.
Mifare ePurse Command (2C-0A)
Use this command to instruct the ViVOpay reader to carry out Debit, Credit and Backup
operations on value blocks in a Mifare card. These functions require that the related data
blocks be formatted as a value block and that operations and keys used match the defined
Access Conditions for that sector.
The following illustration shows the format of a value block: