UDD406A 3BHE041465P201工控模块机器人备件
P/C消息具有固定大小
因此不需要支持消息分段。包括以下类型的消息传递：•驱动器状态（运行、故障等）•驱动器命令（启动、停止等）•控制逻辑解析操作（例如，掩码和所有者参数）•进入闪存编程模式•“软”登录和注销外围设备（启用/禁用外围设备控制）对等操作对等消息传递允许两种而不是通过主机或主机（即驱动器）进行通信。它们与C/S消息具有相同的优先级，并将在后台发生。如果LCD HIM连接到PowerFlex 700S驱动器，它将能够使用对等消息直接请求非车载参数（即驱动器中不需要代理支持）。PowerFlex 700S驱动器可以使用所有六个通信端口，因为不需要对等代理操作。所有对等操作都在用户不干预的情况下进行（无论是代理还是正常的P/P操作），不需要设置。
当驱动器处于闪存模式时
不需要对等代理操作。支持DPI系统、控制和消息规范中指定的所有定时要求。外围设备将以10ms的速率进行扫描（“ping”）。驱动器状态消息将以5ms的速率生成，而外围命令消息将在发生时（即状态变化）被驱动器接受。基于这些定时，可能会出现以下最坏情况（与波特率和协议无关）：•外围设备状态（例如，启动、停止等）更改为驱动器中的更改10 ms•参考值更改为驱动器操作中的更改10 ms•数据链路数据值更改为驱动中的更改10ms•驱动器中的参数值更改为所连接数量的20ms外设检测外设通信丢失的最长时间为500ms。52自动化出版物PFLEXRM002DENE2013年8月第1章详细驱动器配置和操作以下时序
P/C messages have a fixed size
Therefore, there is no need to support message segmentation. The following types of messaging are included: • Drive status (running, failure, etc.) • Drive commands (start, stop, etc.) • Control logic parsing operations (for example, mask and owner parameters) • Entering flash programming mode • "soft" login and logoff of peripherals (enabling/disabling peripheral control) Peer to peer messaging allows two types of communication instead of via the host or the host (that is, the drive). They have the same priority as C/S messages and will occur in the background. If the LCD HIM is connected to the PowerFlex 700S drive, it will be able to directly request off board parameters using peer-to-peer messages (that is, proxy support is not required in the drive). PowerFlex 700S drives can use all six communication ports because peer agent operations are not required. All peer-to-peer operations are performed without user intervention (either proxy or normal P/P operations), and no settings are required.
When the drive is in flash mode
Peer to peer proxy operations are not required. Supports all timing requirements specified in DPI system, control, and message specifications. Peripherals will scan ("ping") at a rate of 10ms. The drive status message will be generated at a rate of 5ms, while the peripheral command message will be accepted by the drive when it occurs (i.e., the status changes). Based on these timings, The following worst-case scenarios may occur (independent of baud rate and protocol): • Peripheral status (for example, start, stop, etc.) changes to 10 ms in the drive • Reference value changes to 10 ms in the drive operation • Data link data value changes to 10 ms in the drive • Parameter value changes to 20 ms in the drive The maximum time for peripherals to detect peripheral communication loss is 500 ms. 52 Automation publication PFLEXRM002DENE August 2013 Chapter 1 Detailed drive configuration and operation The following timing
