Chapter. Communications. In This Chapter...

Transcription

1 RX o-more! ommunications hapter In This hapter... Overview... - Terminology... - General oncepts... - US ommunications... - Serial ommunications... - RS RS Serial Port Settings Serial Protocols... - MRX Instruction... - MWX Instruction... - K-Sequence SII... - STREMIN Instruction... - STREMOUT Instruction... - Ethernet... - Wiring... - IP ddressing and Subnets... - Port Numbers... - Ethernet Protocols... - PEERLINK Instruction... - o-more! Protocol... -0

2 Table of ontents 0 E RX WX... - Modbus TP/IP... - MRX Instruction MWX Instruction... - HOST Ethernet Protocol... - LRX... - LWX... - EtherNet/IP (Explicit Messaging)... - EtherNet/IP lient (Master)... - SMTP EMIL... - EMIL RX User Manual, st Edition

3 hapter : RX o-more! ommunications ommunications Overview The purpose of this chapter is to help the user gain an understanding of the communications capabilities of the RX MPU. The RX MPU is capable of both serial and Ethernet communications using a wide variety of protocols. Listed in the table below are the supported methods and protocols. ommunications Serial RS-/RS- Terminology o-more! Protocol (Server) Modbus RTU (lient, Server) K-Sequence (Server) SII (In & Out) Ethernet o-more! Protocol (lient, Server) Modbus TP (lient, Server) HOST EOM Protocol (lient, Server) EtherNet/IP (Explicit Messaging (lient, Server)) Ethernet Remote I/O SMTP ( ) SNTP (Time Server) TP Raw Packet UP Raw Packet uring the course of this chapter we will use terminology and phrases that are specific to a Protocol or Physical Medium the user should understand. y way of explanation we have included some common terms and definitions in this section. efinitions and explanations of specific parameters particular to each Protocol will be discussed later in this chapter. Physical Medium Wires, radios, cellular service, or satellite link. The physical method (hardware) on which the data is being transmitted or received. The physical medium contains no data information. Examples of a physical medium are: RS-, RS- and Ethernet 0/00 ase T. Protocol Protocol is the specification for the formatting of the data (bits, bytes and words) being transmitted through the physical medium. Examples of some common industry protocols are: Modbus RTU, Modbus TP, K-Sequence, irectnet and EtherNet/IP. One way to think of the Physical Medium and the Protocol is to liken them to placing a phone call. The phone call is being placed over wires, cellular service or even perhaps a satellite link. This is the physical medium. Now if the call was to hina, you would say Hello in English. If the person on the other end understands English, they will respond with Hello. If the person on the other end only understands Mandarin hinese they might respond Ni Hao. If you do not understand hinese, you will be confused as to what they are saying. This is the same for a Protocol. If your PL uses Modbus TP/IP and you try to talk to a PL that only understands EtherNet/IP, then you will not be able to communicate with it. The Protocols must match in order to communicate. 0 RX User Manual, nd Edition -

4 hapter : RX o-more! ommunications 0 lient (Master) lient is a Master device that requests data from a Server (Slave) device. Server (Slave) Server is a Slave device that responds to a request from a lient (Master) device. UP User atagram Protocol (UP) is part of the Transport Layer of the Internet Protocol Suite. The Transport Layer is Layer. UP is a simple connectionless transport mechanism for Ethernet packets. hecksums are used for data integrity, however it has no error correction or guarantee of delivery. It is considerably faster than TP/IP due to these factors. It is widely used when data is time sensitive because dropped packets may be preferable to retries and delays. TP TP or TP/IP is part of the Transport Layer of the Internet Protocol Suite. The Transport Layer is Layer. TP is defined as a reliable, ordered and an error checked delivery method. TP/IP is most often used when the data integrity is more important than raw speed. Field evice device external to the RX MPU. General oncepts The RX o-more! MPU is capable of both serial and Ethernet communications to a wide variety of field devices such as HMIs, S systems, PLs, barcode readers and scales. The following sections of this chapter will be of significant help to you when connecting and communicating with the various protocols needed for these types of devices. For advanced users it is possible to write custom protocols using the raw commands provided in the o-more! esigner software. So a thorough working knowledge of the protocol is required to accomplish this. The RX o-more! MPU has tightly coupled security features incorporated into it to protect your installation. See the manual section for each protocol and also the o-more! esigner software help file for more information on password protection and Protocol Specific Memory. Multiple user accounts are supported and logged when accessed. When programming, session based communication with unique Is is utilized to prevent unauthorized access. The o-more! Protocol can access the full memory structure and is capable of utilizing a security account to protect the data. Some HMIs and S software such as -more, -more Micro and Point of View, can utilize the o-more! Protocol for enhanced security while accessing the full memory area. Protocol Specific memory areas are blocked out of the User Memory when using Modbus RTU, Modbus TP/IP, HOST EOM and K-Sequence protocols. These memory areas are only accessible externally by using the specific protocol that corresponds to the type of memory being accessed. They are usable by the programmer to pass data externally when using third party devices. This is discussed in more detail in each Protocol section later in this chapter. - RX User Manual, nd Edition

5 hapter : RX o-more! ommunications US ommunications The POM slot US port is useful for programming the RX o-more! MPU. It is compatible with esktop Ps and Laptops utilizing US.0 or higher, communicating through US Type to US Type cable. It does not support connections to other US devices such as printers. The POM slot US port relies on drivers included with Windows, so there are no drivers to download. It truly is plug and play. 0 RX User Manual, nd Edition -

6 hapter : RX o-more! ommunications 0 Serial ommunications The RS-/ port is a removable three-pin screw terminal block located on the front of the PU. This port is software selectable to communicate as RS- or as RS-. In the RS- mode you can also enable a 0 Ohm termination resistor if needed. The RS-/ port can be connected to the o-more! esigner programming software, Modbus RTU master or slave devices, irectlogic PLs via K-Sequence protocol, as well as devices that send or receive non-sequenced SII strings or characters. RS- RS- is a single point wiring standard that can be used to connect external devices to the PL. uilt-in RS- Specifications Port Name escription Supported Protocols ata Rates RS-/RS- Non-isolated Serial port that can communicate via RS- or RS- (software selectable). Includes ES protection and builtin surge protection. o-more! Protocol (efault) Modbus RTU (lient & Server) K-Sequence (Slave) SII (In & Out) 00, 00, 00, 00, 00, 00, 00, and 00 aud efault Settings RS-, 00bps, No Parity, ata its, Stop it, Station # Port Status LE Port Type RS-/ TX RX RS- TX RS- RX RS- GN RS- Maximum Output Load (TX/RTS) RS- Minimum Output Voltage Swing ±V RS- Output Short ircuit Protection able Requirements Maximum istance Replacement onnector GN RX/- TX/+ Pinout RS GN RX TX Green LE is illuminated when active for TX and RX Removable -pin terminal strip. mm pitch RS- Transmit output RS- Receive input Logic ground kω, 000pf ±m RS- use P/N L-XXX from automationdirect.com 0 meters (00 feet); meters (0 foot) recommended maximum Part # X-RT0S - RX User Manual, nd Edition

7 hapter : RX o-more! ommunications Serial ommunications, continued The manner in which external devices are wired to the PU depend on whether the device is considered to be ata Terminal Equipment (TE) or ata ommunications Equipment (E). The PU is considered a TE device. Most Modbus or SII devices being connected to the PU will also be considered a TE device and will need to swap TX and RX (as shown below), but you should always consult the documentation of that device to verify. If a device such as a Modem, which is a E device, is placed between the PU and another Modbus or SII device it will most likely require connecting the signals straight across (TX to TX and RX to RX). gain, this can differ from manufacturer to manufacturer so always consult the documentation before wiring the devices together. RS- is a ground referenced signal and as such it is susceptible to noise and ground differentials which may make it unsuitable for use in some circumstances. The wiring for RS- is shown below. Please note that there are no connections for RTS (Ready To Send), TS (lear To Send) or for port powered devices (+V). RS-/ TX RX GN RX/- TX/+ TE GN RX TX RX MPU TE GN (0V) RX TX Field evice NOTE: Recommended distance between RS- devices is less than meters (0 feet) in industrial environments. For longer distances, please consider using RS- or Ethernet. 0 RX User Manual, nd Edition -

8 hapter : RX o-more! ommunications 0 RS- RS- is a multi-point wiring standard that can be used to connect external devices to the PL. uilt-in RS- Specifications Port Name escription Supported Protocols ata Rates RS-/RS- Non-isolated Serial port that can communicate via RS- or RS- (software selectable). Includes ES protection and builtin surge protection. o-more! Protocol (efault) Modbus RTU (lient & Server) K-Sequence (Slave) SII (In & Out) 00, 00, 00, 00, 00, 00, 00, and 00 aud efault Settings RS-, 00bps, No Parity, ata its, Stop it, Station # Port Status LE Port Type RS- Station ddresses RS- TX-/RX- RS- TX+/RX+ RS- GN RS- Input Impedance RS- Maximum Load RS- Output Short ircuit Protection RS- Electrostatic ischarge Protection RS- Electrical Fast Transient Protection RS- Minimum ifferential Output Voltage RS- Fail Safe Inputs RS- Maximum ommon Mode Voltage able Requirements Maximum istance Replacement onnector Green LE is illuminated when active for TX and RX Removable -pin terminal strip. mm pitch RS- transceiver low RS- transceiver High Logic ground kω 0 transceivers, kω each, 0Ω termination ±0m, thermal shut-down protection ±kv per IE000-- ±kv per IE V with 0Ω load Logic high input state if inputs are unconnected -. V to. V RS- use P/N L-XXX from automationdirect.com 000 meters (0 feet) Part # X-RT0S The RS- port is useful for connecting multiple devices on one network and/or connecting devices to the PU at much longer distances than RS-. The RS- standard supports distances of up to 000 meters without requiring a repeater. The distance can be increased by placing an RS- repeater on the network, if necessary. The RS- Port on the PU can support up to 0 devices, depending on the load of each device (assuming a kω load for each device). - RX User Manual, nd Edition

