我們的品牌

Impact-Company-Logo-English Black-01-177x54

歡迎造訪施耐德電機全球網站

歡迎訪問我們的網站
		
我们今天能为您提供什么帮助?
ATV320 with EtherNet/IP, why the drive does not start with assemblies 20/70?

Issue:

ATV320 with EtherNet/IP is not starting with assemblies 20/70.

Product Line:

ATV320

Environment:
Ethernet IP

Cause:

n/a

Resolution:

With assemblies 20/70, it's mandatory to respect dedicated drive configuration on : CD1, FR1, CHCF, CD2, FR2, CCS, RFC parameter

But in addition, it's mandatory to write via acyclic messaging the NetRef and NetCtrl parameters.

With Assemblies 20-70 «NetRef» and «NetCtrl» objects must be set by explicit messaging to control the drive by Network.
NetCtrl and NetRef are CIP object.

NetCtrl
This object defines if requests Run/Stop control come from local or from the network.

When NetCtrl=0: Local command.
When NetCtrl=1: Network command


NetRef
This object defines if Requests torque or speed reference to be local or from the network.

When NetRef =0: Local Reference.
When NetRef =1: Local Reference.


Here with assemblies 20-70 its necessary there is no bit inside the assembly object so it’s necessary to send these 2 CIP objects by acyclic exchange

To activate the command by EtherNet/IP you need to write 1 in NetCtrl.

In the path 16#29/01/05 (or "41/01/05" address in decimal), you write 1.

To activate the reference by EtherNet/IP you need to write 1 in NetRef.

In the path 16#2A/01/04 (or "42/01/04» address in decimal), you write 1.

You need to write these 2 CIP objects after:
- drive power on
- Disconnection of DeviceNet/Ethernet cable.

Note: The default setting (value 0) of NetCtrl and NetRef will applied each time you Power ON the drive or after DeviceNet/Ethernet cable disconnection.

施耐德電機Taiwan

探索更多
系列:
探索更多
系列:
  • 產品文檔
  • 軟體下載
  • 產品選型工具
  • 產品替代和替換
  • 幫助和聯絡中心
  • 尋找我們的辦公室
  • 取得報價
  • 施耐德電機社群
  • 人才招募
  • 公司簡介
  • 舉報不當行為
  • 無障礙
  • 新聞中心
  • 投資者
  • 專業洞察
  • 台灣施耐德電機學院
  • 綠色影響力落差調查
  • Schneider Go Green 2025
  • 隱私政策
  • Cookie通告
  • 使用條款
  • Change your cookie settings