Delay without using pause

[HenrikOlsson]

Hi,

Even basic logic doesn't seem to work !!!

if Cvar => 1 or Cvar =< 10 then

Can you tell me when the above is NOT evalutated true?
When CVar is 0? When CVar is 8? When CVar is 11? When CVar is 25?

EDIT... seems it likes if Cvar =>11 and Cvar =< 20 then... rather than OR

I think YOU like it better with AND rather than OR. The compiler and the PIC likes either one equally well - and it works as expected, just not the way YOU want it to.....

/Henrik.

[Art]

You realise a zero value skips that whole block right?
Speed probably is no issue here, but you’re making it work hard!
It would matter if you’re watching a tilt sensor on a moving part or something like that.

If Cvar < 13 then
If Cvar > 9 then ShowLCD4
If Cvar > 6 then ShowLCD3
If Cvar > 3 then ShowLCD2
If Cvar != 0 then ShowLCD1
endif // Cvar < 13

[Art]

The only difference between the ShowLCDx commands is x constant?

Pid_channel=x

I had a play with every consideration for the micro, and no consideration for the Human

i var byte; bonus loop counter
x var byte; initial value to subtract 3 from


x = 9
If Cvar < 13 then
for i = 3 to 0 step -1
If Cvar > x then
Pid_channel=i
LCDOUT $FE,$C0,"Viv",DEC1 Pid_channel+1," "
TempC = Temperatures(pid_Channel)
gosub read_dht 
LCDOUT $FE,$C0+5 
TempWD = TempC
GOSUB TempToLCD
; if nothing else calls TempToLCD it can go straight in here
LCDOUT $DF
if SensorActive(pid_Channel) = 0 then lcdout $FE,$C0+5,"N/C"
LCDOUT $fe,$94,dec Cvar
goto check
; I don’t see check in what you’ve posted
; but you can drop it straight here if nothing else goes there
endif
x = x - 3
next i
endif;

[Scampy]

Art,

Thanks for the suggestion.... like I said my original code was bulky and crude, but worked, but I know it could be made simpler, but after 10 hrs of coding I think my brain just gave up

[Art]

It was really just a play... It's not simpler for the Human to read six months later.
Wherever there's not likely to be a performance problem,
and thinking of the possibility of having to adjust those constants later,
I'd avoid the above code like the plague!
but would personally go for the smaller block directly above that.

[Scampy]

It's not simpler for the Human to read six months later.
Wherever there's not likely to be a performance problem,
and thinking of the possibility of having to adjust those constants later,
I'd avoid the above code like the plague!
but would personally go for the smaller block directly above that.

That's the thing, I can see the need for tight compact code in a commercial arena where costs etc matter, but for home projects I like things more simpler to follow. As mentioned, it might not be the best way, but if it gets the end result I'm after, and there is little impact on speed then I'm happy. If it means I have to throw an overkill PIC at it to maintain the performance, or to have enough memory to hold my bloated code then so be it