9 hapter : RX o-more! ommunications RS- utilizes a differential signal which makes it much more immune to noise and grounding issues than RS- and is therefore a much better choice when available for communications. This port only supports RS-, -wire connections. For -wire RS- or RS-, a converter, such as an F-ISOON must be used. The wiring for RS- is shown below. Please note that there are no connections for RTS (Ready To Send), TS (lear To Send) or for port powered devices (+V). RS-/ TX RX GN RX/- TX/+ Signal GN TX / RX TX+ / RX+ elden, or equivalent, is recommend for RS- networks. 0V RX+ TX+ 0 TX RX L0 PU Port RTS + TS + RTS TS Signal GN TX / RX TX+ / RX+ Jump RTS + and TS + Jump RTS and TS 0 RX User Manual, nd Edition -

10 hapter : RX o-more! ommunications 0 Serial Port Settings Setting up your serial port is straightforward. Follow the simple steps below.. You must know what physical medium your connecting device uses.. Establish which protocol your device supports.. Wire the physical medium using the wiring diagrams for either RS- or RS- on the previous pages.. Select supported protocol from the configuration list in the o-more! esigner software.. Select baud rate, data bits, stop bits and parity for your device.. Set the baud, data bits, stop bits and parity to match your device and o-more! esigner software.. If your device is a lient device such as an HMI, then your setup is completed.. If your device is a Server device and the RX o-more! MPU will be requesting data from it, then some ladder logic must be written. Please refer to the specific section for your chosen protocol. The o-more! esigner software help file is also a good resource for setting up communications. To set up your serial communications port in o-more! esigner, from the PL drop-down menu at the top of the screen, select System onfiguration. -0 RX User Manual, nd Edition

11 hapter : RX o-more! ommunications The System onfiguration dialog will appear. Within this dialog box you can (a) pick the Protocol and (b) Port Type, whether the port should be used for RS- or RS-. Once you have selected the desired Protocol and Port Type, click (c) the button labeled evice Settings. The Edit Serial Port Settings dialog (right) will appear. Here you will configure the serial port settings to match any additional device(s) settings. These settings must match exactly in order for the devices to communicate properly. Unit I This is the Modbus protocol identification number when the RX o-more! MPU functions as a server device. For RS- this value should always be set to. For RS-, this value will depend on how many other devices are present on the network and how they are to be numbered. aud Rate The rate at which the data is transmitted. The higher the number the faster the data will be transmitted. hoosing a lower value can help with issues when the data is not being received reliably. vailable aud Rate choices: 00, 00, 00, 00, 00, 00, 00, 00 ata its The number of bits in each character. vailable choices: or. 0 RX User Manual, nd Edition -

12 hapter : RX o-more! ommunications 0 Edit Serial Port Settings Parameters, continued Stop its The number of bits sent to denote the end of each character. vailable choices: or. Parity The method of error detection used during transmission. vailable choices: None, Odd, Even Transmit ontrol esignates when data will be transmitted. vailable choices include: Unconditional ata will be transmitted as soon as it reaches the output buffer Wait for TS ata will be transmitted when the TS line is asserted. elayed ms, delayed 0ms, delayed 0ms, delayed 00ms fter data reaches the output buffer, the RTS line will be asserted, and the transmitting of the data will be delayed by the selected number of milliseconds. RTS ontrol This setting is unused in RX o-more! MPUs and should always be set to Follows Transmitter. Timeout how many milliseconds should the instruction wait for the remote Modbus RTU Server to respond, this can be any constant from 0 to. Retries how many times should the instruction retry the communication with the remote Modbus RTU Server, this can be any constant from 0 to. Inter-packet elay the amount of time (in microseconds) the Modbus/RTU lient will place between packets as they are sent, this can be any be any constant value between 0 and. - RX User Manual, nd Edition

13 hapter : RX o-more! ommunications Serial Protocols The RX o-more! MPU has several Protocol choices for communicating to external devices. In this section we will go over the choices and describe each choice. o-more! Protocol K-Sequence (Server) The o-more! protocol is a proprietary protocol that is used SII (In & Out) exclusively by the o-more! family of controllers. This is a very feature rich and secure protocol that is used to communicate between the o-more! esigner software and o-more! controllers. It can also be used to communicate between multiple o-more! controllers or to other devices such as the -more HMI, and some S systems such as Point of View support the o-more! Protocol. Modbus RTU Modbus RTU is a protocol overseen by Modbus.org. This is an open standard, meaning that anyone can utilize it freely. Modbus RTU can be utilized as either a client or server configuration. It supports multiple server (slave) devices on RS- and a single server (slave) device on RS-. Modbus RTU Server (Slave) s a Modbus RTU Server (Slave), the RX MPU is functioning as a listening/replying device. When an external lient (Master) device requests data from the RX MPU, the MPU will reply with the appropriate data. ll Modbus data is stored in four sets of registers in the RX MPU. This memory area is blocked off specifically for Modbus communications. You must place data in these registers in order for a Modbus device to be able to access it. The Modbus data area is loosely data typed and casting or other instructions such as PULISH and SUSRIE can be utilized to convert data in this area to the correct data type required. Modbus Register Type Register Name Range Holding oil M Input oil MI Holding Register MHR Input Register MIR Please reference the Help file on casting, PULISH and SUSRIE. Serial RS-/RS- o-more! Protocol (Server) Modbus RTU (lient, Server) NOTE: Ranges can be expanded in the Memory onfiguration section of the o-more! esigner software as needed. 0 RX User Manual, nd Edition -

14 hapter : RX o-more! ommunications 0 Serial Protocols, continued The Modbus RTU Server (Slave) supports the following function codes: Modbus Function ode Read coil escription Read discrete inputs Read holding registers Read input registers Write single coil Write single registers Read exception status Write multiple coils Write multiple registers Mask write registers Modbus RTU lient (Master) s a Modbus RTU lient (Master), the RX MPU is requesting data from a Modbus RTU Server (Slave) device. In order for this to work, you need to know quite a few things about your Server device such as the function codes that it supports, the data registers that are accessible and possibly the Unit I or Slave ddress. RX MPU lient evice RX MPU used as a Modbus RTU lient (Master) Example Server evice Unit I Server evice Unit I - RX User Manual, nd Edition

15 hapter : RX o-more! ommunications Serial Protocols, continued NOTE: Only one Modbus RTU lient (Master) can be on a network. Opening the System onfiguration dialog box you will find the Serial Port onfiguration section where you can select the required protocol. Setting the serial port as (a) Modbus RTU Server (Slave), select (b) to create a the This device will handle all of the communications with the external Modbus Servers (Slaves) through the serial port on the front of the RX MPU. s a Modbus RTU lient (Master), you do not have to sequence the MRX read and MWX write instructions. You can just drop them into your program and they will work in a round robin manner. However, sequencing the instructions will give you better control and allow you to build complex communication patterns to optimally communicate with your devices. Selecting (c) Modbus RTU lient (Master) creates the licking on (d) brings up the EditModbus RTU lient Settings dialog box (below). Here you can configure Modbus Protocol Settings. Timeout Time in milliseconds that the instruction waits for the remote Modbus RTU Server to respond, this can be any constant from 0 to. Retries The number of retries of the instruction to communicate with the remote Modbus RTU Server, this can be any constant from 0 to. Inter-packet elay Time, in microseconds, that the Modbus/RTU lient will place between packets as they are sent, this can be any be any constant value between 0 and. ommunication instructions in o-more! esigner have Success and Error feedback built in so that you can either set a bit or move to a Stage if you are doing stage style programming. There are examples of using Stage (state) programming in the software Help file that show how you could use this to implement a complex communications routine. 0 RX User Manual, nd Edition -

16 hapter : RX o-more! ommunications 0 MRX Instruction The MRX instruction, found in the Instruction Tool ox under the Protocol-Standard tab (right and below), is used to read from a Modbus RTU Server (Slave). (For more detailed information please refer to the o-more! esigner Help files.) evice The device associated with the physical port that you want to communicate is the name of the device associated with the built in serial port when set as a Modbus lient (Master). Unit I The I number of the Server (Slave) device that the RX MPU will talk to. Typically this is for RS-. For RS-, this number could change depending on which device number you are talking to on the network. Function ode Select from the drop-down list one of the following Modbus function codes to use: - Read oils - Read iscrete Inputs - Read Holding Registers - Read Input Registers - Read Exception Status - RX User Manual, nd Edition

