khoih-prog / dx_slow_pwm Goto Github PK

Is your feature request related to a problem? Please describe.

if the need is over driving 16 channels, it means we must to use another object for 16 additionnal channels if I m not wrong?
juste to be sure how to process on that case.

So what happen if non other hardware TIMER still available?? (usually One is for millis(), one will be for ISR_Timer interupt generating this PWM, another one can be keep for core operations (in my case NMRA DCC signal management).... so few solution available!
Worst case on megatiny CPU with less TIMER ( A0 B0 B1 only)

Describe the solution you'd like

May it would be possible to limit frequency ( ex between 50hz-120hz range and add PWM channels on the 16 ones on the initial range as a way? (may be not at all!)

Describe alternatives you've considered

using biggest hardware on the family to have enough TCB Timer ressources is the intial possibility if available!

other is to get capacity or possibility to move millis() on a TIMER A type? (not sure it would be well managed by dx core or megacorex and megatinycore?)
May require some additionnal settings according optional links between TIMER A type and B type.

using millis on same timer as the one managing PWM? (stupid way? uncompatible?)

Additional context

optimisation of selected hardware according usages needs specially for limited TIMER numbers.

Describe the bug

Comment is

// You can assign any interval for any timer here, in Microseconds
float PWM_DutyCycle[] =
...

May be should be described like for a defined freqency (juste before this step) set the duty cycle according to value range [0;99] (or 100)
(add comment like duty cycle manage light itensity level on an avarage Vout on the define frequzency)
adjust frequency to avoid flikering
adjust ducty cycle for intensity (Vout average)

Steps to Reproduce

N/A

Expected behavior

N/A

MAy be need to precise that some step are requird to use a channel

0 define inital settings
1/ define pin
2/ set frequency
3/ set duty cycle

Actual behavior

N/A

Debug and AT-command log (if applicable)

N/A

Screenshots

If applicable, add screenshots to help explain your problem.

Information

Example

Additional context

Describe the bug

Hpp file line 153 TIMER should be TIMER4

Steps to Reproduce

Steps to reproduce the behavior. Including the MRE sketches

Expected behavior

need to change TIMER3 TIMER4

Actual behavior

TIMER4 defined incorreclty (define as TIMER3 again)

Debug and AT-command log (if applicable)

set TIMER4

Screenshots

N/A

Information

Please ensure to specify the following:

N/A

Additional context

N/A

Describe the bug

Not correct information on file name description

Steps to Reproduce

bad comment typo

Expected behavior

line 23 in comment swap #include "megaAVR_Slow_PWM.h" by #include "Dx_Slow_PWM.h".

Actual behavior

N/A

Debug and AT-command log (if applicable)

N/A

Screenshots

N/A

Information

N/A

Example

Additional context

N/A