STM32F107 CL设备上的电机控制库异常

为了更清楚地了解上述问题，我在STM32F107xC连接线设备上的MC实现适用于：
 
  - 单电机
  - 编码器或3x霍尔效应。
 在执行调用期间，实现崩溃：
 MCboot（OMCI，OMCT）; //

在调整CL设备的库配置时，我忽略了调整电路板上特定晶体的启动代码。现在我已经在我的CL设备上调整了8MHz晶振的时钟配置代码 - 提供的库代码假定为25MHz晶体 - 崩溃已经停止。
 
 
 现在我已经掌握了MCWB软件。
 
 正在解决为什么当电机现在没有运行时报告“过流”的原因。我与MB459套件的增益电路略有不同，但在MCWB设置中进行了相应的调整。
 
 虽然我不是100％肯定它正在处理运算放大器模拟处理。发送到源代码的#defines虽然包含有关增益的信息，但似乎不包含有关“零”级别的信息。
#define RSHUNT 0.220
#define AMPLIFICATION_GAIN 2.12
 
 
 ......似乎是唯一进入代码的#defines;因此，当我知道没有电机电流流动时（在MCBoot（）时间？），我假设磁带库通过自校准自动神奇地调整电流“零”（单端运算放大器前端偏置） - 是这个案子呢？
 
 有任何想法吗？



以下为原文








In adjusting the library configuration for the CL device I neglected to adjust the startup code for the specific crystal on my board.  Now that I've adjusted the clock config code for my 8MHz crystal on my CL device - the provided library code assumes a 25MHz crystal - the crashing has stopped.


Now I have comms up with the MCWB software.

Just working through why it's reporting 'overcurrent' when the motor is not running now.  I have slightly different gain circuits from the MB459 kit, but have adjusted accordingly in the MCWB setup.   

Although I'm not 100% sure it's handling the op-amp analog processing right.  The #defines which are sent through into the source code, while including information about the gain, doesn't seem to include information about the 'zero' level.

#define RSHUNT                        0.220

#define AMPLIFICATION_GAIN            2.12

  
... seem to be the only #defines going into to code; so I assume that the library auto-magically adjusts for current 'zero' (the single-ended op-amp front-end biasing) by self calibrating when it knows there is no motor current flowing (at MCBoot() time?) - is this the case?

Any ideas?

看起来该库确实执行了它自己的零电流校准，这非常好 - 因此MCWB正在将足够的模拟电流信号处理传递给库。
 
 
 过电流。我很困惑。似乎需要一些术语的一致性，以及增加术语的相关性。
 
 显然，“紧急停止”相当于“制动”输入相当于“过电流”。
 
 但我不确定MCWB对此的控制在哪里。
 “Power Stage - Over-current protection”下有可疑设置，然后是“过流保护禁用网络”。
 如果这是真的，这是==＆gt;同名的4个名字!!!! ＆LT; ===
 
 然后，再次，这次只是为了好玩，在“控制阶段”和过流保护拓扑下，可以选择“外部保护”或“无保护”。
 
 因此我选择了“无保护”，现在过流警告已经消失，因为我的应用程序使用PE15（不能在MCWB中重新分配）用于其他目的。



以下为原文











It seems that the library does perform it's own zero-current calibration, which is excellent - so the MCWB is passing enough analog current signal processing to the library.


Over-current.  I am confused on this.  It seems that some consistency in nomenclature is required, along with increased pertinence of terms.

Apparently 'Emergency Stop' is equivalent to 'Brake' input is equivalent to 'over current.'

But I'm not sure where the MCWB control for this is.
There are suspicious-looking settings under 'Power Stage - Over-current protection,' and then 'Over-current protection disabling network.'
Which, if this is true, this is ==> 4 names for the same thing !!!! <===

Then, again, just for fun this time, under 'Control Stage' and Over-Current Protection Topology, 'External Protection' or 'No protection' can be selected.

So I selected 'No protection' and now the over-current warning is gone, since my application uses PE15 (not re-assignable in the MCWB) for another purpose.

Ciao Luke，
 
 是的，lib在每次重启电机时执行偏移校准，
 是的，命名法中有一点冗余：过电流，制动输入和紧急停止是等效的。
 “过电流保护禁用网络”具有不同的含义，是一种允许暂时禁用过电流保护的网络，可以使用“额外”电流。
 如果您没有可用的紧急输入/过电流/制动输入/ PE15引脚，则唯一的想法就是禁用保护...然后交叉手指。
 
 再见
 梁咏琪



以下为原文





Ciao Luke,

yes, the lib performs the offset calibration at each restart of the motor,
and yes, there is a little bit redundancy in the nomenclature: Over current, Brake Input and Emergency stop are equivalent.
The 'Over-current protection disabling network' has different meaning and is a network to allows to disable temporary the over current protection to have the possibility to work with an ''extra'' current.
If you don't have the Emergency Input/Over current/Brake input/PE15 pin available the only think is to disable the protection as you did... and then cross the finger.

Ciao
Gigi