Configuring the port to no flow control will make it ignore all of that and send the data regardless of the status of the other side. If the port is setup to use hardware flow control (the default setting), it will not pass data until it sees the CTS signal from the other side. Depending on the cable, it may not be properly passing the hardware handshakes between the machines. When you say that data is not exchanged, what exactly do you mean? How are you trying to exchange data? Are you opening the terminal program on both machines, setting them to the same baud and port settings, then getting nothing on the other machine when you type into the first? If this is the case, make sure you are setting both sides to no flow control. It is very different than a regular network connection. State management and error detection are the domain of the application using the port. Your terminal program will be perfectly happy doing that. You can, in fact, send things to a serial port that isn't connected to anything at all. You will never see any kind of state indicator in Device Manager. So if the hardware is there and the driver loaded, it will show in device manager regardless of whether something is actually hooked to it or not. HyperTerminal is an award winning terminal emulation program capable of connecting to systems through TCP/IP Networks, Dial-Up Modems, and COM ports. There is no supervisor function on a serial port. It isn't like a network link where Windows will tell you if a cable is unplugged. Device manager doesn't monitor the state of the serial connection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |