Team, I read below known issue from DW release notes
When using the Microsoft Bluetooth stack, after pairing a Bluetooth device with the mobile computer, DataWedge must be stopped and restarted for the comm ports to be available in the DataWedge configuration screens.
Do we have to do this manually? Does SS1 BT Stack has this issue as well?
4 Replies
thanx for the confirmation. another known issue : In MC75 and VC6090 WM6.5 devices Bluetooth scanner disconnection not reflected for the first time. After that the DataWedge status updates correctly. Don't really understand this statement clearly
This is relevant to RS507 Bluetooth scanner. It explains a scanner driver issue. Scanner driver doesn't send the disconnected notification to DataWedge in first disconnection. If Scanner is connected again and disconnect, then scanner driver sends the disconnection notification. Ex: "Removing Batter in RS507" Should disconnect the scanner. But First time removal is not visible to DataWedge. It is visible to DataWedge from second removal onward.
Found the bug that was causing this issue and i have fixed it. It wont be available until the next MR (not the upcoming release but the one after). If customer is seeing this issue an SPR should be created and the ECRT team can create a cab file that installs the latest dll that fixes it. Yusuf
Yes. User need to manually stop and start DataWedge. Device reset also works since DataWedge is started on boot up normally. Stone street doesn't have this issue. SS1 uses set of predefined port numbers.