EEPROM Variables (EE_Vars.pbp)

[Darrel Taylor]

•Adding 'MotorRPM = 127' just before the spin up does work

The default value was 150, so it seems logical that setting it to 127 would make it run slower.

And I assume this is just a schematic error ?? Might cause a few problems. Sure confused me for awhile.



Try the attached program.

[RossWaddell]

I just changed it to 127 so it would be even slower to make it obvious. If I use 150 it has the exact same effect.

Thanks for spotting the schematic error! The board itself is fine, though.

[RossWaddell]

BTW, this problem applies to both EE_vars (MotorRPM & PortEngDir) - unless I specifically set them in code they do not get initialized with the default values (150/127 & 0). I know this for the 2nd EE_var because in a later iteration of the same code I do a check on PortEngDir: if it's 0 make the motor spin CCW; else make the motor spin CW. Without the line 'PortEngDir = 0' the motor **always** spins CW after the chip has been programmed more than once.

Darrel - I missed seeing that you had provided a code file too. I'll try that out tonight after work (and thanks).

[RossWaddell]

Darrel - your file works (all except the interrupt handler to reset the motor speed via the rotary encoder's button)! Does that tell you anything more about what's going on?

[Darrel Taylor]

Oops,

Add this line after the WRITE command in the RotEncBtnPress: handler.

MotorRPM = MotorRPM_Default

[RossWaddell]

It works! Thanks again Darrel.

Does this mean there's a problem with EE_var? I've used that include in a bunch of projects and love it. For this project, I still have more work to do (possibly with more EEPROM variables) and would ideally continue to use your EE_var if possible. Could this be a problem with my local version of DT_INTS-14.bas (which I had to modify for the PIC16F1825)?

DT_INTS-14.txt

[Darrel Taylor]

First off, you should not be modifying DT_INTS-14.
It even says so in the code that you modified.
The changes that you made were incorrect (see the comments in DT_INTS-14), but I don't think they would have affected EE_Vars.

Since I cannot duplicate your problems with the same hardware and software, I can't agree that there is a problem with EE_Vars.
It all works perfectly here.

You don't have any way to debug your program/hardware, no LCD, the USART pins are used for other purposes.
So you are left to make guesses on what is happening, and I can't ask you to check register values.
Naturally, those guesses point blame at everything you didn't do. It's human nature.

I would recommend building in some form of debugging capabillity in your next project.
A serial LCD that only uses one pin can be extremely usefull.

With that said, there have been many changes to PBP since I wrote EE_Vars, and much of it's functionality is now included in the compiler.
So there's not much reason to use EE_Vars anymore.