Serial Port Component For Lazarus Pit Red Serial Communication And

Serial Port Component For Lazarus Pit Red Serial Communication And

Sometimes when chunks of communication are not that long you can fix this by putting Application.ProcessMessages in comm loops or by putting it right after one serial communication and before next one is started.

The component then fails at the Application.processMessages line.

Can I tell it only to run when I request DataAvailable and not to trigger the RX event.

They should be defined in file termios.inc.

In other operating systems andor Lazarus versions they are, but not in Lazarus 2.0 under Raspbian Stretch, Nov 2018 edition.

As a quick and very dirty intermediate fix I replaced the constants in these lines with literal expressions.

But anyway: components are not the way to go here, simply use synaser in a non-visual manner.

That would skip any incompatibilities caused by the component author and is much easier in the end.

No sleur en pleur (dutch) or drag and dump programming involved.

Keep components to the visual parts of your application is my personal opinion.

The problem is that when I fire up the Lazarus program it has difficulty connecting to the Arduino.

The receive light on the Arduino flashes to show that I am interrogating it but the transmit light stays off.

On the other hand I do NOT have that problem when I interrogate it from the Arduino monitor - it responds immediately and correctly.

So it looks as though LazSerial may not be turning on Rx I could really use some help here Im ready to burn it.

Heres the Arduino: void loop() Code borrowed and modified from Robin 2 on Arduino forum.

When the echo is turned on, nothing comes back after connection.

E34 queries the laser on Serial2 which returns a string of info 112 characters long, etc.

The point is, that if I send V235 from the Arduino monitor, there is a buzz and the valve switches to position 5 and returns V23Valve to pos 50 When I start the Lazarus program and send the same command, nothing happens.

The Rx light on the Arduino flashes but there is no flash of Tx or a return.

It never sees data available and exits after if form1.LazSerialArduino.DataAvailable then.

Delays occur only when the program is connected to the COM port.

FormCreate ( Sender: TObject ); begin end; procedure TTenesiCreator.

FormClose ( Sender: TObject; var CloseAction: TCloseAction ); begin If Tenesi.

Timer2Timer ( Sender: TObject ); Var HH, MM, CC, KK: word; s, Comand: string; begin Label1.

When that main thread is blocked with something as slow as serial communication, windows messages do not get processed and your application is not responding looking frozen until communication is finished.