Wow, You just NOW saw that?
Hi All ,
Can Anyone Please Clarify Why This Weird Output Occurs ?
Using PBP 2.60 , Pic18f2550 .
DEFINE OSC 48
@ __CONFIG _CONFIG1L, _PLLDIV_5_1L & _CPUDIV_OSC1_PLL2_1L & _USBDIV_2_1L
Congratulations to K8LH (Mike) for getting attention on H A D . link http://hackaday.com/2014/02/12/the-three-chip-retrocomputer/
Not PBP but very nice Mike.
Which code is that exactly? I'm sort of guessing here so if I'm referring to the wrong one please disregard this.
The only code in this thread, which could be interpreted as if that's...
Just looking at your code and decided to ask a question or two.
Why do you set the same configs twice? I think either will accomplish the task but they may be contradictory also.
I added & _BODEN_OFF to __CONFIG and reduced the current from 120uA to 5uA
Thanks Robert ,
Already Did Now But , Doesn't Help In My Situation (Multimedia & qwerty Keyboard) .
I just forget to past it here but already found in my code , thanks for mention
Yes, I think floating point is going to take too much resources and I'm not sure it'll actually solve anything. The position is still "set" and sampled at discrete intervals, there's no way...
I am not an expert on this subject but would try to help. Is it necessary to use the PID routine all the time?
Why not just call it just before the target point is close so that it will be used...