17 hapter : RX o-more! ommunications MRX Instruction, continued Modbus ddress offset value entered below: From Modbus Offset ddress The address in the Modbus Server (Slave) that you will be reading from. This address may be offset by a value of + depending on how the manufacturer followed the Modbus standard.. Number of Modbus oils/ Registers ased on the Function ode selected, this selection specifies how many consecutive elements to read. For example, if using function code, read holding registers, with an offset of, your request starts with MHR, which corresponds to Modbus address To o-more Memory ddress Specifies the beginning address of a range of bits or numeric locations in the MPU where the data that is read will be stored. This data type (bit or register) must match the type expected by the Function ode. o-more Range This is the ending register where the data will be stored at, calculated by taking the To o-more Memory address and adding the Number of Modbus oils/registers value to it. Enable esignates how this instruction will operate. Select from one of the following: Once on Leading Edge Select this option to have this instruction run to completion exactly one time. Typically, this instruction will take more than one controller scan to complete. onfigured this way the instruction is Edge Triggered. ontinuous on Power Flow at Interval Select this option to have this instruction run as long as the instruction has power flow. fter the instruction has initially run, if the instruction still has power flow, the instruction will remain enabled and will wait the specified amount of time before running again. The following options select how much time (in milliseconds) to wait between successive runs. value of zero milliseconds (0ms) means the instruction will re-run immediately. On Success When the instruction completes successfully this action will be performed. On Error When the instruction does not successfully complete, this action will be performed. Exception Response For errors where the message was received properly by the Server (Slave) device, this will contain a value to indicate why the Server rejected the message. This can aid in troubleshooting the issue. 0 RX User Manual, nd Edition -

18 hapter : RX o-more! ommunications 0 MWX Instruction The MWX instruction, found in the Instruction Tool ox under Protocol - Standard (right and below), is used to write to a Modbus RTU Server (Slave). (For specific information please refer to the o-more! esigner help files.) evice The device associated with the physical port that you want to communicate is the name of the device associated with the built in serial port when set as a Modbus lient (Master). Unit I The I number of the Server (Slave) device the RX MPU is talking to. Typically this is unless there are multiple devices on the network.. Function ode Select from the drop-down list one of the following Modbus function codes to use: - Write Single oil - Write Single Register - Write Multiple oils - Write Multiple Registers - RX User Manual, nd Edition

19 hapter : RX o-more! ommunications Modbus ddress offset value entered below: To Modbus Offset ddress The starting register to which you will be writing data. This address may be offset by a value of + depending on how the manufacturer followed the Modbus standard. Number of Modbus oils/ Registers This selection specifies how many consecutive elements to write from the Modbus Offset ddress. For example, if using function code,write a single register, with an offset of, it would write a value to Modbus address From o-more Memory ddress specifies the beginning address of a range of bits or numeric locations in the MPU to where the data will be written. This data type (bit or register) must match the type expected by the Function ode. o-more Range This is the ending register from where the data will be written, calculated by taking the From o-more! Memory address and adding the Number of Modbus oils/ Registers value to it. Enable esignates how this instruction will operate. Select from one of the following: Once on Leading Edge - Select this option to have this instruction run to completion exactly one time. Typically, this instruction will take more than one controller scan to complete. onfigured this way the instruction is Edge Triggered. ontinuous on Power Flow at Interval - Select this option to have this instruction run as long as the instruction has power flow. fter the instruction has initially run, if the instruction still has power flow, the instruction will remain enabled and will wait the specified amount of time before running again. The following options select how much time (in milliseconds) to wait between successive runs. value of 0ms means the instruction will re-run immediately. On Success When the instruction completes successfully this action will be performed. On Error When the instruction does not complete successfully this action will be performed Exception Response For errors where the message was received properly by the Server (Slave) device, this will contain a value to indicate why the Server rejected the message. This can aid in troubleshooting the error issue. 0 RX User Manual, nd Edition -

20 hapter : RX o-more! ommunications 0 K-Sequence Server The RX o-more! MPU can serve as a K-Sequence server to communicate to legacy devices that utilize the K-Sequence protocol such as irectlogic PL s, -more HMI, S systems, etc. ll K-Sequence data is stored in four sets of registers in the RX o-more! MPU. The memory area is blocked off specifically for K-Sequence communications. You must place data in these registers in order for a K-Sequence lient device to be able to access it. The K-Sequence data area is loosely data typed. Instructions such as Publish and Subscribe are used to communicate with a K-Sequence lient and then casting can be utilized to convert data in this area to the proper data type needed as well. Please see the Help file for more information on asting, PULISH and SUSRIE. K-Sequence Register Type Register Name Range Input Register LX 0 Output Register LY 0 Internal oil Register L 0 Internal Word Register LV 0 NOTE: Ranges can be expanded in the Memory onfiguration section of the o-more! esigner software as needed. -0 RX User Manual, nd Edition

21 hapter : RX o-more! ommunications SII The RX o-more! MPU can communicate with devices that utilize a non-sequenced or a custom protocol. When using SII messaging it is important to know how the external device communicates. This will require knowledge of how the external device expects to send and receive the data. Most SII devices have specification guidelines in the user manual that explain the methods needed to facilitate communications. Having this reference handy can be invaluable, saving time while programming instead of struggling with getting the communications working. Utilizing SII as a messaging medium requires that the serial port (a) be set to Program ontrol. To configure the port settings select (b) the evice Settings button. This will bring up the (c) Edit Serial Port Settings dialog. The communications settings here need to match those of the device you are communicating with. Once set, the STREMIN and STREMOUT instructions (right) can be utilized. One beneficial feature of the RX o-more! MPU is that the serial ports are buffered so that bi-directional data transfer is possible without needing the external device to pause between sending and receiving. RX User Manual, nd Edition - 0

22 hapter : RX o-more! ommunications 0 STREMIN Instruction The STREMIN instruction is found in the Instruction Tool ox under the Protocol-ustom/SII tab. evice The device name associated with the physical port to which you want to is the name of the device associated with the built in serial port for SII control. omplete when... Length is...bytes OR Specifies the number of characters received that will signal the completion of the instruction. The OR is used if elimiter(s) received OR is selected. elimiter(s) received OR Message characters that once received will signal the completion of the instruction. The OR implements: Exact sequence The specified characters must be receive in the order specified ny one delimiter(s) Receipt of any of the specified characters will signal completion. Trim elimiter(s) from Output String Removes the delimiter characters from the ata estination. Network Timeout The maximum amount of time that the instruction waits for completion. dvanced When selected a text box opens on the right. llows the backspace character to remove characters from the received string before being placed into the ata estination. ata estination String Structure The String memory location for the incoming data to be stored. Numeric ata lock Start ddress The offset into the yte uffer ata lock to store the incoming data. reate yte uffer reates a data block of bytes to store the incoming data. uffer Size in ytes The maximum number of bytes that will be placed in the yte uffer ata lock. Number of ytes Read Stores the number of bytes that were read into the yte uffer ata lock. Endian Settings Swap yte Swaps the bytes in each word of incoming data. - RX User Manual, nd Edition

23 hapter : RX o-more! ommunications STREMIN Instruction, ontinued Swap Word Swaps the words in each ouble Word of incoming data. On Success When the instruction completes successfully this action will be performed. On Error When the instruction does not complete successfully this action will be performed. Example using STREMIN instruction. barcode reader is an example of using STREMIN and SII messaging. The string represented by the barcode is transmitted to the MPU as SII text with the use of the STREMIN instruction. egin String NOTE: > 0 is the best way to trigger the STREMIN function. 0 RX User Manual, nd Edition -

24 hapter : RX o-more! ommunications 0 STREMOUT Instruction The STREMOUT instruction is found in the Instruction Tool ox under the Protocol- ustom/sii tab. evice The device associated with the physical port from which you want to is the name of the device associated with the built in serial port for SII control. ata Source String Structure The String memory location that contains the data to be transmitted. Numeric ata lock reate yte uffer... Only available when Numeric ata lock is selected. licking this button opens reate Unsigned yte ata lock box (right). Here you will name and create a data block of bytes to store the data to be transmitted. uffer Start The offset into the yte uffer ata lock for the data to be transmitted. Number of ytes to Output The number of bytes that will be transmitted. Endian Settings Swap yte Swaps the bytes in each word of incoming data. Swap Word Swaps the words in each ouble Word of incoming data. Flush INPUT device first lears the input buffer to ready it for a return response. - RX User Manual, nd Edition

25 hapter : RX o-more! ommunications Example using STREMOUT Instruction. The example below uses the STREMOUT instruction and SII messaging. sensor on the conveyor triggers a conveyor jam event in the program. The string onveyor Jam is transmitted as SII text with the use of the STREMOUT instruction. 0 RX User Manual, nd Edition -

26 hapter : RX o-more! ommunications 0 Ethernet The RJ- Ethernet port connector is located on the PU faceplate. Rated at 0/00 Mbps, it accepts standard Te cable and has built-in auto-crossover capability; no crossover cable is required. Ethernet Port Specifications Port Name Ethernet Port Type escription Transfer Rate Port Status LE Supported Protocols able Recommendation Modbus TP/IP EtherNet I/P (Explicit Messaging) HOST EOM o-more! Protocol ETHERNET RJ, Te, 0/00 SE-T, uto rossover Standard transformer isolated Ethernet port with built-in surge protection 0 Mbps (Orange LE) and 00 Mbps (Green LE) LE is solid when network LINK is established. LE flashes when port is active (T). o-more! Protocol Ethernet Remote I/O Modbus TP/IP (lient & Server) EtherNet/IP (Explicit Messaging) HOST EOM (irectlogic) SMTP ( ), SNTP (Time Server) TP/IP, UP/IP (Raw packet) E-STxxx-xx from utomationirect.com Ethernet Port Numbers 0 (configurable), TP (configurable), UP, UP, UP - RX User Manual, nd Edition

27 hapter : RX o-more! ommunications Wiring The Ethernet port on the RX o-more! PU s utilizes standard networking cables and devices. ategory e cabling is preferred. ables can be either patch (straight through) or crossover as the RX o-more! PU Ethernet port has uto MI detection. T+ T R+ R RJ OR/WHT OR GRN/WHT LU LU/WHT GRN RN/WHT RN rossover able 0ase-T/00ase-TX IP ddressing and Subnets GRN/WHT GRN OR/WHT LU LU/WHT OR RN/WHT RN T+ T R+ R RJ IP ddresses (used in conjunction with the Subnet Mask and efault Gateway address) are used for network routing. This allows for easy and logical separation of networks. It is outside of the scope of this user manual to explain how IP ddresses and Subnet masks are configured for actual usage. There are many books, documents and tools (Subnet calculators) on the Internet that provide this information. Each facility and network will incorporate their own rules and guidelines for how their networks are to be configured. We suggest that users maintain their IP addressing and Subnets according to common networking practices by using private network addressing when at all possible. Examples of private addressing IP ranges can be found in the table below. IP ddressing and Subnets IP ddress Range Typical Subnet lassful escription lass Network lass Network lass Network NOTE: Notice that the IP range of is not listed above. This range is reserved for PIP addressing and is not recommended for use with most networks. 0 RX User Manual, nd Edition -

28 hapter : RX o-more! ommunications 0 Port Numbers When doing TP and UP/IP communications, there is a Source Port number and estination Port number for every message. The lient device must be aware of the estination Port Number(s) the Server device is expecting to see, while the Server device must listen for this estination Port number. fter the Server device has received the message with the estination Port Number on which it is listening, it will formulate the return message (if the applications require this) with the Source Port Number from the message sent as its estination Port Number. It is important to understand a little about the Port numbering concept because many Ethernet devices, such as routers with firewalls, will block messages with estination Port numbers that are not configured for that device. Listed below are the default Port Numbers used in the RX o-more! platform. Some of the Port Numbers are configurable, allowing more flexibility when going through many different router applications. efault Port Numbers Ethernet Port Numbers TP or UP onfigurable Peerlink UP No o-more! Protocol (lient, Server) UP Yes Modbus TP (lient, Server) 0 TP Yes HOST EOM Protocol (lient, Server) UP No EtherNet/IP (Explicit Messaging (lient, Server)) TP Yes Ethernet Remote I/O UP No SMTP ( ) TP Yes SNTP (Time Server) TP No TP Raw Packet -- TP Yes UP Raw Packet -- UP Yes Secondary Ethernet onnection can be enabled for the built-in Ethernet port of a RX MPU. y default it has a UP Port Number of 000. It can be configured to any decimal number between 000 and, except for.purposes While all of these protocols can be enabled on the RX o-more! PU Ethernet port, it should be noted that Ethernet has a finite amount of traffic that can be handled. The amount of traffic load on the Ethernet port should be considered and polling times for lients and Servers adjusted accordingly to allow ample time for the RX o-more! PU to respond to and create requests for other devices. NOTE: are should be taken when adding a RX o-more! MPU to an existing network as some protocols can create a significant traffic load. - RX User Manual, nd Edition

29 hapter : RX o-more! ommunications Ethernet Protocols The RX o-more! MPU has several Ethernet Protocol choices for communicating to external devices. In this section we will go over the choices and describe each choice. Ethernet Protocols Peerlink o-more! Protocol (lient, Server) Modbus TP (lient, Server) HOST EOM Protocol (lient, Server) EtherNet/IP (Explicit Messaging (lient, Server)) SMTP ( ) SNTP (Time Server) TP Raw Packet UP Raw Packet PEERLINK Instruction The PEERLINK instruction allows easy data sharing across any PL that is running o-more! technology. To set this instruction up, place your data into the appropriate PL (PEERLINK) registers that you wish this PL to share to other o-more! PLs. Then check the box that corresponds to that memory area. When this instruction is enabled, it will then automatically broadcast this information to all other o-more! PL s that are listening with a PEERLINK instruction. To listen for broadcasts from other o-more! PL s, all you have to do is place the instruction in your ladder code. If this PL is not sharing data, do not check any boxes. Incoming data will automatically be placed into the same register area that the broadcasting PL has checked. Using PULISH and SUSRIE instructions can help to get data into and out of the PL memory area as the PL memory area is untyped data. See the o-more! esigner help file for more information on PEERLINK, PULISH and SUSRIE instructions. NOTE: Keep in mind that multiple o-more! PL s cannot broadcast to the same memory area. This will cause an error. 0 RX User Manual, nd Edition -

30 hapter : RX o-more! ommunications 0 o-more! Protocol The o-more! protocol is a proprietary protocol that is used exclusively by the o-more! family of controllers. This is a very feature rich and secure protocol for communication with the o-more! esigner software and between o-more! controllers. It can also be used to communicate between multiple o-more! controllers or between some brands of HMI s, such as -more, to a o-more! controller. Some S systems such as POV also support the o-more! Protocol. RX The o-more! Network Read (RX) instruction uses the o-more! proprietary protocol to read incoming data on the on-board Ethernet port from another Ethernet-equipped o-more! PU. RX uses UP (not TP) protocol to communicate with the remote o-more! PU. Each RX instruction can contain up to 0 individual read requests for a total of up to 000 bytes of data. The RX instruction can read from all of the built-in memory blocks, all of the built-in structures, and any user-created memory blocks from the remote PL. RX does NOT support reading a Heap Item from a remote o-more! PU. In contrast to irectlogi (LRX / LWX) and Modbus/TP (MRX / MWX) network communication which only has access to the protocol-specific memory blocks in the remote PUs, o-more! RX has direct access to nearly all of the memory in the remote o-more! PU - including direct access to the PU I/O memory. The RX instruction establishes a session with the remote o-more! PU. The session is established using one of the User ccounts on the remote o-more! PU. It is through that User ccount (System Security) that any access restrictions on what can be accessed can be enforced. y default it will use the efault User account (no password required). -0 RX User Manual, nd Edition

31 hapter : RX o-more! ommunications RX, continued IP ddress The IP ddress of the o-more! PU to read the data from. This can be either a Fixed (static) IP ddress or a Variable (dynamic) value. Fixed IP ddress The TP ddress assigned to the o-more! PU. IP addresses are canonically represented in dot-decimal notation, consisting of four decimal numbers, each ranging from 0 to, separated by dots. Variable IP ddress The IP ddress resides in the specified memory location. This can be any readable Word numeric location. UP Port Number The port number of the o-more! PU) to read the data from. The default value of (0x00) is typically the correct number for o-more! protocol. It is possible to use a different UP Port Number if the Enable Secondary Ethernet onnection is turned on under the PU onfiguration settings. This secondary UP Port Number defaults to 000. This UP Port Number can be any decimal value between 000 and, except for (the port number used by o-more esigner).. Remote Password The RX instruction requires that a communication session be established with the remote o-more! PU before the data read operations can be processed. epending on how the remote system is configured, this may require the user to enter the password for the User ccount to allow the session to be established. If no remote password is selected, the connection will be established using the efault User account. Enable esignates how this instruction is enabled. Select from one of the following: Once on Leading Edge Select this option to have this instruction run to completion exactly one time. Typically, this will take more than one controller scan. onfigured this way the o-more! Network Read (RX) instruction is Edge Triggered. ontinuous on Power Flow at Interval Select this option to have this instruction run as long as the instruction has power flow. fter the o-more! Network Read (RX) has initially run, if the instruction still has power flow, the instruction will remain enabled and will wait the specified amount of time before running again. The following options select how much time (in milliseconds) to wait between successive runs. onstant specifies the interval time in Hours / Minutes / Seconds / Milliseconds. Variable This can be any readable numeric location that contains a value between 0 and,,, which represents the number of milliseconds to wait before running again. value of 0 ms means this instruction will be set to run on the next scan. On Success Selects which of the following actions to perform if the Network Read operation is successful: Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Success ounter Enable this option and select a Word location to store the total number of times the RX completed successfully. This can be any Word location. On Error Selects which of the following actions to perform if the Network Read operation 0 RX User Manual, nd Edition -

32 hapter : RX o-more! ommunications 0 RX, continued is unsuccessful: Set it Enable this selection then specify writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Error ounter Enable this option and select a Word location to store the total number of times the RX failed to complete. This can be any Word location. Extended Error Information Enable this selection then enter a memory location to store any error codes returned for this instruction. This can be any writable numeric location. The list following is of the Extended error responses and their meaning: - = Protocol Error occurred. The value in LastProtoError (ST) contains the protocol error code as follows: (0x0) = Out Of Sessions: the remote PL currently has concurrent connections and cannot accept any more. (0x0) = Illegal Operation: the User ccount for the password in the instruction does not have Write ata privilege. (0x0) = Invalid Session: an error occurred with the session to the remote PL, for example the remote PL lost power during the session. (0x0) = Invalid rgument: the write requests are not formed properly (you should never see this). (0x0E) = Invalid Password: the password in the instruction does not match any User ccount in the remote PL, 0 (0x) = ad MPP Request: one or more of the write requests cannot be processed, most likely the request is for a location that is out of range on the remote PL or the memory block doesn t exist on the remote PL. The Extended Error location will contain the entry number of the write request that is causing the error. 0 = No Extended Error 0 = row number of the bad read request if the Last Protocol Error ode was 0 (0x). Insert Select Insert to open Read From Remote Into Local setup dialog box (See page following). - RX User Manual, nd Edition

33 hapter : RX o-more! ommunications RX, continued Read From Remote Into Local Read From Remote The first location in the remote PL to begin reading data: Type (a) The lock Name of the remote memory location to read. This drop-down list contains an entry for all of the built-in memory data blocks, all of the built-in structures, and an entry for a User lock that exists on the remote PL. Number of Elements (b) The number of consecutive elements to read. Into Local (c) The beginning location in the PL to store the data from the read operation. The Into Local location must be the same data type and have the same element size as the specified Read From Remote data location. For example you can read from WY (Signed Word) into N (Signed Word) but you cannot read from WY (Signed Word) into V (Unsigned Word). The remaining fields (d) are to help you maintain the size limitations. Fields validate immediately as you make changes in the editor. urrent The number of bytes in the read request currently being edited. Others The number of bytes in the read requests already in this instruction. New Size The total number of bytes of all the read requests in the instructions, including the one currently being edited. ytes Remaining The number of bytes of the 000 byte limit remaining for read requests. 0 RX User Manual, nd Edition -

34 hapter : RX o-more! ommunications 0 WX The o-more! Network Write (WX) instruction uses the o-more! proprietary protocol to write data over the on-board Ethernet port to another Ethernet-equipped o-more! PU. WX uses UP (not TP) protocol to communicate with the remote o-more! PU. Each WX instruction can contain up to 0 individual write requests for a total of up to 000 bytes of data. The WX instruction can write to all of the built-in memory blocks, all of the built-in structures, and any user-created memory blocks in the remote PL. WX does NOT support writing to a Heap Item in the remote o-more! PU. In contrast to irectlogi (LRX / LWX) and Modbus/TP (MRX / MWX) network communication which only has access to the protocol-specific memory blocks in the remote PUs, o-more! WX has direct access to nearly all of the memory in the remote o-more! PU including direct access to the PL s I/O memory. The WX instruction establishes a session with the remote o-more! PU. The session is established using one of the User ccounts on the remote o-more! PU. It is through that User ccount (System Security) that any access restrictions on what can be accessed can be enforced. y default it will use the efault User account (no password required). IP ddress The IP ddress of the o-more! PU to write the data to. This can be either a Fixed (static) IP ddress or a Variable (dynamic) value. Fixed IP ddress The TP ddress assigned to the o-more! PU. IP addresses are canonically represented in dot-decimal notation, consisting of four decimal numbers, each ranging from 0 to, separated by dots. Variable IP ddress The IP ddress resides in the specified memory location. This can be any readable Word numeric location. UP Port Number The port number of the o-more! PU) to write the data to. The default value of (0x00) is typically the correct number for o-more! protocol. It is possible to use a different UP Port Number if the Enable Secondary Ethernet onnection is turned on under the PU onfiguration settings. This secondary UP Port Number defaults - RX User Manual, nd Edition

35 hapter : RX o-more! ommunications WX, continued to 000. This UP Port Number can be any decimal value between 000 and, except for (the port number used by o-more esigner). Remote Password The WX instruction requires that a communication session be established with the remote o-more! PU before the data write operations can be processed. epending on how the remote system is configured, this may require the user to enter the password for the User ccount to allow the session to be established. If no remote password is selected, the connection will be established using the efault User account. Enable esignates how this instruction is enabled. Select from one of the following: Once on Leading Edge Select this option to have this instruction run to completion exactly one time. Typically, this will take more than one controller scan. onfigured this way the o-more Network Write (WX) instruction is Edge Triggered. ontinuous on Power Flow at Interval select this option to have this instruction run as long as the instruction has power flow. fter the o-more! Network Write (WX) has initially run, if the instruction still has power flow, the instruction will remain enabled and will wait the specified amount of time before running again. The following options select the time (in milliseconds) delay between successive runs. onstant - specifies the interval time in Hours / Minutes / Seconds / Milliseconds. Variable - This can be any readable numeric location that contains a value between 0 and,,, which represents the number of milliseconds to wait before running again. value of 0 ms means this instruction will be set to run on the next scan. On Success Selects which of the following actions to perform if the Network Write operation is successful: Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Success ounter Enable this option and select a Word location to store the total number of times the WX completed successfully. This can be any Word location. 0 RX User Manual, nd Edition -

36 hapter : RX o-more! ommunications 0 WX, continued On Error Selects which of the following actions to perform if the Network Write operation is unsuccessful: Set it Enable this selection then specify writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Error ounter Enable this option and select a Word location to store the total number of times the RX failed to complete. This can be and Word location. Extended Error Information Enable this selection then enter a memory location to store any error codes returned for this instruction. This can be any writable numeric location. The following lists the Extended error responses and their meaning: - = Protocol Error occurred. The value in LastProtoError (ST) contains the protocol error code as follows: (0x0) = Out Of Sessions: the remote PL currently has concurrent connections and cannot accept any more. (0x0) = Illegal Operation: the User ccount for the password in the instruction does not have Write ata privilege. (0x0) = Invalid Session: an error occurred with the session to the remote PL, for example the remote PL lost power during the session. (0x0) = Invalid rgument: the write requests are not formed properly (you should never see this). (0x0E) = Invalid Password: the password in the instruction does not match any User ccount in the remote PL. 0 (0x) = ad MPP Request: one or more of the write requests cannot be processed, most likely the request is for a location that is out of range on the remote PL or the memory block doesn t exist on the remote PL. The Extended Error location will contain the entry number of the write request that is causing the error. 0 = No Extended Error 0 = Row number of the bad read request if the Last Protocol Error ode was 0 (0x). Insert Select Insert to open Write From Local Into Remote dialog box. - RX User Manual, nd Edition

37 hapter : RX o-more! ommunications WX, continued Write From Local Into Remote Write from Local (a) The first location of the source data in the Local PL: Number of Elements (b) The number of consecutive elements to write. Into Remote (c) The beginning location in the remote PL to store the data from the write operation. The Into Remote location must be the same data type and have the same element size as the specified Write From Local data location. For example you can write from WY (Signed Word) into N (Signed Word) but you cannot write from WY (Signed Word) into V (Unsigned Word). I (d) The beginning offset to write the data. The remaining fields (e) are to help you maintain the size limitations. These fields validate immediately as you make changes in the editor. urrent The number of bytes in the read request currently being edited. Others The number of bytes in the read requests already in this instruction. New Size The total number of bytes of all the read requests in the instructions, including the one currently being edited. ytes Remaining The number of bytes of the 000 byte limit remaining for read requests. 0 RX User Manual, nd Edition -

38 hapter : RX o-more! ommunications 0 Modbus TP/IP Modbus TP is a protocol overseen by Modbus.org. This standard is an open standard meaning that anyone can utilize it freely. Modbus TP can be utilized as either a client or server configuration. It supports lients and Servers in a Peer to Peer fashion. Server s a Modbus TP Server (Slave), the RX o-more MPU is functioning as a listening/replying device. The external lient (Master) device will request data registers from the RX o-more! and the RX o-more! will reply with the appropriate data. ll Modbus lient data is stored in four sets of registers in the RX o-more!. This memory area is blocked off specifically for Modbus communications. You must place data in these registers in order for a Modbus lient device to be able to access it. Modbus ata Registers Register Type Register Name Range Holding oil M Input oil MI Holding Register MHR Input Register MIR The Modbus data area is loosely data typed and casting or other instructions such as PULISH and SUSRIE can be utilized to convert data in this area to the proper data type needed as well. Please see the help file for more information on casting, PULISH and SUSRIE. NOTE: Ranges can be expanded in the Memory onfiguration section of the o-more! esigner software as needed. The Modbus TP Server (Slave) supports the following function codes: Function ode escription Read oils Read iscrete Inputs Read Holding Registers Read Input Registers Write Single oils Write Single Registers Read Exception Status Write Multiple oils Write Multiple Registers Mask Write Register - RX User Manual, nd Edition

39 hapter : RX o-more! ommunications Modbus TP lient (Master) s a Modbus TP lient (Master), the RX o-more! MPU is requesting data from a Modbus TP Server (Slave) device. In order for this to work, you need to know quite a few things about your Server (Slave) device such as the function codes that it supports, the data registers that are accessible and possibly the Unit I or Slave ddress. In order to utilize the RX o-more! as a Modbus TP lient you will need to create a Modbus TP lient evice. This device will handle all of the communications with the external Modbus servers by using the Ethernet port on the front of the RX MPU. Note that there is a device created automatically. You can choose to use this device, however we strongly recommend that you make a new evice for each Modbus TP server that you will be communicating with. This will allow simultaneous communications to flow uninterrupted if one of the Modbus TP servers goes offline. RX MPU lient evice IP=...00 Ethernet Switch Modbus TP Server evice Node Modbus TP Server evice Modbus TP Server evice s a Modbus TP lient, you do not have to sequence the MRX read and MRX write instructions. If you are so inclined, you can just drop them into your program and they will work in a round robin manner. However, sequencing the instructions will give you better control and allow you to build complex communication patterns to optimally communicate with your devices. The communications instructions in o-more! esigner have Success and Error built into the instructions so that you can either set a bit or move to a Stage if you are doing state style programming. There are examples of using Stage (state) programming in the software help file to show how you could use this to implement a complex communications routine. 0 RX User Manual, nd Edition -

40 hapter : RX o-more! ommunications 0 MRX Instruction The MRX instruction is used to read from a Modbus TP Server. Following is a brief description of the MRX instruction parameters. For more detailed information please refer to the o-more! esigner help files. evice The device associated with the physical port that you want to communicate is the name of the device associated with the built in Ethernet port when set as a Modbus TP lient. We strongly recommend that you make a new evice for each Modbus TP server that you will be communicating with. This will allow simultaneous communications to flow uninterrupted if one of the Modbus TP servers goes offline. IP ddress The IP ddress of the Modbus TP Server (Slave) to read the data from. This can be either a Fixed (static) IP ddress or a Variable (dynamic) value. Fixed IP ddress The TP ddress assigned to the Modbus TP Server (Slave). IP addresses are canonically represented in dot-decimal notation, consisting of four decimal numbers, each ranging from 0 to, separated by dots. Variable IP ddress The IP ddress resides in the specified memory location. This can be any readable Word numeric location. TP Port Number This should normally be set to 0 unless the end device has had the default port number changed. Unit I The I number of the Server (Slave) device. Typically this is unless you are talking to a Modbus Serial Gateway style of device. Function ode selects which of the following Modbus function codes to use: - Read oils - Read iscrete Inputs - Read Holding Registers - Read Input Registers - Read Exception Status -0 RX User Manual, nd Edition

41 hapter : RX o-more! ommunications MRX Instruction, continued From Modbus Offset ddress The address in the Modbus Server (Slave) that you will be reading from. This address may be offset by a value of + depending on how the manufacturer followed the Modbus standard. Number of Modbus oils/ Registers ased on the Function ode selected, this selection specifies how many consecutive elements to read. To o-more Memory ddress Specifies the beginning address of a range of bits or numeric locations in the PU where the data that is read will be stored. This data type (bit or register) must match the type expected by the Function ode. o-more Range This is the ending register where the data will be stored at, calculated by taking the To o-more Memory address and adding the Number of Modbus oils/registers value to it. Enable esignates how this instruction will operate. Select from one of the following: Once on Leading Edge - Select this option to have this instruction run to completion exactly one time. Typically, this instruction will take more than one controller scan to complete. onfigured this way the instruction is Edge Triggered. ontinuous on Power Flow at Interval - Select this option to have this instruction run as long as the instruction has power flow. fter the instruction has initially run, if the instruction still has power flow, the instruction will remain enabled and will wait the specified amount of time before running again. The following options select how much time (in milliseconds) to wait between successive runs. value of 0ms means the instruction will re-run immediately. On Success When the instruction completes successfully this action will be performed. Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Error When the instruction does not complete successfully this action will be performed. Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. Exception Response For errors where the message was received properly by the Server (Slave) device, this will contain a value to indicate why the Server rejected the message. This can aid in troubleshooting the issue with the message. 0 RX User Manual, nd Edition -

42 hapter : RX o-more! ommunications 0 MWX Instruction The MWX instruction is used to write to a Modbus TP Server. For specific information please refer to the o-more! esigner help files. evice The device associated with the physical port that you want to communicate is the name of the device associated with the built in Ethernet port when set as a Modbus TP lient. We strongly recommend that you make a new evice for each Modbus TP Server (Slave) that you will be communicating with. This will allow simultaneous communications to flow uninterrupted if one of the Modbus TP servers goes offline. IP ddress The IP ddress of the Modbus TP Server (Slave) to read the data from. This can be either a Fixed (static) IP ddress or a Variable (dynamic) value. Fixed IP ddress The TP ddress assigned to the Modbus TP Server (Slave). IP addresses are canonically represented in dot-decimal notation, consisting of four decimal numbers, each ranging from 0 to, separated by dots. Variable IP ddress The IP ddress resides in the specified memory location. This can be any readable Word numeric location. - RX User Manual, nd Edition

43 hapter : RX o-more! ommunications MWX Instruction, continued TP Port Number This should normally be set to 0 unless the end device has had the default port number changed. Unit I The I number of the Modbus TP Server (Slave) device. Typically this is unless you are talking to a Modbus Serial Gateway style of device. Function ode Selects which of the following Modbus function codes to use: - Write Single oil - Write Single Register - Write Multiple oils - Write Multiple Registers To Modbus Offset ddress The starting register that you will be writing to. This address may be offset by a value of + depending on how the manufacturer followed the Modbus standard. Number of Modbus oils/ Registers This selection specifies how many consecutive elements to write from the Modbus Offset ddress. From o-more Memory ddress Specifies the beginning address of a range of bits or numeric locations in the PU where the data that will be written from. This data type (bit or register) must match the type expected by the Function ode. o-more Range This is the ending register where the data will be written from, calculated by taking the To o-more Memory address and adding the Number of Modbus oils/registers value to it. Enable esignates how this instruction will operate. Select from one of the following: Once on Leading Edge Select this option to have this instruction run to completion exactly one time. Typically, this instruction will take more than one controller scan to complete. onfigured this way the instruction is Edge Triggered. ontinuous on Power Flow at Interval Select this option to have this instruction run as long as the instruction has power flow. fter the instruction has initially run, if the instruction still has Power Flow, the instruction will remain enabled and will wait the specified amount of time before running again. The following options select how much time (milliseconds) to wait between successive runs. value of 0ms means the instruction will re-run immediately. On Success When the instruction completes successfully this action will be performed. Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Error When the instruction does not complete successfully this action will be performed. Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. Exception Response For errors where the message was received properly by the Server (Slave) device, this will contain a value to indicate why the Server rejected the message. This can aid in troubleshooting the issue with the message. 0 RX User Manual, nd Edition -

44 hapter : RX o-more! ommunications 0 HOST Ethernet Protocol Server The RX o-more! MPU can serve as a HOST Ethernet Protocol server to communicate to legacy devices that utilize the HOST Ethernet protocol such as irectlogic PL s, -more HMI, S systems, etc. ll data is stored in four sets of registers in the RX o-more!. This memory area is blocked off specifically for HOST Ethernet Protocol communications. You must place data in these registers so that a HOST Ethernet Protocol lient device will be able to access it. HOST ata Registers irectlogic Type o-more lock Name efault Octal Range iscrete Input (X) LX 0 iscrete Output (Y) LY 0 ontrol Relay () L 0 -it ata (V) LV 0 The HOST Ethernet Protocol data area is loosely data typed and casting or other instructions such as PULISH and SUSRIE can be utilized to convert data in this area to the proper data type needed as well. Please see the help file for more information on casting, PULISH and SUSRIE. NOTE: Ranges can be expanded as needed in the Memory onfiguration section of the o-more! esigner software. - RX User Manual, nd Edition

45 hapter : RX o-more! ommunications irectlogic lient (Master) The RX o-more! MPU can be a HOST Ethernet Protocol lient to communicate to legacy devices that utilize the HOST Ethernet protocol such as irectlogic PL s. LRX Network evice The device associated with the physical port that you want to communicate is the name of the device associated with the built in Ethernet port. Remote ddress specifies which of the following addressing modes to use: Slave I - Selects the Slave I (Module I) of the remote irectlogi slave. The Slave I can be any constant value in the range of to 0, or any readable numeric location that contains a value in that range. If Slave I is selected, a TP/IP broadcast is used to perform the network read operation. This means that both the o-more! controller and the remote EOM module must be in the same roadcast omain. Fixed IP ddress Specifies the IP ddress assigned to the remote slave EOM module. IP addresses are canonically represented in dot-decimal notation, consisting of four decimal numbers, each ranging from 0 to, separated by dots. Variable IP ddress The IP ddress resides in a memory location in the PL, allowing the IP ddress to be changed at runtime. This can be any readable Word numeric location. Each octet of the IP ddress is stored in one byte of the Variable ddress location. 0 RX User Manual, nd Edition -

46 hapter : RX o-more! ommunications 0 LRX Instruction, continued From L - esignates the data type and the address of the data to read from the irectlogi controller. V-Memory Locations in a irectlogi controller are unsigned -bit values. Each V-Memory location is bytes in length, so reading V-Memory requires the length be in -byte increments. The memory address value must begin on a byte boundary. Single it locations in the irectlogi controllers cannot be read individually, you must read the byte that contains the desired bit. Number of ytes esignates the number of elements of the selected type to read. X, Y,, S, T, T, GX, GY, SP it locations must be read in -byte increments Enable designates how this instruction will operate. Select from one of the following: Once on Leading Edge - select this option to have this instruction run to completion exactly one time. Typically, this instruction will take more than one controller scan to complete. onfigured this way the instruction is Edge Triggered. ontinuous on Power Flow at Interval - Select this option to have this instruction run as long as the instruction has power flow. fter the instruction has initially run, if the instruction still has power flow, the instruction will remain enabled and will wait the specified amount of time before running again. The following options select how much time (in milliseconds) to wait between successive runs. value of 0ms means the instruction will re-run immediately. On Success When the instruction completes successfully this action will be performed. Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Error When the instruction does not complete successfully this action will be performed. Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. - RX User Manual, nd Edition

47 hapter : RX o-more! ommunications LWX Network evice The device associated with the physical port that you want to communicate is the name of the device associated with the built in Ethernet port. Remote ddress - Specifies which of the following addressing modes to use: Slave I Selects the Slave I (Module I) of the remote irectlogi slave. This can be any constant value in the range of to 0, or any readable numeric location that contains a value in that range. If Slave I is selected, the a TP/IP broadcast is used to perform the network read operation, this means that both the o-more controller and the remote EOM module must be in the same roadcast omain. Fixed IP ddress Specifies the IP ddress assigned to the remote slave EOM module. IP addresses are canonically represented in dot-decimal notation, consisting of four decimal numbers, each ranging from 0 to, separated by dots. Variable IP ddress The IP ddress resides in a memory location in the PL. This allows the IP ddress to be changed at runtime. This can be any readable Word numeric location. Each octet of the IP ddress is stored in one byte of the Variable ddress location. 0 RX User Manual, nd Edition -

48 hapter : RX o-more! ommunications 0 LWX Instruction, continued From Specifies the beginning memory address in the o-more controller of the data to send to the remote slave. This value can be any readable numeric location. To L esignates the data type and the address of the data to Write to the irectlogi controller. V-Memory locations in a irectlogi controller are unsigned -bit values. Each V-Memory location is bytes in length, so reading V-Memory requires the length be in -yte increments. The memory address value must begin on a yte boundary. Single it locations in the irectlogi controllers cannot be read individually, you must read the yte that contains the desired it. Number of ytes esignates the number of elements of the selected type to read. X, Y,, S, T, T, GX, GY, SP it locations must be read in -yte increments. Enable designates how this instruction will operate. Select from one of the following: Once on Leading Edge Select this option to have this instruction run to completion exactly one time. Typically, this instruction will take more than one controller scan to complete. onfigured this way the instruction is Edge Triggered. ontinuous on Power Flow at Interval Select this option to have this instruction run as long as the instruction has power flow. fter the instruction has initially run, if the instruction still has Power Flow, the instruction will remain enabled and will wait the specified amount of time before running again. The following options select how much time (in milliseconds) to wait between successive runs. value of 0ms means the instruction will re-run immediately. On Success When the instruction completes successfully this action will be performed. Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Error When the instruction does not complete successfully this action will be performed. Set it Enable this selection then specify any writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. - RX User Manual, nd Edition

49 hapter : RX o-more! ommunications EtherNet/IP (Explicit Messaging) Server The EtherNet/IP Explicit Message Server must be enabled in the System onfiguration dialog box. Once this is enabled, you must click the EtherNet/IP Settings button to set the data blocks that will be served to outside EtherNet/IP lients. 0 RX User Manual, nd Edition -

50 hapter : RX o-more! ommunications 0 EtherNet/IP (Explicit Messaging), continued TP Port Number ( is default) esignates the TP port number on which the EtherNet/IP Explicit Message Server will accept connections. The default value of is the industry standard and will rarely need to be changed. However, this can be any constant value between 0 and. evice Name Up to characters that will be returned in requests for the Identity lass. NOTE: Runtime status of the EtherNet/IP Server is accessed through the built-in structure $IntEIPServer which has the following members:.ctivesessions (read-only) The number of concurrent open connections to EtherNet/IP clients..lasterror Last error reported to an EtherNet/IP client..errors Total number of errors returned to all EtherNet/IP clients..transactions Total number or completed client requests to EtherNet/IP clients. Select the quantity of ata locks (up to data blocks - lock to lock ) that will be made available to EtherNet/IP lients. You can specify how many data blocks will be used and then configure each of the blocks in the sections below. ccess ontrol Specify external access ability. Enable Reads (Get Single ttribute Service ode: 0x0E) llows EtherNet/IP lients to read from this data block using Get Single ttribute. Enable Writes (Set Single ttribute Service ode: 0x0) llows EtherNet/IP lients to write to this data block using Set Single ttribute. o-more Mapped Memory Specifies the first location in a data block in the o-more PL memory that will be accessed when requests with this lass/instance/ttribute are received. Element Type Select the memory block to use from the drop-down list of available numeric memory blocks. Starting Element Specify the first element in the memory block to use. Element ount The number of successive Elements in the o-more memory block to use. The maximum total size on an EtherNet/IP request is 00 bytes, so the maximum number of elements per block will depend on the size of the individual elements. Refer to the chart below: Mapped Range isplays the currently selected range of Elements. Size isplays the size of the selected Element range in ytes. Explicit Messaging ssembly Instance isplays the Path (class / instance / attribute) of the data block being configured. Element ount Element Type it 000 yte 00 Word 0 Word Real Maximum Number of This Type per ata lock -0 RX User Manual, nd Edition

51 hapter : RX o-more! ommunications EtherNet/IP (Explicit Messaging), continued lass The lass of all the data blocks is fixed at 0x0 (assembly class). Instance Each of the blocks is assigned a unique Instance as shown in this table. ttribute The ttribute of each of these data blocks is fixed at 0x0. ONFIGURTION NOTES: This area contains information pertinent to the configuration selections being made. Instance locks lock Number Instance I 0 0 (0x) 0 (0x) 0 (0x) 0 (0x) 0 (0x) 0 (0x) 0 (0x) 0 (0x) 0 RX User Manual, nd Edition -

52 hapter : RX o-more! ommunications 0 EtherNet/IP lient (Master) EIPMSG Instruction The Send EtherNet/IP Message instruction implements an Explicit Unconnected EtherNet/IP lient using the on-board Ethernet port of a o-more! PU. n explicit message client initiates request/response oriented communications with EtherNet/IP servers. Message rates and latency requirements should not be too demanding. Examples of other explicit message servers you can talk to are barcode scanners, scales, drives, or other intelligent devices. evice esignates which of the pre-configured EtherNet/IP lient devices to use when sending the message. Part of the configuration for a device is assigning a name to the device. It is that name which will show up in the evice selection drop-down menu. For more information on configuring devices go to the Help file. IP ddress The IP ddress of the EtherNet/IP Server (Slave) to send the message to. This can be either a Fixed (static) IP ddress or a Variable (dynamic) value as described below: Fixed ddress The TP/IP ddress assigned to the EtherNet/IP Server (Slave). IP addresses are canonically represented in dot-decimal notation, consisting of four decimal numbers, each ranging from 0 to, separated by dots. NOTE: Invoking the Element rowser (F) for this field will bring up the IP ddress Lookup utility that can find the IP ddress for a given name. Variable IP ddress The IP ddress resides in the specified memory location. This can be any readable Word numeric location. TP Port Number The port number of the EtherNet/IP Server (Slave) to send the message to. The default value of is typically the correct port number for EtherNet/IP protocol. This can be any constant value between 0 and, or any readable numeric location containing a value in that range. - RX User Manual, nd Edition

53 hapter : RX o-more! ommunications EtherNet/IP lient (Master), continued Path Specifies the parameters for the request. The specific values needed for the fields will be provided by the manufacturer of the EtherNet/IP server that you are talking to. lass The lass I value (defined by the EtherNet/IP Server). This can be any positive integer value or any readable numeric location. Instance The Instance I value (defined by the EtherNet/IP Server). This can be any positive integer value or any readable numeric location. Use ttribute Enable this option to specify the ttribute value (defined by the EtherNet/IP Server). This can be any positive integer value or any readable numeric location. Service - Specifies the operation to perform on the set of objects. hoose from the following list of predefined Services, or select Generic and enter the Service number. Specific Service Select one of the predefined Service Requests below: Get Single ttribute (, 0x0E) - request a single attribute Set Single ttribute (, 0x0) - write a single attribute Get ll ttributes (, 0x0) - request all of the attributes Set ll ttributes (, 0x0) - write to all of the attributes Generic Service Specify a Service that is NOT one of the predefined Service Requests. This can be any constant integer value or readable memory location. reate ata lock If an appropriate data block does not already exist, or if you want to create an additional data block for use in this instruction, then click this button to open a dialog where you can create a new data block of the required type. Use Request Service ata uffer This selection will be automatically enabled when any Set ttribute service is selected and automatically disabled when any Get ttribute service is selected. This buffer can be enabled any time the Generic Service is selected. Req is String Structure Select this option if the data for the Set ttribute service or any Generic service is contained in a String, then enter the String element to use. This can be any of the systemdefined Short Strings, or system-defined Long Strings, or any of the user-defined Strings. The maximum length of the String to send is 00 bytes. Req is Numeric ata lock Select this option if the data for the Set ttribute service or any Generic service is contained in a numeric memory block. The maximum size of the data block that can be sent in a single service request 00 bytes (0 Words, Words, Reals). Req Start Specify the first element of the memory block that is the data for the Set ttribute or Generic service. Req Number of ytes - The number of consecutive YTEs of data for the Set ttribute or Generic service (Words = ytes, Word = ytes, Real = ytes). 0 RX User Manual, nd Edition -

