Download presentation
Presentation is loading. Please wait.
1
Motorola ACE3600 Solutions
STS Programming Suite 11.70 Programming Overview (with a little IRRInet)
2
ACE 3600 STS 11.70 Features System oriented
Handles multiple sites in a system design approach. User can save / view all the sites in the system / project. Integrates all the functionality in one tool Except Protocol Analyzer, Encryption Tool. The Application Programmer can run also as a standalone tool. Manages all files for a given site Manages the various STS files per project, Instead of across entire toolbox. Automatic path suggestion for STS communication Current version supports ACE3600/IRRInet-ACE, IRRInet-M, MOSCAD (download-only), MOSCAD-L (download-only) It has the infrastructure to support many product types in the same project. .NET oriented System oriented – every project is a system, The system's network is graphiaclly viewed, All application for this system aremanaged together .... More Features – Less Actions
3
STS Application Programs
ToolBox 9.5XX Application System oriented – every project is a system, The system's network is graphiaclly viewed, All application for this system aremanaged together ....
4
Table of Contents STS features The STS framework
Adding a new site into the project Site View System View Working with Inventory/Gallery PC Communication setup Network tables Links Configuration - Configuring MDLC links in the project IP Communication / Conversion Table
5
Table of Contents - Continued
Phonebook & Dialup Download to RTU Logger Tools -Error Logger, Software Diagnostics Time TAG Logger Date & Time Hardware Test Ladder Applications Upload New Site (from RTU) Upload Files from RTU (to existing site) New STS / IRRInet-ACE/M Support Highlights
6
STS Application Programs Description (1)
Application Programmer function: • Programming a user application (database and process) to be executed by the system software in the RTU’s. Before the ACE3600 STS can communicate with the various sites in the system, certain parameters to be used by the MDLC communication driver must be set. Any change to a parameter in Communication Setup will cause all MDLC communications which are in progress to be aborted automatically. The MDLC driver will be restarted the next a communication request is sent. No need to stop all applications, stop driver.
7
STS Application Programs Description (2)
The Protocol Analyzer is a diagnostic tool which enables the user to monitor and analyze MDLC communication over various channels in two different ways: • By means of an additional RTU defined as an adaptor that collects data for the Protocol Analyzer. This adaptor monitors one port and transfers the received data through a second port to the Protocol Analyzer program. • By monitoring the communication between two RTUs through RS-link, between a computer and RTU through a computer Port, or between an RTU and an external modem. Stop MDLC Communication Driver: For changing communication setup, For changing the MDLC password Releasing the port for other Windows application.
8
STS Application Programs Description (3)
The STS Application Manager enables the user to create, edit, delete application programs and assign applications to sites. Will open the Readme files for ACE3600 (Firmware & STS) Will open the ACE3600 STS Manuals
9
The STS framework Diagram area System explorer The STS allows you to define and configure the system, the network and individual sites, and perform tests and diagnostics on RTUs. Inventory Gallery The framework is built from: Inventory – item supplied with installation Gallery – built by user Explorer – tree view of project Diagram view area – Graphical view of the project components Table view area - Table view of the project components
10
The STS framework (System View) (1)
System level operations Creating a site/area Managing applications and network tables Downloading to all sites uploading from an RTU Site level operations View/edit the site configuration Download and upload to/from a site Retrieve/set the site’s date and time Retrieve the site’s errors and diagnostics Test the hardware Create an application, etc.
11
The STS framework (System View) (2)
Creating a site alternatives Selecting an RTU type from the list of RTUs in the Elements tree of the Inventory tab Uploading a site definition from a local or remote RTU Selecting defined RTU from Gallery Copy & Paste existing RTU Managing a given site Click on the site in the project tree of the system or in the workspace (table or diagram view.) Configuring the site Defining which ports present in the unit and assigning their links Defining what I/O modules are used and where they will be placed in the module rack. Setting advanced parameters Defining an application program for the RTU Customizing the network configuration for the site based on the generic network configuration produced by the STS Assigning additional (Add-Ons) file for download
12
Site view (2) A default site configuration is provided for each new site. This site configuration is customized during the site definition. Customization of a site configuration can also be done after the initial definition of the site. Customizing the site can include one or more of the following: Port configuration I/O configuration Advanced parameter configuration Optional Add-On files Site view is where we can view and set the following site properties - 1. Site ID and name 2. Site description 3. Ports configuration 4. IO modules 5. Advance configuration 6. Add-on files downloaded to the RTU
13
Site view – Set Communication Ports (1)
When dragging new RTU from inventory, the new site that is created does not have communication ports configured. The user has to configure each one of the ports. PI1 – An add-on port, can have one of the following piggybacks: a. Ethernet 10\100 BT b. RS232 c. RS485 d. Radio SI1 – RS232 \ RS485 port SI2 – RS 232 ETH1 (3640 only) – 100 BT Ethernet PI2 – Same as PI1 except 100 BT Ethernet.
14
Site view – Set I/O Modules (1)
ACE 3600 can have 1 IO frame with up to 8 IO slots. Each one of the slots can have any IO module. User can configure IO module for slot from a list of available IO modules.
15
Site view – Set I/O Modules, automatic recognition
Automatic I/O recognition allows Automatic I/O recognition upon start-up – BUT the DO/DI module is defined by default as all outputs! So, for each module in the rack, you MUST select the I/O type to be assigned from the drop-down list. BE SURE TO DISABLE THIS FEATURE WHEN USING DO/DI MODULE FOR IRRIGATION! ACE 3600 can have 1 IO frame with up to 8 IO slots. Each one of the slots can have any IO module. User can configure IO module for slot from a list of available IO modules.
16
Site View – Advanced Parameters
The entire parameters were designed in such way that in most case user will not need to enter this tab. Advanced parameters have been categorized into groups. Default parameters are set automatically by “IRRInet-ACE” and “IRRInet-M” and usually do not require any adjustment.
17
System view – Diagram view (1)
The top of ACE STS graphical user interface includes a menu bar, icons, and a contextual link trail for navigation. On the left side of the screen: System tab contains system tree. Inventory tab contains system components to add to your system. In the main workspace, the system is depicted in graphical (diagram) or table format, with additional icons. 1. Every new site added to the project is displayed on the system view. 2. Sites that have a common MDLC link will a line that connects them. 3. Site ID ,Site name and firmware version is displayed on site's ICON. 4. If a site needs to be download (due to change done by user) a "Needs Download" sign is displayed on the site's icon. 5. If the site's ladder application needs to be re-compiled then a sign will be sipaled on the site icon. 6. Every MDLC link available on this site will have a graphical presentation on the system view whether it is connected or not.
18
System View – Diagram View (2)
Displays information on a system level, i.e. diagram /system view. In this view, system level commands are available, both from the System menu and the context menu (right click in the empty space in the diagram/table view or on the system name in the system tree). This how a 5 Sites system may look like.
19
System view – Using areas
To view the system graphically, go to the system view (either by clicking on the System item in the tree in the System tab or on the <System Root> link at the top of the window) and click on the Diagram View button in the STS main window. Areas can be used to re-arrange the view of system with large amount of sites. Area is a logical container of sites and areas.
20
System view – Table view
The projects can be viewed in a table view. Table view can be more comfortable for a large sites project.
21
System view – Site graphical information
User can navigate to different sites and areas using the system explorer and the ‘navigation line’ For each site, the Site name, Site ID, RTU model, STS software version and links are displayed. When the mouse is positioned over the site/area, information about the site/area is displayed, including site name, site ID, description, unit type, system firmware version, number of links, number of I/O modules, application name, and download status.
22
Working with Inventory
Inventory contains All possible IO modules, Ports and RTU types that STS supports. User can select RTU object and drag it into the diagram area. Then it can select IO’ s or communication port and drag it over a specific RTU that will contain them.
23
Reuse your Work with Gallery
Since several RTUs in the system usually have the same configuration, the system provides the option of storing user-defined site configurations, I/O configurations or port definitions in the gallery. The configuration can then be used in different RTUs with only minor changes. Gallery is most useful to reuse a custom build port or I\O module and duplicate sites. Gallery can contain RTUs , I\Os and Ports. Gallery items are application level item, meaning that Item that was added in specific project will be available for any future projects.
24
Gallery – Add to Gallery
To store an RTU configuration in the gallery: Click on the site in the system view (diagram or table view) Select Add to Gallery from the Site menu or from the site view. Click on the Add RTU to Gallery button. To store an I/O configuration in the gallery: Select the desired I/O configuration in the site view. Click on the Add I/O to Gallery button. To store a port configuration in the gallery: Select the desired port configuration in the site view. Click on the Add Port to Gallery button. Result: The “Add Item To Gallery” dialog box will be displayed.
25
Inventory vs. Gallery Inventory Gallery Content Property Ordering
Configured items that come with the STS installation User-defined elements Property Read only User can add or edit Ordering Arranged by type and version Items can be stored in ANY folder regardless of their type Designed for easy reuse. User can use pre-configured items: RTUs, ports or IOs Inventory contains configured items that come with the STS installation. Gallery contains items that were defined by the user. Inventory folders and items are read only and arranged by type and version. Gallery folders can be edited by the user (items can be stored in any folder regardless their type).
26
PC Communication Setup
No need to close driver in order to change IP address or to move from Ethernet to Serial and the opposite. Only case where close driver is need – is when you want to change the password.
27
Network table – Generic Network (default)
Generic network is built from the entire sites in the project. It is updated once a site is added or removed and attached by default to all of the site in the project.
28
Network table – Generic vs. Custom
The STS builds automatically generic network which includes all sites in system. The costs associated with each type of communication link in the system can be modified. The application uses the link costs to calculate the costs of each transmission route and to decide which route to use. IMPORTANT! IGNORE THE GENERIC AND CREATE YOUR OWN FOR IRRIV! (Site 2 / Radio-Line / RSLink19) Generic network is built from the entire sites in the project. It is updated once a site is added or removed and attached by default to all of the site in the project.
29
Network table – Links Configurator
The number of links in the system assigned to each medium, such as wire-line, RSlink and Radio can be changed using the Links Configuration dialog. This should be done prior to system definition, before links have been assigned to ports in sites. Generic network is built from the entire sites in the project. It is updated once a site is added or removed and attached by default to all of the site in the project.
30
Network table – Customized Network
User can create new network file based on the ‘Generic network’. While the ‘Generic network’ file name cannot be changed, the user must give a name to the new network files. Each network file can be attached to site\s, every site can be attached with one network file. Customized network files update should done manually by the user.
31
IP Conversion Table (1) IP conversion table can have more than one link id for site. Each site’s link id can have IP address or domain name. A project can have more than one IP conversion table. IP conversion table is attached to site manually by the user. Every site \ Group of sites can have a specific conversion table. Every conversion table has a unique name. Once a conversion table is changed – all the attached sites need to be dowloaded.
32
IP Conversion Table (2) The STS IP Conversion Table Manager lets the user to create, edit, copy, and delete IP conversion tables and assign an IP conversion table to a site. Accessing IP Conversion Table Manager from the System menu. To create an IP conversion table, click on the New Table icon. In the table set the desired site ID/link ID and IP address/host domain name information and click OK. If site ID is changed in the project or new sites added to the project, any user defined IP Conversion tables must be updated manually by the user.
33
Phone Book and Dialup Dialup is done from the phonebook editor. Phonebook is selected for download automatically once a site has a dialup port. If phonebook is change it will have to re-downloaded to the relevant sites. There is one phonebook per project.
34
Ladder Applications Creating application:
STS Project can contain ladder applications Creating application: Import from other project / ToolBox into the STS project Created inside the STS project Each ladder application in the project can be attached to one or more sites. Pre-compiled ladder applications for IRRIV7 are provided with STS Application programmer can be activated within the STS in two modes: Not attached: Application programmer is available for rungs and the database editing only. I/O link and compilation can’t be performed since they are operations that related to site. Attached to site: All programmer functionality is available including I/O link, compilation, download and monitoring. ‘Compile All’ option can be selected when compiling an application that is attached to more than one site. The compiler knows whether to compile once or more according to differences in the I/O link.
35
Application Manager Activated within the Menu by:
System->Application Manager … OR by right click on empty space within the system view. Attach ladder applications to sites. User can import applications from other projects. A new application can be built from here. Application can be compiled for the entire sites that are attached to it. Application can be compiled also for a specific site. Note: The application version is detailed
36
Add-ons Manager (1) Add-ons are files that will be downloaded to the RTU and they are not handled by STS automatically. User can attach an add-on file to one site or to a group of sites.
37
Add-ons Manager (2) Add-ons are files that will be downloaded to the RTU and they are not handled by STS automatically. User can attach an add-on file to one site or to a group of sites.
38
Add-ons Manager (3) Add-ons are files that will be downloaded to the RTU and they are not handled by STS automatically. User can attach an add-on file to one site or to a group of sites.
39
Add-ons Manager (4) Enables the user to attach a number of files to the site, like: PLC files ‘C’ applications – such as WeatherCon ‘C’ application parameter files Modem configuration files Add-On Manager is available from: The System menu Add-On Manager button from the site view File selection: Set the appropriate filter, browse the HD and select Site view is where we can view and set the following site properties - 1. Site ID and name 2. Site description 3. Ports configuration 4. IO modules 5. Advance configuration 6. Add-on files downloaded to the RTU
40
Add a Comment Comment is a multi line text box.
Number of comment box is not limited.
41
Download – To a specific RTU (1)
42
Download – To a specific RTU (2)
Download all types of files, such as: System (OS) file – ALWAYS DOWNLOAD THIS FIRST Site configuration – ALWAYS DOWNLOAD THIS SECOND C Application – IRRIV, Weather Network configuration RTU application Phonebook IP conversion table Predefined IO module values Additional optional files, such as: Modem files, PLC files, ‘C’ application parameters, special drivers… Downloader automatically select the relevant files to be downloaded to the RTU. User may modify the selection.
43
Download – To All Priority among the sites can be set
Every site has a check box, once checked the site will be downloaded. Download order is done using ‘Download Priority’. User can select the specific download link for each site. By clicking on the ‘Download’ button, download process will download to all sites.
44
Upload site from RTU By right clicking on the system diagram area user can decide to upload new site to project. ‘Upload New Site’ wizard helps to decide the site id and link id of the upload. Once uploaded – the entire sites info is displayed: General site info: site id , name, firmware version and product type (3640 or 3610). Ports – view of the communication ports. IO – configured IO modules. Files – the files found in the flash file of the RTU. User can decide to add this site to the project or stop here. User can decide to create a new site in the project or to upload this site into an existing site in the project.
45
Logger Tools – Error logger
Error level indicated in RTU by the ERR LED color Site ID and Link ID - Logger tool can be opened from a site view, by right clicking on a site or from a site’s menu. Once opened from a site’s view logger utility will have the specific site as the site id it wants to address to. The available link id will be taken from this site’s configuration. Every logger message has a severity. Severities - Error , warning & Message. Logger messages can be resorted using the following keys - date and time , site id , link id and severity. User can select if he wants to erase error messages or not. Recent log can be open from the Errorlogger utility.
46
Logger Tools – Diagnostic
Site ID and Link ID – Logger tool can be opened from a site view, by right clicking on a site or from a site’s menu. Once opened from a site’s view logger utility will have the specific site as the site id it wants to address to. The available link id will be taken from this site’s configuration. Recent log can be open from the Diagnostic utility.
47
Logger Tools – Time Tag Site ID and Link ID – Logger tool can be opened from a site view, by right clicking on a site or from a site’s menu. Once opened from a site’s view logger utility will have the specific site as the site id it wants to address to. The available link id will be taken from this site’s configuration. Recent log can be open from the Time Tag utility.
48
Site Date & Time The same look as in MOSCAD Tool box.
User get or set the RTU time.
49
Sync Sync utility is not part of the ‘Date and Time’ as in MOSCAD Tool Box.
50
Sync - In brief Time sync methods Extended Sync
RTU sends sync frame containing time zone and password, with nanosecond resolution (2 millisecond accuracy over synchronous media (radio) and over asynchronous RTU to RTU media). Legacy Sync For synchronizing legacy MOSCAD RTUs (5 millisecond accuracy). The sync command coming from ICC/STS is ”Legacy”. It is up to ACE decide how to send the sync forward according to its advanced ‘sync’ parameters (site config). Sync utility is not part of the ‘Date and Time’ as in MOSCAD Tool Box.
51
Hardware Test (Mixed analog module)
To test an AO attached to an I/O module, click on the desired AO module from the list of modules in the Hardware Test IO Modules tab. When the module entry changes color, click on the Test Module button. Result: The Module Diagnostics will be displayed.
52
STS Files and Folders Structure (1)
Project Folder .spj file - The STS project file. The user opens this file. “stsgraph.dat” and “siteconf.cache” - internal STS files used for the STS layout “port.txt”, “links.txt” - contain the links configuration of the project. It is set by the MDLC links configuration screen “UsedLinks.txt” - list that contains the used link names for each site in the project Each field unit gets a machine-readable unique name folder under the main project folder System Applications .adb, *.out - the ladder application files
53
STS Files and Folders Structure (2)
.sfl, *.bin - the firmware system files that exist in the project .scf, *.tbl files - network files ('generic' is created automatically by the STS project) .ipc - the IP conversion table files in the project .tel - the project phonebook file Other Add-On files (like C applications, PLC drivers, dat files,...) Site Folders (with Unique ID names) conf.cfi - the site configuration file Other cfi files - irrelevant to the project. These are the previous configurations of the site. *.b, *.dis,*.ios,... - the deliverables of the compiled ladder application (*.b file is the compiled ladder application that is downloaded to the RTU)
54
STS Files and Folders Structure (3)
STS Project Folder \ Main project file (.spj) Other project files System Folder \ Applications Folder Contains applications (.adb) Files Folder \ Contains project-wide files: Network configuration (.scf) Flash ROM files (.sfl, .bin) Phonebook (.tel) Site Folders \ Consist of digits Files subfolder \ Site Configuration (.cfi) I/O Link information (.l4), I/O State (.ios) Compiled application for this site (.b) Other site files
55
STS version 11.70 - Hardware elements
Analog output - new modules supported in site configuration and Hardware Test 4 AO / 8 AI ±20 mA (V562/FLN3816) 4 AO / 8 AI ±5 V (V460/FLN3815) 4 AO (V118/FLN3817) PS 24V - Supported in Hardware Test PS 12V Low Tier - PS 24V Low Tier - Supported in Hardware Test (can not be controlled by application) Radio CDM750 / XTL2500 now supported in site configuration SRAM – supported in hardware test (and in C toolkit) XTS2500 support - STM file available by add-ons manager
56
STS V11.70 & FW V11.05 – software elements
PID function MODBUS over IP - Added to the IP port configuration. Ladder system table was added to the ladder to support it. 2 new IPV4 types in the application programmer: IP ADDRESS value and IP ADDRESS parameter. Protocol Analyzer was updated to support ACE baud rates and new commands (like extended Sync) Radios rate support as in MOSCAD. Legacy (MOSCAD) scaling for AO and AI in ICC
57
STS version (1) Updated Inventory supports previous ACE3600 firmware versions
58
STS version 11.70 (2) Operations on ‘Legacy RTUs’:
Download toolbox files (not firmware) Read error loggers, diagnostics Get\Set\Sync the RTU date and time Updated Inventory supports ‘Legacy RTUs’: MOSCAD\MOSCAD-L\MOSCAD-M\IP-Gateway
59
Example of legacy support
60
Example of IRRInet-M in STS 11.70
61
STS version 11.70 (3) New GUI for Dial-up utility:
Separated from the phonebook editor Accessible from STS system menu
62
STS version (4) Site source - a mechanism to back up the site and user files in the RTU flash. Gallery - the ability to import gallery that was made by other STS. Table Monitor - Refresh time can be set to 0 (no delay between communications) Site configuration - allow parameters to exceed value range Downloader – - download screen log files are logged in the STS’s log folder - cosmetic enhancements Communication - animation to indicate the process System View - conflicts of media type \data speed are indicated with red line Ladders data base- copy\paste for tables and rungs within a specific project and between projects
63
New Radios support in Site Configuration
Mobile two-way radio CDM750 Astro – XTL 5000 & XTL2500 (mobile digital and analog trunking)
64
MODBUS TCP/IP slave ports in site configuration (1)
65
MODBUS TCP/IP slave ports in site configuration (2)
The MODBUS TCP/IP Slave protocol is configured as an ‘Add On’ to the selected port. The selected port is configured as follows: Protocols – select MODBUS Slave. Port Name – PLC1-3
66
MODBUS TCP/IP slave ports in site configuration (3)
MDLC logical link name PLC logical link name
67
MODBUS TCP/IP slave ports in site configuration (4)
68
MODBUS clients authorization in Ladder
The ladder’s PLC TCP/IP Access Control (system) table defines the IP connections to authorized MODBUS Clients.
69
STS updated inventory (1) – ACE3600 FW versions
70
STS updated inventory (2) – Legacy RTUs
71
ACE3600 and Legacy RTU system
72
STS System View – Links conflict (1)
If there is any link conflict (data speed / media type), the link is displayed in red and the conflict information is provided in a tooltip.
73
STS System View – Links conflict (2)
Right Click:
74
STS Downloader logging
Downloader logging data is located at C:\STS1170\Log\DnldLog
75
STS – Monitor Table
76
STS – advanced site configuration
Advanced parameters can be configured with values exceeding their formal range (RED marked).IRRIV has many custom settings which require it to be the FIRST file downloaded to ACE, due to the way the OS handles the memory allocation.
77
and IRRInet-ACE / M / XL / XM
ACE3600 STS V11.70 and IRRInet-ACE / M / XL / XM
78
STS and Irrigation The ACE3600 STS can be used to build, configure and maintain sophisticated distributed SCADA-based (Supervisory Control and Data Acquisition) irrigation systems. The elements and handling of irrigation systems differ slightly from other SCADA systems – namely, IRRInet applications are “canned” and network configuration is different. An irrigation system consists of an IRRInet Control Center (ICC), field units (RTUs) and portable (PocketPC) device for on-site programming of field units. For detailed information on planning and setting up an irrigation system, refer to the updated IRRInet System Planner.
79
STS and ACE/M The ACE3600 STS can be used to build, configure and maintain sophisticated distributed SCADA-based (Supervisory Control and Data Acquisition) irrigation systems. The elements and handling of irrigation systems differ slightly from other SCADA systems. An irrigation system consists of an IRRInet Control Center (ICC), field units (RTUs) and portable (PocketPC) device for on-site programming of field units. For detailed information on planning and setting up an irrigation system, see the IRRInet System Planner.
80
Irrigation Unit Types The STS supports the following irrigation system three field unit types: IRRInet-ACE, IRRInet-M (as Master) and IRRInet-M (as Slave). For detailed information on the field units and irrigation functions, see the IRRInet-M System Planner. For detailed information on using the STS to configure and deploy units, see the ACE3600 STS User Guide. References to ACE3600 in the ACE3600 STS User Guide apply to IRRInet-ACE RTUs as well, except as noted otherwise. The STS does not support legacy Irrigation units: IRRIcom, IRRInet-XL or IRRInet-XM. However, the STS can be used with certain legacy units, as described in Legacy Irrigation RTUs below.
81
STS and IRRInet-ACE The IRRInet-ACE unit is an ACE3600 RTU running the Irrigation (Master) application. Its hardware and system software is identical to that of the ACE3600 RTU. The IRRInet-ACE supports two modes of operations: first, as an RTU performing all irrigation functions, reporting to the IRRInet Control Center (ICC), and Stand Alone, performing all irrigation functions as a stand-alone unit when the system is installed without an ICC. With DIOS (Distributed I/O System) connectivity, the IRRInet-ACE can activate Piccolo-XR units with its PIU (Piccolo Interface Unit) functionality. The IRRInet-ACE RTU can be programmed on site, using a laptop or an IRRinet Terminal for PocketPC. The IRRInet-ACE may be installed in a totally new irrigation system, or in a legacy system in addition to, or instead of, a legacy IRRInet-XL or IRRInet-XM unit.
82
IRRInet-M Types and Modes
There are two types of IRRInet-M: IRRInet-M AC (for AC solenoids), and IRRInet-M DC (for DC solenoids). The IRRInet-M RTU supports three modes of operation: • RTU – Performing all irrigation functions, reporting to the ICC via MDLC network (loaded with the IRRIV Master application) • Stand Alone – Performing all irrigation functions as a stand-alone unit when the system is installed without an ICC. (loaded with the IRRIV Master application) • Remote I/O – Serving as a distributed I/O for another “master” unit that performs all irrigation functions (when loaded with the IRRIV Slave software). This is applicable when multi-site control synchronization is needed. With a PIU connected, IRRInet-M can control Piccolo-XR units.
83
IRRInet-M, continued The IRRInet-M RTU can be programmed on site, using a laptop or IRRinet Terminal for PocketPC. The IRRInet-M (master mode) may be installed in a totally new irrigation system, ICC V14 or higher. The IRRInet-M (slave mode) may be installed in a legacy system in addition to/instead of a legacy Scorpio unit. Important: Although the IRRInet-M looks like the IRRIcom and MOSCAD-M on the outside, it is a different unit with different connectors, hardware, and software. These units are NOT interchangeable!
84
STS functions for ACE/M Units
The ACE3600 STS can be used to perform the following functions on IRRInet-ACE and IRRInet-M units, either via local connection or via the communication network. • Designing the system (areas, sites, communication links) in a graphical desktop, with a “multiple sites/areas” approach • Configuring the RTU sites (unit ID, ports, I/Os, advanced parameters) • Real-time monitoring of application tables in the RTU • Downloading/uploading files • Updating the RTU date and time • Testing hardware elements and plug-in communication ports • Retrieving errors and software diagnostics codes logged in the RTUs For detailed information on using the STS to configure and deploy units, see the ACE3600 STS User Guide.
85
Tips on Using the STS for Irrigation
For legacy irrigation systems, MOSCAD ToolBox 9.54 should be installed on the PC along with the ACE3600 STS software. When defining an IRRInet-M unit, follow the instructions in the Operation chapter of the ACE3600 STS User Guide. Differences between handling an IRRInet-M unit and an ACE3600/IRRInet-ACE unit are specified in the individual procedures. Note: When an IRRInet-M is connected to a PIU via RS232, the port’s advanced physical parameter ‘RTS Always On’ MUST be set to Yes!
86
STS and Network Configuration
The figure on the next slide illustrates an irrigation system, with an RTU (FIU) connected to the STS PC via RSlink19 and a set of RTUs (IRRInet-ACE or IRRInet-M) which communicate with the FIU via radio link, and with PIU/Scorpio units via RSlink1 or RSlink2.
87
STS and Network Configuration
88
STS and Network Configuration
Irrigation systems such as the one depicted on the previous slide should not use the generic network configuration table produced automatically by the STS. Instead, a customized network table should be created and maintained, as follows: 1. After defining two connected sites (RTU 100 and RTU 1) with their links (RSlink19 and Radio1 for RTU 100, and Radio1, RSlink1, RSlink2 for RTU 1), save the generic network configuration table produced by the STS as a private network table. (See the Managing the Network and Editing a Network Table sections in the Operation chapter of the ACE3600 STS User Guide.) Initially, the network table should have two entries in it.
89
STS and Network Configuration
2. Delete the second entry (for RTU 1), leaving one entry with a Site ID and two (or more) Link IDs. 3. Continue defining the rest of the RTUs in the system, using the following convention: Only links from the RTU to PIU units should be named RSlink1. Only links from the RTU to IRRInet-M Router (for connection to Scorpio, Impact, and IRRIcom legacy units) should be named RSlink2.
90
STS and Network Configuration
4. Edit the customized network table to show only those communication nodes which are not connected to PIU and legacy units. 5. To simplify the viewing the system in the GUI’s Diagram view, it is recommended to hide the RSlink1 and RSlink2 links in the display. To do so, click on the Links button in the System view.
91
STS and Legacy RTUs The STS does not support legacy irrigation units. However, the STS can be used with IRRInet-XM and IRRInet-XL legacy units, as follows: To define an IRRInet-XM module, drag the Legacy->MOSCAD entry in the inventory. To define an IRRInet-XL module, use the Legacy->MOSCAD-L entry in the inventory. Although the RTUs that are created will be marked as MOSCAD/MOSCAD-L in the STS GUI, you can download relevant Irrigation files to the RTUs and retrieve errors and diagnostics from them. As with legacy MOSCAD RTUs, the site configuration of legacy irrigation units must be imported. See the instructions on importing a site configuration in the Operation chapter of the ACE3600 STS User Guide.
92
STS and Legacy RTUs The table below lists the Add-on files which should be imported from the Toolbox project directories [C|D]:\Tbox954\... and downloaded together with the site configuration and network configuration to the units. See the instructions on using Add-on files and downloading in the Operation chapter of the ACE3600 STS User Guide.
93
STS and Legacy RTUs Important: Because the irrigation system works with ICC V14, all legacy irrigation RTUs must be upgraded to V9.27 of the system files and V5.70 of the project files.
94
STS V11.70 updated inventory – ACE3600 /IRRInet FW versions
95
Application programmer V11.70 – Copy / Cut / Paste Process (1)
96
Application programmer V11.70 – Copy / Cut / Paste Process (2)
97
Application programmer V11.70 – Copy / Cut / Paste Process (3)
98
Application programmer V11.70 – Copy / Cut / Paste Process (4)
99
Application programmer V11.70 – Copy / Cut / Paste Process (5)
100
STS V11.70 Add-On manager
101
Thank You
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.