DT Instant Interrupts

[krohtech]

Hay Darrel,

In the DT_INTS-14 (SPWM_INT - Multiple Software PWM) It says:

DutyVars   VAR BYTE[3]              ; DutyCycle Variables
  DutyVar1 VAR DutyVars[0]          ; group them in an array for easy access
  DutyVar2 VAR DutyVars[1]          ; with FOR loops etc.
  DutyVar3 VAR DutyVars[2]

I do not know how to use arrays or how it can benefit in loops. The way I am doing it now is very cumbersome and code intensive. I have searched the forum and RTFM but I can't get my head around how this concept. Can anyone point me in the correct direction.

[Darrel Taylor]

If you wanted to set all LED's to the same brightness, you could ...

LoopCount  VAR BYTE

FOR LoopCount = 0 to 15         ; 16 channels
    DutyVars(LoopCount) = 50    ; 50% (0-100)
NEXT LoopCount

<br>

[Archangel]

If you wanted to set all LED's to the same brightness, you could ...

LoopCount  VAR BYTE

FOR LoopCount = 0 to 15         ; 16 channels
    DutyVars(LoopCount) = 50    ; 50% (0-100)
NEXT LoopCount

<br>

Hi Darrel,
could you please explain DutyVars(LoopCount) = 50 ; 50% (0-100), I understand the counter loop but do not understand the operation here. Thank You
JS

[krohtech]

Hi Derrel,

Thanks for the code, Unfortunately I was hoping for something that would allow me to set different values to the duty cycle of each channel. The way I have it configured I use CH# as the var name:

DEFINE SPWM_FREQ  100               ; SPWM Frequency
DEFINE SPWM_RES   101               ; SPWM Resolution

DutyVars   VAR BYTE[16]             ; DutyCycle Variables
  CH1 VAR DutyVars[0]          ; group them in an array for easy access
  CH2 VAR DutyVars[1]          ; with FOR loops etc.
  CH3 VAR DutyVars[2]
  CH4 VAR DutyVars[3]
  CH5 VAR DutyVars[4]
  CH6 VAR DutyVars[5]
  CH7 VAR DutyVars[6]
  CH8 VAR DutyVars[7]
  CH9 VAR DutyVars[8]          
  CH10 VAR DutyVars[9]         
  CH11 VAR DutyVars[10]
  CH12 VAR DutyVars[11]
  CH13 VAR DutyVars[12]
  CH14 VAR DutyVars[13]
  CH15 VAR DutyVars[14]
  CH16 VAR DutyVars[15]

and change the duty in this manor:

Main: 
gosub CKINPUT
                             
CH1 = 100
CH2 = 0
CH3 = 0
CH4 = 0
CH5 = 0
CH6 = 0
CH7 = 0
CH8 = 0
CH9 = 0
CH10 = 0
CH11 = 0
CH12 = 0
CH13 = 0
CH14 = 0
CH15 = 0
CH16 = 0
gosub CKINPUT
PAUSE T5
CH1 = 100
CH2 = 100
CH3 = 0
CH4 = 0
CH5 = 0
CH6 = 0
CH7 = 0
CH8 = 0
CH9 = 0
CH10 = 0
CH11 = 0
CH12 = 0
CH13 = 0
CH14 = 0
CH15 = 0
CH16 = 0
gosub CKINPUT
PAUSE T5

and so on... If anyone can suggest a better method I would be very interested in learning better ways to program.

[skimask]

DEFINE SPWM_FREQ  100               ; SPWM Frequency
DEFINE SPWM_RES   101               ; SPWM Resolution
DutyVars   VAR BYTE[16]             ; DutyCycle Variables
  CH1 VAR DutyVars[0]          ; group them in an array for easy access
  CH2 VAR DutyVars[1]          ; with FOR loops etc.
...............
  CH15 VAR DutyVars[14]
  CH16 VAR DutyVars[15]

and change the duty in this manor:

Main: 
gosub CKINPUT
CH1 = 100
CH2 = 0
............
CH15 = 0
CH16 = 0
gosub CKINPUT
PAUSE T5
CH1 = 100
CH2 = 100
CH3 = 0
CH4 = 0
...........
CH15 = 0
CH16 = 0
gosub CKINPUT
PAUSE T5

