Strange Behaviour with Conditional Compile

[HenrikOlsson]

Hi,
You have a lot of PAUSE statements within the LCD sections, most noticable is the PAUSE 1500 (1.5 seconds!) in the Map_VrefInVal_to_PWM_Duty subroutine which you call each time thru your Main routine. When you don't include the LCD sections in the code it runs MUCH faster compared to when you DO include the LCD sections.

/Henrik.

[RossWaddell]

Hi,
You have a lot of PAUSE statements within the LCD sections, most noticable is the PAUSE 1500 (1.5 seconds!) in the Map_VrefInVal_to_PWM_Duty subroutine which you call each time thru your Main routine. When you don't include the LCD sections in the code it runs MUCH faster compared to when you DO include the LCD sections.

/Henrik.

Thanks Henrik. That would definitely seem to explain the slow reaction to reading ADC during the main loop, but why would the duty cycle on the PWM output go HIGH as soon as power is turned on?

[HenrikOlsson]

Hi

You might want to make sure that the dutycycle is set to 0 before enabling the PWM module.
As it is now, when you "activate" the LCD sections, there will be a 7 second delay between the PWM module being enabled (you setting CCP4CON at the start of the program) and the time at which the ramp up actually starts, ie when you actually set the dutycycle to 0.

/Henrik.

[RossWaddell]

Thanks again, Henrik. Do you mean I should have:

    CCP4CON.4 = 0
    CCP4CON.5 = 0
    CCPR4L    = 0

before the CCP4CON register setting?

I will try that out tonight, as well as reducing the PAUSE statements.

[RossWaddell]

As usual, you were right Henrik. I added the code above right after turning on CCP/PWM on CCP4 and reduced all the pauses within the #IFDEF USE_LCD_FOR_DEBUG and now everything works as before. It was obvious once you pointed it out, so thanks again for being so patient.