Help with Maxim Ibutton "IF THEN ELSE" statements please

[andybarrett1]

Laughs...

Yes BOS Plant ..... Told if Really lucky might get to see your 4 Queens of steel making too....

Before dining in style at Deans on Brigg road !

Thanks for help again all

[EarlyBird2]

You saw the four queens!

I bet that made your day.

I assume Deans is a burger van.

You are welcome.

[Dave]

Steve, I beg to differ about your statement:"Your if correct then labels construction can not be in one line format." Oh really, and what makes you say that? If the statement is TRUE the operation is passed to the address of Correct#. Although it is not the way I would write the compound statement it is 100% acceptable.

[EarlyBird2]

Steve, I beg to differ about your statement:"Your if correct then labels construction can not be in one line format." Oh really, and what makes you say that? If the statement is TRUE the operation is passed to the address of Correct#. Although it is not the way I would write the compound statement it is 100% acceptable.

Dave you are correct as Henrik's post has already demonstrated. We both agree that we would not write the compound statement this way. My biggest objection is the use of the 'goto' statement which although perfectly valid is an instruction I was taught not to use a long time ago. I read the "Correct#" as a gosub instruction not a goto statement which was my mistake.

[Amoque]

It is typically necessary to use parenthesis between logical comparisons as:

If (Serial[1]=$15) and (Serial[2]=$D3) and (Serial[3]=$7D) AND (Serial[4]=$16) AND (Serial[5]=$00) AND (Serial[6]=$00) then correct1

I believe that it forces a Boolean comparison rather than a mathematical evaluation.

One last - is it necessary to compare ALL bytes, or might you only compare say... the first one. This would seem to yield a unique condition and save the effort and complexity of so long a line:

If (Serial[1]=$15) then Correct1

[Demon]

...

One last - is it necessary to compare ALL bytes, or might you only compare say... the first one. This would seem to yield a unique condition and save the effort and complexity of so long a line:

If (Serial[1]=$15) then Correct1

Speaking out my bellybutton, I'd say yes. The other serial numbers still have to be validated (knowing absolutely nothing about his application).

Robert

[EarlyBird2]

There is some good code here

http://www.picbasic.co.uk/forum/cont...r-nine-of-them

I particularly noted there is no pause between the owout and owin.

[HenrikOlsson]

Hi,

Tried the above and variants of it....It is now just going staight to the gosub routine (wrong) I suspect because with no Ibutton in place the "Serial Number" is after all wrong!!

Well, if what you're saying is that you don't actually have an IButton connected then I think you've found the problem. Of course the numbers will be wrong, none of the IF statements will evaluate TRUE so the exection will fall thru to the GOSUB wrong statement.

Help........!!!!

This may sound like a totally crazy idea but you might try connecting an IButton and see if that possibly helps.

:-)

/Henrik.

[andybarrett1]

Speaking out my bellybutton, I'd say yes. The other serial numbers still have to be validated (knowing absolutely nothing about his application).

Robert

Yes they do ALL need verifying...

BR
Andy