PIC18F26K22：MCC如何在TMR1/比较模式下禁用ECCP1引脚？

非常感谢您的澄清。自从我开始将MCC融入到我的工作流程中，这些解决方案是可行的，也是一种解脱：它的图形化方法减少了我的错误。S？



      以下为原文

    Many thanks for clarifying so well.
 
The workarounds are workable and a relief since I've started incorporating MCC into my workflow: it's graphical approach reduces MY errors.
 
As a matter of interest, clearly identified bugs such as this are steadily fixed by the MCC team or likely to around for years? 
 
 

嗨，在CCP比较模式设置中做了一些额外的实验。我抱怨消息2中的硬件问题，更多的是因为我缺乏阅读能力。在一些实验中，它似乎是这样工作的：在CCP和ECP硬件模块中，“软件中断”模式和“特殊事件”。触发器的模式，是明显不同的操作模式，这两种模式都可用于所有的CCP和ECP模块的硬件。特殊事件触发模式不限于CCP5，特殊事件触发模式将设置中断标志，CCPxIF，对于启用该模式的每个模块，区别在于CCP5，除了中断标志之外，该模式还将为ADC发出GO信号。特殊事件触发模式将重置所使用的计时器，使得触发周期将是计时器从0到CPRXH和CCPRXL的值的时间。软件中断模式似乎与特殊事件触发模式完全不同。相反，软件中断模式，功能与比较模式2, 8和9相同，唯一的区别是没有输出引脚操作。在比较模式中：2, 8, 9和10，从定时器再装入值运行的定时器寄存器，从0xFFF到0x0的定时器滚动，然后触发定时器中断，可用于重新加载定时器寄存器。当比较寄存器CCPRXH和CCPRXL与计时器寄存器TMRXH和TMRXL相匹配时，比较中断被提出。CCP的MCC轻松设置框中的引用：“请参阅指定的定时器来调整比较跳闸点”是误导性的。这是可以在指定的计时器设置中设置的重复周期。比较跳闸时间必须在寄存器窗口中设置：CCPRxH和CCPRXL，或者调用MCC创建的运行时设置函数。MCC应为CCP触发器提供设置计算，将所选择的计时器时钟频率和计时器再装入值计入计费。CCPRX寄存器设置应大于计时器重载值，以便在使用除事件触发器以外的比较模式时进行比较匹配。当选择事件触发模式时，不应使用定时器重载。



      以下为原文

    Hi,
Did some additional experimentation with CCP Compare mode settings.
What I complained about hardware problem in message #2, is more due to my lacking ability to read.
 
With some experimentation, it seem to work like this:
In CCP and ECCP hardware modules,
 'Software Interrupt' mode, and
 'Special Event Trigger' mode,
are distinctly different modes of operation, and both these modes are available in hardware for All CCP and ECCP modules.

Special Event Trigger mode is not exclusively for CCP5,
Special Event Trigger mode will set Interrupt flag, CCPxIF,
for every module where this mode is enabled,
the distinction is that for CCP5, this mode will also make a GO signal for the ADC in addition to the interrupt flag.

Special Event Trigger mode will then Reset the timer used,
such that Trigger period will be time used for Timer to count from 0 to value of CCPRxH and CCPRxL.

Software Interrupt mode seem to be completely different from Special Event Trigger Mode.
Instead, Software Interrupt mode, function the same as Compare modes 2, 8 and 9, the only difference is that there is no output pin manipulation.

In Compare modes: 2, 8, 9 and 10, Timer register running from Timer Reload value, to Timer rolling around from 0xFFFF to 0x0, then it trigger Timer interrupt, which may be used to Reload Timer register.
Compare interrupt is raised when Compare registers CCPRxH and CCPRxL match with Timer registers TMRxH and TMRxL.

The reference in MCC Easy Setup box for CCP:
   'Please refer to the assigned timer to adjust the Compare trip point'
is misleading.
It is the repeat period that may be set in the assigned Timer Setup.
Compare trip time will have to be set in Registers window: CCPRxH and CCPRxL
or by calling runtime setting function created by MCC.

MCC should provide Setup calculation for CCP trigger, taking the selected Timer clocking frequency and Timer Reload value into account.

CCPRx register setting should be larger than Timer Reload value,
for compare match to occur, when Compare modes other than Event Trigger is used.

When Event Trigger mode is selected, Timer Reload should not be used.
 
Regards,
   Mysil

昨天我从拣选机上拿了几根LED。问附近有谁是阴极。他想了大约一分钟，几次试图在嘴唇上形成答案。然后他意识到他不能确定，于是我们去寻找一个最近和他们一起做的董事会。不久，另外两个人也加入了我们，我们在寻找通道。然后突然间集体承认这些小事情是一场噩梦，每一件事情都与下一步略微不同，没有数据表就没有办法知道。有人建议把细节写在卷筒上。另一种方法就是让测试员手。只有这么多的精力用于决策，一天只有这么多小时。发光二极管的极性？什么？！！！我还没有看到任何复杂的书面文本，聪明人找不到一个以上的解释。MCC如果能从数据表中免费计算小时，就可以知道是否出错了，这真是一件好事。MCC是一个很好的东西，如果它防止复制/粘贴配置从以前的项目，以避免痛苦重新思考。MCC是一件很棒的事情，如果它能让我们确定一个确定性，使我们能够集中精力于那些可以真正增值的有趣的东西。我已经厌倦了盯着配置比特，试图找出哪个振荡器选择对应于数据表中的选项。也不应该产生一个完美的定时中断和服务，而不减慢计数器到下一个是痛苦的。



      以下为原文

    Yesterday I took a few LED from the pick and place machine. Asked somebody nearby which end was the cathode. He thought for about a minute and several times an answer tried to form on his lips. Then he realised he just couldn't be sure and so we went off to find a board that had recently been made with them. Soon two other people had joined us and we were all peering, looking for vias. Then there was the sudden collective admission that these little things are a nightmare, each LED slightly different from the next, no way of knowing without having the datasheet to hand etc.. Somebody suggested writing the details on the roll. Another that the only way was to have a tester to hand. There is only so much energy for decision making, only so many hours in the day. Polarity of LED? What?!!
 
I've yet to see a written text of any complexity for which intelligent people can't find more than one interpretation.
 
MCC is a really good thing if it can free up hours of calculating constants from the datasheet thne wondering if one made a mistake. MCC is a really good thing if it prevents one from copy/pasting configurations from previous projects to avoid the pain of thinking afresh. MCC is a great thing if it allows us a measure of certainty, enables us to concentrate on the fun stuff where value can really be added.
 
I'm tired of staring at the config bits trying to figure out which oscillator selection corresponds to what option in the datasheet. Nor should it be painful to generate a perfectly timed interrupt and service it without slowing up the counter to the next one.

我总是用电池和电阻器测量/测试SMD发光二极管。



      以下为原文

    I always measure/test SMD leds with a battery and a resistor

有些人总是把振荡器带到一个PIN上，以确认他们正在得到他们认为应该得到的东西。DMCY很高兴MCC消除了各种计算小部件的疑虑。



      以下为原文

    And some people always bring the oscillator out to a pin to confirm that they are getting what they think they should be getting. :D
 
Very happy for the doubts MCC eliminates with its various calculation widgets.