当前位置: 首页 > news >正文

(转)The Ten Commandments of Digital Cotrol(Part1)

Dave Wilson, Motion Products Evangelist, Texas Instruments

Despite the fact that I now work for the Microcontroller Division of Texas Instruments; deep down, I still consider myself to be an analog engineer.  I must confess that I didn’t always respect digital designers, as I used to believe their ranks were filled with slacker engineering students who flunked their Laplace Transform classes.  After all, how difficult could it be to do a digital design?  With an LS7400 NAND gate, there are a thousand ways to hook up the inputs and output, but only one way is correct.  With an LM324 op-amp, there are also a thousand ways to hook up the inputs and output, and they are ALL correct!  So I concluded that analog design was where the REAL engineers were!

Having said that, you can imagine my dismay as I watched the digital juggernaut begin devouring my analog motor control playground.  One bastion after another of analog design expertise fell to the relentless onslaught of the ubiquitous microprocessor.  I was inevitably dragged kicking and screaming into the digital age.  But somewhere along the way, I began to see the microprocessor as a friend rather than an enemy.  I soon realized that digital system design wasn’t just a copout for engineers who couldn’t solve differential equations.  In fact, when viewed through the prism of the z-transform, designing digital control systems is just as challenging (if not more so) as designing an analog controller.   Today it’s hard to imagine motor control without the microcontroller, as some technologies such as Field-Oriented-Control would not even be economically possible.

The process of dropping a microcontroller into the heart of a motor control system is a fairly common practice today.  However, there are some subtleties that are worth mentioning, which I refer to as my “Ten Commandments of Digital Control”.  I plan to write 5 blogs this week, each containing two commandments.  So without further ado, here they are, counting down from commandment number 10:

10.  Be prepared…Model-based code generation is coming!

While this is technically not a commandment, it is certainly a phenomenon!  It won’t be long before we will be relying on computers themselves to write the actual motor control code.  Today we use software drivers to abstract the hardware details of a peripheral from the rest of the software.  Soon, simulation tools will be able to abstract the entire motor control software effort!  Just as I was forced to embrace a different design methodology for motor control hardware, I predict we will see the same effect play out with many software engineers who have grown comfortable with writing their own motor control code.  You can read more of my thoughts about this topic in a previous blog here.

9.   Be skeptical…Garbage in, garbage out!

You’ve probably heard the adage that “you can put lipstick on a pig, but it’s still a pig.”  The same statement applies to a beautiful simulation output which is based on a faulty interpretation of your control system.  Simulation technology already plays a critical role in the motor control design process, and this trend will continue to increase as discussed above.  But while this shortens the design process, it can also be dangerous if you don’t have a reference point grounded in reality to interpret the simulation results.  The computer can NEVER be used as a replacement for human experience or intuition.  You can read more of my thoughts on this topic in a previous blog here.

So, there you have the first two.  Stay tuned for the rest of the list all this week.  And in the meantime...

Keep those motors spinning!

转自https://wisconsin793.rssing.com/chan-12782796/article492.html

http://www.hskmm.com/?act=detail&tid=25356

相关文章:

  • ctf逆向常见算法----base64
  • 02020409 EF Core基础09-一对一、多对多、EF Core基于关系的复杂查询
  • 02020503 EF Core高级03-分页查询、IQuerable底层的实现形式、DataReader、DataTable、EF Core中的异步方法
  • 02020502 EF Core高级02-IQuerable会延迟执行、分部和动态构建IQuerable、IQuerable的复用
  • 在 PyCharm 中,环境:bert_env , 执行 import wandb 报错。但是,在CMD窗口,环境:bert_env , 执行 import wandb 正常。
  • Linux_T(Sticky Bit)粘滞位详解 - 详解
  • P2831 [NOIP 2016 提高组] 愤怒的小鸟 题解
  • 库存中心(三层库存模型)
  • Valley靶机渗透实战:从凭证复用到Python库劫持
  • 10.05模拟赛反思
  • MariaDB收购SkySQL增强AI与无服务器能力
  • 单片机寄存器的四种主要类型! - 实践
  • TDengine 高级特性——读缓存
  • 非合作博弈之软性均衡:东方智慧与西方理论的融合框架
  • 如何快速搭建spring-boot工程 - murphy
  • Ai元人文:东谈西论——非合作博弈之软性均衡
  • 反向传播与梯度下降:神经网络如何真正学会分类
  • Spring Cloud Alibaba微服务开发
  • OI 各种东西的板子
  • 价值弥漫:AI元人文的场域革命与共生之路
  • 做题记录 #1
  • 阿爸阿爸
  • 深度学习优化器算法巧思速览
  • 完整教程:LangChain完全指南:从入门到精通,打造AI应用开发新范式
  • NDK开发与实践(入门篇微课视频版)
  • 调了很久的代码总结
  • CF700E
  • 价值弥漫:“AI元人文”的场域革命与共生之路
  • k8s之pod概念
  • CF 1055 Div.1+Div.2