Multiple if then optimization

[Mugelpower]

Hi Darrel,

looks impressive to me like a motorcycle to a small boy.....

Whats this command:

Uin = Uin */ 124 ; same as (* 100 / 207)

|
|
|
the above means two mathematic orders in one? something like shifting bits?

there would be a small mistake but thats totally acceptable because the bargraph is that crude which is really fine enough.

will test that of course although there should be no need.....

regards

Mugel

[Darrel Taylor]

The */ operator first multiplies the 2 values (Uin * 124).
Then it discards the low byte, and returns the rest.
So effectively, it divides the result by 256, without having to do the divide part.

100 / 207 = 0.48309178
124 / 256 = 0.484375 ; not exact, but pretty close

You're correct that there are small differences between the 2 formulas, but the error is less than +/- 1. And, you will never see a difference with the resolution of a 16 block bargraph.

And, there probably is a need to test it.
I was using a 16F877 with a 4x20 LCD. Could have missed something for your 16F628A and 1x16 LCD.
<br>

[Acetronics2]

Hi, Darrel

Could you tell us for LCD Initialization at powerup ...If Uin first value is > 10 ... I do not see any ???

you just suppose exhaust is air filled ???

Alain

[Darrel Taylor]

I'm not sure what you mean Alain.

If the first value is > 10, it will just draw the bargraph like normal.
It doesn't do anything until a serial byte is received.
<br>

[Acetronics2]

I'm not sure what you mean Alain.

If the first value is > 10, it will just draw the bargraph like normal.
It doesn't do anything until a serial byte is received.
<br>

Hi,Darrel

What I ment is you initialize the LCD ... ONLY if the value is < 10 ... ( when writing TOO LOW )

What if you stop the engine and start it again ??? ... first value will be > 10 , due to the exhaust gases still in the exhaust tubing ... and I do not see any LCDOUT $FE,1 in this figure.

Alain

[skimask]

What if you stop the engine and start it again ??? ... first value will be > 10 , due to the exhaust gases still in the exhaust tubing ... and I do not see any LCDOUT $FE,1 in this figure.
Alain

Exhaust gases might still be in the tubing, but I wonder how quickly the sensor will cool off and not make a decent output. In my experience, those things cool off fairly quick. But then again, the 3/4 wire ones heat up pretty fast too...

[Mugelpower]

Hi Guys,

now thats stuff I´m into ! Those lambda probes are reacting pretty fast when hot, about the whole scale from too lean to too rich in half a second . Reliable results will be in after about half a minute with a cold engine starting when using 4 wire probes, 2 minutes or more with one wire probes and those one wire probes without heating are useless for idle control, heats too low. You can see lots of hidden stuff like choke or accelerator pump work or fuel cutoff when stepping off the gas. Funny to watch but most times absolut neccessary for the first setup.

[Darrel Taylor]

What I ment is you initialize the LCD ... ONLY if the value is < 10 ... ( when writing TOO LOW )

What if you stop the engine and start it again ??? ... first value will be > 10 , due to the exhaust gases still in the exhaust tubing ... and I do not see any LCDOUT $FE,1 in this figure.

Oh, you mean the "Clear Screen".
Since it writes to all 16 characters on each pass, I used "Home Cursor" ($FE,2) instead of "Clear Screen" ($FE,1) to prevent blinking of the display during updates.

Or, if you're referring to the Power-On initialization that gets rid of the black blocks and makes the LCD work in the first place .... Mugel didn't have any specific initialization sequences in his original program and reported it to be working. So I assumed his display didn't need it.

The first character sent to the LCD will cause PBP to initialize the display (if it hasn't already). It doesn't have to be $FE,1.
<br>

[paul borgmeier]

A Different Approach (317 Words ... without most of Darrel's amazing methods, which means there is room for more codesavings)

;@__config _XT_OSC & _WDT_ON & _MCLRE_ON & _LVP_OFF & _CP_OFF
CMCON=%00000111
DEFINE DEBUG_BAUD 2400   'Debug baud rate 
DEFINE DEBUGIN_REG PORTB 'Debugin pin port 
DEFINE DEBUGIN_BIT 0     'Debugin pin bit 
DEFINE DEBUGIN_MODE 1    'Debugin mode: 0 = True, 1 = Inverted 

;DEFINE OSC 4

xB0 var byte     ; SERIAL IN IS A BYTE SO MAKE IT A BYTE
;inputData var word ' variable to receive data into

' START OF MAIN PROGRAM
'
CMCON = 7 ' RA0-RA3 are digital I/O
TRISA = 0 ' PORT A is output
TRISB = 1 ' RB0 is Input others output

MAIN:

DEBUGin [xB0]

;B0 = 100 * B0  ; why do these two lines?  B0 is already a Byte so work with Bytes
;Uin = B0 / 207  ;

LCDOUT $FE, 1

If xB0 < 21 then
    LCDOUT "TOO LOW"
    GOTO OUT
ENDIF

IF xB0 < 34 then BARGRAPH1
IF xB0 < 42 then BARGRAPH2
IF xB0 < 52 then BARGRAPH3
IF xB0 < 63 then BARGRAPH4
IF xB0 < 73 then BARGRAPH5
IF xB0 < 92 then BARGRAPH6
IF xB0 < 112 then BARGRAPH7
IF xB0 < 131 then BARGRAPH8

LCDOUt $FE, $C0

IF xB0 < 152 then BARGRAPH9
IF xB0 < 170 then BARGRAPH10
IF xB0 < 181 then BARGRAPH11
IF xB0 < 191 then BARGRAPH12
IF xB0 < 201 then BARGRAPH13
IF xB0 < 210 then BARGRAPH14
IF xB0 < 220 then BARGRAPH15
IF xB0 < 230 then BARGRAPH16

LCDOUT $FE,$C0,"TOO RICH"

goto OUT

BARGRAPH16:
gosub p255
BARGRAPH15:
gosub p255
BARGRAPH14:
gosub p255
BARGRAPH13:
gosub p255
BARGRAPH12:
gosub p255
BARGRAPH11:
gosub p255
BARGRAPH10:
gosub p255
BARGRAPH9:
gosub p255

LCDOUT $FE, $80   ; line 1

BARGRAPH8:
gosub p255
BARGRAPH7:
gosub p255
BARGRAPH6:
gosub p255
BARGRAPH5:
gosub p255
BARGRAPH4:
gosub p255
BARGRAPH3:
gosub p255
BARGRAPH2:
gosub p255
BARGRAPH1:
gosub p255

OUT: 
Pause 5
goto MAIN

p255:
lcdout 255
return


END ' End of program

[disclaimer] untested [/disclaimer]