The following code snippet will work similarly as the one given above, but it make use of core WMI and returns a list of Management objects: The following C# code examples will return a list of Serial port names connected to the computer:įoreach (String portName in System.IO.())Īnd it is enough for further processing.NET can understand where to communicate via the port name in string like “COM1”, “COM2” etc. As a prerequisite, you need to make sure that, while the application is running, the windows user must need to have access to the ports. OK, lets first see whether we can detect the serial ports from within our application. But if you are using any specific type of devices which facilitate this kind of communication via USB interface, you can retrieve their PID/VID respectively and communicate accordingly.NET has a very useful internal classes which can make this kind of communication to be very easy and efficient. One interesting thing that you might need to remember that, when the physical serial port are being used, it doesn’t have any PID or VID. This type of communication aren’t as much easy as other similar tasks such as working with logic drive on computer via c# and need use of specific kind of communication protocol. If the device do require a serial port and your computer don’t have any, you can make use of such converters easily.
Serial communications can be done via either direct to physical serial port connected to the computer or via a USB to serial converter interface. In today’s programming tutorial, I am going to describe some basics about how we can perform serial port communication from our C#.NET applications.
0 kommentar(er)
