I hate to tell you this, Adam, but your program makes the outputs high for 4 ms and low for 12 ms, just like mine. And, I am refrencing the scope to VSS.
I hate to tell you this, Adam, but your program makes the outputs high for 4 ms and low for 12 ms, just like mine. And, I am refrencing the scope to VSS.
Are you sure you don't have a inverted probe type??? or scope setting.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Aarrrggghh, I hate hearing that, too!![]()
Mister-e’s suggestion on the other tread sounds plausible (“Where's the CMCON setting?”).
The other idea is: you may not be really re-programming the PIC.
Try changing the times to 100 times longer. Just to check.
or
Try erasing the PIC, reading it, look at the hex to make sure it is erased. Then, program it with the new code compiled from MCS and PBP. Then read the device again to see it has really been re-programmed.
I seem to remember some forum postings about forgetting to re-compile before re-burning.
So they just kept burning the original (Version 1 of their code) ASM into HEX, not the new PBP (Version 2 of their code).
-Adam-
Good suggestions, Adam. But, I have done all those things (except make the time longer). Look at post#15, why is that waveform the same as post#1?
Thanks fellas, I started a new thread and got the answer: CMCON=7. I have not figured out why that works, maybe it is just one of those things I was not meant to know.
I'm thinking the problem overall is the fact that you've got one resistor for current limiting for 2 LEDs. If you pull either pin low and you're measuring your signal on the LED side of the resistor, it won't matter which pin gets pulled low, they will probably both read low at back side of the LED (the connection nearest to the resistor).
What do you get if you 'scope the actual pins themselves, right at the PIC with nothing else connected?
Bookmarks