t h e n e w d i m e n s i o n a b r i d g e b e t w e e n w o r l d s Upgrade from NETxKNX OPC Server 3.0 to NETxKNX OPC Server 3.

Transcription

1 a b r i d g e b e t w e e n w o r l d s Upgrade from NETxKNX OPC Server 3.0 to NETxKNX OPC Server 3.5 t h e n e w d i m e n s i o n Member of the OPC Foundation. Member of Konnex Association. April 2009, Version:

2 I n d e x Upgrading from NETxEIB OPC Server 3.0 to NETxKNX OPC Server HOW TO... 5 System requirements Support and contact Important Notes Version: Seite 2 von 13

3 Copyright This published handbook refers to the release 3.0 and 3.5 of the software system NETxKNX OPC Server. The software is published by NETxAutomation, Maria-Theresia-Strasse 41, Top 10, 4600 Wels, Austria. (C) Copyright by NETxAutomation, The correct and usable documentation can only be guaranteed in connection with the regulations of the software agreement. Changes regarding the size of the function of the mentioned software can be done and do not include a change of the documentation. All rights are reserved. Copies, translations, micro filming and the storage and processing in data processing systems are copyrighted. No part of this publication may be reproduced without the prior permission of the publisher NETxAutomation. Version: Seite 3 von 13

4 Upgrading from NETxEIB OPC Server 3.0 to NETxKNX OPC Server 3.5 Important Information A workspace from NETxEIB OPC Server 3.0 can not be used without manual changes within s directory. Filenames and s have changed. So best way to upgrade is to create a new workspace, open each configuration file with an Editor and fill out manually each definition using copy and paste. A future version will have an import tool. Version: Seite 4 von 13

5 HOW TO Install NETxKNX OPC Server 3.5 at the PC. Open NETxKNX OPC Studio 3.5 and create a new workspace with the name of old workspace from 3.0. Do not copy the old workspace of 3.0 into workspace of 3.5. Then stop the NETxKNX OPC Server. Now we have to go through each configuration file in the old workspace and in the new workspace. So let s start with these and open both with an Editor: NxEopOPCSystem.3.cfg nxaopcsystem.35.cfg As you can see the names have changed a little bit and also the order. So let s take each parameter from 3.0 and search it in 3.5 and change it value accordingly. Just by copy and paste. Version: Seite 5 von 13

6 NETxKNX OPC Server 3.0 NETxKNX OPC Server 3.5 OPC_GroupAddressType OPC.GroupAddressType OPC_PrefixedItemID OPC.PrefixedItemID OPC_SystemInterfaceEnabled OPC.SystemInterfaceEnabled OPC_AsyncTimeout OPC.AsyncTimeout OPC_AsyncReadFromDevice OPC.AsyncReadFromDevice OPC_AsyncWriteConfirmation OPC.AsyncWriteConfirmation OPC_AsyncRefreshFromDevice OPC.AsyncRefreshFromDevice OPC_RefreshOnEqualValue OPC.RefreshOnEqualValue OPC_EnableAliases OPC.EnableAliases OPC_ShowETSStructure OPC.ShowETSStructure EIB_ServerPhysicalAddress KNX.ServerPhysicalAddress EIB_Timeout KNX.Timeout EIB_RefreshAllValuesOnConnect KNX.RefreshAllValuesOnConnect EIB_CyclicRefreshAllValues KNX.CyclicRefreshAllValues EIB_CyclicRefreshAllValuesInterval KNX.CyclicRefreshAllValuesInterval EIB_CyclicRefreshAllValuesStartDelay KNX.CyclicRefreshAllValuesStartDelay EIB_CyclicRefreshAllValuesTelegramGap KNX.CyclicRefreshAllValuesTelegramGap EIB_CyclicEventStartDelay KNX.CyclicEventStartDelay EIB_CyclicEventTelegramGap KNX.CyclicEventTelegramGap EIB_SetLinkOnReceive KNX.SetLinkOnReceive EIB_SetLinkOnSend KNX.SetLinkOnSend EIB_ShowUndefinedTelegrams KNX.ShowUndefinedTelegrams SYS_UseTelegramDataFile SYS.UseTelegramDataFile SYS_MaxSizeOfTelegramLogFile SYS.MaxSizeOfTelegramLogFile SYS_GatewayConnectionTimeoutAttemptCount SYS.GatewayConnectionTimeoutAttemptCount SYS_EnableDeviceManager SYS.EnableDeviceManager EIB_PhysicalDeviceTimeout KNX.PhysicalDeviceTimeout The next configuration files are the following and open both with an Editor: NxEopOPCRouter.3.cfg nxaopcrouter.35.cfg Version: Seite 6 von 13

