KUC755AE105 3BHB005243R0105使用开关S启动驱动器来启动输送机

ACS355驱动器有许多解决常见问题的方案。以下示例说明了KUC755AE105 3BHB005243R0105 COUNTER STOP（计数器停止）功能如何在输送机卸载程序中运行。在预定数量的箱子通过传感器后，该功能停止输送机。操作员通过使用开关S启动驱动器来启动输送机。该开关连接到数字输入1（DI1）。

驱动器在1秒的斜坡时间内加速至30 Hz的恒定速度。同时，传感器或接近开关P连接到数字输入5（DI5）。每当输送机上的箱子经过时，该传感器就会产生一个脉冲。当所需数量的箱子（在本例中为20个）经过传感器时，驱动器会在1秒的斜坡时间内停止。参数设置启动数据正确的电机参数设置在参数组99中。但是，如果电机和驱动器的电流和电压设置匹配，则没有必要这样做。

ACS355还具有矢量控制功能，可通过设置相关参数和进行ID运行来使用。启动/停止/方向逻辑参数1001 EXT1 COMMAND设置为COUNTER Stop[24]。在某些情况下，计数器输出将修改用于停止的启动/停止信号。定速选择参数1201 CONST speed SEL设置为DI1[1]。当数字输入1激活时，参数1202 CONST SPEED 1充当速度参考源。参数1202 CONST SPEED 1设置为30 Hz。

ACS355具有以下电机控制功能：

•电流、扭矩、速度和频率限制

•欠电压和过电压控制器

•启动旋转机器

•线性，标量控制的平方和用户定义U/f曲线

•标量控制的IR补偿

•节能的通量优化

•改善斜坡下降的通量制动

•驱动器温度控制的开关频率控制

•电机噪声平滑

•感应电机的无传感器矢量控制

•永磁电机的无传感矢量控制

•平稳启动永磁电机功能

•矢量控制模式下的PID速度控制器

•加速度补偿

•速度控制器自动调谐

•独立和旋转电机识别运行

•闭环矢量控制的可选速度反馈

The quality standards of software will only introduce the following commonly used software quality indicators:
(1) Mean time between non work (MTBD). If Tv is the total normal working time of the software, and d is the number of times the system has stopped working due to software failure, then MTBD=Tv/(d+1)
(2) Number of times the system is not working (within a certain period of time). The number of times that the software stops working due to a malfunction and must be restarted by the operator to continue working.
Mean time to repair (MTTR). It reflects the efficiency of taking countermeasures after software defects occur. For online systems, MTTR<2d is generally required, while for regular systems, MTTR<7d is required.
(4) Average downtime MDT. The average time the system stops working due to software failures. For online systems, MDT<10min is required, while for regular systems, MDT<30min is required.
(5) Availability A. If Tv is the normal working time of the software and TD is the time when the system does not work due to a software fault, then the definition is: A=TV/(TV+TD) The above equation can also be expressed as A=MTBD/(MTBD+MDT)
(6) Initial failure rate. Generally, the initial failure rate period is three months after the software is delivered to the user. The initial failure rate is measured in units of failures per 100 hours. It is used to evaluate the quality of software delivery and predict when software reliability is basically stable. Generally, the initial failure rate is required to not exceed 1, that is, less than one failure per 100 hours.
(7) Accidental failure rate. Generally, the accidental failure period is four months after the software is delivered to the user, and the accidental failure rate is generally measured in the number of failures per 1000 hours, which reflects the quality of the software in a stable state. The general requirement is that the accidental failure rate should not exceed 1, that is, there should be less than one failure every 1000h, that is, the MTBF should exceed 1000h.
(8) Misuse rate of the user. Any error caused by the user not following the software manual or other documents is called misuse by the user. The percentage of misuse by the user in the total number of uses is called the user misuse rate.
(9) Number of supplementary requests from users. If the user puts forward supplementary requirements for the software, it reflects that the functionality of the software cannot fully meet the user's needs. If this situation occurs frequently after a period of software application, it indicates that the software has entered an aging period and should be replaced by developing new software. Generally, during the period of accidental failure, the number of monthly requests made by users should not exceed 1. If the average has exceeded 1, it is considered that the software has entered an aging period.
(10) Processing ability. There are various indicators of processing ability. For example, it can be represented by how many process input variables are processed per second, and how many seconds it takes to replace each CRT screen. The above introduces some basic concepts related to the reliability of decentralized control systems.