White Electric | Standard Range, Single Power Outlet

Sometimes there is a need to restart alarm redirection sequence if a particular alarm does not get acknowledged or cleared in specified time. Consider an example where a redirection action is configured to send an e-mail once a point goes into alarm. If the alarm does not get cleared within 30 minutes, another e-mail needs to be sent out. The e-mails should be sent out repeatedly every 30 minutes until the alarm is cleared.

This can be achieved by using the RestartRedirections() method. Below is a quick run through on how this method could be used.

1. Consider an analog point named Pressure with an alarm redirection action configured to send an e-mail whenever the point is in alarm.

2. Locate this E-Mail Action in Database Explorer and assign this action to a particular redirection group for which alarm redirection needs to be restarted. If no redirection groups have been configured yet, type in an arbitrary name to create a redirection group.

3.Create new Method Action and specify Method Object. In this case, Method Object is going to be the object for which alarm redirection needs to be restarted. Select Restart Redirections as Method. Enter the redirection group's name in single quotes ('Redirection Group Name') as the value for the Redirection Group argument.

4. Add the newly created method action to the list of redirection actions in point's properties. Make sure to specify a delay to restart alarm redirection.

Only redirection actions configured under the same redirection group (PressureGroup in this case) will be restarted. Do not assign other redirection actions to the same redirection group if they do not need to be triggered repeatedly. Make sure the method action is also assigning the same redirection group (PressureGroup in this case) to be triggered again.

Issue:
Connecting SoMove to the VFD using the Ethernet network connection.
 

Product Line:
ATV61 
ATV71 
ATV630
ATV930
ATV320
ATV340
ATV32

Environment:
Ethernet IP or Profinet option installed.
VW3A3316, VW3A3320, VW3A3627 VW3A3720

Cause:
Drive is not detected when attempting to connect.

Resolution:
See attachment for screenshots showing SoMove V2.9.4

STEP 1
Turn OFF your computers firewall before starting so you will have access to your Ethernet port. 


STEP 2
Edit Connection on your computers ethernet port and setup IP address in the Altivar Drive using an HMI.
Computer or PC setup:
Example setting up your PCs IP address.
Search Ethernet settings
-Change adapter options
- Choose the Ethernet port you want to use.
-Choose Properties
-Make sure IPV4 and IPV6 are both checked. 
-Double click on the IPV4 settings
-Select "Use the following IP address" and now enter in an IP address for your PCs ethernet port. 
Note this IP address needs to match your Drives IP address up to the last octet. 
Drives IP address= 10.172.86.1 (for the Drive) and your PC's IP address = 10.172.86.10 (your computer)
Subnet address= 255.255.255.0
-Choose ok


Drive Setup
Example set your Drives IP address using the remote HMI under the Ethernet settings in the programming. 
Type=Fixed
IP address= 10.172.86.1 (for the Drive) 
Subnet address= 255.255.255.0
-Power cycle your Drive after changing the IP address 


STEP 3 
Open up Somove 2.9.4 or newer and setup your "edit connection/scan" settings.
-Click on  "edit connection/scan"
-Choose Modbus TCP double click
-Choose the advanced settings (small gear wheel icon).
-Choose More
-Choose Scan tab
-Now type in your Drives IP address example 10.172.86.1  
-Choose Single Scan and enter 1 
-Apply and OK
-Ok again 


STEP 4 
-Now Scan for the Device to see if your PC finds the Drive. 
-double click on the picture of the drive to connect and load from the device.



Please read and understand before checking OK. 



Somove is loading settings from the Drive to your Somove on your PC. 




Your are now connected to the Drive when the bar across the top turn's orange. 



Done.  

NOTE:  

This example should work using. 
-Ethernet TCP
-Ethernet IP
-Profinet

 

This article goes over some common issues that one might encounter when configuring ClearSCADA Mobile and provides some basic steps to troubleshoot these issues. In addition, please familiarize yourself with ClearSCADA Mobile system requirements  to make sure your ClearSCADA Mobile runs in the  supported environment.

Connection to ClearSCADA Mobile times out or an internal error reported:

This may be caused by the following issues:

1. The mobile device is not on the same network or routing is not implemented/configured correctly. One could check the Internet Information Server (IIS) log files which are usually located in "C:\inetpub\logs\LogFiles". The IIS logs should record connection attempts similar to below with timestamp in UTC if the mobile device is able to reach Mobile Server. Due to the way the IIS logs operate, new entries might be delayed for up to a few minutes.

To resolve this issue, make sure that mobile devices are connected to the same network as ClearSCADA Mobile if no routing is implemented. If there is routing in place, check the configuration of the router(s).

