Note: The information in this chapter applies to both the Dolphin HomeBase and Dolphin eBase devices unless otherwise indicated. As the hub of your Dolphin 6100 system, the Dolphin HomeBase charging and communication cradle supports full-speed USB 1.1 and RS-232 communication with a workstation.
We bought a Honeywell Dolphin 6100 less than a year ago for a barcode scanner that runs Windows Mobile CE 6.5 to track assets in our agency with Track-It. The problem is, for an unkown reason it is only recognized on a few select PC's, one of which is myold laptop running Vista 32bit and the other Windows 7 64bit; however, both of these loptops are soon to be replaced with our virtual environment. Even after windows recognizes the device for the first time and auto-installs the drivers, the device still won'tbe recognized under the Windows Mobile Device Center, Sync center, or My Computer. Since we couldn't get WMDC running correctly on our virtual envornment (running Windows 7 64bit) we opted to keep a desktop PC (running Vista 32bit as well) around only to beused a sync machine, which is currently having the same problem; drivers installed without error but device is not recognized. We only use the USB cradle only for connectivity, not bluetooth.I contacted Honeywell about this problem and performed the few hotfixes they suggested (reinstalling drivers, WMDC update, etc). On top of that they informed me that this is an ongoing issue with Microsoft and the security features built in to WMDC.
Honeywellstated Microsoft knows of this issue but has yet to release any sort of fix on their end. Does anyone know why the device isn't being recognized and how I get it to sync? I use Track-It software for our IT logging which has it's own link software (TiBarcodeLink.exe). While the device is connected to the PC, this is ran, the plugin installs to the PC's Track-It technician client, which can only be used on one PC due to devicepartnerships generating a new device ID, even after a custom device name is established.
Once successful, it auto installs the their barcode software on the device. The technician client has a proprietary synchronization in the plugin, but the device mustbe connected through WMDC. Even after mentioning said randomly generated device ID to PC partnerships the Honeywell support tech stated it was not the device's amount of partners and went on syaing it was a problem with WMDC. Descargar gratis tmpgenc video mastering works 5 full crack.
I was able to get it synced toa soon to be surplus vista machine (without Track-It) without removing any previous partnerships on the device, which plays in his favor. So yes, the device syncs with PC (it gets the data fields we use to attach to devices); but, it is not syncing with WMDCor sync center and a sync removes the 1 data file that has scanned barcode records and sends the data fields to the device as a database file.
Thanks for the help. I was getting to more how you set up the partnership rather than if it showed it was connected or not. When you plug in the device USB to a PC, phone drivers install, and WMDC opens, you have a choice to connect to the device or connect withoutsetup. Something to that effect. The first option is a full blown partnership that should only be used if you want to sync Outlook PIM info locally with that PC.
It will give you the option to sync contacts, calendar, notes, and tasks, as well as files, bookmarks,etc. There are only two of these types of partnerships allowed on the phone.
I suppose it was to cater to a home and work PC for casual users. So in the enterprise solution, you want to connect to multiple PC throughout your building, I would suppose, andnot have to be tied to one PC. Then you should pick the option, connect without setup. It is considered a guest partnership.
So, if your device is letting you connect to a third PC, outside of the Vista 32 and Win 7 64 boxes, that is unusual as it should complainand say one partnership needs to be deleted, unless you chose to connect without setup. Full partnerships are strictly to be used with only that PC. I am thinking if you delete one of the partnerships off the device that you don't need, it should connect again.Or we may have to tinker with firewall settings.
We bought a Honeywell Dolphin 6100 less than a year ago for a barcode scanner that runs Windows Mobile CE 6.5 to track assets in our agency with Track-It. The problem is, for an unkown reason it is only recognized on a few select PC's, one of which is myold laptop running Vista 32bit and the other Windows 7 64bit; however, both of these loptops are soon to be replaced with our virtual environment. Even after windows recognizes the device for the first time and auto-installs the drivers, the device still won'tbe recognized under the Windows Mobile Device Center, Sync center, or My Computer.
Since we couldn't get WMDC running correctly on our virtual envornment (running Windows 7 64bit) we opted to keep a desktop PC (running Vista 32bit as well) around only to beused a sync machine, which is currently having the same problem; drivers installed without error but device is not recognized. We only use the USB cradle only for connectivity, not bluetooth.I contacted Honeywell about this problem and performed the few hotfixes they suggested (reinstalling drivers, WMDC update, etc). On top of that they informed me that this is an ongoing issue with Microsoft and the security features built in to WMDC.
Honeywellstated Microsoft knows of this issue but has yet to release any sort of fix on their end. Does anyone know why the device isn't being recognized and how I get it to sync?
I use Track-It software for our IT logging which has it's own link software (TiBarcodeLink.exe). While the device is connected to the PC, this is ran, the plugin installs to the PC's Track-It technician client, which can only be used on one PC due to devicepartnerships generating a new device ID, even after a custom device name is established. Once successful, it auto installs the their barcode software on the device. The technician client has a proprietary synchronization in the plugin, but the device mustbe connected through WMDC. Even after mentioning said randomly generated device ID to PC partnerships the Honeywell support tech stated it was not the device's amount of partners and went on syaing it was a problem with WMDC. I was able to get it synced toa soon to be surplus vista machine (without Track-It) without removing any previous partnerships on the device, which plays in his favor. So yes, the device syncs with PC (it gets the data fields we use to attach to devices); but, it is not syncing with WMDCor sync center and a sync removes the 1 data file that has scanned barcode records and sends the data fields to the device as a database file.
Thanks for the help. I was getting to more how you set up the partnership rather than if it showed it was connected or not. When you plug in the device USB to a PC, phone drivers install, and WMDC opens, you have a choice to connect to the device or connect withoutsetup. Something to that effect. The first option is a full blown partnership that should only be used if you want to sync Outlook PIM info locally with that PC. It will give you the option to sync contacts, calendar, notes, and tasks, as well as files, bookmarks,etc. There are only two of these types of partnerships allowed on the phone.
I suppose it was to cater to a home and work PC for casual users. So in the enterprise solution, you want to connect to multiple PC throughout your building, I would suppose, andnot have to be tied to one PC. Then you should pick the option, connect without setup. It is considered a guest partnership.
So, if your device is letting you connect to a third PC, outside of the Vista 32 and Win 7 64 boxes, that is unusual as it should complainand say one partnership needs to be deleted, unless you chose to connect without setup. Full partnerships are strictly to be used with only that PC. I am thinking if you delete one of the partnerships off the device that you don't need, it should connect again.Or we may have to tinker with firewall settings.