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

[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

[Scampy]

Interesting project.

I'm no expert on schematics, but something doesn't sit right with the coms section. The 5v logic is used to turn on the 2n3906 via a 4k7 current limiting resistor. To prevent a direct short R10 is used, with R8 restricting the current drawn through the transistor. Normal RS232 ports like to use 12v not 5v as shown, so wondered if this could be part of the problem. But then in the linked post it must of worked for the OP who designed the volt meter ?? uhmm.

Just for clarity, I would get an FTDI based 5v USB to Serial TTL converter, that is seen as a normal com port by the PC and see if that works... If so then the com1 port on the PC is not getting a true voltage and corrupting the system. In the original schematic there is a 20v max line. If this was 12v and the emitter of the transistor was connected to this line than that might work as it's closer to the normal RS232 voltage levels, but then again - I'm no expert and wouldn't want you to damage the PC.

One other thing you can try - check the com setting in the serial capture program and set the flow control to none... I found that with this set to any other option in many serial terminal programs you get garbage displayed on the screen.

Disclaimer: you follow any suggestions at your own risk.

[fratello]

Thanks for support !
The schematic is "valid" since with the original soft works just fine ... When I "give up" to voltage monitor program (VB) I am unable to receive consistent data.

[Scampy]

Hey, wasn't being negative....like I stated - I'm no expert... if it works with the original code then the hardware is fine....

[mackrackit]

You screen shot shows 300 baud, that is why I gave the example that I did.

Now I notice you code a schematic showing 2400 baud.....