pulsin followed by serin2 problem

[Dwayne]

Hello Scott...

Thats it...

you are going SUBROUTINE and instead of branching to the END of the subroutine, you are branching OUT of it with a goto statement!!!

THAT IS WRONG! (Cruising for a bruising.)...Maybe some others can verify ths for me and you.

If I were you, I would *always* branch to the Return statement when you are into a Subroutine. Helps clear the stacks and all that good stuff. If I were to place my bet, it would be located here.

Dwayne

edit:
Took another quick look at your code...(very quick)

case else
return

End select

I am not sure about this.. Its been a while.. But usually you want your return AFTER the end select...

[mister_e]

It's amix of many things. One thing scratch my brain

main: 
    input PORTB.0
    input PORTD.4
    gosub xmit_off
    gosub wait_for_t0

wait_for_t0: 
    if portb.0= 0 then wait_for_t0 ' loop until rssi goes high

Take care of the Gosub / Return use. It's amazing how fast your program can behave weird when using few nested gosubs...

the following snip is the source of your headache

wait_for_t0: 
    if portb.0= 0 then wait_for_t0 ' loop until rssi goes high
    
    pulsin portd.4,1,PLENGTH1 ' MEASURE TIME C2 IS HIGH AND STORE
    IF PLENGTH1 > 255 AND PLENGTH1 < 270 THEN COUNTPULSes ' 42 usec error allowed
    gosub get_comnd
        ' made into sub routine get_cmnd 
        'serin2 b2,16780,1000,wait_for_t0,[WAIT ("$$"),cmnd] ' get command wait $$ timeout 1 secs added
        'HSEROUT ["debug command = ",dec2 cmnd,13,10]
    GOTO wait_for_t0 
    '
    '
    '    
get_comnd: 
    serin2 b2,16780,1000,wait_for_t0,[WAIT ("$$"),cmnd] ' get command wait $$ timeout 1 secs added
    HSEROUT ["debug command = ",dec2 cmnd,13,10]
    return

easy to overflow the stack with this

[Acetronics2]

Hi, Steve

have a look there : http://www.picbasic.co.uk/forum/showthread.php?t=1952

I had a similar problem there, It seems that having GOTO',s outgoing and coming back to sub's did not work very well ...
IF - Then, placed after the GOTO line ( in the sub ...) tests had always "yes" as a result ...
This was added to a page boundary crossing ... ( worked on a 628, but no more on a 648 !!! )

The solution for me was to place the program bits in good order ( all sub's at the end of the program and no "main" lines after ...

Alain