Debug/Serout/Serout2 - please, need advice ...

[fratello]

Hi !
I try to understand how work communication between PIC and PC.
I wrote this simple code :

@ __config _INTRC_OSC_NOCLKOUT & _WDT_ON & _PWRTE_ON & _MCLRE_OFF & _BODEN_ON 
 
INCLUDE "modedefs.bas"       
DEFINE OSC 04                 
        CMCON = 7               
        VRCON = 0               
        WPU = 0                 'no wake pullup
        IOCB = 0                'no int. on change
        ANSEL = %01010001       
        ADCON0 = %10000001      'right just , Vref=Vdd , ch.0 , A/D on
        GPIO = %00101001        'preset I/O
        TRISIO = %00001001      'configure direction  1=input 0=output
        OPTION_REG = %10000111

advalue        var     word

Main:
PauseUs 50                  'sample time
        ADCON0.1 = 1                'start A/D
        @ nop
        while ADCON0.1 = 1          
        wend
        advalue.byte1 = ADRESH         'get A/D value
        advalue.byte0 = ADRESL

        if advalue < 650 then
           SerOut2 GPIO.5,300,["Advalue : ",DEC advalue, 13, 10]   ; the calculated result is "93" , but ?!
        endif
goto Main

I use on GPIO.0 one 1k resistor to +5 volts and one 100R resistor to ground. Advalue is 93, don't ?!

But on RealTerm I am unable to see the "real" value of Advalue, no matter what option I choose...
What I do wrong ?!
Thanks in advance !

[Tabsoft]

Hi Fratello.

You don't say how your PIC is connected to the PC.
Whether you have the PIC connected via a MAX232 chip or direct to the PC.
e.g.
PIC -> MAX232 -> PC
or
PIC -> PC

It makes a difference on how you use SEROUT or SEROUT2.

Also, take a look in the PBP manual for the SEROUT2 command.
I don't think your MODE setting is quite right for you comms settings on the PC, not to mention what I said above about the connectivity between the PIC and the PC.
If you are trying to use 300 baud 8N1 then setting MODE 300 is most likely not correct.

Read through section 5.73 (SEROUT2 command) and then look at the table in section 8.6 (SERIN2/SEROUT2 Mode List).

With this I think you can find the correct MODE value.

A couple of more suggestions.
1. You have DEFINE OSC 04
I don't know if this is an issue since no errors are reported during compile, but you may want to use DEFINE OSC 4 instead as per the manual.
2. Try a simple program that you just send out a known text string and maybe a value via the serial port without the ADC stuff.
See if you can get just that to work with your PC and then move on to the ADC stuff.

Just some suggestions.

[fratello]

Thanks for reply !
I use simple link PIC to PC (GPIO.5 connected to DB9 - pin 2).
I tried DEBUG command too ... with same results ...
Of course I added in my program :

 DEFINE DEBUG_REG GPIO          'Set Debugin pin por
 DEFINE DEBUG_BIT 5             'Set Debug pin bit
 DEFINE DEBUG_BAUD 2400         'Set Debug baud rate
 DEFINE DEBUG_MODE 0            'Set Debug mode: 0=true,1=inverted

My schematic is based on Mr.GioppY "serial voltmeter" (http://www.picbasic.co.uk/forum/showthread.php?t=7182) with modification for my purpose ...
Mr.GioppY use, in his program :

debug  dec TmpW dig 4,dec TmpW dig 3,",",dec TmpW dig 2,Cr,Lf

but with VB program.
First I tried "Debug DEC Advalue, 13, 10" , but I have same results in RealTerm.

[Art]

for 2400 baud try mode 16780 for inverted data.
Like Tabsoft suggested, you don’t have a real RS232 serial port there.

[mackrackit]

SEROUT2 GPIO.5,19697,[ "Hello World !!! ",$D ,$A]

Try the above for 300 baud without a MAX232 chip.

[Art]

And if that doesn’t work, just get the chip to tell you what it is

mode var word
mode = 100;
WHILE mode < 60000
SEROUT2 GPIO.5,mode,[ "     ",DEC mode,"     ", $0D, $0A]
mode = mode + 1;
WEND