INTL 3:770/1 3:770/3
REPLYADDR dave@davehigton.me.uk
REPLYTO 3:770/3.0 UUCP
MSGID: <0b542d485b.DaveMeUK@BeagleBoard-xM> 1ea04857
REPLY: bd771217
PID: SoupGate-Win32 v1.05
In message
The Natural Philosopher wrote:
> I am slightly curious as to how the PICO could miss what is a several
> hundred microsecond wide pulse.
AFAICS there are many pitfalls:
1) An interrupt can be being serviced, so the pulse is over before you
get to see it.
2) If you're looking for a pulse, you should be looking edge triggered
rather than level triggered, but even then you may not get to react to
the edge immediately because of an interrupt being serviced, so you'd
get an anomalous result.
3) You can look level triggered, but you need to turn off all interrupts
to ensure you really are loking at it in real time.
4) I had a play with an ultrasonic ranger a couple of years or so ago.
I couldn't understand why I wasn't getting any return pulses at all.
I eventually realised that I was sending another start pulse before
the current cycle had finished.
Regardless, you need an escape from any and every potential infinite
loop. Whatever you're doing.
If you can use a hardware timer in the chip, that's a much more reliable
solution.
David
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225
SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17
SEEN-BY: 226/30 100 227/114 229/110 111 112 113 200 206 307 317 400
SEEN-BY: 229/426 428 470 550 616 664 700 240/1120 266/512 267/800
SEEN-BY: 282/1038 291/111 292/854 301/1 113 812 310/31 320/219 322/757
SEEN-BY: 335/364 341/66 342/200 396/45 460/58 633/280 712/848 770/1
SEEN-BY: 770/3 100 330 340 772/210 220 230 5020/400 1042 5058/104
SEEN-BY: 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
