We have developed an app for the MC3300x. The app is reading rfid through DataWedge and Android Intents (which we understood is the preferred way of doing it). It worked perfectly when we developed the app about a year ago.
But now rfid-reading has stopped working. No new developing has been done from us on the app. It is though a slightly more updated model of the MC3300x that is now malfunctioning.
It is still on the Android 10, but the DataWedge seem to have a newer version; 8.2.16 (as we recall during development it was on v7.3).
And also the demo app called "RWDemo" wont scan rfid tags. In contrast though the demo app called "123RFID Mobile" is reading rfid as before, but this app is (as we understood it) not using the DataWedge interface.
Another mysterious thing is that the DataWedge profile can be configured to read traditional barcodes, and this is still working as usuall.
It seems like the rfid-scan through DataWedge is somehow broken on updated devices. Is there some initial setup that has to be runned on new devices?
We have followed the online guide about creating a DataWedge profile in code. But to no avail. What can we do?
https://techdocs.zebra.com/datawedge/8-2/guide/api/setconfig/
Accepted Solution
As an answer to my own question. I finally got it to work!
It was not so very well documented (or logical) but here it goes:
Why is this new? I dont know. And I also do not know how to set it programmatticaly. So as for now it had to be done manually editing the profile (after it was created by our app). I tried the new scanner_trigger_resource introduced in DW 8.2, but it I did not seemed to get it to work.
7 Replies
You can try navigating to the RFID Manager application and select the configuration wheel cog, from there make sure the Reader Power Off/On is selected to the 'ON' position. It is possible on OS update this was moved to the off position.
Thank you for quick answer. Unfortunately it did not do the trick.
I even tried via the mentioned RFID Manager to reset the scanner, even to factory reset it. And restart device. But the problem persists.
When holding down the scan-button the app though is saying "blip blip, scan is active" but no result is received (but here if I point it to a barcode the that result is received as expected).
I just want to be sure that you followed the below settings?
1. Open DataWedge settings
2. Select target profile, example Profile0 (default)
3. Scroll down and enable RFID Input
Yes, exactly as that.
The profile for our app is called Builid. And it has both the Barcode input and the RFID input. And also the Intent output. All programmatically added as in the guide at https://techdocs.zebra.com/datawedge/7-3/guide/api/setconfig/. Initially when developed about a year ago this was working fine.
And also the profile for rhe RWDemo standard app (with profile RWDemo) is active and has the RFID input and Intent output. And even that app is not reading rfid.
Both are just sounding "blip" when trigger is pressed indicating reader activated. But no rfid-data received (with rfid-chip within 10 cm). (Although barcode-data is received, so the intent capturing code is working as intended.)
Hi Hakan - The MC33x0XR you are working with - can you check the (Settings - About Phone - Build Number) on the device?
( My MC3330XR is currently running A11, and RWDemo does work, but I currently have the Keypad Scan button re-assigned to the Barcode Scanning and not the optional RFID scanning.)
I may recommend using the "Restore Defaults" on Datawedge to refresh the Datawedge settings ( a normal Troubleshooting suggestion from Help Desk) - this will only configure the three default profiles - Profile0, DWDemo, and Launcher. None of these will have the RFID Settings.
If you open RWDemo - you will see that RWDemo will auto-provision a profile that configures for RWDemo use.
I cannot speak to your "Builid" app - but if that app auto-creates a Datawedge Profile - then you can test that. If "Builid" needs a profile created manually - you can create it and then "Backup Profile" to save this for future (Compatible Datawedge version) useages.
Please try the above and let me know the build number - and I will see what further suggestions I may make.
Also make sure in the "Reader Selection" menu - that you have chosen the "Available reader" check box in the profile you are working with.
As an answer to my own question. I finally got it to work!
It was not so very well documented (or logical) but here it goes:
Why is this new? I dont know. And I also do not know how to set it programmatticaly. So as for now it had to be done manually editing the profile (after it was created by our app). I tried the new scanner_trigger_resource introduced in DW 8.2, but it I did not seemed to get it to work.