54 hapter : RX o-more! ommunications 0 EtherNet/IP lient (Master), continued Use Response Service ata uffer This selection will be automatically enabled when any Get ttribute service or any Generic service is selected and automatically disabled when any Set ttribute service is selected. This buffer can be enabled any time the Generic Service is selected. Res is String Structure Select this option to store the data from the Get ttribute service or any Generic service in a String, then enter the String element to use. This can be any of the systemdefined Short Strings, or system-defined Long Strings, or any of the user-defined Strings. The maximum length of the String that could potentially be received is 00 bytes, so make sure the String can handle the maximum response for the desired service. Res is Numeric ata lock Select this option to store the data from the Get service or any Generic service in a numeric memory block. The maximum size of the data block that can be read in a single service request 00 bytes (0 Words, Words, Reals). Res Start Specify the first element in the numeric data block to store the data that was returned by the Get ttribute or Generic service. This can be any writable numeric location. Res Length in YTEs Specify a memory location to store the actual number of ytes of data that was returned by the Get ttribute or Generic service. This can be any writable numeric location. Res Max Length in YTEs Specify the maximum number of YTEs of the returned data to retain to store in the data block. This can be any positive integer constant between and 00 or any readable numeric location. NOTE: The byte length value should be a multiple of the number of YTEs in a single element in the numeric memory block. For example, if the memory block consists of Words or Reals, this value should be a multiple of, as there are YTEs per Word or Real. General Status ode enable this option to store the value returned from the EtherNet/IP Server in response to processing the Service Request; enter the numeric location to store the value. This can be any writable numeric location. This value could indicate success or be an error code. onsult the documentation for the EtherNet/IP Server for information on how to interpret General Status ode values. Extended Status Enable this option to store any extended status value returned from the EtherNet/ IP Server in response to processing the Service Request. Ext is String Structure Select this option to store the extended status information in a String, then enter the destination String element. This can be any of the system-defined Short Strings, or systemdefined Long Strings, or any of the user-defined Strings. Ext is Numeric ata lock Select this option to store the Extended Status data in a numeric data block. Ext Start Specify the first element in the numeric data block to store the Extended Status data. This can be any writable numeric location. Ext Length in YTEs Specify a memory location to store the actual number of ytes of Extended Status data. This can be any writable numeric location. Ext Max Length in YTEs Specify the maximum number of YTEs of Extended Status data to store in the data block. This can be any positive integer constant between and 00, or any readable numeric location. - RX User Manual, nd Edition

55 hapter : RX o-more! ommunications EtherNet/IP lient (Master), continued NOTE: The byte length value should be a multiple of the number of YTEs in a single element in the numeric memory block. For example, if the memory block consists of Words or Reals, this value should be a multiple of, as there are YTEs per Word or Real. Enable esignates how this instruction will operate. Select from one of the following: Once on Leading Edge - Select this option to have this instruction run to completion exactly one time. Typically, this instruction will take more than one controller scan to complete. onfigured this way the instruction is Edge Triggered. ontinuous on Power Flow at Interval - Select this option to have this instruction run as long as the instruction has power flow. fter the instruction has initially run, if the instruction still has power flow, the instruction will remain enabled and will wait the specified amount of time before running again. The following options select how much time (in milliseconds) to wait between successive runs. value of zero milliseconds (0ms) means the instruction will re-run immediately. On Success When the instruction completes successfully this action will be performed. Set it Enable this selection then specify writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Error ounter Enable this option and select a Word location to store the total number of times the RX failed to complete. This can be any Word location. On Error When the instruction does not complete successfully this action will be performed. Set it Enable this selection then specify writable bit location. JMP to Stage Enable this selection then specify any Stage number from S0 to S in the current Program code-block. On Error ounter Enable this option and select a Word location to store the total number of times the RX failed to complete. This can be any Word location. 0 RX User Manual, nd Edition -

56 hapter : RX o-more! ommunications 0 EtherNet/IP lient (Master), continued reate ata lock If an appropriate data block does not already exist, or if you want to create an additional data block for use in this instruction, then click this button to open a dialog where you can create a new data block of the required type. ata lock Name ( to letters) lock names must be unique, and consist of to characters (-Z, a-z; no numbers, no spaces). Number of Elements Specifies the number of bytes in the data block. The data blocks must be created on a Word (-byte) boundary. The maximum number of ytes that can be received from a single packet is 0. ata lock Range isplays the first and last element of the block that will be created based on the current entries for ata lock Name and Number of Elements. ata Type The data block will consist of Unsigned ytes. Make ata lock Retentive (retain values after power loss) data block marked as retentive will hold its state through a power cycle or a Program-to-Run mode transition. The status of memory NOT marked as retentive will be cleared at power up and during a Program-to-Run mode transition. - RX User Manual, nd Edition

57 hapter : RX o-more! ommunications SMTP EMIL The Edit SMTP lient Settings dialog is used to configure an SMTP connection from the o-more! controller to an SMTP server in order for the controller to send . The information that is required to configure an SMTP connection is always going to be specific to the installation. It is up to the programmer to locate the required information. 0 RX User Manual, nd Edition -

58 hapter : RX o-more! ommunications 0 SMTP EMIL, continued evice Name The name given to the SMTP lient. This is the name that will be referenced in the Send (EMIL) instructions. evice Names can consists of to alphanumeric characters. evice names must follow Nickname rules. SMTP Server IP ddress The IP address of the SMTP server that will process the sent from the controller. If the IP ddress of your SMTP Server is not static, you can use the NSLOOKUP and EVWRITE instructions to determine it at runtime before executing an EMIL instruction. See the example in the EMIL Help Topic M00. If this is the case, just fill in a dummy IP ddress in the SMTP onfiguration. licking the NS Loopkup button will open the IP ddress Lookup utility so that o-more! esigner can search for the IP ddress assigned to a given SMTP Server name. This requires a functional connection to a NS Server. NOTE: The IP ddress of the SMTP Server can be resolved at runtime by using the Name to IP ddress (NSLOOKUP) instruction to find the IP ddress associated with a Server s name, then use the Write evice Register (EVWRITE) instruction to set the SMTP lient evice to use the IP ddress that was found. SMTP Server Port The default value of is the standard IP port number that is used by SMTP servers. The SMTP Server Port number can be examined at runtime with the Read evice Register (EVRE) instruction, and changed at runtime through the Write evice Register (EVWRITE) instruction. Timeout This is the amount of time (in seconds) the SMTP lient will attempt to connect to the specified SMTP server before reporting an error. The default value of 0 seconds should be sufficient in most instances. e aware that it is quite normal for communications with SMTP servers to take several seconds of time; setting this value too low will only cause needless problems. From ddress Specifies the address that all s using this SMTP lient will use in the From field. addresses must be in the form of X@Y.Z. SMTP servers typically require that the From address be configured as a recipient address on that SMTP server before they will accept s from that address. uthentication If the SMTP server requires authentication before it will accept an from the controller, select one of the following three methods: isabled If the SMTP server does not require authentication UTH LOGIN uthenticate by logging into the SMTP Server with the Username and Password specified below UTH PLIN uthenticate by logging into the SMTP Server with the Username and Password specified below POP before SMTP n authentication that attempts to get before attempting to send an , the premise being that if an client can log in and read the lient must be legitimate Pop Port The default port number of 0 is the standard IP port number for POP requests and should not need to be change. The Pop Port number can be examined at runtime with the Read evice Register (EVRE) instruction, and changed at runtime through the Write evice Register (EVWRITE) instruction. - RX User Manual, nd Edition

59 hapter : RX o-more! ommunications SMTP EMIL, continued ccount Information The three authentication methods above require a UserI and Password. For UTH LOGIN and UTH PLIN, the account information is for the SMTP account, for POP before SMTP method, the account information is for the POP account. Username - to characters Password - to characters 0 RX User Manual, nd Edition -

60 hapter : RX o-more! ommunications 0 EMIL The Send (EMIL) instruction is used to send an message. This instruction is only valid for o-more! controllers that have an on-board Ethernet port. The message portion of the can be any combination of text and data elements from the controller. n can also send an attachment which can be any file on any of the built-in file systems. SMTP evice esignates the SMTP lient device to use to send the . n SMTP lient device must be configured before the Send instruction can be added to a program. To One or more primary audience addresses separated by semicolons. This can be a string literal (text in double quotes), or any String element. c (optional) One or more ourtesy opy (or arbon opy) addresses separated by semicolons. This can be a string literal (text in double quotes), or any String element. cc (optional) One or more lind arbon opy addresses separated by semicolons. This can be a string literal (text in double quotes), or any String element. Subject The Total number of characters in Subject line is limited to 0 characters. This can be a string literal (text in double quotes), or any readable String element. utomatically insert space after each term Will insert a space between the terms when the instruction is processed. This is most useful when the Message Field contains only a list of elements that would otherwise require a manually entered space character to separate the items. -0 RX User Manual, nd Edition