.NET Forum / .NET Framework / Compact Framework / January 2006
Unsuccessfull serial communication with CF 2.0
|
|
Thread rating:  |
Lonifasiko - 17 Jan 2006 09:06 GMT Hi,
I must communicate my PDA with a device via serial communication. The device brings a cable ready for that, and in order to provide a seriaI port to my PDA, I bought this cable: http://www.cablematic.com/index.php?_cl_id=1&fam=128&p=25&pp=&mode=1&id=90&fam=1 28&pag=2&p=25
Well, I have some specifications from my manufacturer. They are related for device-PC (not PDA) communication via serial port, but I suppose they will be the same for device-PDA coomunication. I sum up them:
Baud Rate = 9600 bps Data Bits = 8 Stop Bits = 1 Parity = none Flow Control = None Com Port = port utilized (I'm trying with "COM1")
And here are another conditions: 1. The computer must assert (apply a positive RS-232 voltage to) RTS and/or DTR. Either or both of these signals supply power to the cable circuitry. 2. The computer may leave RTS "open" but may not drive it to a negative RS-232 level. 3. The computer communications port must be set to 9600 baud, 8 data bits, no parity, and one stop bit.
I've been able to open the serial port on COM1, and send a command specified by the manufacturer (no error indeed) that should wake up the device, but I'm not seeing any result on the device's screen. I've carefully followed the manufacturer's specifications and I'm using CF 2.0 with System.IO.Ports.SerialPort class. This is my code:
------------------------------------------------------------------------- SerialPort sp = new SerialPort(); sp.BaudRate = 9600; sp.StopBits = StopBits.One; sp.Parity = Parity.None; sp.DataBits = 8; sp.PortName = "COM1"; sp.RtsEnable = true; sp.DtrEnable = true; //sp.Encoding = Encoding.ASCII; //sp.Handshake = Handshake.None;
try { sp.DataReceived += new SerialDataReceivedEventHandler(this.ReceiveData); sp.ErrorReceived += new SerialErrorReceivedEventHandler(this.ErrorInSerialCommunication); sp.WriteTimeout = System.IO.Ports.SerialPort.InfiniteTimeout; sp.Open(); sp.WriteLine("DMP"); MessageBox.Show("Command sent"); } catch (Exception exc) { MessageBox.Show(exc.Message); }
private void ReceiveData(Object sender, SerialDataReceivedEventArgs e) { MessageBox.Show("Receive Data"); }
-----------------------------------------------------------------------------------------
Hope you can see something that is not letting me communicate properly with the device.
Thanks very much in advance.
Lonifasiko - 17 Jan 2006 09:51 GMT Hi again,
from Microsoft's documentarion about SerialPort class: "Use this class to control a serial port file resource. This class provides SYNCHRONOUS and event-driven I/O, access to pin and break states, and access to serial driver properties "
Only synchronous I/O? Asynchronous would not be supported by this class? I've noticed specification from device's manufacturer also tells me this:
"The device supports ASYNCHRONOUS, RS-232 communications via the data port at 9600 baud only. Data are transferred as 8-bit characters with no parity and one stop bit. Communication is via three-wire (RS-232 designations of BA, BB, AB) cable."
So I'm seeing an incompatibility right now. Can anybody explain me this and give me a clear solution?
Thanks.
<ctacke/> - 17 Jan 2006 12:44 GMT Does your device support DTR or RTS? Not al UARTs do.
As for the synchronous v. asynchonous, the docs are wrong. RS232 by definition is asynchronous and I know that the serial classes will not work for synchronous serial.
-Chris
> Hi, > [quoted text clipped - 67 lines] > > Thanks very much in advance. Lonifasiko - 17 Jan 2006 13:07 GMT Hi Chris,
Thanks for your interest. What do you mean by UART? This is what I can tell you:
"supports asynchronous, RS-232 communications via the data port at 9600 baud only. Data are transferred as 8-bit characters with no parity and one stop bit. Communication is via three-wire (RS-232 designations of BA, BB, AB) cable."
and.....
"The following conditions must be met: 1. The computer must assert (apply a positive RS-232 voltage to) RTS and/or DTR. Either or both of these signals supply power to the cable circuitry. 2. The computer may leave RTS "open" but may not drive it to a negative RS-232 level. 3. The computer communications port must be set to 9600 baud, 8 data bits, no parity, and one stop bit."
Therefore you mean that after knowing RTS or DTR, I would be able with CF 2.0 SerialPort class to send and receive data via serial port? I'm using event driven communication like this:
sp.DataReceived += new SerialDataReceivedEventHandler(this.ReceiveData);
I understand that after sending the specific command I need with Write or WriteLine(), if device sends me back something, ReceiveData method should be called.
Thanks very much.
<ctacke/> - 17 Jan 2006 13:42 GMT Your device requires voltage on RTS or DTR. I'm saying that the UART used for the serial port on your device may not support them, and the manuafacturer therefore would not have run any signals. The port could still send and receive data, it just can't support the handshaking lines. You have to check with the OEM.
-Chris
> Hi Chris, > [quoted text clipped - 31 lines] > > Thanks very much. Lonifasiko - 17 Jan 2006 15:48 GMT Chris,
I've connected the device to my PC, using COM1 serial port. I'm able to run HyperTerminal , send commands and see what the device is returning. The configuration of hyperterminal, as you will know, it's really simple: just establish parity, stop bits, flow control, data bits, port name and baudrate........and works!
I've also built a little example application in Winforms and ReceiveData event is correctly fired after I've sent a command. However, the value I read is not the value I expected. In all examples they say "ReadExisting()" method is enough to read all data. This method only gives me a "?" character, when I expect al least 20 characters.
Any other good way to read received data?
Thanks.
Joseph Byrns - 17 Jan 2006 16:21 GMT I think the trouble here is likely that the RTS pin on the PDA is not high (i.e. does not provide a voltage supply). On the other hand I guess a PC always provides a voltage to this pin (even though hardware flow control is not enabled). I don't have the relevant connections to test this.
Judging from what you have written it would seem the other device gets its power from the RTS pin (RTS is pin 7 at the PDA/PC end). So for you to get this to work with a PDA you may have to provide your own voltage (using a battery presumably) to the RTS pin on the other device (infact as the PC RTS pin connects to CTS on the other device you would need to provide a voltage to pin 8 on the other device, with ground at pin 5).
HTH
> Chris, > [quoted text clipped - 15 lines] > > Thanks. DickGrier - 17 Jan 2006 16:55 GMT Hi,
To follow up on what Joseph said, one problem may be that the RTS output from your device has both too low a voltage level AND cannot drive the current required. If you attempt to power an external device from a PPC serial port (DTR and RTS), often you will fail. There simply isn't enough power available on the output pins. Thus, you have to provide a separate power supply for such devices.
Dick
 Signature Richard Grier, MVP Hard & Software Author of Visual Basic Programmer's Guide to Serial Communications, Fourth Edition, ISBN 1-890422-28-2, Mabry Publishing (391 pages, includes CD-ROM). July 2004. See www.hardandsoftware.net for details and contact information.
Markus Humm - 17 Jan 2006 18:36 GMT Hello,
there are two things, one already mentioned:
1. the RS232 of the PDA might not supply any voltage, e.g. Acer n30 doens't supply any voltage (which is bad habbit), it "steals" it from the PC.
2. often the cable for the pda rs232 is crossed, since a rs232 connection of two PCs (a PDA is like a PC in this case) requires a crossed cable, but other devices (like a serial mouse) requires a straight cable. "de-crossers" are available for purchase.
Greetings
Markus
Lonifasiko - 18 Jan 2006 06:59 GMT Hi folks, thanks for your replies.
I'm afraid I'm quite lost in the hardware issues you are mentioning, talking about pins, voltages and so on ;-)
>From your replies, I understand the following: 1. The CompactFlash cable I've purchased provides a serial port for the PDA but the problem is not here. The problem is that the PDA does not provice any voltage to RTS or DTR pins of the CompactFlash slot. 2. You tell me to supply power to this pin externally. How? A battery attached to the PDA? Tell me please (although I don't like the idea very much). 3. The PDA I'm trying with is an iPAQ h5500. Are iPAQs so special for serial communication? 4. I don't know about crossed cables and de-crossers. Could you give me a good link based on the CompactFlash cable I mention above in the post? 5. The problem could be because of the manufacturer's cable?
If I do not supply voltage to the mentioned pin, isn't there another solution? Just I won't be able to achieve satisfactory serial communication? I can't believe my eyes :( I thougth serial communication did not depend so much on the PDA and on the external device. I thougth the Compact Flash was the only thing I need.
Thanks very much.
Lonifasiko - 18 Jan 2006 08:07 GMT Why can I see in HyperTerminal the text the device is sending back to PC via serial port and a simple Winforms application does nothing?
Simply returns me "?" character. I don't understand anything. And I'm trying with the PC, not with the PDA. I see PDA communicating via serial port almost impossible!
Bye..........
Joseph Byrns - 18 Jan 2006 10:09 GMT Inline:
>>From your replies, I understand the following: > 1. The CompactFlash cable I've purchased provides a serial port for the > PDA but the problem is not here. The problem is that the PDA does not > provice any voltage to RTS or DTR pins of the CompactFlash slot. It is the CF card does not provide power to the RTS pin.
> 2. You tell me to supply power to this pin externally. How? A battery > attached to the PDA? Tell me please (although I don't like the idea > very much). If you are not comfortable with this you should ask the manufacturers of the serial device, or better still an electronics engineer, for advice on this.
> 3. The PDA I'm trying with is an iPAQ h5500. Are iPAQs so special for > serial communication? Every serial device I have ever used has it's own power supply so would work perfectly with your PDA, I am aware that some serial devices use RTS for power but have never used any.
> 4. I don't know about crossed cables and de-crossers. Could you give me > a good link based on the CompactFlash cable I mention above in the > post? > 5. The problem could be because of the manufacturer's cable? You should get a volt meter and see if the pins at the end of your cable provide a voltage (ground is pin 5 and RTS will connect to pin 8 at the other end of the cable (which is infact CTS)). The pins are actually numbered on normal serial cables (with little tiny numbers). If there is a suitable voltage there then you have other problems (as Dick mentioned perhaps there is insufficient power for your device, back to the manufacturer again I am afraid).
> If I do not supply voltage to the mentioned pin, isn't there another > solution? Just I won't be able to achieve satisfactory serial > communication? I can't believe my eyes :( > I thougth serial communication did not depend so much on the PDA and on > the external device. I thougth the Compact Flash was the only thing I > need. Ordinarily the compact flash serial card may well have been the only thing you needed, unfortunately in your case you have chosen a serial device that requires power from the serial to work (which in my opinion is not the norm).
Additionally, as you are using the iPaq h5500, why are you using a CF card for the serial comms? You can get a serial cable for the h5500 that plugs into the connector at the bottom of the PDA that gives you access to COM1 on the PDA, you may find that this does provide the necessary voltages? (here for example http://www.expansys.com/product.asp?code=109386 )
Lonifasiko - 18 Jan 2006 10:52 GMT The cable you mention is just a synchronization cable via serial port of the PC. It can substitute USB connection with the PC. I think this it's different from providing the PDA a serial port. That's why I bought the CF card. I also wrote a post for this in this newsgroup and people advised me to buy the CF card.
Anyway, the cable you mention seems to have a female ending and I need male ending. My device's cable ending is female, therefore I need male ending for my cable.
Back to device-PC communication, to see wether communication works......I send a command via hyperterminal and device switches on.OK. Another command is sent and I got response. If I do this, with the same configuration, from a Winforms application, device is not switched on and always returns me "?", that seems to be an error character.
This is my Winforms code (forget about Compact Framework for a moment), see wether you can help me please:
private void ReceiveData(object sender, SerialDataReceivedEventArgs e) { try { MessageBox.Show(serialPort.ReadExisting()); } catch (Exception ex) { MessageBox.Show(ex.Message); } }
private void ErrorInSerialCommunication(object sender, SerialErrorReceivedEventArgs e) { MessageBox.Show("ERROR!"); }
private void button1_Click(object sender, System.EventArgs e) { try { serialPort.BaudRate = 9600; serialPort.StopBits = StopBits.One; serialPort.Parity = Parity.None; serialPort.DataBits = 8; serialPort.PortName = "COM1"; serialPort.Handshake = Handshake.None; serialPort.DataReceived += new SerialDataReceivedEventHandler(ReceiveData); serialPort.ErrorReceived += new SerialErrorReceivedEventHandler(ErrorInSerialCommunication); serialPort.Open(); serialPort.RtsEnable = true; serialPort.DtrEnable = true; serialPort.Write("DM"); } catch (Exception exc) { MessageBox.Show(exc.Message); } }
I understand port must leave opened after sending the command. ReceiveData event is fired but as I've said, always returns "?" character. I'm using Write() method instead of WriteLine(), because in Hyperterminal don't need any return character. Just typing "DM", device gets ready. With this example, not.
Please tell me if you see something suspicious. Thanks very much.
Joseph Byrns - 18 Jan 2006 11:06 GMT Does it work if you leave out these lines?
serialPort.RtsEnable = true; serialPort.DtrEnable = true;
> The cable you mention is just a synchronization cable via serial port > of the PC. It can substitute USB connection with the PC. I think this [quoted text clipped - 67 lines] > > Please tell me if you see something suspicious. Thanks very much. Lonifasiko - 18 Jan 2006 11:45 GMT Ok, I still have these two lines because of the CF example. Manufacturer said to enable RTS and/or DTR, that's why I still had them.
I've erased them but still device-PC example does not work. I'm really getting worried with this issue.
Thanks very much.
Joseph Byrns - 18 Jan 2006 11:59 GMT Then I don't know, hopefully someone else will have a better idea.
> Ok, I still have these two lines because of the CF example. > Manufacturer said to enable RTS and/or DTR, that's why I still had [quoted text clipped - 4 lines] > > Thanks very much. DickGrier - 18 Jan 2006 18:31 GMT Do you have an online link to the technical description for your device, or can you email me a PDF or DOC? I don't mind looking at it more closely.
 Signature Richard Grier, MVP Hard & Software Author of Visual Basic Programmer's Guide to Serial Communications, Fourth Edition, ISBN 1-890422-28-2, Mabry Publishing (391 pages, includes CD-ROM). July 2004. See www.hardandsoftware.net for details and contact information.
Lonifasiko - 19 Jan 2006 08:32 GMT Thanks very much Dick for your interest.
I'm now trying to communicate with the device from my PC. When I achieve this, I will continue with the PDA-Device serial communication and resume with you the cabling issue. I'm also having problems to communicate via serial port from my PC. Serial communication is hellish!
All you can follow my new post and help me here:
http://groups.google.es/group/microsoft.public.dotnet.languages.csharp/browse_th read/thread/3825a9c868d916d8/d27ecb402dd9e81a
Seems to be an encoding issue but I think I've tried everything!
Thanks very much.
DickGrier - 19 Jan 2006 18:08 GMT Hi,
If you don't mind VB, I think I cover the subject fairly well in my book, both for desktop and compact devices. You do have to get the details right, and an understanding of the underlying hardware is REALLY helpful, both the h ardware of the PC or PPC and the hardware in the actual serial ports -- along with the hardware and software requirements of the devices with which you communicate. This last issue can be the real challenge. Often, inexpensive devices have inadequate documentation. That's one of the lessons that I use in my book, where I have examples that cover many of the situations that I've encountered over the years. The theams seem to repeat.
Dick
 Signature Richard Grier, MVP Hard & Software Author of Visual Basic Programmer's Guide to Serial Communications, Fourth Edition, ISBN 1-890422-28-2, Mabry Publishing (391 pages, includes CD-ROM). July 2004. See www.hardandsoftware.net for details and contact information.
DickGrier - 19 Jan 2006 18:10 GMT theme
 Signature Richard Grier, MVP Hard & Software Author of Visual Basic Programmer's Guide to Serial Communications, Fourth Edition, ISBN 1-890422-28-2, Mabry Publishing (391 pages, includes CD-ROM). July 2004. See www.hardandsoftware.net for details and contact information.
DickGrier - 19 Jan 2006 18:13 GMT BTW, did you set the RThreshold property to 1? I didn't see that in the code that you posted. I also don't see the OnComm event code.
 Signature Richard Grier, MVP Hard & Software Author of Visual Basic Programmer's Guide to Serial Communications, Fourth Edition, ISBN 1-890422-28-2, Mabry Publishing (391 pages, includes CD-ROM). July 2004. See www.hardandsoftware.net for details and contact information.
Lonifasiko - 20 Jan 2006 06:51 GMT RThreshold property has changed to ReceivedBytesThreshold property, and its default value is 1. There is no OnComm event in CF 2.0 for SerialPort component. I think the unique way of receiving data is using DataReceived eventhandler.
Regards.
DickGrier - 18 Jan 2006 18:29 GMT Hi,
The cable you mention is just a synchronization cable via serial port of the PC. It can substitute USB connection with the PC. I think this it's different from providing the PDA a serial port. That's why I bought the CF card. I also wrote a post for this in this newsgroup and people advised me to buy the CF card. <<
No, the internal serial port is a true serial port. It shares the connector with USB but has no other hardware in common. The issue here is that the serial cable FOR THE INTERNAL port is wired as a DCE. Thus, it can be used to communicate with PC, but the cross over of Tx and Rx lines (and the handshaking lines) means that you must insert a null-modem adapter in series with the cable in order to connect it to a non-PC device. Also, the voltage and current available on this port is quite limited, so furnishing power to your device from the handshaking lines is problematic. To use this port as a normal serial port, all you must assure is that ActiveSync does not attempt to use it for synchronization. Use the PPC ActiveSync settings to disable its use there. The internal serial port is Com1.
You ask how to furnish power to your device using an external power supply? This requires a little skill with a soldering iron, a suitable power supply, and two diodes (IN4001 will surely work). Total, probably about $10 at Radio Shack. You can contact me offline for more information -- I'd need to know more about your device to offer any exact details.
Dick
 Signature Richard Grier, MVP Hard & Software Author of Visual Basic Programmer's Guide to Serial Communications, Fourth Edition, ISBN 1-890422-28-2, Mabry Publishing (391 pages, includes CD-ROM). July 2004. See www.hardandsoftware.net for details and contact information.
Markus Humm - 20 Jan 2006 17:53 GMT [snip]
> You ask how to furnish power to your device using an external power supply? > This requires a little skill with a soldering iron, a suitable power supply, [quoted text clipped - 3 lines] > > Dick Did you ever have the issue that the PPC doesn't seem to provide any voltage level on the RS232? e.g. when the other device doesn't provide one the communications doesn't work?
I have at least two PPC models with these simptoms and my application works pretty well otherwise! One of these two can even power my rs232 device from the RS232, but then it seems to be short of power and the communication fails.
Any hints on that?
Greetings
Markus
Lonifasiko - 30 Jan 2006 10:08 GMT Hi guys,
I finally achieved serial communication between the device and PC (not PDA) by code. It just was a necessary delay-time. For sending "DM", it was necessary to send "D", wait for 200 miliseconds and the send "M" character. Incredible but true! Seems like the electronic of the device is quite slow and antique. That's the good notice.
Nevertheless, same code does not work between the device and the PDA, that's why I resume again this thread.
Do you remember my hardware specifications? I've got this cable to provide my PDA a serial port: http://www.cablematic.com/index.php?_cl_id=1&fam=128&p=25&pp=&mode=1&id=90&fam=1 28&pag=2&p=25 The device I'm trying to connect to comes with an interface cable that nds with a female 25 pin port. The I've got a 25 pin to 9 pin adapter that makes possible the connection with the CF serial male serial port.
What do I exactly need? A female to male null modem adapter like this?
http://www.expansys.es/product.asp?code=NM-D9F-D9M
I don't think "male to male" would do it as long as the CF card that provides me the serial port interface has got a male ending. Female to male then?
That would be enough or do I have to provide my own voltage to the CF card's serial port?
Thanks very much in advance.
<ctacke/> - 30 Jan 2006 12:48 GMT A wait of 10 seconds shouldn't matter. You code should not assume that all data is available when the first byte arrives, which it sounds like you're doing. THat can lead to bugs on the PC as well, especially with slower data rates and larger buffer sizes. Try running your existing PC code at 300 baud and see if it still works.
-Chris
> Hi guys, > [quoted text clipped - 27 lines] > > Thanks very much in advance. Markus Humm - 30 Jan 2006 20:03 GMT [snip]
> What do I exactly need? A female to male null modem adapter like this? > [quoted text clipped - 3 lines] > provides me the serial port interface has got a male ending. Female to > male then? I think it would be worth a test. Depending of the device and the cable a male to male one might be necessary as well (additionally to the null modem adaptor mentioned by you).
Greetings
Markus
Lonifasiko - 31 Jan 2006 08:47 GMT I've also tried with ActiveSync synchronization cable connected to COM1 port of my PC. I run the application from my PPC, send the commands and I'm able to see these commands with HyperTerminal. Well, at least the commands are being sent correctly over this cable.
If I just connect ActiveSync cable with the help of some converters to my external device, I suppose commands are also sent, but device does not switch on and does nothing. I understand the problem is in the device.
What do you think guys?
Thanks.
Lonifasiko - 31 Jan 2006 08:51 GMT I just forgot a couple of details:
The previous example was developed of course using COM1 port. I think it's the unique valid port for serial communication over ActiveSync cable. Am I correct? What port should use the CF card I told you? I've also tried with COM7, COM3, COM2, COM9, COM5 and COM8. These are the names of possible serial ports that method GetPortNames() returns me. Could anybody deeply explain me for what kind of communication is each port used?
Thanks again.
Markus Humm - 31 Jan 2006 19:25 GMT Lonifasiko schrieb:
> I just forgot a couple of details: > [quoted text clipped - 5 lines] > ports that method GetPortNames() returns me. Could anybody deeply > explain me for what kind of communication is each port used? Hello,
afaik these ports may all be different on different devices. I don't know any standard for this. One might be the infrared one, one might be bluetooth...but who knows which one?
Greetings
Markus
<ctacke/> - 31 Jan 2006 12:55 GMT So if you connect with Hyerterminal you see readable data coming over? I don't understand the problem any more.
-Chris
> I've also tried with ActiveSync synchronization cable connected to COM1 > port of my PC. I run the application from my PPC, send the commands and [quoted text clipped - 9 lines] > > Thanks. Lonifasiko - 31 Jan 2006 13:50 GMT Hi guys,
Finally with a little help I build up a null modem adaptor (I don't like HW definitively) and placed it between my device and the serial cable coming from PDA's cradle. Run the program and data is correctly received! Incredible but true! All problems were because I needed a null modem adaptor, that indeed was suggested to me here in this thread.
Therefore, I'm now using the ActiveSync serial cable for serial communication and from now on I'll use it even more ;-) Thanks very much for your help!
The other old problem: Do you remember my CF card providing my PDA a serial port? What could I do with that? Should CF card use as well COM1 as AS serial cable does? I've also tried placing the null modem adaptor between my device and the CF card's serial port but nothing occurs. Seems like that serial port is not very reliable. What do you think about?
Thanks very much.
Chris Tacke, MVP - 31 Jan 2006 17:24 GMT Why is that incredible? You have to have the Rx on one end tied to the Tx on the other for data transmission to occur - that's how hardware works.
-Chris
> Hi guys, > [quoted text clipped - 17 lines] > > Thanks very much. Markus Humm - 31 Jan 2006 19:29 GMT Chris Tacke, MVP schrieb:
> Why is that incredible? You have to have the Rx on one end tied to the Tx > on the other for data transmission to occur - that's how hardware works. Yes, but normally no manufacturer writes on the pacage or manual how the RS232 cable from the PDA is wired and that one needs a null modem adaptor for communication with devices other than PCs.
These silly manufacturers symply pull their own legs by assuming that anybody buying a RS232 cable for a PDA wants to synchronize over it. They mostly can't imagine that most customers buying such a cable have other use for it!
Greetings
Markus
Markus Humm - 20 Jan 2006 17:45 GMT Hello,
that standard HP cable is not only usefull for sync, it also provides a standard COM1 on your device! The only problem for you: it has crossed lines (Rx and Tx signal lines are crossed), which is necessarry for connecting two PCs with each other or your PDA (which is like a PC) to a PC. It's on the other hand useless for a direct connection to a pheriperal device. But there is a solution to this: you need a thing called "null modem gender changer". Most of them are male to female, so you'd need another thing called "male to male adaptor", but look at expansys, I think they sell a "null modem adaptor male to male". This is what you need.
Greetings
Markus
Sebastian@appliedpda.com - 31 Jan 2006 23:46 GMT Hello,
The built-in rs232 serial port is always labeled COM1: , with other ports being assigned by their driver. I have seen Bluetooth ports at COM6 and COM8, COM2 and COM3 usually deal with RawIR and IRCOMM. Compact Flash serial cards can usually find a place at COM4, and so forth. If you're curious to identify some of these ports, might I recommend you try our software product, PocketDAQ Pro (http://www.appliedpda.com). It will scan through your registry and display the available COM ports, with the ability to interrogate any device connected to them as well. Please check out our connections page (http://www.appliedpda.com/Products_PocketDAQ_connections.html); as this should help explain further regarding connecting devices to your Pocket PC unit.
Hope this helps!
Cheers,
Sebastian Dwornik Applied PDA Software www.appliedpda.com
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
|
|