PIC18F1320 HPWM on 2 pins

[richard]

Define ADC_BITS 4 ' Set number of bits in result

from manual

You may set ADC_BITS to values 8-16, but in reality the result will either be 8-bits or the maximum precision available (10-bits, in most cases).

DEBUG #adval

could send 1 to 5 ascii chrs for a word value {adc value 1 to 4 chrs }

DEBUGIN 1000,timeout,[adval]

how is that meant to work ? you will also discover debug sends/receives bytes not words

DEBUGIN 1000,timeout,[dec adval]
might have a chance.

simplistic async coms like this is seldom reliable, especially if the receiver has other tasks to perform other
than sitting there waiting for a transmission.

packetizing data in stx/etx codes and preferably with crc too is a better choice

[Mugelpower]

Hello Richard,
o that... Itried for hours, read many threads here in the forum, tried "dec,dec2,dec3 , hex, bin,#" and without, ADC 8 bits, ADC 4 bits. It makes simply hardly a difference. Possible outcomes are:
0 to 3
000 to 003
48 to 51

or nothing.

when I change

DEBUG adval

into

DEBUG adval,10,13

I will receive a 3 digit fast running number, impossible to read and no correspondece to the position of the poti for the analog Input.




I got the input in the 16F876A from 0 to 3
which is in the direction i need but way too coarse, then changed DEBUGIN_MODE 0 to 1 at the receiver still having DEBUG_MODE 1 at the transmitter and what: made no difference receiveived 0 to 3.
That was the point when I realized that I´m stuck.

Of course tried serin, serin2,hserin. Nothing worked.
Debug/Debugin shows at least anything at the receiver end.

maybe my include file for the 16F88 is corrupt because I changed something 10 years ago. I will control that.

[richard]

DEFINE DEBUG_Mode 0

IS INCORRECT and simply won't do anything

pbp defines must be uppercase


try it this way tx:-

DEFINE DEBUG_MODE 0
DEFINE DEBUG_BAUD 9600



DEBUG "*.*",DEC5 GLCDBM ,13,10




rx


SERIN2 PORTC.7,84,[ WAIT("*.*") , DEC RX] ;





if this is still your goal

So I guess its waaaay easier to use two
PICs than to scramble everything in just one

then you are sadly misguided , its never easier . get a better chip that's way easier
if your goal is different why not start a more relevant thread

either way post your latest code

[Mugelpower]

Hello Richard,

thank you for your fast answer.

I Know about the upper case sensitivity of Defines but it was obviously too late yesterday.

Didn´t know DEBUG and SERIN2 can be mixed.

I always thought how would one PIC know when to receive without handshake. Tried HSERIN for that with the RX and TX lines.

Didn´t work of course althoug both PICs have a USART.

Will try that at home this evening because its about noon by now and I´m at work. Nothing with PICs, just metal and engines.

regards

Mugel

[Mugelpower]

Hello Richard,

by using the right PIC you may think of something like this:

http://www.microchip.com/wwwproducts/en/PIC16F15323

I don´t believe PBP supports that one or similar new ones.

I´m shure with 10 (or 30) more IQ points I could program an older one thats supported by PBP

but I´m stuck to my own miserable brain.


regards
Mugel

[Dave]

Actually Mugel, PBP3.1 does support the PIC16F15323. At the cost of a few extra pins might I suggest something like the PIC18F26K22. It has 2 USART ports and can run @64Hhz.

[Mugelpower]

ahhh,

you are trying to talk me weak for buying PBP3?

may work......

[Mugelpower]

Hello Richard,

i tried your example and i get compilation error "DEBUG " bad expression or "SERIN2 bad expression"

I even used a PBP example that was delivered with my software and I get the same "HSERIN bad expression" compilation error.
So I have a software problem but I don´t know where to search.