I loaded the following code in my 12F675 PIC and tested it with my Kenwood Oscilloscope. The results was not what I expected. I then loaded the file into my simulator (Proteus) and there the results came out as what I expected.
Now the question is: Do I need a new scope? Which of these two pieces of test equipment should I trust? I'd rather believe the scope vs. computer simulated software.
Can someone with a newer scope perhaps test the code?
Now the question is: Do I need a new scope? Which of these two pieces of test equipment should I trust? I'd rather believe the scope vs. computer simulated software.
Can someone with a newer scope perhaps test the code?
Thanks.
The scope looks like it is probably working fine. I am assuming the display is stable as pictured indicating no triggering / holdoff problems.
I can't think of any failure mode of an analog scope that would muck with timing between pulses... well, not without distorting the display but that isn't happening.
You must be a software guy if you're blaming the hardware. J/K
The scope looks like it is probably working fine. I am assuming the display is stable as pictured indicating no triggering / holdoff problems.
I can't think of any failure mode of an analog scope that would muck with timing between pulses... well, not without distorting the display but that isn't happening.
You must be a software guy if you're blaming the hardware. J/K
Yes, I suppose I can be called a software guy, but in this case I'd rather believe the hardware. It just seems odd that the On/Off periods don't display the same on the scope.
But if the trace is stable on the scope, then WYSIWYG I am pretty sure.
The scope has a timing circuit that controls the horizontal sweep. If there is a problem with it, the trace will look funny (varying intensity across the sweep). If there is a problem with triggering or holdoff I would think it'd affect all signals in funny ways.
So... maybe it is some weird timing issue with the interrupts... or maybe the MCU isn't configured the way it needs to be (ie, the way the simulation assumes it is) ... ??
The scope looks like it is probably working fine. I am assuming the display is stable as pictured indicating no triggering / holdoff problems.
I can't think of any failure mode of an analog scope that would muck with timing between pulses... well, not without distorting the display but that isn't happening.
You must be a software guy if you're blaming the hardware. J/K
I added to my code a start pulse of 50µs and assigned the output to one of the unused I/O pins. I connected the scope’s external trigger probe to this I/O pin, and continued using the channel A probe to measure the databus, and voila, my old scope is still as good as the day I bought it.