SdpoSerial.zip Serial port interface component for Lazarus. Serial port component for Lazarus. In most of my tutorials, I guide. Sorry for my short of knowledge of Lazarus. All done in Main Have ad a if/waitingData, makes total: ====================== serial.writeData( stOut ); if ( serial.waitingData >0 ) then stIn:= serial.readDate; label4.caption:= stIn; ====================== Results in compile-error: identifier idents no member 'waitingData' So, serial at itself is 'known' because serial.writeData and serial.readData are doing ok. Tried the following: Placed in interface-section of main: serial: TBlockSerial; Results againin compile-error: identifier idents no member 'waitingData' Then I removed 'serial: TBlockSerial;' out of interface-section.

LazSerial v0.2 Serial Port Component for Lazarus (windows and linux). By Jurassic Pork 03/2013 - 01/2017 This library is Free software; you can rediStribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later. Jul 23, 2013  Re: TLazSerial: serial port component for Lazarus (windows and linux). « Reply #26 on: July 23, 2013, 02:04:57 pm » I have installed Lazarus 1.0.6 on the PC and LazSerial installs fine and the test app works.

Then placed in interface-section: myTestSerial: TBlockSerial; And changed in the write-read code: if ( serial.waitingData >0 ) then stIn:= myTestSerial.readDate; label4.caption:= stIn; Now, I don't get compile-error! But the programm hangs imideately, no response, and shows error as in the picture. I can stop it with the red-stop-button in the LAzarus-IDE. Anyone a hint for me? 1.) Thanks for the Lazserial, great work.

I wish it would be included in the Laz.distribution package, because the installation needs some hands on. To have it work for me, I needed to point the poject inspector to the location of 'LazSerialPort.pas'. Now the compiler gives me the warning: 'other unit files search path (aka unit path) of.

Contains: lararus components Lazserial. Maybe my fault, since I am an absolute Lazarus newbie(noob).

Anyway, it works now, thanks alot again for the great piece of software. 2.) I noticed that I am loosing characters on the RS232, whenever 'Windows-Defender' is running, regardless of UART configuration/speed/workload/etc. Setup: IntelAtom Win10home-32bit with a RS232/USB converter with FT232 chipset.

It's not Lazarus(Serial) fault, but is there a workaround? 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.

Debeaking in poultry pdf online. 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. 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?