Originally Posted by idpnd
Per, you have to change the dongle port settings, not the windows port settings!!
You *might* be able to use PolarCOM
input/output settings to produce a different baud rate. I have not tested this however.
PolarCOM does what any other program can do - it controls port settings through appropriate OS API. That is to say - based on the system it will call a function that sets port baud rate to whatever user selected.
1) the "baud rate" on the virtual serial
port that is visible to the system is meaningless by itself - the data is arriving over USB which has no concept
of "baud rate" (well, it has a rate, lots of bauds
2) if the serial2usb device has appropriate functionality implemented, it will apply this "external" USB-side baud rate to the physical serial
port on the other side. If it works with Maxsea
- it does sound like the device has this capability.
A bit offtopic:
There is a ton of Prolific drivers out there and under different systems I had success with different ones (XP worked with the driver that failed for Windows Vista and vice versa). The only way to find out is to try.
There is also a ton of poorly designed USB-to-serial devices based on Prolific chipset. I just discarded two that could only input, not output data - and am waiting for a new set. It's a lottery - there is little guarantee that a new device will work any better. FTDI-based devices have somewhat better track record
. This is not a fault of chipset per-se, however Prolific is less expensive so all sorts of low quality manufacturers tend to use it to build sub-standard devices.