Figure 48: Data Capture with Camera
4 Move the MC67 until the bar code is centered under the red target.
5 The Left and Right LEDs light green, a beep sounds and the MC67 vibrates, by default, to indicate the bar code
was decoded successfully. The captured data appears in the text field.
Profiles
DataWedge is based on profiles and plug-ins. A profile contains information on how DataWedge should behave with
different applications.
Profile information consists of:
• Associated application
• Input plug-in configurations
• Output plug-in configurations
• Process plug-in configurations.
Using profiles, each application can have a specific DataWedge configuration. For example, each user application can
have a profile which outputs scanned data in the required format when that application comes to the foreground.
DataWedge can be configured to process the same set of captured data differently based on the requirements of each
application.
DataWedge includes the following visible and hidden pre-configured profiles which support specific built-in
applications:
• Visible profiles:
- Profile0 - created automatically the first time DataWedge runs. Generic profile used when there are no user
created profiles associated with an application.
- Launcher - disables scanning when the Launcher is in foreground.
- DWDemo - provides support for the DWDemo application.
• Hidden profiles (not shown to the device):
- RD Client - provides support for MSP.
- MSP Agent - provides support for MSP.
- MspUserAttribute - provides support for MSP.
- Camera - disables scanning when the default camera application is in foreground.
- RhoElements - disables scanning when RhoElements is in foreground.
Profile0
Profile0 can be edited but cannot be associated with an application. That is, DataWedge allows manipulation of
plug-in settings for Profile0 but it does not allow assignment of a foreground application. This configuration allows
58 | DataWedge Configuration
May 2015 | MN000116A02-A
To Next Page
Loading...
Need help?
General
