电脑桌面
添加小米粒文库到电脑桌面
安装后可以在桌面快捷访问

OBDII通讯协议VIP免费

OBDII通讯协议_第1页
1/8
OBDII通讯协议_第2页
2/8
OBDII通讯协议_第3页
3/8
OBD-II 通讯协议 OBD-II Network Standards » J1850 PW – Adopted by GM; also known as Class 2. – Adopted by Chrysler (known as J1850). – Some references to PW mode heard about in regards to Toyota (and Honda ?). – 10.4 kbps, single wire. » J1850 PWM – Adopted by Ford; also known as Standard Corporate Protocol (SCP). – Also seen in some Mazda products. – Some references to PWM mode heard about in regards to Mitsubishi. – 41.6 kbps, two wire balanced signal. » ISO 9141 and ISO 9141-2 (also known as ISO 9141 CARB) – Seen in some Chrysler and Mazda products. – Seems to be more common in Europe. – 10.4 kbps, single wire. OBDII 通讯协议 obdii generic communication protocols by manufacturer Recently I tried to install my product on Peuzeot(406 or something similar). There was KWP 2000 bus. I tried to get the speed alue from the bus by sending the following string 0xc2 0x33 0xf1 0x01 0x0d 0xf4. On responce I receied two answers from 2 different ECUs: 1) 0x83 0xf1 0x10 0x7f 0x01 0x12 0x16 1) 0x83 0xf1 0xa4 0x41 0x0d 0x00 0x66 The first ECU sent me NACK (This response code indicates that the requested action will not be taken because the serer (ECU) does not support the arguments of the request message or the format of the argument bytes do not match the prescribed format for the specified serice.) My question is: if there was something wrong with the arguments of the request message, the second ECU also should not understand the request, bit it did ! And the second question is: why the first ECU did send the negatie answer. If you look at the j1979 PDF you will find there that "If an ECU does not support any of the PIDs requested it is not allowed to send a ...

1、当您付费下载文档后,您只拥有了使用权限,并不意味着购买了版权,文档只能用于自身使用,不得用于其他商业用途(如 [转卖]进行直接盈利或[编辑后售卖]进行间接盈利)。
2、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。
3、如文档内容存在违规,或者侵犯商业秘密、侵犯著作权等,请点击“违规举报”。

碎片内容

OBDII通讯协议

确认删除?
VIP
微信客服
  • 扫码咨询
会员Q群
  • 会员专属群点击这里加入QQ群
客服邮箱
回到顶部