Does variable value change being transferred to code running in interrupt loop?

[Art]

If that code is in your interrupt, the interrupt can never exit and you might as well have put this in your main program.
You can’t run a continuous loop. The ISR is always a call i.e.. GOSUB, and you always have to return from interrupt or your main code will never run.
What is currently triggering the interrupt?

Also, it looks like you want PWM at 50% duty cycle, but if more than one condition is true, it will break all of them.

There is a thread a little below about frequency counters. Darrel didn’t want to shove his own timer code down someone’s throat,
but it was really the answer to the problem. To his merit, he gave advice about a less efficient manner the OP was already working on.
Similarly DT’s code is the answer to your problem.

[Art]

It looks to me you want three software PWM channels, all 50% duty cycle 100ms ON/100ms OFF,
that you switch on & off based on the values in variables A,B & C.

Even though this code won’t do that, I don’t understand why you check X=1, X>1, X>2, all for the same result.
Could you have just:

IF A != 0 THEN
HIGH LED1
PAUSE 100
LOW LED1
PAUSE 100
ENDIF

and then the same for B & C?

Just want to be sure of what you want to do.

[CuriousOne]

Just checked, sorry, I've pasted ENDIF at wrong place. It should look like this

SOFTPWM:
IF A=1 THEN
HIGH LED1
ENDIF
PAUSE 100
LOW LED1
PAUSE 100
GOTO SOFTPWM

and so on, for all LEDS and cases.

I want to run this code in background of main task, so this is why I wanted to use interrupt. Seems like it is impossible?

[Dave]

You mean you want to run the above lines of code as an interrupt? I don't think so.... The pauses will kill you.... What is your anticipated interrupt period?
By the way, What processor are you using and at what frequency?

[CuriousOne]

I want to run this task in a way, that main task won't interfere with it, nor it execution will affect main task.

Processor can be any of 16F family at any possible frequency.

[Art]

It’s not the pauses, the loop never ends:

SOFTPWM:
code
GOTO SOFTPWM

Only your main program can do that.
This ISR doesn’t allow your main program to ever run once it’s called.

[Art]

If you get this going I’ll do the rest from there.
The code to flash one led on/off per second is only needed
to prove the include file is being included from the right directory and everything works.

At the speeds you’re talking about you can have up to eight software PWM channels
who’s rising and falling edges are synchronised to the clock cycle fairly easily.
especially easy if the frequency of the outputs are the same.

DEFINE OSC xx
‘ tell PBP the clock frequency you’re using
DEFINE NOCLRWDT
‘ this only means the program has it’s own clrwdt instruction
‘ you can still set the watchdog timer on at programming time

include “Elapsed.bas”
‘ DT’s Elapsed Timer code from PBP forum
‘ drop the Elapsed.bas file in the PBP folder

‘don’t bother declaring SecondsChanged variable,
‘it should already be accessible because it’s declared in the include file

‘CMCON = 7
‘uncomment to set analogue ports digital if the device has analogue ports
‘and the led is connected to one of them

trisb.1 = 0
‘ set led output whichever pin you have the led connected
ledstate var bit

gosub ResetTime		'reset time 00:00:00
gosub StartTimer	'start timer
'
cycle:
@ clrwdt
‘
if SecondsChanged = 1 then
SecondsChanged = 0
ledstate = ledstate + 1
portb.1 = ledstate
‘ use your led pin of course
endif
‘
goto cycle
‘