LCD_AnyPin.pbp

[PICn-It]

In your code above, you have MCLRE enabled.

But in the schematic you don't have a pull-up on MCLR (Pin 1).
<br>

I'll try adding that, thank you. I'm sorry to keep bugging you about this.

Just curious why you have LCD Data on RB2,3,4 & 5. If you simply moved them up two pins and moves E and RS down, you could use the standard PICBasic product with no modifications. I can understand if you have a PIC which doesn't have four consecutive pins available on a port, but why go to all the inconvenience when there is no need?

The circuit board is an existing design, I'd love to move things but I have to go with the produced PCB. The next thing one might wonder is how a person like me ends up with this on his plate? well I have VB, C, C++, MFC and C# experience and someone, in their infinite wisdom thought I'd be good to take this on as a "challenge". What I have absolutely zero experience with is PIC microcontrollers which seems to be a long-shot away from Windows programming.

I'm sorry if I'm testing anyone's patience over this, perhaps PBP isn't the right tool for this task, perhaps I'll look into some C implementations for achieving this task.

[Ioannis]

Unless Darrel has done this routine in C, I think you won't find a solution in other places...

Ioannis

[sayzer]

I touched nothing on your code.

Just compiled it as is.

And it works with no problem as seen in the simulation (attached).



http://www.picbasic.co.uk/forum/atta...1&d=1259222341

[Darrel Taylor]

WooHoo!
Now there's a $1000 simulation.
<br>

[PICn-It]

I touched nothing on your code.

Just compiled it as is.

And it works with no problem as seen in the simulation (attached).



http://www.picbasic.co.uk/forum/atta...1&d=1259222341

Actually I see you have a pull-up on pin 1 and also have pin 7 tied low.

I don't see how pin 7 can be any problem for me but looking at the PCB I notice it doesn't have the pull-up on pin 1.

Existing (pre-programmed) 16F883's I have on my bench are working fine when inserted into this PCB so I have reservations thinking that's the problem at hand.

Thanks for your responses everyone.

[Pic_User]

Actually I see you have a pull-up on pin 1 and also have pin 7 tied low.

I don't see how pin 7 can be any problem for me but looking at the PCB I notice it doesn't have the pull-up on pin 1.

Existing (pre-programmed) 16F883's I have on my bench are working fine when inserted into this PCB so I have reservations thinking that's the problem at hand.

Thanks for your responses everyone.

See Darrel's Question...

In your code above, you have MCLRE enabled.

But in the schematic you don't have a pull-up on MCLR (Pin 1).
<br>

Is the RW pin on the LCD connected to the PIC, or is it grounded?
<br>

[PICn-It]

See Darrel's Question...

I'm sorry I don't understand your post, but I tried it with MCRLE_OFF and it makes no difference. I must have some other issues I'm yet unaware of. I have ordered a proper dev board so when that comes maybe I can get a handle on the problem.

I had set MCRLE_ON from trying to interpret the data sheet:

Page-212:
MCLRE: RE3/MCLR pin function select bit(4)
1 = RE3/MCLR pin function is MCLR
0 = RE3/MCLR pin function is digital input, MCLR internally tied to VDD

Page-215 (14.2.2)
An internal MCLR option is enabled by clearing the
MCLRE bit in the Configuration Word Register 1.

When MCLRE = 0, the Reset signal to the chip is generated
internally. When the MCLRE = 1, the RA3/MCLR pin
becomes an external Reset input. In this mode, the
RA3/MCLR pin has a weak pull-up to VDD.

These data sheets are a long read and at times I'm having trouble interpreting some of the pages.

[PICn-It]

Ok, making great progress.

I recieved my development board, plugged everyting in and coded up the demo example again ....and I'm getting text!
(woo-hoo!)

I'm getting:

#numbers Hello,
$hex From DT!

is this correct?