So bear with me while I explain the problem. I have a device that we connect to via USB port. Xojo recognizes the serial port and I can write to it. However, the device never responds. The only thing I know I have to do is set RequestToSend = false when I'm opening it up (more on this in a bit).
After going round and round with the vendor on possible causes he sent me a test utility made in .NET that simply looks at the properties of the serial port and my app then connects and communicates just fine. If I use their utility (again presumably written in .NET) used for Factory Acceptance testing and quit it, my app connects and communicates just fine as well. If I restart the Win 10 64 bit computer my app no longer communicates with the device. I *must* use one of their utilities first before I can communicate with the device.
Obviously this is not an acceptable solution. If I have to resort to creating a small .NET app that I call when starting my app I can but that seems silly.
I have tried every possible combination of Serial properties so I'm starting to think it's something lacking in the Xojo Serial Class that's causing the failure. Does anyone have any insight into this issue? Recommendations? Naturally, I'm onsite with the client. :)