SERIN2 freezes

[KaanInal]

Hi xnihilo,

I think the problem is about STR, i mean PBP doesn't work well (not a bit) with strings.
But, i have the same problem, SERIN2 freezes when i add a timeout and label of delay. This code doesn't work:

'**
'
'Purpose: How many delays do i have?
'
'**
myRX VAR PORTB.0

myVar VAR BYTE
data VAR BYTE

CALL OnScreen

loop:

        SERIN2 myRX,396,100,delay,[wait ("N"),data]

GOTO loop

delay:
        myVar=myVar+1
        CALL OnScreen 
RETURN

OnScreen:
      lcdout $fe,1
      lcdout #MyVar
RETURN

the code doesn't go to delay label.

[mackrackit]

I think the problem is about STR, i mean PBP doesn't work well (not a bit) with strings.
But, i have the same problem, SERIN2 freezes when i add a timeout and label of delay. This code doesn't work:

Hmmm. Put the blame on the compiler when your code does not work?

Maybe you need to look at the CALL section in the manual.
And that RETURN right after that might not be helping either.

[KaanInal]

Sorry for the misunderstanding it was not a blame, i love this compiler. I didn't find any string functions on my sources, if you knew some please tell me so i can change my sources with correct ones. It was an opinion.

It was a part of my code but i don't understand what is wrong with the call? Should i use gosub? What do you suggest ?

Also,
there is an answer on this page: http://www.picbasic.co.uk/forum/show...highlight=idle

xnihilo, is that solves your problem too?

[mackrackit]

No problems

The PIC it's self is not really a string type setup, but PBP gives it a good shot by treating strings as an array. The STR modifier is for that. Yes, more string handling might be nice, or a different way of handling them... But we are so limited on memory the way it is with most PICs that it may be a shot in the foot.

CALL -- that is for "CALLING" an ASM function.

The TIME OUT/GOTO label is just that. a GOTO.
So wherever you send things after a serial time out do not use a RETURN.

SERIN2 myRX,396,100,delay,[wait ("N"),data]

GOTO loop

delay:
        myVar=myVar+1
        CALL OnScreen 
RETURN

In the above case replace the RETURN with GOTO LOOP.
Looks like that is what you want....

[KaanInal]

I got it .

Thank you by the way, that explains the "CALL and RETURN overflow" problems on my simulations .

[mackrackit]

Glad to bof soivice