DS200RTBAG2AFB通用電氣模塊
LONWORKS通信將選項板A-1添加到控制器以擴展I/O容量。董事會使用LonWorks通信
通過單雙絞線網絡與遠程LonWorks設備通信的協議。圖表顯示：選項板添加到MPU控制器板和遠程安裝的LonWorks節點。LonWorks遠程I/O板使用自由拓撲收發器，以78.1 Kbps通信。
最多可將十五（15）個物理節點連接到控制器。
首先將所有節點連接到網絡，安裝LonWorks網絡。下一步，臨時連接基于PC的使用Echelon公司生產的SLTA（串行鏈路通話適配器）將網絡管理器連接到網絡
網絡管理器（MetaVision 3.0）和SLTA包含在LonWorks啟動工具包中。然后，每個單獨的節點由網絡管理器安裝并保存在項目文件中。項目文件是網絡安裝的永久記錄，必須保留以備將來進行任何網絡維護。當
首先安裝節點，網絡管理器讀取程序ID和神經元ID（每個LonWorks設備都有包含全球唯一ID的神經元芯片）。如果以前沒有具有相同程序ID的節點安裝后，它將從節點讀取所有自文檔。網絡管理器現在將有一個所有該節點內的可用參數和I/O變量?？赡苄枰渲媚承﹨担珜τ趯τ诖蠖鄶祽贸绦颍J設置是可以接受的。然后使用網絡管理器綁定網絡變量（即將i/O變量從一個節點連接到另一個節點）。
從遠程節點到控制器的網絡變量連接通過以下方式在控制器內使用：單個環路配置中的LonWorks I/O功能塊12。這些功能塊在本手冊的“功能塊”部分允許將網絡變量連接到其他塊控制器內的輸入。有許多不同的塊類型可用。塊選擇取決于要連接的變量類型。
西門子支持LonWorks標準網絡變量類型：
?模擬輸入和輸出的SNVT_lev_percent
?離散輸入和輸出的SNVT_lev_disc
?SNVT_state，用于西門子16通道離散輸入或輸出模塊，固件1.30或更高
每個網絡限制有15個節點。當控制器應用程序需要大量I/O計數時，請使用物理
具有較高I/O計數的節點，以最小化所需的物理節點數量。例如，西門子提供
16通道離散輸入和輸出模塊。在控制器配置中，每個控制器最多可使用六個。A 4-還提供通道模擬輸入模塊和2通道模擬輸出模塊。服務考慮
LonWorks網絡的功能可能受到以下因素的影響：
?升級MPU控制器板固件
?用具有不同固件版本的板替換控制器的MPU控制器板
?將LonWorks板移動到具有不同MPU控制器板固件版本的控制器
LONWORKS COMMUNICATIONS
Option board A-1 is added to a controller to expand the I/O capacity. The board uses the LonWorks communication
protocol to communicate with remote LonWorks devices over a single twisted pair network. The diagram shows
the option board added to an MPU Controller board and remote mounted LonWorks nodes.
A LonWorks Remote I/O board uses a Free Topology transceiver communicating at 78.1 Kbps.
Up to fifteen (15) physical nodes can be connected to a controller.
Install a LonWorks network by first wiring all the nodes to the network. Next, temporarily connect a PC-based
Network Manager to the network using a SLTA (Serial Link Talk Adapter) manufactured by Echelon Corp. The
Network Manager (MetaVision 3.0) and the SLTA are included in the LonWorks Startup Kit.
Each individual node is then installed by the Network Manager and saved in a Project file. The Project file is a
permanent record of the network installation and must be retained for any future network maintenance. When a
node is first installed, the Network Manager reads the Program ID and the Neuron ID (every LonWorks device has
a Neuron chip that contains a worldwide unique ID). If a node with the same Program ID had not been previously
installed, it will read all of the self-documentation from the node. The Network Manager will now have a list of all
the available parameters and I/O variables within that node. Some parameters may need to be configured, but for
most applications, the default settings are acceptable. The Network Manager is then used to BIND network
variables (i.e. connect I/O variables from one node to another).
Network variable connections from remote nodes to the controller are used within the controller by selecting
LonWorks I/O function blocks within individual loop configurations12. These function blocks, which are detailed in
the Function Blocks section of this manual, enable connections to network variables to be made to other block
inputs within the controller. There are a number of different block types available. Block selection depends on the
types of variables to be connected. Siemens supports LonWorks Standard Network Variable Types:
? SNVT_lev_percent for analog inputs and outputs
? SNVT_lev_disc for discrete inputs and outputs
? SNVT_state for use with the Siemens 16-channel discrete input or output modules available with firmware 1.30
or higher
There is a 15 node per network limit. When large I/O counts are needed for a controller application, use physical
nodes with higher I/O counts to minimize the number of physical nodes required. For example, Siemens provides
16-channel discrete input and output modules. Up to six of each can be used within a controller configuration. A 4-
channel analog input module and a 2-channel analog output module are also available. SERVICING CONSIDERATIONS
The functioning of a LonWorks network can be affected by:
? Upgrading the MPU Controller board firmware
? Replacing a controller’s MPU Controller board with a board having a different firmware version
? Moving a LonWorks board to a controller with a different MPU Controller board firmware version
