You have RETURNs with GOTOs .
Try going to the subroutines with GOSUB and then RETURN. Not both GOTO and RETURN.
|
You have RETURNs with GOTOs .
Try going to the subroutines with GOSUB and then RETURN. Not both GOTO and RETURN.
Dave
Always wear safety glasses while programming.
|
Dave,
There are two iterations of that, in a somewhat silly attempt to validate that the RETURN was working - or failing. No difference. Irrespective, they've been removed.
The TRIG output goes high and low exactly as it should, when the CHUBB input goes high or low. That tells me the loop is looping. (Loopy?)
After startup, the TWO led routines do work. ONCE.
I can't see anything that is unhappy in the counting, the compiler likes it, and it seems to read ok, it just doesn't work.
What the heck....
|
Hi Gary,
try ADCON0 = 0
If you do not believe in MAGIC, Consider how currency has value simply by printing it, and is then traded for real assets.
.
Gold is the money of kings, silver is the money of gentlemen, barter is the money of peasants - but debt is the money of slaves
.
There simply is no "Happy Spam" If you do it you will disappear from this forum.
|
Joe,
No better.
This is very very strange....
|
Something is strange.
I just tried your code for giggles and this is what happened.
It is not your code, something else is the matter. A lot of folks seem to be having problems with this chip....Executing: "C:\PBP\PBPW.EXE" -ampasmwin -oq -z -p12F675 "C:\MAC\PIC PROGS\TEST\12f675.bas"
PICBASIC PRO(TM) Compiler 2.50c, (c) 1998, 2008 microEngineering Labs, Inc.
All Rights Reserved.
ERROR: RAM END must be defined.
ERROR: RAM BANKS must be defined.
ERROR: No LIBRARY statement or LIBRARY parameter.
ERROR: No LIBRARY statement or MACRO parameter.
ERROR: Unable to open file PBPMAC.INCHalting build on first failure as requested.
BUILD FAILED: Tue Sep 15 20:40:41 2009
Dave
Always wear safety glasses while programming.
|
Dave,
That's interesting.....
I tried with various settings in the config, watchdogs on and off, etc. I always use a 4k7 from MCLR to +5. That's just a "standard" here, and I always use the internal osc, and have never strayed far from 4mhz, so suffice to say that the config is pretty "plain".
Most of the timing floats someplace around variations of 1000 so that an aprox count in seconds should tell me when things happen.
The ONLY change here since the last functional chip is 4.31 software on the MELabs Programmer. And it's interesting that there's another thread nearby that the fellow is using the same programmer (although a much older code) and having "odd" issues.
Once again I've shipped it over to MELabs with a request for help.
Thanks to all who have responded. This kind of discussion is enlightening..
Cheers
Gary
|
Jerson,
The only change I see in your suggestion is an "else" for the Chubb. That part of the code is the only part that works repeatedly....
There is something whacked in the way the counter stuff is getting either compiled or put to the chip, or interpreted by the chip. That part is going off into lala land.
Gary
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks