Modbus Plus Applications

Modbus Plus Applications
Modbus Plus is a local area network system for industrial control applications. Networked devices can exchange messages for the control and monitoring of processes at remote locations in the industrial plant. Modicon products supporting Modbus Plus communication include programmable controllers and network adapters. The network is also supported by a variety of products from other manufacturers.
Each Modicon controller can connect to Modbus Plus directly from a port on its front panel. Additional networks can be accessed through Network Option Modules (NOMs) installed in the common backplane. The network also provides an efficient means for servicing input/output subsystems. Modicon Modbus Plus Distributed I/O (DIO) Drop Adapters
and Terminal Block I/O (TIO) modules can be placed at remote I/O sites
to allow the application to control field devices over the network link.

Extending the Network
Each network supports up to 64 addressable node devices. Up to 32 nodes can connect directly to the network cable over a length of 1500 ft (450 meters). Repeaters can extend the cable distance to its maximum of 6000 ft (1800 meters) and the node count to its maximum of 64. Fiber optic repeaters are available for longer distances.

Bridging Networks
Multiple networks can be joined through Bridge Plus devices. Messages originated on one network are routed through one or more bridges to a destination on another network.Bridgesare applicable to networks in which fully deterministic timing of I/O processes is not a requirement.In a network requiring deterministic I/O timing, messages for DIO/TIO nodes are passed on that network only, and do not pass through bridges. Modbus and custom RS232/RS485 serial devices can access Modbus Plus through Bridge Multiplexers. Each Bridge Multiplexer provides four configurable serial ports. A serial device can communicate with Modbus Plus networked devices, as well as with other devices at the serial ports.

Overview
A programming device can be connected to the tap to facilitate monitoring and
maintenance of the devices installed on the network. For more information on
programming, refer to Modbus Plus Network Planning and Installation Guide (890
USE 100 00). The tap has a connector port for that purpose, located on the front
cover. The RJ-45 programming port is for programming purposes only, and is
not intended as a permanent connection.
A programming cable is available separately from Schneider Automation by
ordering part number 990 NAA 215 10. It is not included with the tap package.

Network address
Before you connect or disconnect any device on an active network, you must be
aware of its effect on the communication between your existing devices. Any new
device’s network address must be different from all the other addresses. In addition,
the network communication may be disrupted for up to 15 seconds while the network
reconfigures upon connecting or removing the device. Contact your network
administrator to make sure that your application will not be affected.

Panel Mount
Loosen the tap’s two cover screws, and remove the protective front cover. This will
expose the two mounting holes inside the tap base. Position product, and mark two
holes with a pencil on the panel surface at the planned location for mounting the tap.
Remove product to avoid chip contamination, and then drill the holes in the panel
surface.
The tap body has two through holes of 0.197 in (5 mm) diameter suitable for a #8
screw.
Mount the tap to the panel with two #8 screws. Reinstall the tap cover.

Variable Programming from GE Fanuc

What is Variable Programming?
In Control, a variable must be created for every contact or coil reference and for every function block parameter. In variable programming, a variable is defined to communicate information about the data it represents:
· Name: The name you assign to the variable. Defines the physical location of the variable. The address can be set in one of three ways:
· The address may be set to a reference address, referencing PLC data types supported by the PLC.
· The address may be left blank, allowing the software to locate the variable when the program is compiled.
· The address may contain the name of an existing variable. For example, if you want a new variable, Pump_1, to use the same address as an existing variable, Main_Pump, – set the address field to Main_Pump.
Note: If the variable name you want to reference is an array, you must provide a subscript for the variable. For example, Warehouse_Data[1] will locate the new variable at address of the first location for Warehouse_Data.
· Type: Defines the data type for the variable. Common data types include BOOL, BYTE, WORD, INT, DWORD, DINT, REAL, UINT. All variables must have a type defined. The data type determines how the variable is used in the program: as a discrete reference, as a signed or unsigned integer, etc.
· Len: Specifies the length of the variable. The length is defined in units based on the data type. For example, a Boolean variable (Type BOOL) with length of 8 causes the program to allocate 8 bits for the variable, whereas a double-precision integer variable (Type DWORD) with a length of 8 causes the program to allocate 256 bits for the variable (eight 32-bit integer values). 4· Address: Defines the physical location of the variable. The address can be set in one of three ways:
· The address may be set to a reference address, referencing PLC data types supported by the PLC.
· The address may be left blank, allowing the software to locate the variable when the program is compiled. (This is the Auto Variable Locate feature.)
· The address may contain the name of an existing variable. For example, if you want a new variable, Pump_1, to use the same address as an existing variable, Main_Pump, – set the address field to Main_Pump.
Note: If the variable name you want to reference is an array, you must provide a subscript for the variable. For example, Warehouse_Data[1] will locate the new variable at address of the first location for Warehouse_Data.
· Scope: Specifies the level in the programming hierarchy where the variable is defined. There are three scopes for variables: Configuration, Program, or Local. Variables can be defined as you enter program logic or can be defined before you begin writing your program. Other optional fields can be completed to further express how the variable is used by the program.

Counter, Pulse Width Modulation, and Pulse Train GE Fanuc

Counter, Pulse Width Modulation, and Pulse Train Output

To configure the High Speed Counter, Pulse Width Modulation, and/or Pulse Train Output

functions, go to the Edit menu and select Module Operations, Configure Parameters, HSC/PWM/PTO. You can also choose Configure Parameters, HSC/PWM/PTO from the context-sensitive menu. A Parameter Editor window similar to the one shown below will
appear (Nano PLCs have only three counter tabs.) For details on configuring these functions, choose Module Help from the Help menu.

Dust Colector

Principle of Operation
As dust laden air passes through the fabric filter bags dust is collected on the
outside of each filter. The collected dust accumulates to form a filter cake, which
also filters the dust laden air. The clean air flows upward inside each filter into the
clean air plenum, and then out of the dust collector.Each row of filter bags is cleaned at timed intervals during operation. A pulse of
compressed air is directed through a venturi down inside each filter bag. This
induces a clean air flow which briefly inflates the filter bag, stopping the flow of
dust laden air and dislodging the surface layer of the filter cake. The dislodged dust
drops into the hopper for discharge.

USB to Serial GE fanuc

USB to Serial Adapter
It is recommended to use an USB to Serial Adapter manufactured by D-Link System, Inc., California (Model number – DSS25) to connect to a PLC through the USB port. This adapter will work only on Windows 98/ME/2000 Operating systems.
Other Significant Issues
1. Folder is corrupted when doing load with 50 subroutines from 90-30 Release 9.10/10.0 VersaMax PLCs 1.5 and earlier with Ethernet connection. Details: When using an Ethernet connection with VersaPro 1.11, if you store a program with a _MAIN and 50 subroutines to a 90-30 Release 9.10/10.0 or VersaMax PLC Release 1.5 and earlier, the store will complete correctly without error. If you do a verify, VersaPro says everything is EQUAL. If you load the program back from the PLC into a temp folder, the last subroutine (SUB50) comes back with no name. During the load there is an error message stating that blk.blk could not be found. In the folder browser VersaPro shows an -LD only block.In VersaPro Release 2.0x the store is successful, but during the verify it says SUB50 is not in the PLC, and all the
subroutines come as NOT EQUAL. On a CPU352 using a serial connection, the symptom is that communications times out during a verify or load. (CR75074) Resolution: If you add a subroutine (SUB51) with one rung of logic or delete a subroutine, store to PLC and then load, the problem goes away in both VersaPro 1.11 and 1.50. The problem is resolved in the 90-30 Release 10.5 and VersaMax Release 2. Please upgrade your firmware to these versions. 2 A Stop Fault error is displayed when a VersaPro 1.x or 2.0x folder having ACC300 Input simulator configured is stored to PLC with the Internal switch on the module in 8 pt mode. Resolution: After opening the folder in VersaPro 2.0x, you have to delete the existing ACC300 module in the hardware configuration and configure the module again. Note that the value of the reference length selected (8 or 16) should match the 8 pt or 16 pt switch setting on the rear of the module.
3. Hardware configuration of VersaPro 1.x and 2.0 folders should be reconfigured in VersaPro 2.0x if the Hardware Configuration Data View displays incorrect Rack and Slot locations Details:
1. Open the VersaPro 1.x or 2.0 folder in VersaPro 2.0x.
2. Launch HWC and open the Hardware Configuration Data View from the Tools menu. 18 Important Product Information GFK-1671P
3. Click on the I/O Config tab and check whether the Rack and Slot entries for all the Segments match their actual location of the modules in the Rack. Resolution: If the Rack and Slot entries do not match, delete and reconfigure the modules. The Rack and Slot entries will now match their actual location of the modules in the Rack.
4. Configuring communication timeouts for use with EZ program store device.
Two timeouts parameters must be configured when the EZ program store device is used. One associated with the hardware port and another global timeout. Both must be configured to the maximum value 63,000 and the global parameter must be set before the port. Select tools in the drop down menu and select Communication Setup. Select the global parameters tab then click the edit button and set the connect and request timeouts to 63000. Next, select the ports tab and choose the port you are using from
the list and push the edit button. The edit port dialog box appears, click the Advanced button and configure the connect and request timeouts to 63000.
5. Store process aborts when reference addresses exceeds limits
While storing to PLC, if the reference addresses configured for variables exceeds the limits, then the store process get aborted before the actual transfer of data to PLC begins. Though, the error dialog says that store is not completed, the Store process has not actually started.
6. Mfc42.dll error comes up while launching VersaPro
Resolution: If you get this error while opening VersaPro then performing following steps will resolve the problem.

Un-install VersaPro from control panel.

Delete VersaPro keys out of Registry.
Run regedit... then delete
HKEY_CURRENT_USER > Software > GE Fanuc Automation > VersaPro -ANDHKEY_
LOCAL_MACHINE > Software > GE Fanuc Automation > VersaPro

Install VersaPro
7. VERSAPRO on Windows 2000 Professional - Gets error message not licensed – When logged in as non-
Administrator
Resolution: If you get this error while opening VersaPro when logged in as non-administrator then performing following
steps will resolve the problem.

Right click the C:\WINNT folder, go to "Property", then the "Security" tab

Give the "Users" and "System" Account Full access, then make certain that the C:\WinNT\Versapro.exe has the same
security permissions.

Now, log in as a Non-administrator and you should now be able to run VersaPro.