I wrote a code for Input capture and make the input to it's pin PWM
and there is a wrong in result
maybe in PWM code or in Input Capture
so I need a thing like oscilloscope to test. as I didn't have one
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I wrote a code for Input capture and make the input to it's pin PWM
and there is a wrong in result
maybe in PWM code or in Input Capture
so I need a thing like oscilloscope to test. as I didn't have one
Amit Ashara said:...never used the IDE to monitor high speed signals.
Indeed that's where scopes shine - enabling the view of one or multiple signals - at "controlled" points in time.
Can an IDE do that - w/the same ease, flexibility & precision - unlikely...
For those w/out scope access - often an array of signal monitoring Leds - driven by digital or analog signals configured to "latch" - may serve. At high speeds the Led toggle rate will be unrecognizable - yet by "scaling" the input frequency (i.e. divide by 10:1, 100:1 or higher) led toggle speeds may be made viewable - and the overall logic of the user's design confirmed.
This suggestion has bounds - as frequencies increase signal delays, board layout and stray capacitance cause greater impact. That said - even when proper equipment is available - operating at lower speeds (initially) usually does prove of value by confirming the circuit/stage's overall design correctness...