linUpdateResponse与输出-LIN模拟节点有何不同? [英] linUpdateResponse vs Output - how are they different for LIN simulated nodes?

查看:263
本文介绍了linUpdateResponse与输出-LIN模拟节点有何不同?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在LIN模拟从节点中,输出 linUpdateResponse 有什么区别?

In a LIN simulated slave node, what is the difference between output and linUpdateResponse?

来自输出文档:

To reconfigure response data of LIN frame. In that case RTR selector has to be set to 0. The LIN hardware responds to the next request of the specified frame with the newly configured data.

因此,我可以重新配置输出,下次(真实的)硬件应该说出我已经成功覆盖它,对吧?

So, I can reconfigure the output and next time (real?) hardware should talk I've successfully override it, right?

来自 linUpdateResponse 文档:

Updates the response data of a specific LIN frame.

让我为特定帧ID设置数据长度(dlc)和数据内容。

letting me set data length (dlc) and data content for a specific frame ID.

它们有何不同?是否有可用的示例?我不太理解如何通过提供的示例来使用后者。

How are they different and are there examples available? I can't quite understand how to use the latter with the example provided.

推荐答案

对于LIN从属节点,实际上并没有输出 linUpdateResponse 之间的差异。

For LIN slave nodes, there is not really a difference between output and linUpdateResponse.

两者都修改

正如您所发布的那样,当使用<时,请更改(模拟的)从设备的内部状态,并更改将在下次主设备请求该帧时发送的帧。 code>输出,您已经设置了 RTR 选择器。

As you have posted, when using output you have the set the RTR selector.

但是

我个人认为 linUpdateResponse 更为方便。

I, personally, think that linUpdateResponse is more convenient to use.

这篇关于linUpdateResponse与输出-LIN模拟节点有何不同?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