![IDTECH Vivopay Neo 2 Developer'S Manual Download Page 307](http://html.mh-extra.com/html/idtech/vivopay-neo-2/vivopay-neo-2_developers-manual_618786307.webp)
NEO 2 Interface Developer’s Guide
Copyright © 2019, International Technologies & Systems Corporation. All rights reserved.
307
a read is requested starting at Block 3 and Block Count is 2 then 16*2=32 bytes of data are
returned consisting of Page # 3, 4, 5, 6, 7, 8, 9, and 10.
Typically
, Mifare Ultralight Cards are read by the ViVOpay reader, but are not written. This is
because they are typically used for disposable applications such as ticketing.
8.16.3.
Mifare Write Blocks (2C-08)
Use this command to instruct the ViVOpay reader to write data to one or more blocks on the
Mifare Card. The terminal can instruct ViVOpay to write up to 15 blocks of data using this
command. If more than one block is defined, then the reader automatically writes to the
starting block and the blocks that follow.
The block size depends on the type of Mifare card being accessed. For Mifare Standard Cards
the block size is 16 bytes. For Mifare Ultralight Cards the block size is 4 bytes.
If the card specified is a Mifare Standard card, then the terminal must have successfully sent
at least one
command to the reader for the first block to write. This
does not authenticate the block; it stores a key for use by the reader as it performs reads and
writes.
If the card specified is a Mifare Standard card and the write command is a single block write,
the reader tries to write the data regardless of whether the block is a sector trailer block or
not.
If the card specified is a Mifare Standard card, and the write is a multi-block write, then the
reader skips writing to the sector trailer blocks that contain the Keys. Skipped blocks are not
included in the block count. While writing blocks to a Mifare Standard Card, if the write requires
access to the next sector, then the ViVOpay reader carries out authentication for this
block/sector automatically by using the Key Type and Key Value that were used by the
terminal to authenticate the sector for the Starting Block via the
command.
Block reads and writes that span multiple sectors assume that the keys to authenticate
those sectors are the same as the one that was set using the Mifare Authenticate Block
command.
Command Frame
Byte 0-9
Byte 10
Byte 11
Byte 12 Byte 13
Byte 14 …
Byte 14+n-1
Byte 14+n
Byte 15+n
Header Tag &
Protocol
Version
Command
Sub-
Command
Data
Length
(MSB)
Data
Length
(LSB)
Data
CRC (MSB)
CRC (LSB)
ViVOtech2\0
2Ch
08h
Variable Variable See Table below