Renard firmware Timer1

[ctmal]

I'm working on a small project that I'm editing the existing Renard firmward and I need to use timer1. My project is strictly using dc but I've come to realize that if it works for ac it could be of some use too.
In the app notes in the beginning of the code it states that timer1 is not being used but down in the code timer1 gets initialized to count the interval between zero-crossings.
I have removed(actually just remarked) all references to timer1. Will this have any impact on how the code dims(using ac)?
I'm going to give it a try once I've ironed out my code, I just want to know if there's anything I should look for.

Thanks!

[P. Short]

Yes, that code adjusts the timing to go along with the AC power-line frequency.

[P. Short]

You might want to consider switching to the PIC16F1823. It is cheaper, has a compatible pinout, is faster, and has an extra timer. The internal register architecture is a bit different, and the firmware would take some work to make it run on that architecture.

[ctmal]

Ok, thanks Phil. I'll just stick with using it for DC purposes.

[djulien]

I'm working on a small project that I'm editing the existing Renard firmward and I need to use timer1.

How do you want to use Timer1? You might be able to reuse or extend how Timer1 is currently being used without affecting the operation of the existing code.

don

[ctmal]

You might want to consider switching to the PIC16F1823. It is cheaper, has a compatible pinout, is faster, and has an extra timer. The internal register architecture is a bit different, and the firmware would take some work to make it run on that architecture.

I'll look into that. Thanks again Phil.

[ctmal]

How do you want to use Timer1? You might be able to reuse or extend how Timer1 is currently being used without affecting the operation of the existing code.

don

I need it to get a 100ms or 50ms pulse. Currently the speed it is set up for is way too fast to get that.

[CaptKirk]

How about using it at the current setting and have the code count the pulses to get the timing you need? If it is set to 1MS, count 100 or 50 ticks and use THAT for your timing. Too fast is usually workable that way, too SLOW is what sucks (like it is set to 200MS and you need a 100 or 50MS timing).

Kirk

[ErnieHorning]

It's easy to waste time, a bit tougher to make it.

[LabRat]

It's easy to waste time, a bit tougher to make it.

Unless your PIC is bigger on the inside than the outside... and/or you are working with Ponds.