no more data/variables available

You must set offset to zero before every reading with cread.

you are missing the point...

offset is incremented by number of characters received every time CREAD is processed so sooner or later you are going to run out of space (buffer array length). to receive again, you need to reset offset value. and this needs to be done over and over... right now your example shows that you reset it once but - you are using CREAD in a loop.

consider moving line 8 just before line 15 so both are always executed in tandem.

INT OFFSET, BCI
DECL STATE_T SR_T, SC_T
DECL MODUS_T MR_T
REAL TIMEOUT

MR_T=#ABS
TIMEOUT=10
COPEN(:SER_3,HANDLE)
IF(HANDLE==0) THEN
HALT
ENDIF
LOOP
IF($DATA_SER3>0)THEN

OFFSET=0
CREAD(HANDLE, SR_T, MR_T, TIMEOUT, OFFSET, "%r", BCI);
ENDIF
ENDLOOP

you need to receive data, then parse what ever the data is.

to receive data you need to create a buffer, open channel, fetch data from the channel into buffer, process what is in the buffer, clear buffer, fetch more data etc. the part you seem to be stack on is streaming... as received data is streaming in, you need to process what is already in the buffer and make room for next data to be received. this need to be carefully crafted in order to keep running... if you cannot process the received data in time, use handshaking. this allows you to tell to sender "hold on a minute, i am still busy...". and once you are ready, then negotiate to get some more data. either way this is not trivial. most examples are likely to be very basic. for this to be practical in any way or form, you will need to handle much more, including channel loss, restart etc.

also you did not state what the received values are and what they are representing so there is no telling how to decode...

Quote from m.dinio

how can i read from serial in binary format

IN $Config.dat define the variables (here just examples)

; --- variables ---
INT CNT
REAL VALUES[6]

In your program
OFFSET_CR=0
CREAD(HANDLE,SR_T,MR_T,TIMEOUT,OFFSET_CR,"%r%.6r",CNT,VALUES[])

In my post #10 I answered the question of your post #6
from my point of view: question answered!

Quote from panic mode

offset is incremented by number of characters received every time CREAD is processed so sooner or later you are going to run out of space (buffer array length)

This also is applied to your transmit buffer and I have not seen how your source code looks like.

Quote from m.dinio

sometimes cwrite command not send , why?

i using cwrite in sps.src

Not enough information for answering.

You are mixing up different questions in one thread, that's not the best idea.

and...? what about it?

it is incomplete so one cannot even tell if it would compile.

and what is the problem? keep in mind not everyone has access to a robot, certainly one of that vintage. so whatever you do, or ask, better support it with your observations... state behavior, messages, data transmitted etc.

did you read the manuals? according to CWRITE manual for KSS5.5 it is missing $CMD but manual for 4.1 does not use it. so what is your KSS version? also your o1f flag is never reset, so will let your IF statement only be processed once.

but this is just program. are you sure that wiring and port configuration is correct? what is sending data that you are receiving? are you sure the port settings are the same? do you have a loopback adapter?

if you do not have other device to talk to, it is practical to use loopback. basically it is just a DB9F connector with pins 2 and 3 connected to each other. the nice thing about this is that port settings are almost irrelevant, no external device to setup, and whatever you send comes back. so you can do the development in stages, have your code write something and make sure that this part compiles. then you can add code to read what you just sent... and program examples from manual should be piece of cake to try out.

if talking to external device, you need proper cable. type of cable depends on type of device (DCE/DTE). you can have program that compiles and runs but if wiring is incorrect, this will go nowhere...

Quote from MOM

This also is applied to your transmit buffer and I have not seen how your source code looks like.

Using CWRITE you do not need to set an offset - my fault.

But you must check the return code
CREAD : SR_T
CWRITE: SW_T

I cannot find them in your code snippet (post #15)

Hint:

search for the document "CREAD CWRITE R4.1 07.02.00 en"