Problems debbuging

[Carlos Romero]

Hi, I'm having problems with the debbuging feature.
My @INIT goes like this:

@INIT 10
10 A = baud 96
11 Z=1
12 S=0
13 U=0
14 R=0
15 D=0
16 Q=1
17 A = pioout 9
18 J=20
19 GOSUB 370
20 J=9
21 GOSUB 370
22 A = name "AIR-A"
23 GOSUB 50
24 $0="                     "
25 $2="                     "
26 $3="                     "
27 GOSUB 90
28 RETURN

But I only get the debug in my UART when I have the original UART0.11 files running and I upload my program and config, and only the first time. When I reboot the device, it stops showing messages.
Is needed to get the UART on in my program?
 I have other problems too, getting a shell running for example (I guess I should put the Z=0 and call A=shell somewhere in the program, but it's not working... any ideas')

Sub 370 is a blinking subrutine
Sub 50 gets the adress and stores it
Sub 90 is the main program. (I could use just GOTO, but it is to mantain the flux diagram...)
The program uses the @MESSAGE interrupt.

And The last question... how much time does a device need to realise that a message cannot get to its receiver?
I have this code
0 REM MENSAJE(X,K)
100 $0=$3
101 K=800+X-33
102 A=message $K
103 E = status
104 IF E < 1000 THEN 107
105 WAIT 5
106 GOTO 103
107 S=success
108 RETURN

I have a list of addresses in 800, X is an index character starting with the ascii "!", 33 in decimal.
It works, but I don't know how much time is needed to realise that a device is off and not getting the message.

Thank you for your help

[Carlos Romero]

Oh, I've seen that the shell should only be used in the slave code... one problem less :p