and so on... If anyone can suggest a better method I would be very interested in learning better ways to program.

I don't see what the problem is...
You've already got CH1 an as alias to DUTYCYCLE[0]...therefore:
CH1 = 0 (or whatever)
is equal to
DUTYCYCLE[0] = 0 (or whatever)
They are functionally equivalent....

Therefore, if you had to use a loop:

for temp = 0 to 16 : dutycycle[ temp ] = 0 : next temp

would be equal to

ch1 = 0
ch2 = 0
and so on until....
ch15 = 0
ch16 = 0

[krohtech]

Hi Skymask,

Maybe I can clarify what I am trying to do. I didn’t post my entire code because it is very long. I will attach as a text file. I am designing a sign controller AKA sign animator AKA sign speller. What I need to do is CH1 ON pause X, add CH2 on Pause X, add CH3 pause X … This is an oversimplification but you can get the idea. It will allow me to program patterns left to right, right to left, center out, outside in, fade from left to right etc.

I guess I was hoping for was some kind of nested for next loop with an array?

I probably am not phrasing it correctly as I am a beginning programmer. Most of my experience is in programming large theatrical RGB lighting clusters which is not really programming in the same use of the word. I really haven’t “written code” since high school.

I do appreciate all the help and am enjoying the journey!!!

[skimask]

Hi Skymask,
Maybe I can clarify what I am trying to do. I didn’t post my entire code because it is very long. I will attach as a text file. I am designing a sign controller AKA sign animator AKA sign speller. What I need to do is CH1 ON pause X, add CH2 on Pause X, add CH3 pause X … This is an oversimplification but you can get the idea. It will allow me to program patterns left to right, right to left, center out, outside in, fade from left to right etc.
I guess I was hoping for was some kind of nested for next loop with an array?
I probably am not phrasing it correctly as I am a beginning programmer. Most of my experience is in programming large theatrical RGB lighting clusters which is not really programming in the same use of the word. I really haven’t “written code” since high school.
I do appreciate all the help and am enjoying the journey!!!

Where do you plan on storing all of this data? On chip eeprom, program memory, off chip serial eeprom, CF card?
I can see using a FONT table to store all of the characters, each character being a mini-array of points. Then depending on how you read out those points from that array, it may look like the character is shifting left/right/up/down, whatever.

I think you need to setup an array of data and do matrix operations on that array when dealing with the full screen.
I.E.
4 x 4 array = 16 data points, array var byte[16]
x / y = 4 / 4 = 16
point 0,0
x + (y*4) = point in array, in this case point 0, first byte in array
point 3,3
x + (y*4) = point in array, in this case point 15, last byte in array
PBP doesn't do multi-dimensional arrays but you can easily overcome that with some simple math.

[Archangel]

Hi Darrel,
could you please explain DutyVars(LoopCount) = 50 ; 50% (0-100), I understand the counter loop but do not understand the operation here. Thank You
JS

Anybody ???

[skimask]

Anybody ???

Nothing more than an index'd variable.

DutyVars(LoopCount) = 50

(not code below...)
If loopcount = 1 then the following two lines are equivalent

-DutyVars(1) = 50

-loopcount = 1 : DutyVars(loopcount) = 50

At least I think that's what you were asking about.
If that's what you were asking, the book explanation is in Chapter 4.5 of the manual...if not...whoops! My bad

[Archangel]

OK, so dutyvars is an array holding the changing value loopcount and that = 50 ? This really is Fuzzy . . .

 label VAR size[number of elements]
label = DutyVar
size = Loopcount
what does = 50 do exactly?
Does it give you a 16 byte array all having the value of 50?

[krohtech]

what does = 50 do exactly?
Does it give you a 16 byte array all having the value of 50?

Hi Joe,

50 would be the duty cycle of the PWM. In this example the SPWM_INT duty cycle was setup to be 0 - 100 so 50 would be roughly 50% at 100 Hz. See Below

DEFINE SPWM_FREQ 100 ; SPWM Frequency = 100 Hz
DEFINE SPWM_RES 101 ; SPWM Resolution = 0-100