same question and same blink
Quote:
Originally Posted by
Darrel Taylor
The blinking problem has been fixed.
There is NO blinking at all with
MIBAM.
<br>
when i do the same bam as u. blink as u,haha.
i find ur post, it is very interesting.
in fact u let the bam is high, such as 2.4kHz, u will not watch the blink ,same.
patents and royalty fees for BAM
I'm not sure this is the right place to ask, but I was wondering if BAM is a patented technique (e.g. by Artistic License or any other company) and hence commercial use of BAM requires fees to be paid, or if it just like PWM a technique that can be freely implemented in any device.
10x in advance for any info
Is it possible to combine MIBAM and DT_INTS?
Is it possible to combine MIBAM and DT_INTS?
I am attempting to use MIBAM in a program where I have been using SPWM_INT. I understand that MIBAM need exclusive use of TMR1 and HI priority INTs. The thought was to see if I could still use DT_INTs to handle low priority ints for a pulse time capture and a HSER routine. I still have to play with it to decide if I can make them function with the probability of MIBAM cutting off the other two, but that is a separate problem.
The issue that I see is that DT_INTS has:
"DEFINE INTHAND INT_ENTRY_H"
"DEFINE INTLHAND INT_ENTRY_L"
and MIBAM has:
"DEFINE INTHAND doBAM"
Can the doBAM section be added to the INT_ENTRY_h section and eliminate the "DEFINE INTHAND doBAM"? If so how?
Until I understand this better, I'm going to continue with the SPWM_INT version of the code and work on finishing the rest of the code that way. I may not need the advantages of MIBAM, but it sure is a cool routine. Even with my limited coding ability, DT's routines have multiplied my capabilities tremendously. Thank you Darrel and all the others that have put in the effort and patience and have been willing to share your wisdom so freely.
Bo