Count Per Second

[skimask]

I had a similar problem where the count might exceed 65000.
I divided up the COUNT into 4 COUNTS.
It can be argued that there is holes between each COUNT. It does work! Don't think about the holes. time=4 seconds
rons
COUNT GEIGER, 1000, CNT1
COUNT GEIGER, 1000, CNT2
COUNT GEIGER, 1000, CNT3
COUNT GEIGER, 1000, CNT4

And those 'holes' between COUNT statements will be on the order of a few microseconds anyways and since the pulses are > 90us, it should catch them.

[oslinux]

ok, so i will use one word variable every 5 seconds, everything into an array, and every 500 seconds i will put the array in an external eeprom, this should work!

Now it's only up to the EEPROM that's not working (In the other topic)

Thank you!

Luca

[skimask]

ok, so i will use one word variable every 5 seconds, everything into an array, and every 500 seconds i will put the array in an external eeprom, this should work!

Now it's only up to the EEPROM that's not working (In the other topic)

Thank you!

Luca

Which PIC are you using anyways?

[HenrikOlsson]

Hi,

ok, so i will use one word variable every 5 seconds, everything into an array, and every 500 seconds i will put the array in an external eeprom, this should work!

I may be missing some key information here but why store it in array? Why not count for 5 seconds, write the value to the EEPROM, increase adress pointer by one (or two), reset count and start over?

/Henrik Olsson.

[oslinux]

PIC16F877A

If i store it in an array, i can write it directly via a page write in the external I2C EEPROM, i can't store in the EEPROM every 5 seconds, because it takes more than 10mS.

Luca

[mister_e]

PBP count is bul**** anyways, use a PIC timer for that. It will do the job in background.

From your sampling time you substract the needed time to write to your eeprom.

NOW you have something acurate. Unless, it's pure crap.

[oslinux]

please explain what do you mean for a "Pic timer",

P.S.: i'm going to bed, here it's 1:00 A.M....