tag 标签: can

相关帖子
相关博文
  • 热度 2
    2019-9-11 14:21
    2087 次阅读|
    1 个评论
    TJA1043简介
    一:基本信息 · TJA1043 是一个 CAN 收发器,位于 CAN 控制器和 BUS 之间。 · 支持 CAN FD 。在 CAN FD 模式下,速率可达 5Mbit/s 。 · 支持 12V 和 24V 系统。 · 两种封装。 SO14 和 HVSON14 。 二: Pin定义 · VCC: 给 Transimt 供电。电压范围 4.5~5.5V 。 · VIO: 给 I/O 口供电。电压 2.8~5.5V 。此 Pin 需要和 MCU 共用电源。这样 TXD,RXD,STB_N,EN,ERR_N 会和 MCU 有同样的逻辑电平。 · Vbat :直接连接在电池上。当整个系统都处于休眠状态,只有 CAN 内部一小部分活着。为了下一次的 wake up 。 Vbat 就是在此种状态下, CAN 中仍旧活着的那一小部分供电。 · GND · TXD: 这是一根信号输入 pin 。 · RXD: 这是一根信号输出 pin 。 · CANH/L: BUS 信号 · EN :使能输入 pin · INH :输出 pin 。控制 DUT 上电源模块使能 。 · ERR_N :输出 pin 。作为 Error 或者 power on 指示 pin , active 电压是 L 。 · WAKE :本地唤醒输入 pin 。 此 pin 是输入 pin 。它即可以侦测信号从 H 到 L 的变化,也可以侦测信号从 L 到 H 的变化。当侦测到有电平转换,即意味着 CAN 要被唤醒。 为了更好的 EMI 性能,建议此 pin 连接到 VBAT 或者 GND 。 · STB_N : Standby 输入 pin , active 电压是 L 。 · SPLIT :共模稳定输出 pin。 此 pin 连接到分离电阻终端网络,可以稳定 BUS 上的隐性电压。通过一个 DC 泄漏到 GND ,可以降低 EME (电磁辐射)。 在 Normal 和 Listen only mode ,此 pin 输出一个 0.5VCC 的直流电压。在其他三种模式下,它是 floating 的 。 三:电源相关 1. 操作电压 VCC=4.5~5. 5V VIO=2.8~5.5V 2. 耗电 (1) 针对 VCC 正常工作时,耗电最大值是 65mA 处于 Listen only 时,耗电最大 9mA 。 Standby 或者 sleep 状态时,耗电最大 2uA 。 (2) 针对 VIO 工作时,耗电最大 500uA Standby 或者休眠模式时,耗电最大 4uA 。 四:工作模式 1043 有 5 种工作模式。通过 STB_N 和 EN 去设置这些工作模式。 1. Normal mode 在此模式下, 1043 通过 CANH 和 CANL 接收或者发送数据。接收到的模拟差分信号,会被转换成数字信号通过 RXD 输出。 BUS pin 上有偏置电压,其值是 0.5VCC ,即 2.5V 。原因是 1043 的 Ri 造成。 Ri 是 1043 的输入阻抗。 1043 的单端输入阻抗是 9Kohm , 15Kohm , 28Kohm 。其差分阻抗是 19Kohm , 30Kohm , 52Kohm 。 INH 一直是 H 。即相关的电源都是打开的。 2. Listen only mode 在此模式下, 1043 的输出功能是 disable 的。仅仅只有接收功能。仍旧会将 CAN BUS 上的数据通过 RXD 输出到 MCU 。 仍旧还有 0.5VCC 的偏置, INH 也还是 H 。 3.Standby mode 这是一种省电模式。 1043 既不输出数据,也不接收数据。 1043 的 low power receiver 被激活去监控 bus 。 BUS 的偏置位于 GND level 。 INH 仍旧为 H ,即有其控制的相关电源仍旧打开着。 RXD 和 ERR_N 将映射出任何的 wake up 需求。需要提供 VIO 和 VBAT 。 4. Go to sleep mode 此模式是进入 sleep mode 的一个过渡阶段。在此模式下, 1043 的行为像 standby 模式,同时有 go to sleep 命令被传输到 1043. 在进入完全 sleep mode 之前, 1043 将处于 go to sleep mode 若干时间,此时间称为 Th ( min ),即 the Minimum hold time 。 在此时间之前,如果 STB_N 或者 EN 改变,或者 wake flag 被设置,则 1043 不会进入 go to sleep mode 。 5. Sleep mode 需要通过 go to sleep mode 进入 sleep mode ,并且在相关电压( VCC 活 VIO )恢复之前,侦测到 VCC or VIO 处于欠压已经一段时间了。 在此模式下, 1043 行为和 standby 一致,只是 INH 被设置为 floating 。所有 INH 控制的电源都处于 off 状态。进入 Vbat 的电流将被减低到最小。 通过 STB_N , EN 和 wake flag 可以将 node 唤醒从 sleep mode 。 五:2种wake up方式 1. Local wakeup 当 wake pin 有电平变化,并且新的电平持续时间大于 Twake 时,local wakeup被侦测到。 2. Remove wake up * 1043 在 standby or sleep 模式下,可以通过侦测 CAN BUS 上一组特殊的 wake up pattern ,唤醒自己。 * 这个测试 pattern 在 ISO11898-5:2007 中有定义。 * 有 滤波器 可以帮忙滤除假的 wake up pattern 。这些假的 pattern 是由于 BUS 上的噪声和毛刺引起的。 * 测试 Pattern 有三部分组成: · 一份显性信号,至少持续 Twake ( busdom ) · 一份隐性信号,至少持续 Twake ( busrec ) · 一份显性信号,至少持续 Twake ( busdom ) · 无论显性信号,还是隐性信号,只要时间短于上面的时间需求,都会被忽略。 * 完整的三段信号必须在 Tto ( wake ) bus 时间之内被接收并且识别。否则内部的 wake up 逻辑会被复位。接收到的完整的 wake up pattern 将会触发 wake up 事件。注意: RXD pin 一直保持高,直到 wake up 事件被触发,才会变 L 。 六:Local failures 1043 能侦测到 4 中 local failure 情况,同时会设置 local failures flag 。而且大多数情况下, 1043 的输出会被 disable 。 1. TXD dominant 超时 由于 HW 或者 SW 应用出错,导致在 TXD pin 上出现永久的 L level ,这将驱动 CAN BUS 进入永久的显性阶段,锁住整个网络通信。 TXD dominant time out 功能就是:当 TXD 保持 L 电平超过 Tto(dom)TXD 时,去 disable 发射机 ,阻止网络被锁。发射机会持续 disable ,直到 local failure flag 被清除。 2. TXD to RXD 短路侦测 当 RXD pin 和 TXD pin 之间短路时,一旦 bus 被驱动为显性,整个 bus 都会被锁在永久的显性状态。 原因是 RXD 的低边驱动能力一般都强于 TXD 的高边驱动能力。 当出现此种短路时,发射机会被 disable 。直到 local failure flag 被清除。 3.Bus 显性超时 当 CAN BUS 短路到 VBAT 、 VCC 或者 GND ,或者网络上其他节点出现 fail ,都会导致一个差分电压出现在 BUS 上,进而导致 BUS 处于显性状态。 当 BUS 处于显性状态,会导致任何一个 node 不能开始传输。一般的 BUS failure detection 不能侦测到这种失败,但是 bus dominant clamping (固定住) detection 可以侦测到此种失败。 当 BUS 处于显性状态超过 Tto ( dom ) bus , local failure flag 会被设置。通过检测此 flag ,控制器可以确定是否有一个钳位 bus 将网络通信锁住。不需要去 disable 发射机。 注意: local failure flag 不能保持此种 bus 显性 clamping failure ,同时会尽快让 BUS 回到隐性阶段。 4. 过温测试 当结温变的很大, 1043 将 shut down 去保护 输出设备 。 1043 将一直处于 disable 状态,直到此 local failure flag 被清除。 ------------------------------------------------------------------------------ 转载请说明出处。
  • 热度 5
    2016-4-18 20:10
    1328 次阅读|
    4 个评论
    一、 常见 CAN 收发器 TJA1042 的数据手册 TJA1042 datasheet中Block框图描述了收发器的内部结构:          Datasheet中还有关于split管脚的内部模型:          Datasheet的描述很简陋,但是可以用来构建简单的CAN收发器电路模型。 二、 CAN 收发器电路模型(仅用于简单的 DC 分析) 估计把下面的模型放出来,能把IC工程师气得吐血,乃至生活不能自理。 在此,向节假日依然奋战在IC工业的广大工程师指战员们表示慰问!下面的内容,如 此简单粗暴地简化你们复杂而伟大的工作,仅仅是为了DC分析某项小问题,不代表CAN收发器内部结构可以这样简单,     简单的内部结构如下:       使用Cadence公司PSpice仿真软件,可以得到CANH/CANL波形的仿真结果:          有了以上工作的基础,可以进行其它诸如总线CANH断线时波形分析等等问题的分析,免去计算等,可以直观地观察波形。   参考资料: TJA1042,Product data sheet,Rev. 7 — 8 May 2012 PSpice V16-5-13c
  • 2013-10-3 18:30
    674 次阅读|
    0 个评论
    Do we now need a solution better than JTAG? Hard real-time control software is increasingly common in terms of the number of different items in everyday life that use it. Many items that offer better safety, with equivalent or better energy efficiency, are now possible. But most of the people I know who have recently purchased a new piece of electronics, or a vehicle, or some other device have found at least one bug! It is becoming increasingly clear that, without help, JTAG-based ICE (in-circuit emulation) is not up to par on many of today's CPUs. Furthermore, JTAG testing and debugging does not allow one to test all the "at speed problems" one encounters in research and development or in production. This is forcing JTAG test escapes to be found by other means. The CAN bus (for controller area network) came out around the same time as JTAG, and both took time to gain momentum. This was when embedded Flash memory sizes were only a few hundred kilobytes in size. By comparison, modern automobiles and control systems use real-time stacks on 100mbp/sec Ethernet, and 1GHz (or higher) processors with many gigabytes of Flash memory, but they often still use only JTAG for debugging, Flash Loading (often only the boot loader), and partial production test. It is left for each chip maker and OS/OEM to come up with a full Flash load/debug solution on its own. Be it an MCU, an FPGA, or some other device, many are limited in one way or another by limitations in JTAG technology. Isn't it time we come up with a readily affordable, industry-wide solution? The thing is that bad debug and test capability can have a very real human cost. Allow me to relate a story that will illustrate my point... Back in the 90s I worked for an aerospace company designing police, fire, medevac, and special mission radios for helicopters and aircraft. We had one Intel ICE for the 8051. The ICE used the old "Bond Out" chip ICE technology. I was not there when the original code was developed and they first attempted to use this ICE. It was bad enough that we were out in a lab in the middle of the desert with a bad ICE. When we were not dealing with scorpions, poisonous centipedes, black widows, or the occasional side-winder that would craw into our lab (or up through the shower drain in the middle of getting ready for work) we had to find other, less venomous, but equally vexing, "bugs" by the time- honoured tradition of "Burn and Learn." What this meant was that we would "burn" a UV erasable version of the processor and then "learn" whether or not it would then burn out the transmitter. Dealing with ever-so-great equipment and angry customers that could fly in at any minute to lodge a complaint was never dull. It was also interesting having to handle walking, crawling poisonous bugs while we were frantically wrestling our own black widow's nest of a C compiler riddled with bugs coupled with a bad ICE. The ICE was so complicated to set up and get working—and the power in the lab went out so often—that it was damn near impossible to get it all running right before we lost power along with the working configuration. It was a race against time reminiscent of a "Dr. Who" episode. This was in the days of DOS, and there was no such thing as an uninterruptable power supply (UPS) for a PC and ICE, let alone a Flash memory in which to save the ICE configuration. This system had actually been designed to use a VT-100 terminal as the interface! Sadly, it had been made for a large corporation that could have easily afforded a plant-wide UPS. Furthermore, the company executives had all been fined for billing all kinds of executive perks to the government, so there was no money for a better ICE when one finally came out. William Murray Electrical Engineer
  • 2013-10-3 18:27
    641 次阅读|
    0 个评论
    Is a solution better than JTAG now necessary? Hard real-time control software is increasingly common in terms of the number of different items in everyday life that use it. Many items that offer better safety, with equivalent or better energy efficiency, are now possible. But most of the people I know who have recently purchased a new piece of electronics, or a vehicle, or some other device have found at least one bug! It is becoming increasingly clear that, without help, JTAG-based ICE (in-circuit emulation) is not up to par on many of today's CPUs. Furthermore, JTAG testing and debugging does not allow one to test all the "at speed problems" one encounters in research and development or in production. This is forcing JTAG test escapes to be found by other means. The CAN bus (for controller area network) came out around the same time as JTAG, and both took time to gain momentum. This was when embedded Flash memory sizes were only a few hundred kilobytes in size. By comparison, modern automobiles and control systems use real-time stacks on 100mbp/sec Ethernet, and 1GHz (or higher) processors with many gigabytes of Flash memory, but they often still use only JTAG for debugging, Flash Loading (often only the boot loader), and partial production test. It is left for each chip maker and OS/OEM to come up with a full Flash load/debug solution on its own. Be it an MCU, an FPGA, or some other device, many are limited in one way or another by limitations in JTAG technology. Isn't it time we come up with a readily affordable, industry-wide solution? The thing is that bad debug and test capability can have a very real human cost. Allow me to relate a story that will illustrate my point... Back in the 90s I worked for an aerospace company designing police, fire, medevac, and special mission radios for helicopters and aircraft. We had one Intel ICE for the 8051. The ICE used the old "Bond Out" chip ICE technology. I was not there when the original code was developed and they first attempted to use this ICE. It was bad enough that we were out in a lab in the middle of the desert with a bad ICE. When we were not dealing with scorpions, poisonous centipedes, black widows, or the occasional side-winder that would craw into our lab (or up through the shower drain in the middle of getting ready for work) we had to find other, less venomous, but equally vexing, "bugs" by the time- honoured tradition of "Burn and Learn." What this meant was that we would "burn" a UV erasable version of the processor and then "learn" whether or not it would then burn out the transmitter. Dealing with ever-so-great equipment and angry customers that could fly in at any minute to lodge a complaint was never dull. It was also interesting having to handle walking, crawling poisonous bugs while we were frantically wrestling our own black widow's nest of a C compiler riddled with bugs coupled with a bad ICE. The ICE was so complicated to set up and get working—and the power in the lab went out so often—that it was damn near impossible to get it all running right before we lost power along with the working configuration. It was a race against time reminiscent of a "Dr. Who" episode. This was in the days of DOS, and there was no such thing as an uninterruptable power supply (UPS) for a PC and ICE, let alone a Flash memory in which to save the ICE configuration. This system had actually been designed to use a VT-100 terminal as the interface! Sadly, it had been made for a large corporation that could have easily afforded a plant-wide UPS. Furthermore, the company executives had all been fined for billing all kinds of executive perks to the government, so there was no money for a better ICE when one finally came out. William Murray Electrical Engineer  
  • 热度 3
    2012-6-8 21:00
    2613 次阅读|
    2 个评论
    。简介        随着汽车工业的发展,汽车已经成为当今社会的主要交通工具,汽车电子化、网络化、智能化也促使汽车零部件越来越多、构造越来越复杂,作为减少硬联机主要技术的汽车总线系统也越来越被广泛使用和认可。         BLC1006为汽车总线模拟系统,是汽车总线产品开发的必备利器。能为开发汽车总线产品的技术人员提供很高的参考价值,大大减少开发难度及周期,也能为汽车专业广大院生及个人爱好者提供参考,加深理解及领会汽车总线系统。BLC1006支持目前主流的汽车总线系统,包括ISO规定的ISO9141、ISO14230、ISO11898、ISO15765及美国SAE J1850协议。 。主要功能 支持ISO9141协议 支持ISO14230快速初始化协议 支持ISO14230 5波特率初始化协议 支持ISO15765 CAN250K标准协议 支持ISO15765 CAN250K扩展协议 支持ISO15765 CAN500K标准协议 支持ISO15765 CAN500K扩展协议 支持SAE J1850 PWM协议 支持SAE J1850 VPW协议 支持EUC四种工作模式:NORMAL、CALIBRATION、LISTEN、AUTO         …… 。ECU 工作模式介绍 NORMAL MODE:在这种模式,所有OBD产品请求的PID模拟量数据可以通过手动调节FR1~FR6获取,PID与FR1~FR6的映射关系参考附录A       ……      MAF曲线图:      …… 串口监控:     ……  FREEZE FRAME:      安装说明           类似于安装在汽车上即插即用,可直接将特开发的OBD产品连接到BLC1006的OBD母插座 可开发产品举例 OBD2 汽车检测仪 OBD2 诊断仪 OBB2 通用油耗仪 智能行车电脑 GPS 导航行车电脑  ……         (如有需要请联系,加入QQ请注明所在公司)          联系人:袁生          Mobile:13613076578          QQ:573143979 E_MAIL:veni_gps@163.com   下面是本店连接: http://item.taobao.com/item.htm?id=17540164883_u=kqdtr7m8f59
