P-Bus Gateway Firmware PBGW2.128 Version 1.40 Easy configuration with web interface (HTML) P-busses configurable separately in master or slave mode Status display of each P-bus Fixed IP address or dynamic with DHCP (configurable) Modbus RTU data communication over RS-232, RS-485 and TCP / IP Status display of all I/O-modules on P-Bus Open communication to third party systems
General The gateway is being configured by means of a web interface (HTML). Use a standard web browser ie. MSIE5.5 or higher. If you have more than one PC, you must use an external hub. Connect the Ethernet port on the gateway (X6) to a port on the hub using a straight through Ethernet cable. If you only have one PC, you can connect the gateway to the PC directly without a hub. For a single PC, connect the Ethernet port on the gateway (X6) to the Network Adapter on the PC using a crossover cable (red tag). Make sure that the PC is configured in the same subnet as the gateway is. Go to the Network Connections of your PC from the Control Panel. Make sure the LAN connection to which the gateway is connected is disabled. If not, right click on the LAN connection and choose disable. Now, right click on the LAN connection and choose properties. In the next window select Internet Protocol (TCP/IP) and click Properties. 2/17
Select Use the following IP address: and use the following settings: IP address 192.168.1.1 (last digit could range from 1-253) Subnet mask 255.255.255.0 Now click OK to confirm these settings. Click OK again in the next window. Establish a connection by double clicking the LAN connection in the Network Connections Window. Factory defaults The standard IP settings (factory default) of the gateway are: IP address 192.168.1.254 Subnet mask 255.255.255.0 When the gateway isn t reachable (anymore) over TCP / IP or the configuration isn t desirable somehow, it can be set back to factory defaults. Follow the next procedure in order to set the gateway to factory defaults: 1. Interrupt the gateway s power supply by unplugging the screw terminal X1 2. Press the RESET-button and keep it pressed 3. Power up the gateway by plugging in the screw terminal X1 4. Keep pressing the RESET-button until the STATUS-led is off 5. Release the RESET-button NOTE: When the gateway is set back to factory defaults, all settings are lost. 3/17
Device configuration System Overview Open the web browser and type the IP address of the gateway in the URL field of the browser. The following page will show (System Overview): In the upper right corner of the page you can find the current Firmware version in the gateway (see also Firmware upgrade ). On the left is the navigation panel. You can navigate to a page by clicking on the corresponding menu item in the panel. The page is being reloaded and the active item is printed bold in the menu. As you can see in the example above we are currently in the System Overview. This page displays the present status and configuration of the gateway. To make changes in the configuration navigate to the corresponding subject in the navigation panel. 4/17
Device Setup TCP / IP Settings NOTE: In this page you can make changes in the TCP / IP communication settings. The Physical Address (or MAC address) is unique for each device and can be used by the DHCP server to identify the gateway and to assign it a reserved IP address. When the gateway is configured in a network containing a DHCP server, and you want the DHCP server to configure the gateway s IP address and Subnet mask, check the checkbox next to DHCP Enabled. If you want to manually specify the IP address and Subnet mask, uncheck the checkbox next to DHCP Enabled. The fields IP Address en Subnet mask will become active and the addresses can be filled in here. To apply the settings click Apply Settings. The settings will be saved to the nonvolatile memory and the gateway will restart. After restart you ll have to reconnect to the gateway by specifying the new IP address in the URL field at the top of the browser. If you want to discard the settings click Discard Settings. The same result can be achieved by reloading the page.!! When applying the settings ( Apply Settings ) all communications could be interrupted temporarily. 5/17
Device Setup Port Settings In this page you can make changes in the RS-232 and RS-485 configuration. This configuration is being applied to the Modbus RTU protocol when enabled in the Modbus RTU Server Protocol Settings. Match these settings to the device the gateway communicates with (Modbus Client). The possible settings are: Baudrate: 110, 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 Databits: 8 Parity: None, Even, Odd Stopbits: 1, 2 Handshaking: None, RTS/CTS The factory defaults for RS-232 are: 9600, 8, N, 1, No Handshaking The factory defaults for RS-485 are: 9600, 8, N, 1. If RTS/CTS handshaking is used with RS-232, pin 7 & 8 of the DSUB-9 connector (X5) have to be connected also. NOTE:!! When applying the settings ( Apply Settings ) all communications could be interrupted temporarily. 6/17
P-Bus Settings (1) In this page you can make changes to the P-bus configuration. At Configured Operating Mode you can choose the operating mode for the corresponding P-bus. The possible operating modes are: Slave and Master. At Current Operating Mode the current operating mode of the corresponding P- bus is being displayed. Choose Slave mode if the corresponding P-bus has already a master controller (Siemens PRU/PRV or PX) attached to it. In this mode the gateway depends on the master controller which also provides the reference voltage on the PU-line. The gateway will act as a slave on the P-bus. The green led MASTER above the P-bus connector (X2 or X3) is off in this mode. Choose Master mode if you want the corresponding P-bus of the gateway to act as a master controller on the P-bus. The reference voltage on the PU-line will then be provided by the gateway. The green led MASTER above the P-bus connector (X2 or X3) is on in this mode. To protect external equipment and the gateway itself, the reference voltage is switched on only when the gateway doesn t detect any reference voltage on the PU-line. If the gateway does detect a reference voltage on the PU-line, it will configure the particular P-bus automatically in slave mode. This could lead to a P- bus configured in master mode displaying the Current Operating Mode as SLAVE. In this case, check if there is a master controller already present on the P-bus. At I/O-Modules the number of slaves (I/O-modules) currently detected on the P- bus is being displayed. When Overload displays YES, this means that there are too many load units detected on the P-bus. In this case, reduce the number of slaves on the P-bus. 7/17
P-Bus Settings (2) NOTE: Each P-bus can handle a maximum of 64 load units. For the gateway in total (2x64) the maximum is 128 load units. The buffer in the gateway has space for a maximum of 127 slaves per P-bus in the range of address 1..127.!! When applying the settings ( Apply Settings ) all communications could be interrupted temporarily. 8/17
P-Bus Modulelist (1). This page displays the status of all I/O-modules on the P-Bus. Each module-type is being displayed with the module-address number in front. By mouse-click on the + sign the module expands and all I/O-channels become visible: 9/17
P-Bus Modulelist (2) To expand all modules at once simply click expand all : The value / status of each I/O-channel is displayed depending on the module type as measurement, command, input or control-output followed by the standard unit. The LG Ni-1000 modules PTM1.*R1K are displayed as -50.. 150 C n.c. = not connected M = manual control short-circuit = input is short-circuited By clicking on collapse all all I/O-modules are collapsed to their initial state. By default, the I/O-modules being displayed are those which are actually on the P- Bus ( hide empty modules ). To show all I/O-addresses (also the unused addresses) click show empty modules. In order to switch the display to P-Bus 2 navigate by clicking on P-Bus 2 in the navigation bar: 10/17
P-Bus Virtual Modules (1) Open communication through the P-Bus gateway is possible by making use of virtual modules. These virtual modules are fictitious modules which are read by the system-controller if the corresponding P-Bus is configured as SLAVE. The modules are read as if they were really present at the P-Bus. The data fed to these virtual modules is coming from the modbus-registers in the gateway. In this manner an open communication path is created between the system-controller and an open DDC system by means of modbus-communication. 11/17
P-Bus Virtual Modules (2) In this picture an example is shown in which a communication-link is created with a PRU / PRV through the P-Bus gateway. The PRU / PRV communicates with the I/O-modules via P-Bus. The P-Bus of the gateway is configured as SLAVE and is also visible by the PRU / PRV. In the virtual module-list fictive I/O-modules can be configured which are provided with information by the universal DDC controller. Click add to create a new virtual module: 12/17
P-Bus Virtual Modules (3) In the left column the fictive module address can be configured. By clicking on the module-type in the right column the type can be configured. A listbox is being shown in which you can choose from all available PTM-.. moduletypes. Choose the desired type. The delete a module move the indicator in the most left column to the module you wish to delete by clicking in the empty square. Click delete. To delete all modules click clear all. If all desired virtual modules are entered into the table you need to store the table into the gateway s non-volatile memory by clicking apply. If you wish to discard the changes you made in the table click discard. 13/17
Modbus RTU Server Protocol Settings In this page you can make changes to the Modbus communication configuration. A Modbus RTU connection can be established over each of the 3 electrical interfaces: RS-232, RS-485 and Ethernet (TCP/IP). It s recommended to use one connection at the same time. Check the checkbox next to Enabled of the electrical interface you want to use and uncheck the other two. At RS-232 and RS-485 you can specify a Slave-address. This is the modbus slave address the gateway will respond to at modbus requests form a modbus client. Also the modbus inter-frame timeout can be specified. If the checkbox before Auto is checked, the gateway will calculate the inter-frame timeout automatically. In most cases this auto timeout is sufficient for reliable communication. Sometimes it s desirable to manually specify the inter-frame timeout to be able to adjust the value to the connected client. For example if the client drops out in the middle of a modbus frame for a long period of time, the frames don t always survive intact when they ve reached the gateway. This could lead to frame-errors and delays in the communication. In this case uncheck the checkbox before Auto and specify the inter-frame timeout in the field next to it (in tenths of milliseconds). Under Modbus on TCP/IP you can specify the TCP Port number at which the gateway listens for modbus requests. Match this to the Port number at which the modbus client sends out its requests. The default TCP Port for modbus communications and also the gateway s factory default is 502. NOTE:!! When applying the settings ( Apply Settings ) all communications could be interrupted temporarily. 14/17
ModBus Registers Each PTM I/O-module contains 9 registers (16-bit). There are 4 read registers, 4 write registers and 1 register to identify the moduletype. The interpretation of the read and write registers depends on the moduletype. For example: a digital output module (PTM1.2Q250) with 2 relay outputs just needs 2 bits (0 or 1) of one register to indicate if a relay is on or off. An analog input module (PTM1.4R1K) with 4 inputs uses one register for each A/D converter (input). A detailed description of the I/O module s register contents can be found in the documents: PCS013x to PCS018x. The P-bus Gateway is a transparent gateway. This means: all of the I/O-module s registers are identically matched on modbus level. With use of holding registers or input registers the register contents of every I/O-module can directly be read or written to. modbus functions The following modbus functions are supported by the gateway: Function Code Modbus Function Dec. Hex. Description 3 0x03 READ HOLDING REGISTERS 4 0x04 READ INPUT REGISTERS 6 0x06 WRITE SINGLE REGISTER 16 0x10 WRITE MULTIPLE REGISTERS There s no distinction being made between input registers and holding registers. So the modbus functions 3 and 4 will always have the same result. register mapping The general mapping of the modbus registers is as follows: Dec. Hex. Description 0 0x0000 Diagnostic functions of the gateway 255 0x00FF 256 511 512 2559 2560 2815 0x0100 0x01FF 0x0200 0x09FF 0x0A00 0x0AFF Moduletype Registers PBUS 1 Register 256 matches the moduletype at moduleaddress 0. Register 257 matches the moduletype at moduleaddress 1. etc, etc.. Read/Write Registers PBUS 1 Per I/O-module: 4 read registers 4 write registers Register 512-515 matches read register 0-3 of module 0. Register 516-519 matches write register 0-3 of module 0. Register 520-523 matches read register 0-3 of module 1. Register 524-527 matches write register 0-3 of module 1. etc, etc.. Moduletype Registers PBUS 2 Mapping in the same manner as for PBUS 1 2816 4863 0x0B00 0x12FF Read/Write Registers PBUS 2 Mapping in the same manner as for PBUS 1 Only the I/O module write registers are writable (modbus functions 6 and 16). All other registers are read-only. 15/17
Calculating example If you want to calculate the modbus register offset Y to control an I/O Module at address A then: for P-Bus 1: Y = 512 + A * 8 and for P-Bus 2: Y = 2816 + A * 8 in which the registers: Y + 0 to Y + 3 are the read registers 0 3 of the I/O Module at address A and Y + 4 to Y + 7 are the write registers 0 3 of the I/O Module at address A. Now, suppose you ll want to control an I/O Module at address 7 on P-Bus 2 then: Y = 2816 + 7 * 8 = 2872. The read registers 0 3 of the I/O Module at address 7 are: 2872 2875 and The write registers 0 3 of the I/O Module at address 7 are: 2876 2879. An easy tool for calculating the modbus-addresses is available on our website: www.persy.nl and can be found under document number: PCS018x diagnostic functions Detailed mapping of the diagnostic functions: Dec. Hex. Description 0 0x00 Device Status 1 7 0x01 0x07 Not used 8 0x08 PBUS 1 Current Operating Mode 9 0x09 PBUS 1 Error Status 10 0x0A PBUS 1 Number of I/O Modules present 11 0x0B PBUS 1 Number of load units present 12 15 0x0C 0x0F Not used 16 0x10 PBUS 2 Current Operating Mode 17 0x11 PBUS 2 Error Status 18 0x12 PBUS 2 Number of I/O Modules present 19 0x13 PBUS 2 Number of load units present 20 255 0x14 0xFF Not used Device Status: 0 = normal operations 1 = firmware upgrade mode 2 = reset 3 = hardware failure, gateway need to be reset or exchanged PBUS Current Operating Mode: 0 = not used 1 = slave 2 = master PBUS Error Status: Bit Description 0 Set = general failure, gateway need to be reset or exchanged 1 Set = overload 2..15 not used 16/17
Firmware upgrade The firmware in the gateway can be upgraded. New firmware releases will be offered to you on our website or can be ordered by mail and keep your product upto-date. The upgrade is done by use of a SD card. If you have downloaded the firmware from our website you can copy it to a SD card with a PC equipped with a cardreader/writer. Check if the SD card is formatted with the FAT16 (or FAT) file system. Only SD cards with a capacity between 32MB and 2GB are supported. Copy the firmware file PBGW2128.BIN into the root folder of the SD card. If the firmware file is placed in a sub folder the gateway will not respond to it. To upgrade the gateway follow the next procedure: 1. Place the SD card with the firmware in the SD slot of the gateway. 2. Press the RESET-button until the STATUS-led starts blinking. 3. The gateway is now ready for the upgrade. Release the RESET-button. 4. Firmware upgrade process has started. Wait until the STATUS-led is off. The upgrade process takes approximately 2 minutes. During the process the STATUS-led will blink rapidly. On completion of the upgrade the gateway will restart and the STATUS-led will go off. If the STATUS-led doesn t start blinking in step 2 this means that: - the gateway couldn t find the firmware file PBGW2128.BIN in the root folder of the SD card Copy the firmware file into the root folder - the firmware file on the SD card is corrupted Download the file again from our website and copy it onto the SD card - the gateway can t handle the file system on the SD card Format the SD card with the FAT16 file system and copy the firmware file onto it - the SD card isn t properly placed in the SD slot Take the SD card out and place it back again in the SD slot of the gateway Warning!!! Never switch off the gateway or interrupt its power supply during the firmware upgrade process (rapidly blinking STATUS-led)!! Switching off the gateway or interrupting its power supply during the upgrade process can permanently damage the gateway. NOTE: During the upgrade process the normal functions of the gateway are interrupted. Data communication over RS-232, RS-485, Ethernet and P-bus is not possible. 2009 www.persy.nl Subject to changes 17/17