Reading a EAN13 barcode

Hi Ricardo,

Thank you for your feedback.

We will investigate this issue and keep you posted.

Best Regards,

Hi Ricardo,

We have tried to reproduce the problem over 50 times and we are not able to reproduce it.

Can you provide more information? The device you are using, OS version, your RDP server version, etc...

Regards,

Thank you Nicolas,

the device is this (https://www.amazon.es/gp/product/B075FTSXTQ/ref=oh_aui_detailpage_o07_s00?ie=UTF8&psc=1), android 5.1.

The problem is connecting to a Windows 2003 Terminal server.

The Remote Destop Manager version is 3.81.

If I connect with the Microsoft RD Client for Android the problem doesn't happen, but I prefeer to use devolutions

Hi Ricardo,

Thank you for the information.

We will continue investigating.

Regards,

Hi Ricardo,

Are you able to type with your keyboard at the same time that you scan.

Regards,

Hi Nicolas,

yes, I can type with both keyboards (the integrated and virtual keyboard).

Hello,
is there a solution in meantime?
We have the same problem with scanning of barcodes with a Zebra TC20 with Android 7.1.2 and RDP to Terminal Server Windows 2003 32Bit

If we scan a Code39 Barcode 123456 scan result in our application or cmd.exe is correctly
But we have errors as following:
Scan 123345 => result 12345
Scan 112233 => result 123

Regards
Peter

Hi Peter,

I will do some tests with the equipment I have available to me which, unfortunately, doesn't match your use case.
Can you confirm that you can scan and still use the integrated keyboard at the same time?

Regards

Hi Jonathan,
YES, i can scan and use the integrated keyboard at the same time:
Connect by RDP to terminalserver, open cmd.exe, enter value 112233 and Enter with integrated keyboard, then scan a barcode 112233 directly afterwards is possible without problem. Only the scan result is wrong [123 instead 112233]

Regards

Our scanner replaces the integrated keyboard and acts exactly the same.
Your integrated scanner doesn't seem to.
I might have an idea what is happening and will investigate.

Hi Peter,

We think we found a solution. We could make a special build and send you a download link so that you can test it.

Would you be interested in testing it? If so, just send an email at the following address: ndufour@devolutions.net and we will send you a link where you can download and test the application as soon as it is available.

Best Regards,

We have received our zebra device and was able to reproduce your issue.
It seems to be application specific tho. Can you confirm that scanning in notepad is fine?

I can not confirm. Scanning in Notepad of an RDP session is wrong. Even scanning in cmd.exe is wrong.

Hi Peter,

If it is ok with you, we could send you a special build next week (like we did the last time).

It would be the easiest way to find out if we were able to fix the problem.

Regards,

Hi Nicolas,
yes, it is ok for me. From Wednesday on i could test the special build.

Hi Nicolas,
i have tested the new update you have sent.
The scan result with 112233 is now correctly :):thumb:

But i there is now another problem: :(
If i scan a Code39 with "DRK-GLS" the result is "DRKGLS".
The "-" is lost. Same happens with "+".

Hi Peter,

Thank you for the update.

We will continue to work on the problem.

Best Regards,

Hi Peter,

Barcode scanning reliability has been improved in the new release (Version 4.2).

Version 4.2 is currently rolling out on Google Play and the update should be available to 100% of our users within a few days.

Best Regards,