Same code in different Pins

[skimask]

This is another one of those examples where arrays act differently depending on whether a Constant or a Variable is used as the index.
Using the same statement...
owout pin.0[index], 1, ["data here"]
If index is a Constant, it does what you thought, and will use the index to select the Pin as an offset from PORTA.0. So 8 would be PORTB.0. But then, you can't change it at run-time.
IF index is a variable, then it makes it an Array operation that will read the value of the indexed Pin (0 or 1), that value then becomes the "PIN Number".
When a statement works 2 different ways like that it's hard to grasp sometimes.
Not sure why meLabs did things that way.
<br>

Might be the difference between a $250 compiler and a $2,500 compiler.
But I got what you were getting at.

I think the original post'ers only option is to do the SELECT CASE thing, combine all OWOUT's into one place, use a generic "data here" string type array variable and go with it.

[Darrel Taylor]

I think the original post'ers only option is to do the SELECT CASE thing,

Well, I think Josuetas' best option can be found in Post #4
<br>

[skimask]

Well, I think Josuetas' best option can be found in Post #4
<br>

True, but what if the pins are on PortA, or D, or E, or F, or G, or H, or J

[Darrel Taylor]

True, but what if the pins are on PortA, or D, or E, or F, or G, or H, or J

Then you would change the PORTL and or PORTH assignments in the .bas file for the chip you are using.

PORTL and PORTH determine which ports are used for "Pin Numbers".
PORTL is 0-7
PORTH is 8-15
<br>

[skimask]

Then you would change the PORTL and or PORTH assignments in the .bas file for the chip you are using.

PORTL and PORTH determine which ports are used for "Pin Numbers".
PORTL is 0-7
PORTH is 8-15
<br>

Are you talking about the .bas file in the PBP directory?
I would've thought the compiler would go nuts if you changed anything in those .bas files... I know you can change the .inc files....hmm... interesting thoughts brewing in my head now...
Thanks a lot...now I got more crap to think about!

[Darrel Taylor]

Yes, the .bas file in the PBP folder. ie. 16F877.BAS

And, just like you do with the Config lines in the .inc file.
You can comment out the PORTL/H and TRISL/H lines, which allows you to define them in your main program.

Then you can...

PORTL   VAR     PORTA
TRISL   VAR     TRISA
PORTH   VAR     PORTD
TRISH   VAR     TRISD

Which puts 0-7 on PORTA, and 8-15 on PORTD.

Or to whichever ports you wanted.

[keithdoxey]

Then you would change the PORTL and or PORTH assignments in the .bas file for the chip you are using.

PORTL and PORTH determine which ports are used for "Pin Numbers".
PORTL is 0-7
PORTH is 8-15
<br>

Hi Darrel,

I have looked in the .bas file for the 18F452 and located the following code

PORTL   VAR     PORTB
PORTH   VAR     PORTC
TRISL   VAR     TRISB
TRISH   VAR     TRISC

Would I be correct in assuming that you also have to "adjust" the TRISL and TRISH aliases as well?

I take it that the ports dont have to be consecutive so that I could put

PORTL   VAR     PORTB
PORTH   VAR     PORTD
TRISL   VAR     TRISB
TRISH   VAR     TRISD

Which would give me 0-7 = PortB.0-PortB.7 and 8-15 = PortD.0-PortD.7

If so that greatly simplifies something I am trying to impliment. The reason I want to change PORTH from C to D is that I need to use the USART which is on C6 and C7 so that would only give me 14 useable pins.


DOH !!!!

Thatll teach me not to make sure I have a newly refreshed view of a thread before I post a reply !!!!

[Darrel Taylor]

I hate when that happens!

At least everything you said was correct.
Could have been worse.

Hey Josuetas,
Still with us?
<br>

[Josuetas]

Thanks Darrel, yes i am here.... i wasnt but now i am....

Well that is great that at least helps me reduce everything, bad thing is that i already made the PCB, i should get it by thursday... :P

God thing is i Used Portb(ALL) and PortC(2Bits) and portD (2 bits), and PORTA (4bits) 16 1Wire devices.

So i Guess by now i will use Darrel`s recomendation for all portb and change the .bas to use portb A, and maybe handle the rest of the bits with select case :'(.

Darrel by the way.. How then do you use DEFINES to work with your include files? (i dont relly know if yours ), does this mean that once the defined is set one is supposed to stay with it and not change it?

Thanks to all for your replies, I am still hoping something better could be done

Bye