相关资源
  • 所需E币: 5
    时间: 2020-7-16 08:05
    大小: 13.84MB
    上传者: oo1try_669943284
    现场总线CAN原理与应用技术
  • 所需E币: 5
    时间: 2020-6-25 16:22
    大小: 244.8KB
    上传者: kaidi2003
    ONSEMI_NCV7341CANTransceiverBehaviorwithaPermanentShortontheCANBus.PDF
  • 所需E币: 2
    时间: 2020-6-19 21:50
    大小: 453.88KB
    上传者: Goodluck2020
    AN-1123控制器局域网(CAN)实施指南(Rev.0).pdf
  • 所需E币: 1
    时间: 2020-5-29 22:51
    大小: 42.94KB
    上传者: 星空下的屋顶
    CAN总线接口电路设计注意事项.docx
  • 所需E币: 1
    时间: 2020-5-31 09:31
    大小: 577.48KB
    上传者: 星空下的屋顶
    can收与发的完整例程.zip
  • 所需E币: 1
    时间: 2020-5-28 14:44
    大小: 436.16KB
    上传者: sense1999
    CAN总线最早是由Bosch和Intel在80年代末开发的,虽然最早是用在汽车级的通信系统中的,但是随着技术的发展,CAN总线应用范围已经不在局限于汽车中,像机器人、工业、自动控制系统中,都有广泛的应用。
  • 所需E币: 1
    时间: 2020-5-25 15:26
    大小: 20.11KB
    上传者: Argent
    VB是早期比较流程的编程语言,VisualBasic由微软公司开发,是世界上使用人数最多的语言。它源自于BASIC编程语言。VB拥有图形用户界面(GUI)和快速应用程序开发(RAD)系统,可以轻易的使用DAO、RDO、ADO连接数据库,或者轻松的创建ActiveX控件。程序员可以轻松的使用VB提供的组件快速建立一个应用程序。感兴趣的网友们快来下载,练练手吧。
  • 所需E币: 5
    时间: 2019-12-26 09:57
    大小: 718.67KB
    上传者: 微风DS
    SJA1000独立CAN控制器……
  • 所需E币: 5
    时间: 2019-12-26 01:42
    大小: 5.36MB
    上传者: quw431979_163.com
    TheDS80C390isafast8051-compatiblemicroprocessor.Theredesignedprocessorcoreexecutes8051instructionsupto3timesfasterthantheoriginalforthesamecrystalspeed.TheDS80C390supportsamaximumcrystalspeedof40MHz,resultinginapparentexecutionspeedsof100MHz(approximately2.5X).Anoptionalinternalfrequencymultiplierallowsthemicroprocessortooperateatfullspeedwithareducedcrystalfrequency,reducingEMI.Ahardwaremathacceleratorfurtherincreasesthespeedof32and16bitmultiplyanddivideoperations,aswellashigh-speedshift,normalizationandaccumulatefunctions.……
  • 所需E币: 4
    时间: 2019-12-26 00:27
    大小: 18.38KB
    上传者: 978461154_qq
    CANLinux驱动代码……
  • 所需E币: 5
    时间: 2019-12-26 00:27
    大小: 158.92KB
    上传者: rdg1993
    CAN总线协议2.0版.asp……
  • 所需E币: 5
    时间: 2019-12-25 23:23
    大小: 1.79MB
    上传者: 16245458_qq.com
    本资料是面向CAN总线初学者的CAN入门书。对CAN是什么、CAN的特征、标准规格下的位置分布等、CAN的概要及CAN的协议进行了说明。……
  • 所需E币: 4
    时间: 2019-12-25 22:50
    大小: 124.39KB
    上传者: 2iot
    介绍了一种基于数字信号处理器TMS320LF2407A和CAN总线技术的火车机车故障数据采集系统,阐述了系统的组成及硬件系统具体实现.并介绍了DS18B20的单总线通信和CAN总线通信及软件系统设计,该系统已在火车机车上成功试验,具有人机界面友好、操作简单、运行可靠,具有一定的应用价值.……
  • 所需E币: 5
    时间: 2019-12-25 22:50
    大小: 189.99KB
    上传者: 978461154_qq
    交流异步电机以其结构简单、坚固、控制性能好等优点广泛应用电动汽车的调速驱动系统之中。本文提出了基于DSP和CAN总线的异步电机全数字控制系统,所有的控制命令例如油门开度,都通过CAN总线传送。本文最后给出CAN通信的流程图和部分样代码。……
  • 所需E币: 3
    时间: 2019-12-27 20:31
    大小: 2.84MB
    上传者: rdg1993
    ADM3052ADM3053V+•集成V+线性调节器•集成V+线性调节器•总线侧由V+和V−供电•V+工作电压:11V至25V•VDD1工作电压:5V或3.3V•符合ISO11898标准•高速,数据速率最高可达1Mbps•总线引脚提供短路保护•集成总线接线错误保护•无电节点不干扰总线•总线支持110个或更多节点•热关断保护•安全和法规认证(申请中)•UL认证:1分钟5000Vrms,符合UL1577标准•符合VDE认证•DINVVDEV0884-10(VDEV0884-10):2006-12•VIORM=848V峰值•温度范围:-40℃至+85°C•16引脚宽体SOIC封装业界首款信号和电源隔离式CAN收发器ADM3052集成V+线性调节器热关断保护VDD1VDD2V+5V集成V+线性调节器安全和法规认证V+SENSEDECENCBUSV+SENSELDOV+RCINT总线侧由V+和V供电(申请中)……
  • 所需E币: 4
    时间: 2019-12-27 20:45
    大小: 138.64KB
    上传者: quw431979_163.com
    CeramicInputCapacitorsCanCauseOvervoltageTransients.pdfApplicationNote88March2001CeramicInputCapacitorsCanCauseOvervoltageTransientsGoranPericaArecenttrendinthedesignofportabledeviceshasbeenBuildingtheTestCircuittouseceramiccapacitorstofilterDC/DCconverterinputs.Toillustratetheproblem,atypical24VwalladapterusedCeramiccapacitorsareoftenchosenbecauseoftheirinnotebookcomputerapplicationswasconnectedtothesmallsize,low……
  • 所需E币: 3
    时间: 2019-12-25 21:09
    大小: 40.5KB
    上传者: quw431979_163.com
    基于提高CAN总线组网能力的考虑,提出一种新颖的CAN中继器设计方法;阐述以LPC2119控制器为核心的硬件设计方案;详细分析在μC/OS-II实时操作系统下的软件实现过程;针对中继器的实时性和安全性以及总线与总线之间可能存在的速度不匹配的问题,确立提升紧急任务优先级、建立相关事件标志、合理地对事件与任务进行同步的改进方法,从而有效地解决组网中最远传输距离和最大节电数限制的问题。……
  • 所需E币: 5
    时间: 2019-12-28 19:30
    大小: 362.38KB
    上传者: 二不过三
    简介控制器区域网络(CAN)总线是设计用于工业应用的一种稳定的协议,最初针对汽车应用而开发。它规定最大电缆长度为40米,最大节点数为30。这种规范十分灵活,优势明显,因此其应用日益广泛。由于CAN总线系统通常用于连接多个系统,铺设距离很长,因此总线和所连接的各系统之间的隔离非常关键。隔离可以防止CAN总线电缆网络与连接至总线的系统之间的过压瞬变造成破坏,同时消除网络中的接地环路,减少信号失真和误差,并防止电压/接地失配影响电路。本应用笔记的目的是向用户简要介绍CAN总线协议,重点讨论系统物理层,并解释系统隔离的重要意义。本应用笔记还详细说明了如何在CAN总线系统中利用ADI公司的iCoupler产品实现隔离。CAN总线概述CAN总线协议国际标准化组织(ISO)将CAN总线协议标准定义为串行通信双线总线,其数据速率最高可达1Mbps。它使用两层:一ISO11898AN-770应用笔记OneTechnologyWayP.O.Box9106Norwood,MA02062-9106,U.S.A.Tel:781.329.4700Fax:781.461.3113www.analog.comCAN总线应用中的iCoupler隔离作者:RonnKliger和SeanClark简介SOFARBITRATIONCONTROLDATACRCACKEOF控制器区域网络(CAN)总线是设计用于工业应用的一种稳定的协议,最初针对汽车应用而开发。它规定最大电缆长图1.CAN总线数据传输帧度为40米,最大节点数为30。这种规范十分灵活,优势明显,因此其应用日……
  • 所需E币: 4
    时间: 2019-12-25 17:30
    大小: 150.9KB
    上传者: rdg1993
    VxWorks下PC/104—CAN驱动程序设计……
  • 所需E币: 4
    时间: 2019-12-25 16:56
    大小: 99.19KB
    上传者: 二不过三
       TheCANmulti-functionboardisprovidedforsoftwareevaluationandsupportinearlystagesofdevelopment.ThisboardcontainsamicrocontrollerincorporatingCANbusmonitorsoftwareforsimpleevaluationandcandisplayloggeddatasuchasCANbuscommunicationmessagesontheLCD.……
广告