Thanks- You have been very helpful. Another question I have is about precise timing; Does the PRU have access to any high precision timers / a way for the cpu to know down to the microsecond how long between 2 data points --- Even if they are very far apart say for example- sampling only AIN-0 with averaging set to 24 and the tmr set @ 100,000-- could the time between the first point and the last point be accurate to 50 +/- microsecond across multiple hours ?
The ideal solution would allow for the pru to send back a 32/64 bit timer every X samples. On Tuesday, August 25, 2015 at 12:02:20 AM UTC-6, TJF wrote: > > Hi! > > Am Dienstag, 25. August 2015 00:44:22 UTC+2 schrieb > 180bob.we.had.a...@gmail.com: >> >> or is something I using out-of-date? >> > > Yes, outdated. In the new (unpublished) code in file > src/pruio/pruio_adc.bas at line 128 > > d *= (Conf->ADC_CLKDIV + 1) * 417 '417 ≈ 1000000 / 2400 (= 1 GHz / > 2.4 MHz) > d += 30 ' PRU cycles for restart [GHz] > > IF Tmr <= d THEN .Errr = @"sample rate too big" : RETURN .Errr > > is replaced by > > d = (d * (Conf->ADC_CLKDIV + 1) * 1000) \ 24 > IF Tmr <= d ORELSE Tmr < 5000 THEN _ > .Errr = @"sample rate too big" : RETURN .Errr > > BTW: The example triggers.bas > <http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/_cha_examples.html#SubSecExaTriggers> > > may give you an idea how to use MM mode. > > BR > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
