HART系列讲座(二):HART报文结构 点击:3757 | 回复:6



吴志扬

    
  • 精华:49帖
  • 求助:0帖
  • 帖子:62帖 | 70回
  • 年度积分:0
  • 历史总积分:502
  • 注册:2001年3月13日
发表于:2002-05-21 21:22:00
楼主
The structure of a HART message is shown below:
The preamble, of between 5 and 20 bytes of hex FF (all 1"s), helps the receiver to synchronise to the character stream. The start character may have one of several values, indicating the type of message: master to slave, slave to master, or burst message from slave; also the address format: short frame or long frame. The address field includes both the master address (a single bit: 1 for a primary master, 0 for a secondary master) and the slave address. In the short frame format, the slave address is 4 bits containing the "polling address" (0 to 15). In the long frame format, it is 38 bits containing a "unique identifier" for that particular device. (One bit is also used to indicate if a slave is in burst mode.) The command byte contains the HART command for this message. Universal commands are in the range 0 to 30; common practice commands are in the range 32 to 126; device-specific commands are in the range 128 to 253. The byte count byte contains the number of bytes to follow in the status and data bytes. The receiver uses this to know when the message is complete. (There is no special "end of message" character.) The status field (also known as the "response code") is two bytes, only present in the response message from a slave. It contains information about communication errors in the outgoing message, the status of the received command, and the status of the device itself. The data field may or may not be present, depending on the particular command. A maximum length of 25 bytes is recommended, to keep the overall message duration reasonable. (But some devices have device-specific commands using longer data fields.) See also the HART data field. Finally, the checksum byte contains an "exclusive-or" or "longitudinal parity" of all previous bytes (from the start character onwards). Together with the parity bit attached to each byte, this is used to detect communication errors.



SEAFLY6869

  • 精华:0帖
  • 求助:0帖
  • 帖子:2帖 | 9回
  • 年度积分:0
  • 历史总积分:15
  • 注册:2002年3月29日
发表于:2002-04-09 12:15:00
1楼
非常感谢你的论文: 我要做的是HART通信, 非常需要此类讲解。希望在底层更详细,更全面。

风9199

  • 精华:0帖
  • 求助:0帖
  • 帖子:0帖 | 1回
  • 年度积分:0
  • 历史总积分:1
  • 注册:2002年3月11日
发表于:2002-04-22 14:42:00
2楼
如有中文资料更好.谢谢!

bayee

  • 精华:0帖
  • 求助:0帖
  • 帖子:1帖 | 16回
  • 年度积分:0
  • 历史总积分:76
  • 注册:2002年2月26日
发表于:2002-04-22 21:06:00
3楼
请问吴老师: 有没有将HART转换成RS232/485的硬件(除了SIMENS的325外)? 急需这方面的资料,谢谢!

gongkongedit

  • 精华:1099帖
  • 求助:0帖
  • 帖子:14392帖 | 54470回
  • 年度积分:0
  • 历史总积分:622
  • 注册:2008年9月08日
发表于:2002-04-23 11:43:00
4楼
有。 我们就提供HART MODEM,您可以致电: 021-64368180-545 找 王骏

pigeon

  • 精华:0帖
  • 求助:0帖
  • 帖子:0帖 | 2回
  • 年度积分:0
  • 历史总积分:2
  • 注册:2002年5月15日
发表于:2002-05-17 15:21:00
5楼
吴老师: 请问SMAR公司的2012芯片在国内市场能买到吗?能否利用其他公司的相关芯片来代替2012实现HART协议的通讯功能?谢谢! 我的EMAIL:GUOKEX@CTA.CQ.CN

希望

  • 精华:0帖
  • 求助:0帖
  • 帖子:0帖 | 1回
  • 年度积分:0
  • 历史总积分:51
  • 注册:2002年5月21日
发表于:2002-05-21 21:22:00
6楼
希望您可以提供HSE/HEAT的相关技术资料,不胜感激

热门招聘
相关主题

官方公众号

智造工程师