I have a potential client who is evaluating MC75 to replace Psion Ikon units. Their 2 concerns are
1. MC75 Camera response time is 4-5 seconds compared to competition 1-2 seconds
2. MC 75 does NOT has page up and page down buttons. ( can any of the qwerty buttons be re-mapped to pge up and page down?).
I need guidance in helping TAM displace competition and get MC75's in the field
1. MC75 Camera response time is 4-5 seconds compared to competition 1-2 seconds
2. MC 75 does NOT has page up and page down buttons. ( can any of the qwerty buttons be re-mapped to pge up and page down?).
I need guidance in helping TAM displace competition and get MC75's in the field
Points: 0
You voted ‘up’
Also this a a competitive environment where we are trying to displace incumbent.
I have found the kbtools for MC75, This should ghelp address issue 2 above.
Points: 0
You voted ‘up’
https://devcentral.symbol.com/shwmessage.aspx?forumid=251&messageid=11841
There is a bunch of information comparing the camera solutions of the MC75, Ikon and CN3 devices. The section on Shutter Sound may help explain the difference in response time between the devices, see below.
SHUTTER SOUND (Pictures & Video Application)
By default Microsoft’s Pictures and Videos (pimg.exe) application plays the shutter sound immediately after the trigger is pressed – not waiting for the exposure to finish. Consequently, if a user moves the camera after the shutter sound plays, but before the exposure finishes the captured image may be blurred. The root-cause of this issue is a flaw in Microsoft’s DirectShow architecture.
We developed a workaround for this issue with some creative engineering in our camera driver stack. According to our testing, Intermec’s CN3 has a similar workaround. The Psion Ikon, however, does not appear to address this issue. As a result, if the camera is moved immediately after the shutter sound plays, the captured image may be blurred.
Points: 0
You voted ‘up’
Thanks for the pointer Dave.
Points: 0
You voted ‘up’
the directshow sample may show quicker responses than the MS API.
Points: 1
You voted ‘up’
Do you have a registry key or know if it is possible to have the autofocus "disabled" persist through a warm boot? We have another case in tech support where this is needed.
Thanks,
Tony
Points: 0
You voted ‘up’
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BarCodeReader2\Settings]
"ReaderParams"=hex:\
84,00,00,00,64,00,00,00,02,00,00,00,00,00,00,00,F4,01,00,00,03,00,00,00,\
98,3A,00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,00,00,00,00,00,00,00,\
00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,28,00,00,00,\
28,00,00,00,B7,01,00,00,53,01,00,00,02,00,00,00,01,00,00,00,E8,03,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00
Points: 0
You voted ‘up’
Thanks!
Petr
Points: 1
You voted ‘up’
[HKEY_CURRENT_USER\Software\Symbol\pictures\camera\user]
"CSPROPERTY_CAMERACONTROL_FOCUS"=dword:0
Points: 0
You voted ‘up’
You can remap any of the Qwery keys to generate Page Up/Down using the kbtools files which allow the keycode tables to be modified. If you specify which keys you want to remap I can send you the modified files for installation on the device.
Best Regards,
Ian Hatton
EMb EMEA
Points: 0
You voted ‘up’
Log in to post comments