Link to home
Start Free TrialLog in
Avatar of ForeroJ
ForeroJ

asked on

Why my scanner gun reads special character instead of the correct data?

I have a scanner gun Motorola MC9090 with DataWedge version 3.2.4.
I have a barcode with the data: 480100*G.
The gun reads: $*)!))+G

These special characters correspond to each number key: 4=$, 8=*, 0=), 1=!
When the barcode contains only the number portion, it work fine.

Is this problem due to a DataWedge configuration? or the gun configuration?

Thanks,
Jose.
Avatar of alexey_gusev
alexey_gusev
Flag of United Kingdom of Great Britain and Northern Ireland image

I believe it is due to DataWedge configuration, in particular what's set for that specific barcode type
Avatar of ForeroJ
ForeroJ

ASKER

I noticed that this happens only when I am connected to a server using Remote Desktop Mobile.

When I scan to a local program in the scanner gun like Word Mobile, it scans fine.
hmm, perhaps Remote Desktop handles it as keyboard clicks with Shift or Fn button pressed?
what are the other characters on those buttons? do they correspond? I don't remember if DataWedge has any settings for delivering the barcode in lowercase or uppercase.
Avatar of ForeroJ

ASKER

Yes. Remote Desktop is handling as keyboard clicks with SHIFT because the special characters correspond to the number keys.

Also after I scan, if I press any NUMBER key, what I get is the correspondent special character. So the keyboard is changed to SHIFT mode and stays in that mode.

Now, If I press the SHIFT key, the keyboard changes the mode from SHIFT mode to normal mode. Then when I press the NUMBER key I get the number instead of the special character.

Is this something that I can control from the DataWedge?
no, you cannot, at least I don't know anything like that in DataWedge
ASKER CERTIFIED SOLUTION
Avatar of ForeroJ
ForeroJ

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ForeroJ

ASKER

I found the solution in Data Wedge setup.