Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.pascal.delphi.misc > #574
| From | "P E Schoen" <paul@peschoen.com> |
|---|---|
| Newsgroups | comp.lang.pascal.delphi.misc |
| Subject | Re: Detecting Bluetooth COM port(s) in Delphi 4 |
| Date | 2013-12-29 13:24 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <l9ppcd$sdo$1@dont-email.me> (permalink) |
| References | <l9p6jb$k53$1@dont-email.me> <biauepFo108U1@mid.individual.net> |
"Hans-Peter Diettrich" wrote in message news:biauepFo108U1@mid.individual.net... > P E Schoen schrieb: >> I haven't been around much lately as my efforts have been elsewhere, but >> recently one of my customers had problems with the USB connection from >> his computer to my Ortmaster device, where he has a 13 kV AC supply >> operating a closing coil on a recloser, and it causes communication to >> stop, requiring a reset of the device and removal/reinsertion of the USB >> connector. I tried a USB isolator but no joy. > >> So, I thought maybe a direct serial connection would be more robust, and >> since he is using a desktop computer it should be possible, whereas for >> laptops the serial port is a rarity except in the Panasonic "Toughbooks". >> I bought one of the cheap ($8 or so) Bluetooth modules on eBay and I used >> it at its default 9600 baud rate to collect some data, and it seemed to >> work very well, even as far as 30 feet away through two doors, and with >> the device inside a metal enclosure. > In the early 80s we used an 16 channgel RS-232 multiplexer in a very noisy > environment, of thyristor-switched supplies in the MW range. Several km of > lines installed, no transmission problems ever :-) > I cannot help with your software problems, though :-( I posted this on a MS forum and received a response: http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/ad5fe4a6-9be8-4780-a8e7-7742533a2b4d/determining-bluetooth-com-port-assignments-in-windows-7?forum=wdk "you don't need to parse the ENUM key (the ENUM key is in fact private and should not be parsed). Rather you can use setupapi to enumerate the com port device interface and restrict the enumeration to the BTHENUM enumerator. for each instance, setupapi can give you the HKEY that represents Device Parameters (without knowing the full parent path) key and you can query these values from there" I am not familiar with the setupapi, but I found some information. I assume I might be able to access it from Delphi? http://msdn.microsoft.com/en-us/library/windows/hardware/ff550855(v=vs.85).aspx Thanks for the reply. And Happy "Gnu" Year to you as well! Paul www.ortmaster.com
Back to comp.lang.pascal.delphi.misc | Previous | Next — Previous in thread | Find similar
Detecting Bluetooth COM port(s) in Delphi 4 "P E Schoen" <paul@peschoen.com> - 2013-12-29 08:03 -0500
Re: Detecting Bluetooth COM port(s) in Delphi 4 Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2013-12-29 16:45 +0100
Re: Detecting Bluetooth COM port(s) in Delphi 4 "P E Schoen" <paul@peschoen.com> - 2013-12-29 13:24 -0500
csiph-web