I have a project in which i draw in drawing and same thing is drawn in glcd. Through serial communication, byte[] buffer_2_send = new byte[1]; byte data_2_send = 0; data_2_send = Byte.Parse(textBox2.Text);//this way you will get the value 12 in your variable //we will use a buffer because the serial_port.Write takes either a string or a buffer of data buffer_2_send[0] = data_2_send; MessageBox.Show(“” + buffer_2_send + ” ” + buffer_2_send.Length); serialPort1.Write(buffer_2_send, 0, buffer_2_send.Length); i basicaly send 12 or like this values on microcontroller but at recieving side i cant recieve respective value so plz guide me. If you have an application that writes to a serial port device through a USB adapter, and the application is hard-coded to use COM port 5, is there anything you can do so that moving a laptop that uses this application from one docking station to another will NOT cause Windows Plug and Play to assign a different COM port based on the VID of the second USB-to-serial device being different from the VID of the first USB-to- serial adapter? The docking stations both use the same peripherals, all plugged into the same USB ports.

The users of these laptops don’t have administrative rights to change the COM port in Device Manager. Some USB-to-serial adapters advertise ‘COM port retention’, but that only seems to make the laptop use the same COM port for the exact same USB-to-serial adapter (the very same one, not just one that ‘seems’ the same but has a different VID) each time the laptop is connected to that device.

DeviceSet( 'COM1 '); // We can change the baud rate, parity, length, stop bits, flow control $serial ->confBaudRate( 2400); $serial ->confParity( 'none '); $serial ->confCharacterLength( 8); $serial ->confStopBits( 1); $serial ->confFlowControl( 'none '); // Then we need to open it $serial ->deviceOpen(); // To write into $serial ->sendMessage( 'Hello! '); State of the project Interestingly enough, this piece of code that is widely untested has created a lot if interest ever since it was created, and especially nowadays with everybody toying around with Arduinos and Raspberry Pis. I receive about 1 email every month asking for help with the code or sending patches/suggestions. I think that it is time for me to remove the dust off this project and to give it a full visibility on modern tools, aka GitHub.

Bugs There is lots of bugs. I know there is. Freizeit dialog na nemeckom video. I just don't know which are they. Platform support • Linux: the initially supported platform, the one I used. Probably the less buggy one. • MacOS: although I never tried it on MacOS, it is similar to Linux and some patches were submitted to me, so I guess it is OK • Windows: it seems to be working for some people, not working for some others. Theoretically there should be a way to get it done.

Concerns I have a few concerns regarding the behaviour of this code. • Inter-platform consistency. I seriously doubt that all operations go the same way across all platforms. • Read operations. Reading was never needed in my project, so all the tests I did on that matter were theoretic. I was also quite naive, so the API is probably not optimal.

What we need is to re-think reading from scratch. • Configuration done by calling functions. This is so Java. It would be much better to be able to pass a configuration array once and for all. Furthermore, I suspect that the order of call matters, which is bad. • Auto-closing the device.