Emdk

Zebra Scanner is reading partial bar codes on some occasions when part of the bar code is hidden

Zebra TC75x Scanner is reading partial bar codes on some occasions when part of the bar code is hidden. We are using EMDK version 4.0. The device's Android version is 7.x.

If we set the expected barcode length(s) in the Scanner config object as shown below, then it is working fine for barcodes of the length specified.

-------------------------
ScannerConfig config = scanner.GetConfig();

Migrating from EMDK to Datawedge

Hey,

Currently, we use the Zebra scanners with EMDK integrated into our app. I've been reading the techdoc and noticed that Zebra "strongly recommends using DataWedge for all applications that require barcode scanning and data capture." It seems like Zebra will also always keep Datawedge up to date first.

So my question is, is it worthwhile to migrate from EMDK to Datawedge? If anyone has migrated before, how difficult is the process?

Thanks a lot!

DataWedge APIs for Notificication.LEDParams and Notification.Beep , similar to EMDK

As stated in the Subject, are there any existing Datawedge APIs for sending Notification params to toggle the LED and Beep actions for bluetooth scanners like RS 507.
There are APIs existing in EMDK for this and would like to know if they are available for DataWedge?

Kotlin and developing Kotlin applications for Zebra devices

It is not news for Android developers that following Google’s announcement of Kotlin support during Google I/O 2017, Google have embraced Kotlin as the preferred development language for Android, even to the extent that the “Build your first app” tutorial on the Android developer site will default to showing Kotlin code.

 

Moving from the EMDK Data Capture Profile to Datawedge

The EMDK Data Capture profiles enable a user to configure barcode scanning and card reading within their application.

Website.png

 

Data Capture profiles have been removed from the latest versions of EMDK, the links in this article have been updated to reflect versions of the EMDK which included this feature.