Hello JP,
yes, I 'RTFM'
, that's how I installed it in LZ1.4.2, after that way of installing it, it gave me when compiling a program the first time an "'LazSerialPort' not found error". Sorry, I cant remember what it was exactly. That error message went away, only after using the projectinspector.
I just removed the path from the projectinspector, voila, now it works without the earlier added path and compiles without any warnings. Again, might have been my mistake (maybe because I tried to use synaser additionally in the 'uses' declaration (sometimes mentioned here in the discussion), what I should not have done/needed).
The FT232 drivers I had been using, were from something beginning 2015, which came with Win10-"Out-Of-The-Box". I just checked, and you're right, there are newer ones. I just updated to version 2.8.30.0 dated 08.07.2015. Now it works perfectly, even without tweaking inside the driver setup, not loosing any characters at all, even with heavy system workload on the weak IntelAtom. Thanks for the hint.
Two more question: Right now, I am using only the OnRxData event for receiving chunks of incoming bytes via LazSerial.ReadData. Is there a way to know, if or which of the byte(s) that I read had frame or parity error(s)? Or will the badly transmitted bytes be skipped and only the OnStatus event be raised?
Another thing: When trying to open a none existing COM the debugger raises an exception, when continuing, message says that "pressing Ok might risk data corruption", normal, or how to avoid that?
Is there some detailed documentation (of the (class)interface) of LazSerial somewhere that I havent found, so I would not bother putting up those (dumb) questions?
Thanks again, really appreciated.
Greets, AD
P.S. My native language is also not english