2. Incorrect connection information is provided. Make sure the connection information the mobile device is configured to follow the general format below. Depending on the situation, one either needs to specify the IP address/Name and the port of the server running ClearSCADA Mobile or the IP address/Name and the port of the router.

• <server IP or server name or URL>:port 

3. Communication ports get blocked by a firewall. Make sure the ClearSCADA Mobile port and the listening port between ClearSCADA Mobile and ClearSCADA Mobile Companion Server are both configured to allow communication. To find out what ports ClearSCADA Mobile uses check the following:

• Launch Internet Information Services (IIS) Manager on the machine hosting ClearSCADA Mobile, select ClearScadaMobile site (ClearSCADA if using ClearSCADA 2015 R1) and click on Bindings. The HTTPS port displayed in Bindings is being used for communication between mobile devices and ClearSCADA Mobile. The default port is 443 in all versions of ClearSCADA except for ClearSCADA 2015 R1. It is port 453 in ClearSCADA 2015 R1.
• Right click on the ClearSCADA Server Icon found on the machine hosting ClearSCADA Server itself, navigate to Configuration -> System Configuration -> Mobile and locate Port. This port is being used for communication between ClearSCADA Mobile and ClearSCADA Mobile Companion Server. The default port is 8008.

4. The ClearScadaMobile web-site is not running on the server. Launch Internet Information Services (IIS) Manager and make sure the ClearScadaMobile site is running as shown below.

5. Check whether the "ClearSCADA Mobile Settings Service"  (named "ClearSCADA Mobile Server" in ClearSCADA 2014 and 2013, and "ClearSCADA Web and Mobile Settings Service" in ClearSCADA 2015 R1) service is running on the machine hosting ClearSCADA Mobile. In addition, make sure the "ClearSCADA Mobile Companion Server" service is running on the machine hosting ClearSCADA Server. If ClearSCADA Mobile and ClearSCADA Server run on the same machine, both services should be present on it.

6. HTTP Activation is not installed as a part of WCF Services as per below. 

ClearSCADA Mobile Connection Port used by another application:

An issue will arise when ClearSCADA Mobile is configured to use the same port that is already in use by another application. The default connection port for ClearScadaMobile is 443 in all versions of ClearSCADA except for ClearSCADA 2015 R1. It is port 453 in ClearSCADA 2015 R1. To check what port ClearSCADA Mobile is configured to, launch the Internet Information Services (IIS) Manager, select ClearScadaMobile site (it is called ClearSCADA in ClearSCADA 2015 R1), click Bindings and see what port is specified for HTTPS connections. If the port configured for the HTTPS connection is being used by another application, change the HTTPS port for ClearSCADA Mobile to a vacant port. Once the change to the port is made, the ClearScadaMobile site needs to be restarted. There might also be a need to reconfigure the SSL certificate for the newly assigned HTTPS port.

Mobile User not created in the ClearSCADA database:

Make sure that users configured in ClearSCADA Mobile have also been configured in the ClearSCADA database - the user names are case sensitive and must be match. Otherwise, users will not be able to access the ClearSCADA database when logging in through ClearSCADA Mobile.

Mismatch in System Name:

Make sure that the same System is specified in ClearSCADA Mobile Configurator and in "Server Configuration -> System Configuration -> Mobile".

Mobile Companion Server not installed (does not apply to ClearSCADA 2015 R1):

ClearSCADA Mobile Companion Server must be installed separately from ClearSCADA Mobile except for ClearSCADA 2015 R1. ClearSCADA Mobile Companion Server must be installed on the machine hosting the ClearSCADA database which might or might not be the same machine hosting ClearSCADA Mobile. To install ClearSCADA Mobile Companion Server, run ClearSCADA Installer and select "Install ClearSCADA" as opposed to "Install ClearSCADA Mobile". Select "Modify" and locate "Mobile Companion" under "Server" group. Continue with the installation process. Once the installation is completed, check to see if the ClearSCADA Mobile Companion Server service is running.

Configuration Mismatch in Listening Ports (applies to ClearSCADA 2013 and 2014 only):

It is possible that ClearSCADA Mobile and ClearSCADA Mobile Companion Server are configured to different listening ports which results in no communication between the two. The listening port of Mobile Companion can be checked from "ClearSCADA Configuration -> System Configuration -> Mobile -> Port".

The listening port configured in ClearSCADA Mobile can be checked as well. Go to ClearSCADA Mobile installation folder - the default directory is "C:\Program Files\Schneider Electric\ClearSCADA Mobile", go into "Server" and open up ClearScadaMobileServer.exe (with Notepad for example):