7 As you can see the names have changed a little bit and also the order. So let s take each parameter from 3.0 and search it in 3.5 and change it value accordingly. Just by copy and paste. NETxKNX OPC Server 3.0 ReceiveBroadcastTelegrams ReceiveOwnTelegrams ReceiveMulticastAddress SendBroadcastAsMultipleUnicast EIBNetworkCardIPAddress SYS_MaxSizeOfTelegramLogFile SYS_GatewayConnectionTimeoutAttemptCount SYS_EnableDeviceManager EIB_PhysicalDeviceTimeout NETxKNX OPC Server 3.5 UDP.ReceiveBroadcastTelegrams UDP.ReceiveOwnTelegrams IGS.ReceiveMulticastAddress UDP.SendBroadcastAsMultipleUnicast NETIP.NetworkCardIPAddress SYS.MaxSizeOfTelegramLogFile SYS.GatewayConnectionTimeoutAttemptCount SYS.EnableDeviceManager KNX.PhysicalDeviceTimeout The next configuration files are the following and open both with an Editor: NxEopNMeshNode.3.cfg nxanmesh.35.cfg Version: Seite 7 von 13

8 As you can see the names have changed a little bit and also the order. So let s take each parameter from 3.0 and search it in 3.5 and change it value accordingly. Just by copy and paste. NETxKNX OPC Server 3.0 UseRedundancy EnableSynchronization MainServerIPAddress BackupServerIPAddress NetworkCardIPAddress NetworkPortNumber StartDelay ConnectionTimeout EnableRouting NETxKNX OPC Server 3.5 NMESH.UseRedundancy NMESH.EnableSynchronization NMESH.MainServerIPAddress NMESH.BackupServerIPAddress NMESH.NetworkCardIPAddress NMESH.NetworkPortNumber NMESH.StartDelay NMESH.ConnectionTimeout NMESH.EnableRouting The next configuration file is the following and can be overtaken without any changes. Just copy and rename the file accordingly: NxEopDeviceDefinitions.3.dat nxadevicedefinitions.35.dat The next configuration files are the following and open both with an Editor: NxEopGatewayDefinitions.3.dat nxagatewaydefinitions.35.dat Version: Seite 8 von 13

9 As you can see one column for the type name of IP gateway has been added. So let s copy each definition from 3.0 and paste it in 3.5 and add the type name of IP gateway accordingly. NETxKNX OPC Server ;3671;GATE 1;Room 51;predefined Gateway 1;;;; ;51000;GATE 1;Room 51;predefined Gateway ;1634;Gate4 NETxKNX OPC Server ;NETIP;3671;GATE 1;Room 51;predefined Gateway 1;;;; ;IGS;51000;GATE 1;Room 51;predefined Gateway ;EIBNODE;1634;Gate4 The next configuration file is the following and can be overtaken without any changes. Just copy and rename the file accordingly: NxEopLinkDefinitions.3.dat nxalinkdefinitions.35.dat The next configuration files are the following and open both with an Editor: NxEopTelegramDefinitions.3.dat nxatelegramdefinitions.35.dat Version: Seite 9 von 13

10 As you can see the columns for Read on Reconnect and Read Cyclically Interval are added F;0 at the end. This has to be added to each line. The best practice would be to transfer the files to Excel in NETxKNX OPC Studio and to add those column entries in the nxatelegramdefinitions.35.xls file. After that do not forget get it from Excel back to nxatelegramdefinitions.35.dat! The next configuration file is the following and can be overtaken without any changes. Just copy and rename the file accordingly: NxEopCyclicEvents.3.dat nxacyclicevents.35.dat The next configuration file is the following and can be overtaken without any changes. Just copy and rename the file accordingly: NxEopResponeEvents.3.dat nxaresponeevents.35.dat The next configuration file is the following and can be overtaken without any changes. Just copy and rename the file accordingly: NxEopTimerEvents.3.dat nxatimerevents.35.dat Version: Seite 10 von 13

11 System requirements Following operating systems are supported: OPC Server Direct(KNX): Microsoft Windows XP Professional Microsoft Windows Vista OPC Server UnifiedDriver: Microsoft Windows 2000 Workstation Microsoft Windows XP Professional Microsoft Windows Vista 32bit Microsoft Windows 2000 Server 32bit Microsoft Windows 2003 Server 32bit Microsoft Windows 2006 Server 32bit Hardware requirements: Minimum PC with INTEL or AMD Processor 512 MB Ram Ethernet-card 10/100 MBit Screen with 800x600 resolution The best would be PC with INTEL or AMD Processor 2048 MB Ram or more Ethernet-card 1000 MBit Screen with 1280x1024 resolution Multicore Processors are recommended. Version: Seite 11 von 13

12 Support and contact Please send all your support questions to: If you have general questions regarding the product please send your to: Version: Seite 12 von 13

13 Important Notes Version: Seite 13 von 13