![Mikrotik email settings for gmail](https://knopkazmeya.com/7.png)
![prolific usb to serial comm port problem prolific usb to serial comm port problem](https://utechcables.com/wp-content/uploads/2017/02/PL2303-USB-to-DB9-Serial-Converter-14-480x480.jpg)
When we started having issues we traced it back to these devices. I’ve worked mostly with embedded applications and we stay away from any USB dongle with a Prolific device. The VisualStudio project may do a better job of firing the receive event.Īnyway, just an observation I have seen, hope it might help. What I did is just read all the data and store it, I then append any new data received and append that to the previously stored data, I then search my new saved data for valid received data, then act accordingly on that. What complicates this is going through a USB to RS232 device, because you don’t really have control over the timing, etc. Since you read the buffer it clears it, then you get another event and get the “ady” and again you ignore. The Serial.DataAvailable may fire when “Re” is received, you go to do a "Serial.ReadAll and don’t recognize it or ignore it. So let’s say you need to receive the command “Ready” from the connected device before you send back a command. The issue here is that there is no documentation on how many bytes or the timing related to that event firing.
![prolific usb to serial comm port problem prolific usb to serial comm port problem](http://elefax.weebly.com/uploads/1/2/6/7/126728925/822624760_orig.jpg)
I will say that I have had issues with the serial.DataAvailable event.
PROLIFIC USB TO SERIAL COMM PORT PROBLEM SOFTWARE
BUT if your software is requiring receiving specific data then it might be useful: Because this is only isolated to a few devices I assume you cannot test the actual condition and am working blind? Is the issue receiving data or sending?Īlthough this is a total guess I will describe a situation that I had, perhaps it will help, perhaps not. If you are only using TX/RC & Ground it can’t get more simple. It seems to be an issue with the way that Xojo is initializing the serial port. Like I said, programs developed in other languages seem to be able to initialize the port correctly and (in many cases) will leave the port in a state where Xojo can then communicate over it.
PROLIFIC USB TO SERIAL COMM PORT PROBLEM WINDOWS
I’ve been able to narrow the problem down to the Windows build of my app (XP/7/8 doesn’t seem to matter) and a USB to serial adapter based on the Prolific 2303 chipset. The weird thing is that if the user runs the basic software which ships with the camera (written in a different language), it works just fine, and then if they immediately close and run my software it will often start communicating perfectly. The serial port is detected in the application, and apparently opens correctly, but no serial communications occur, in or out. I occasionally hear from customers that my software will not communicate with their device - in my case it is an astronomical video camera, always the same make and model. Has anyone else had problems getting Xojo to communicate reliably with Prolific 2303 chip based USB-RS232 serial adapters?
![Mikrotik email settings for gmail](https://knopkazmeya.com/7.png)