I have a problem some of you may have seen and fixed: MC75 (BSP27) using DW 3.3 via APIs from an application. DW is configured to use BT RS507 scanner. Reading does work fine, this is not the problem. When RS507 is paired to MC75 (DW is READY), calling DW's APIs DW.Stop() method does properly kill DW instance in milliseconds. When NO RS507 is paired at all (DW is IDLE), doing the same takes exactly one minute to eventually kill/stop DW!! This is way too long! But the really bad thing is that DW.Status uncorrectly reports STOPPED after a few milliseconds. This is unconsistent with the real status of DW. Any ideas or so? Except raising a case... which is the good ole classic. Thanks! PD: This happens regardless of BT being on or off. Actually, if BT is off, when DW finally dies, it turns it back on!!!