DataWedge provides a convenient mechanism for non-scanning aware applications to receive data from embedded or connected data capture devices. DataWedge v2.02.03 builds on v2.01.02 to include the following new features...
- Support for Inter Character Delay
- Hide devices that are not available such as RFID
- Added support for Gen2 RFID parameters
- Support re-connection on resume for external Bluetooth scanners
- Support re-connection on resume for MSR
- Added support for Aztec barcode type
- DataWedge now supports the ASCII range from 1 to 127 including all Control Characters and provides extended ASCII support
- Log window removed.
- Device support added for...
- WT4090 WinCE 5.0
- VC5090 WinCE 5.0
- In addition following improvements and bug fixes were made...
- Change default value of Serial option to "Send data after X seconds" from "Send data after CR received"
- RFID can now be disabled through registry
- Fixed EAN13 settings persistence issue
- Fixed Carriage Return issue in Pocket Word for CE
- DataWedge command line Shutdown feature was fixed to support shutdown
- CAPS LOCK issue with Remote Desktop Client was fixed
- Feedback window now displays Wave files for Windows Mobile 5.0
- Fixed some issues with dialog inconsistencies
- Fixed issues pertaining to AutoPIE feature
- Fixed a bug where DataWedge was getting stuck in some platform releases in MC9060 and OEM 28 version of MC9090. This was fixed by introducing a feature to deactivate RFID in systems that do not have RFID reader hardware. Please refer to section 5.5 of the DataWedge User Guide for further details.
- Fixed a issue where there were inconsistencies when sending serial data, when "Send data after X number of seconds" was enabled.
- Fixed issue when scanning PDF417 barcodes that contain characters from the extended ASCII table; DataWedge reported incorrect hex values for those characters when switching from standard text to hex string.
- Fixed issue where CAPSLOCK is not (sometimes) detected in Remote Desktop when connection is created after a CAPSLOCK press.
- Fixed issue where a HTML page containing text fields was opened with IE and you tried to scan a TAB character (Code128), the focus was not moved to next field
- Fixed issue with configuring LED Time for Barcode feedback settings.
- Now Data Source in the Test dialog will be updated when RFID tag scanned.
- RFID tag range problem is fixed and now displays tags only if the tag count is within the range
- By default at startup DataWedge Disables/Hides the following devices depending on the given conditions
- RFID - if RFIDAPI32.DLL is not found
- MSR - if MSRAPI32.DLL is not found
- Serial - if serial port cannot be opened
At the same time registry is updated to denote that those devices are disabled. However, if above devices are disabled at startup it becomes very difficult to enable them for use in DataWedge for terminals such as MC1000, since DataWedge does not provide UI support for them. To counter this issue in terminals that do not support User Interface, the new version of DataWedge does not overwrite the flags even if devices could not be enabled at startup.
For the latest software updates, go to the Symbol Developer Zone web site at:http://support.symbol.com
Back to top
The download package for DataWedge consists of the following components:
COMPONENT Folder DESCRIPTION Readme.html This file DataWedge User Guide.pdf User Guide DataWedge.exe \Bin\PPC Executable for PocketPC devices DataWedge.exe \Bin\WCE Executable for Windows CE devices DataWedge.cpy \Application CPY file used to copy the executable into the Windows folder DataWedge.run \Application\Startup RUN file used to automatically launch the application at startup No-Barcode.reg \No-Barcode Registry file to deactivate Barcode device Deactivate-RFID.reg \Deactivate-RFID Registry file to deactivate RFID device DataWedge.lnk \Link DataWedge shortcut file DataWedge.cpy \Link CPY file used to copy the executable and shortcut into the Windows folder
Back to top
To install DataWedge so that it is launched automatically after a cold boot (clean boot for WM2005) , do the following:
- Unzip the DataWedge download package into a temporary folder on your PC
- If installing on a Pocket PC device, copy "\Bin\PPC\DataWedge.exe" from your PC to the \Application folder on the device
- If installing on a Windows CE device, copy "\Bin\WCE\DataWedge.exe" from your PC to the \Application folder on the device
- Copy "\Application\DataWedge.cpy" from your PC to the \Application folder on the device
- Copy "\Application\Startup\DataWedge.run" from your PC to the \Application\Startup folder on the device
- Cold boot (clean boot for WM2005) the device
NOTE: For WT4090 copy "\Link\DataWedge.lnk" and "\Link\DataWedge.cpy" from your PC to the \Application folder on the device. This will enable easy access to the DataWedge menu by placing a shortcut in the Programs folder.
Back to top
- MC 1000 - The user does not have access to the UI when using DataWedge on the MC 1000
- RFID - Support for RFID should be considered as beta; see known issues below
Back to top
- RFID support can be affected by hardware and firmware versions
- On RFID devices with Platform version Plat0301074 DataWedge may not exit correctly; requiring a warm boot
- On RFID devices with internal WJ module DataWedge may intermittently fail to detect/open the RFID module
- The beep time in the feedback settings may not change the length of the beep on the PDT8100 WM2003
- The barcode feedback dialog does not display the beep time and frequency fields on the MC50 WM2003. This is common to all other devices such as MSR and Serial for the MC50
- In Auto-PIE mode, after PIE has popped up and keyboard is on, if you kill PIE and open another DataWedge dialog, keyboard area becomes inactive. User should hide the keyboard via "Hide Input Panel" to get around this problem.
- MC 3000 dialog windows may appear imbalanced and biased to the left side of the screen.
- If you check the option "Send keys only to Pocket IE" at least for one enabled capture device, data from all four capture devices are diverted to Pocket IE.
- MSR will not get re-established when the MSR DLL is changed to a different value and back.
- Using an external scanner with the ADP9000-110, when the mobile device is suspended, power is still active to the external scanner. With the mobile device suspended, the scanner will continue to decode barcodes, but the data will never make it to the mobile device.
- Virtual COM ports do not contain an Index Number.
- For Pocket PC 2003 '\n' in prefix/suffix fields, should be replaced with '\r' in most Microsft applications as '\n' is ignored or not transmitted in certain cases.
- In the MSR options dialog if you enable Re-establish connection on resume, will lead to DataWedge Disabling MSR on certain mobile devices.
- If you keep on opening configuration dialogs without closing them DataWedge may stop responding. The workaround is to warm boot the mobile device.
Back to top
Last revised: May 17, 2007
Copyright © 2005-2008