Scaling ADC Result to a Set Range

[richard]

try
HSEROUT ["ADCInVal=", DEC ADCInVal, " ", LCD_INST,LCD_L2, "MotorDuty=", DEC MotorDuty, " ",13,10]

[RossWaddell]

I used the HSEROUT line exactly as above and when I turn on the power:



Then, as I turn the trim pot wiper:



The serial LCD is 2400 baud by default and that's what I have set in code, but maybe there's some timing issues?

[RossWaddell]

If I'm using a PIC16F1825 how do I know whether to use the USART or EUSART settings from Mister E's PIC Multi-Calc application? This is what I have set currently:

DEFINE OSC 16               ; Set oscillator 16Mhz

DEFINE HSER_TXSTA   20h     ; Set transmit status and control register
DEFINE HSER_BAUD    2400    ; Set baud rate
DEFINE HSER_CLROERR 1

OSCCON    = %01111000       ; 16MHz internal osc

PAUSE 100

APFCON0.2 = 0               ; Tx on RC4 for LCD display
APFCON0.7 = 0               ; Rx on RC5

BAUDCON.4 = 1               ; Transmit inverted data to the Tx pin

I see that Mister E's app doesn't use DEFINE HSER_BAUD. For USART I get:

DEFINE HSER_RCSTA 90h ' Enable serial port & continuous receive
DEFINE HSER_TXSTA 20h ' Enable transmit, BRGH = 0
DEFINE HSER_SPBRG 103 ' 2400 Baud @ 16MHz, 0.17%
DEFINE HSER_CLROERR 1 ' Clear overflow automatically

For EUSART:

DEFINE HSER_RCSTA 90h ' Enable serial port & continuous receive
DEFINE HSER_TXSTA 24h ' Enable transmit, BRGH = 1
DEFINE HSER_CLROERR 1 ' Clear overflow automatically
DEFINE HSER_SPBRG 130 ' 2400 Baud @ 16MHz, 0.0%
SPBRGH = 6
BAUDCON.3 = 1         ' Enable 16 bit baudrate generator

Which should I use? And should I continue to use DEFINE HSER_BAUD which I think I got from this board a ling time ago?

[richard]

either setting will work the 0% error eusart option is probably best ,
if you set the baudrate regs manually ie
DEFINE HSER_SPBRG 130 ' 2400 Baud @ 16MHz, 0.0%/SPBRGH = 6
or
DEFINE HSER_SPBRG 103 ' 2400 Baud @ 16MHz, 0.17%

then DEFINE HSER_BAUD should not be used ,it may cause your setting to be overwritten

ps
baudrate error is not your display problem, you need to find out
1. how to initialise your display and how long it takes to happen
2. how to send control codes to the display ( seems $fe is not correct)

do you have any docs for the display / or a model no ?

[RossWaddell]

I switched to using the EUSART DEFINEs & register settings (commenting out the original ones) and it seems better (no initial wonky characters) but the 2nd line still isn't going to the 2nd line. Maybe if I split out the instruction for the 2nd line with a 5 ms pause?

Here's the data sheet for my serial LCD.

[Archangel]

From Data sheet
Smart Linefeed (control-J, ASCII 10)
Move cursor down one line. If immediately preceded by carriage return, linefeed is ignored

Try it without the 13, see what happens. Or try it with only 13 (more likely)
Failing that, if your message never changes, add spaces between " and MOTOR

[richard]

none of these are correct

#IFDEF USE_LCD_FOR_DEBUG
LCD_INST CON 254 ' instruction
LCD_CLR CON 1 ' Clear screen
LCD_L1 CON 128 ' LCD line 1
LCD_L2 CON 192 ' LCD line 2
#ENDIF

LCD_CLR CON 12 ' Clear screen
LCD_HOME CON 1 ' HOME
LCD_NEXT_LINE CON 13 ' CR does this go back to line 1 when current line is line2 ? seems it will go to first pos of line

LINE 2
WOULD BE HSEROUT [16,80] to be sure


TRY
HSEROUT [1,"ADCInVal=", DEC ADCInVal, " ", 13, "MotorDuty=", DEC MotorDuty, " "]
or
HSEROUT [1,"ADCInVal=", DEC ADCInVal, " ", 16,80, "MotorDuty=", DEC MotorDuty, " "]


ps the display needs 1000ms delay to power on/boot before you try to write to it

[RossWaddell]

none of these are correct



LCD_CLR CON 12 ' Clear screen
LCD_HOME CON 1 ' HOME
LCD_NEXT_LINE CON 13 ' CR does this go back to line 1 when current line is line2 ? seems it will go to first pos of line

LINE 2
WOULD BE HSEROUT [16,80] to be sure


TRY
HSEROUT [1,"ADCInVal=", DEC ADCInVal, " ", 13, "MotorDuty=", DEC MotorDuty, " "]
or
HSEROUT [1,"ADCInVal=", DEC ADCInVal, " ", 16,80, "MotorDuty=", DEC MotorDuty, " "]


ps the display needs 1000ms delay to power on/boot before you try to write to it

What makes you think they're not correct? The clear screen command has worked just fine all along. Nonetheless, I will try what you suggest.