"msilv3r"
Thank you all. Great insights. I'm def gonna end up using the interrupt. This isn't that hard after all! I was actually just thinking of a similar algorithm to yours yhbcoggs. Awesome!
toggle quoted message
Show quoted text
On a slight side note, so since this is 4800bps, I could safely assume that I will receive more than once time code per second. And that, I assume, is the ".ss" part of "hhmmss.ss" - So I could, assuming I was always connected, use a compare within this string to know when a second in time has occurred. Also, it seems like many instructions on the pic are executed within either the nanosecond range, or low microsecond range. Since I don't have that much code for the interrupts I could perhaps say its negligible time. I plan on using a 32.whatever oscillator and using an interrupt count to compare for each second (I stil have some research to do in that area). But then when should I have the clock sync? I think it makes more sense to use an oscillator as the timing mechanism then the string compare mentioned above. Or maybe moth? I was thinking maybe every five minutes I would have it sync with the GPS, just incase its off by a second or two. A bit of scattered thoughts here, sorry. Any thoughts? --- In NEONIXIE-L@..., "yhbcoggs" <rdcjr@...> wrote:
True, you don't need to buffer up the whole line; I did it by just looking at the last 3 characters; Just write a state machine that goes something like: |