Not sure I understand what you are after but have you
_MCLRE_OFF
and made the pin an input?
Not sure I understand what you are after but have you
_MCLRE_OFF
and made the pin an input?
Dave
Always wear safety glasses while programming.
I found that the PIC16F913 INC file didn't have all the configs listed and had to use the meProg, View, Configuration screen to set the configs from before flashing the device.
And thanks to Mark_S for that code sample. I had finally brought the 16F913 and LCD-S401M1TF to life using about 900 Words but rewriting using your example with the LookUp table and IF/THENs reduced it to just over 500 Words.
Last edited by LinkMTech; - 17th April 2010 at 22:31. Reason: Shout out to Mark S
Louie
Hello All,
After getting everything together for the 913, I fired up MIcroCode Studio (for those who use PicBasic Pro) just to find out that they don't support the 16F913 and above.
How does one know how to compile from PBP to the chip?!
[QUOTE=LinkMTech;88500]I found that the PIC16F913 INC file didn't have all the configs listed and had to use the meProg, View, Configuration screen to set the configs from before flashing the device.
How were you able to send the program to your 16F913? Are you using Microcode Studio or something else. My "chip listing" for the 16F series only goes up to 16F88 on the non-pro version 3.0.0.5 and the same for the MCS Pro version. Is there something wrong on my end or does MCS not support this 16F913 series chip. I upgraded to PBP 2.6 just because it had this chip that I have to use!
Frank![]()
Last edited by PulsarProFX; - 17th April 2010 at 23:47. Reason: Not enough info to qualify the question.
I use MicroCode Studio PBP 2.47 with the MPASM compiler. It supports the 16F913 found in the drop down box.
Louie
Bookmarks