Skip navigation

Near Field Communication (NFC) is a set of standards for short-range radio communication for data exchange. There are two types of NFC technology in use: Passive NFC devices and Active NFC devices. Passive NFC devices are tags with simple electronics that are powered by the NFC reader, which can be read from and written to as a small storage device but cannot perform any other tasks.

 

An Active NFC device can communicate information freely back and forth, exchanging data without limitations. Active NFC devices can also write to and read from Passive NFC devices. At least one Active NFC device is required for NFC to operate with another Active or Passive NFC device.

 

While all ZQ500™ series printers have a Passive tag (Print Touch) containing manufacturing information on the side of the unit, some models of ZQ500 series printers include a printer operating system controlled emulated Passive NFC functionality. The ZQ500 series implementation includes functionality as an emulated Passive NFC device, in which Active NFC devices can read from and write to the printer as if it were a Passive (non-powered) NFC device.


Click to read the full Application Note on Active Near Field Communication

Daniel Quagliana

HTTP Post

Posted by Daniel Quagliana Expert Dec 2, 2015

HTTP POST is a request method supported by the HTTP protocol, commonly used on the World Wide Web. The POST request method is designed to request that the web server being communicated with open a connection channel allowing the transfer of data that is included in the body of the request.

The feature is linked with the internal HTTP webserver in the printer, which by default serves up a page with printer configuration information. The HTTP POST feature is controlled by the SetGetDo (SGD) commands, which are outlined below.

When printing is done via HTTP POST, the data sent to the printer must always be in ZPL® format, regardless of the printer’s device.language SetGetDo command setting.

No responses can be made via HTTP POST; it is not implemented as a bi-directional protocol. In practice, this means that no query commands (such as ^HH or ~HS) should be used via HTTP POST. Any data returned from the printer as a result of commands sent via HTTP POST will be discarded.

 

Click to read the full Application Note on HTTP Post

An updated version of the Link-OS Multiplatform SDK has been released and is now available for download.  It is recommended that all new development be done with these new versions due to bugs being addressed.

 

Product

Version

Link-OS SDK

Android

2.9.2275

iOS

1.4.948

PC

2.9.2275

Windows Mobile/CE

1.1.123

Blackberry

1.0.37

Available on the website

Link-OS Multiplatform SDK Page

 

Changes are documented in the Readmes and listed below:

  1. Android
    1. Improved handling of Link-OS printers using JSON settings format and Multi-part Form download where possible.
    2. The PrintConnect for Android app is included in the installation.
    3. The source code for the TestConnect app is included. TestConnect demonstrates how to print using PrintConnect.
  2. iOS
    1. Bug fixes, including a fix for the timeout issue many have encountered.
  3. PC (Java-based)
    1. Added a driverless USB connection type for Windows
    2. Improved handling of Link-OS printers using JSON settings format and Multi-part Form download where possible.
  4. Webservices
    1. Improved handling of Link-OS printers using JSON settings format and Multi-part Form download where possible.
  5. Windows Mobile and Windows CE
    1. Updated the InTheHand Bluetooth library to the latest available version.
  6. Blackberry
    1. No changes

The Zebra Printer ISV Engineering team will be off for the USA Thanksgiving holiday November 26 & 27.  Please understand there may be a delay in answering any questions posted during that time.

After reviewing testing results of ISV Validations & White Listing the Printer ISV team identified a large number of apps failing our tests.  Many of the failures fell into a few basic categories such as verifying the proper printer formatting language (i.e. ZPL vs Line Mode) and checking the status of the printer before sending a print job.

 

To help developers improve the quality of their apps we have documented Best Practices in Creating a Printing Application for Zebra Printers.  We are also working to incorporate these standards into the sample code we have published.

 

Please give it a read and let us know your thoughts or if you think we have missed anything.

Filter Blog

By date:
By tag: