Serial port

[Lauriet]

Everything is a file.......right ?

I want to use the serial port to simply write and read strings thru it.

Can I just:


assign(f, 'ttyxxx');
rewrite(f);
write(f, 'whatever');


Of course I would have to of setup the baudrate etc.

[MarkMLl]

No, you can't. WriteLn() etc. take a parameter of type text, not of type file.

You can do it with a lot of futzing around by messing with the low-level implementation of the buffers etc. as shown in the telnet server project in my Git repo, but (a) that's at the whim of the developers who might decide to break it and (b) it is likely to depend on the OS (and you've not told us what you're using).

MarkMLl

[Lauriet]

Well, what if:

var
  f : text;

assign(f, '/dev/ttyUsb');  { for a usb to serial adaptor}
rewrite(f);
write(f, 'some stuff');

But doesn't /dev/ttyUsb exist as a file ???

[CM630]

I use https://github.com/JurassicPork/TLazSerial . I found no wiki for it, but it has some examples.

[Nimbus]

Or use synapse
https://wiki.freepascal.org/Hardware_Access#Synaser

[Lauriet]

Hmmmmmm 

Maybe I need to google unix/linux sites cause I seem to remember in the dark past being able to use the port as a file. The other options will be OK........but, you know, enquiring minds must have answer.


Here is what "deep thought" says:
In Linux, serial ports are treated as special files within the /dev directory. This allows you to interact with them using standard file I/O operations and utilities, making it easy to read, write, and redirect data to and from serial devices.

[cdbc]

Hi
Hmmm, if I were you, I would have a 'LookSee' at @MarkMLl's github thingy and see how he does it... 
Regards Benny

[paule32]

it give the libusb library.

[MarkMLl]

Hi
Hmmm, if I were you, I would have a 'LookSee' at @MarkMLl's github thingy and see how he does it... 
Regards Benny

Basically, I'm pretty sure that people have looked at direct file access to (typically) /dev/ttyUSBn (on unix, YMMV) in the past and found it wanting. It might be worth trying again though, but there's lots of things like getting the control lines set that you have to use ioctl() for.

The serial.pp unit which is a standard part of the RTL is OK for Windows and Linux, although I've not done any maintentance on it recently. It's untested with the BSD family of OSes, i.e. including Macs. There's also another support file in one of my Github repos that does things like checking how much data is available: the comments go into some detail about a nasty kernel-level problem that affects Linux.

The telnet stuff includes setup of the low-level buffers that support WriteLn() etc. That probably isn't necessary /if/ going directly to the named port works... basically, I do a lot of instrumentation access and normally serial.pp plus possibly Str() etc. is entirely adequate.

MarkMLl

[ccrause]

Basically, I'm pretty sure that people have looked at direct file access to (typically) /dev/ttyUSBn (on unix, YMMV) in the past and found it wanting. It might be worth trying again though, but there's lots of things like getting the control lines set that you have to use ioctl() for.

As said above, you can.  Below an example using virtual serial ports complements of socat (tested on Linux only):

Code: Bash  [Select][+][-]

1. socat -d -d pty,rawer,echo=0 pty,rawer,echo=0
2. 2025/05/23 12:38:35 socat[307365] N PTY is /dev/pts/11
3. 2025/05/23 12:38:35 socat[307365] N PTY is /dev/pts/12
4. 2025/05/23 12:38:35 socat[307365] N starting data transfer loop with FDs [5,5] and [7,7]

Use one endpoint as file in Pascal:

Code: Pascal  [Select][+][-]

1. program Project1;
2.  
3. var
4.   f: text;
5.  
6. begin
7.   Assign(f, '/dev/pts/12');
8.   rewrite(f);
9.   write(f, 'Text from FPC');
10.   CloseFile(f);
11. end.

Open the other end point in a terminal like app, in this case minicom:

Code: Bash  [Select][+][-]

1. Welcome to minicom 2.8
2.  
3. OPTIONS: I18n
4. Port /dev/pts/11, 12:42:24
5.  
6. Press CTRL-A Z for help on special keys
7.  
8. Text from FPC

So it "works" (reading data quickly becomes challenging), but as MarkMLl said, you don't have access to settings such as baud rate, parity, stop bits, blocking / non blocking transmission etc.  There is a good reason for having several serial port libraries and components - quite a bit more than just file I/O is typically needed to interface with a serial port.

[Lauriet]

Socat looks interesting:

would I have to set baudrates and stuff beforehand ???

[Lauriet]

I've tried serial.pp but the SerOpen('/dev/ttyACM0') returns with -1.......so i guess it wasn't opened.

Did i give it the right param ???

[af0815]

-1 can be returned if the device is used by another process or not correct freed from an older process. And only one process can work with this device and you must have the rights to use the device. By default a normal user have no rights for the devices.

[ccrause]

Socat looks interesting:

It is useful to perform testing without hardware. Since socat is software emulation it cannot as AFAIK emulate baud rate mismatches.

would I have to set baudrates and stuff beforehand ???

If you are referring to assigning a serial port as a file, then yes the baud rate etc should be configured separately from Pascal's file handling.

[ccrause]

-1 can be returned if the device is used by another process or not correct freed from an older process. And only one process can work with this device and you must have the rights to use the device. By default a normal user have no rights for the devices.

+1

Check permissions of /dev/ttyUSB0, does it include your username or a group which you belong to?