If I put Windows into Standby or Hibernate, then restart it, the COM port is fine, I don't need to alter it, but if Windows restarts then it is essential to either change to another COM port and reconfigure the plotter to that new port, or simply to change the COM port, then change it back and use the plotter as-was. Just so long as one port reassignment has taken place, the plotter and GPS will happily talk! Any ideas? Would the Toshiba stack help me? Well I seem to have cured my own problem by finally finding R This removed all BT drivers and reinstalled new.
It also allows connection to the device before starting the chart plotter, not that this seems necessary. The only issue is that R EXE Strangely this isn't listed as a driver when I search by service ID, however, other posts I found mentioned it and it does seem to have cured my problems Browse Community.
Turn on suggestions. This all started when windows did an update to Any and all help would be most welcome Please help! Go to Solution. Thanks for the extensive solutions offered But I think I may have solved the problem as I now have my bluetooth and com ports back and working and no longer have a USB error.
I could finally get into windows with all the errors described after a number of restarts. I believe that my hidden boot partition was corrupted somehow I was lucky to have a total system backup and managed to restore this hidden partition and when I rebooted it now seems to work. I was reinstalling my Windows C: drive not this boot partition and this is why I have been having this issue for so long.
I tried to do a factory reset but the media I was given wouldn't work View solution in original post. If you are facing problem while connecting to a Bluetooth device, Temporarily disable security software Antivirus if installed and check this may very helpful. After running the Bluetooth Troubleshooter Also Run the Hardware and Devices Troubleshooter to check and fix if any physical hardware device causing the issue to connect via Bluetooth.
After running both troubleshooters simply restart windows and check on next login Bluetooth devices connected and working properly. Still, have to issue follow the next instructions. After that restart windows and check Bluetooth device started working. The above link is 3rd party and is not owned by HP, I've posted this only so that I may help you resolve this issue by going beyond my support boundaries, please ignore the ads and take only the free suggestions.
If you wish to thank me for my efforts, you could click on "Accept as solution" on my post as the solution should help others too. Just an update about this problem I did get it working but it came back I've been looking around and on the microsoft trouble shooter website and it seems that it is a major problem with the windows update I've tried to replace the drivers manually Replacing this driver had no effect Driver Name: usb.
Thanks for the reply Hope it will be helpful to you. Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. So, which port should we connect o in order to use a terminal program such as RealTerm to communicate with some remote computer over serial port login connection?
Essentially using a db9 serial-bluetooth adapter at the remote end, and my laptop's internal bluetooth on local end. What I want to do is to use an embedded system serial port login for maintenence access, see the bootup log which remote system puts onto db9 serial port, later gives a login prompt that I would like to login to and then be able to check on the system, initiate reboot if needed, collect data, install new files etc.
I have two different db9 serial-bluetooth adapters now, and neither accomplish this as far as I can tell. I have done aloopback test on one of them, which passes, but it cannot talk to a usb-serial adaptor, even with nullmodem adapter in between the two db9 ends. For every byte I type into the bluetooth side RealTerm, I get 3 bytes out at the USB end, like the two db9 ports are talkign different languages, but htey are all configured to baud, 8N1, no hardware handshake, so no reason to be different.
Believing my first buetooth-serial adapter to be garbage, I bought another from adifferent brand, with different shape, internal antenna vs big bendy antenna etc. But sedond one behaves much like the first, and so I assume now that perhaps the concept is wrong for bluetooth? Or perhaps that Windows10 is flaky in this regard, as I find a lot of other complaints about Bluetooth COM ports in Win10, when their thigns had worked fine in Win7, Win8.
By USB-serial adapter connects just fine to my embedded platform and shows me the boot log, lets me login etc. I want that same thing over bluetooth, rather than having a very long serial wire going down the hallway between rooms
0コメント