INSYS GSM 4.2 easy User manual

Add-On Manual
INSYS GSM 4.2 easy
Oct-08

Copyright © October 08 INSYS MICROE ECTRONICS GmbH
Any duplication of this manual is prohibited. All rights on this documentation and the
devices are with INSYS MICROE ECTRONICS GmbH Regensburg.
Trademarks
The use of a trademark not shown below is not an indication that it is freely available for
use.
MNP is a registered trademark of Microcom Inc.
IBM PC, AT, XT are registered trademarks of International Business Machine Corporation.
INSYS ® is a registered trademark of INSYS MICROE ECTRONICS GmbH.
Windows™ is a registered trademark of Microsoft Corporation.
inux is a registered trademark of inus Torvalds.
Publisher:
INSYS MICROE ECTRONICS GmbH
Waffnergasse 8
D-93047 Regensburg, Germany
Phone: [phone]
Fax: [phone]
e-mail: [email protected]
Internet: http://www.insys-tec.de
Date: Oct-08
Item: 31-22-03.089
Version: 1.1
anguage: EN

Contents
4 Oct-08
1 Scope of Delivery...............................................................................................6
2 General ..............................................................................................................7
2.1 Application Possibilities of t e INSYS GSM 4.2 easy......................................................... 7
2.1.1 Remote Control via Mobile Phone or Data Connection .......................................... 8
2.1.2 Remote Programming via Data Connection .............................................................. 8
2.2 Possibilities wit t e Preceding Version INSYS GSM ........................................................ 8
2.3 Restrictions / Notes............................................................................................................ 9
3 Functional Description.....................................................................................10
3.1 Definitions........................................................................................................................ 10
3.1.1 Objects, Instances, Object Short Names ................................................................... 10
3.1.2 Alias..................................................................................................................................... 10
3.2 Automatic Actions............................................................................................................ 10
3.2.1 Object Instances Monitoring........................................................................................ 10
3.2.2 Periodic SMS ..................................................................................................................... 12
3.3 Querying and Controlling via SMS .................................................................................. 14
3.3.1 SMS Commands...............................................................................................................14
3.3.2 Monitoring of an Object Instance...............................................................................15
3.3.3 Setting an Object Instance............................................................................................ 17
3.3.4 Status Query .....................................................................................................................18
3.3.5 Status Change ..................................................................................................................18
3.4 New History-Entries ......................................................................................................... 19
4 Initial Operation ..............................................................................................20
4.1 Installation Overview....................................................................................................... 20
4.1.1 Installation for Configuration...................................................................................... 20
4.1.2 Installation for the operation with Moeller easy....................................................20
4.2 Initial Operation............................................................................................................... 21
4.3 Troubles ooting............................................................................................................... 23
4.3.1 No response on commands ..........................................................................................23
4.3.2 No connection established ........................................................................................... 23
4.3.3 Alarm SMS is not dispatched........................................................................................23
4.3.4 Signal Quality ...................................................................................................................24
4.4 Log-In State in GSM Network .......................................................................................... 25
5 Configuration wit t e Software HSComm easy ............................................26
5.1 General ............................................................................................................................. 26
5.2 Help .................................................................................................................................. 26
5.3 Menus ............................................................................................................................... 26
5.3.1 File .......................................................................................................................................26
5.3.2 Interface.............................................................................................................................26
5.3.3 Program Settings.............................................................................................................27
5.3.4 Terminal............................................................................................................................. 27
5.3.5 Sprache / anguage ........................................................................................................27
5.3.6 Overview............................................................................................................................27
5.3.7 Send / Receive Protocol.................................................................................................. 27
5.3.8 Info ......................................................................................................................................27
5.3.9 Help.....................................................................................................................................27
5.4 Status Bar ......................................................................................................................... 27

Contents
Oct-08 5
5.5 Buttons ............................................................................................................................. 28
5.5.1 Send Settings.................................................................................................................... 28
5.5.2 Read Settings....................................................................................................................28
5.5.3 Send default setting .......................................................................................................28
5.5.4 Reset.................................................................................................................................... 28
5.5.5 Synchronize....................................................................................................................... 28
5.5.6 Abort ................................................................................................................................... 28
5.6 Tabs................................................................................................................................... 29
5.7 Basic Settings ................................................................................................................... 29
5.7.1 GSM Connection..............................................................................................................30
5.7.2 System Monitoring ......................................................................................................... 32
5.7.3 Date / Time........................................................................................................................32
5.7.4 Serial Interface .................................................................................................................32
5.8 Moeller easy™ Settings ................................................................................................... 33
5.8.1 Alias Configuration.........................................................................................................34
5.8.2 Configure monitoring .................................................................................................... 35
5.8.3 Configure Periodic SMS..................................................................................................36
6 Remote Configuration wit EASY-SOFT and INSYS Connect ...........................37
7 Declaration of Conformity...............................................................................39

6 Oct-08
1 Scope of Delivery
Please check the scope of delivery before initial operation:
 INSYS GSM 4.2 easy
 PC connection cable 9/9 pin (RS232)
 User Manual INSYS GSM 4.2
 Additional Manual INSYS GSM 4.2 easy
 CD-ROM
In case the content is not complete, please contact your supplier. Please check the
device for shipping damage. Please also refer to your supplier if damage exists.
Please keep the packaging material for dispatch or storage.
Optional Accessories
 Adapter cable D-SUB 9 pin, male to 9 pin, male
 GSM aerial
• Outside mounted aerial, magnetic base aerial or patch aerial
 Connection cable GSM easy 500 for connecting the INSYS GSM 4.2 easy to
a Moeller easy 500/700 (Art.-Nr.: 31-02-02-011)
 Connection cable GSM easy 800 for connecting the INSYS GSM 4.2 easy to
a Moeller easy 800/MFD (Art.-Nr.: 31-02-02-012)

2 General
Basically, the INSYS GSM 4.2 easy offers the same technical characteristics and
functionalities as the standard version.
The indication of technical data and functional descriptions of the standard ver-
sion will be omitted in this manual (if possible). Please refer to the user manual
INSYS GSM 4.2.
If the INSYS GSM 4.2 easy behaves differently than the standard version, we will
mention this fact in the according passages.
The INSYS GSM 4.2 easy is available in two versions. These are
 INSYS GSM 4.2 easy
 INSYS GSM 4.2 easy compact
The INSYS GSM 4.2 easy compact differs by a compact housing for in-wall connec-
tion boxes and the missing audio interface from the INSYS GSM 4.2 easy. Both
versions are referred to as INSYS GSM 4.2 easy in the further course of this man-
ual. If the INSYS GSM 4.2 easy compact differs from the INSYS GSM 4.2 easy, this
will be mentioned in particular in the respective sections.
Supported Moeller easy versions:
The following easy models are supported:
 easy 500
 easy 700
 easy 800
 easy MFD
The communication protocols of the easy 500 and the easy 700 as well as the pro-
tocols of the easy 800 and easy MFD are identical as file. In the following, we only
need to distinguish between easy 500/700 and easy 800/MFD.
Dedicated connection cables are available for the connection (refer to Optional
Accessories in the in the Scope of Delivery section on page 6)
2.1 Application Possibilities of t e INSYS GSM 4.2 easy
The object instances (peripherals and extension modules) of the easy device can
be monitored regarding defined conditions or levels, to enable the sending of
fault messages when changes occur. Depending on the used easy model, not all
object instances are available.
The following object instances can be monitored:
 Digital inputs
 Digital outputs

8 Oct-08
 Digital registers
 Analogue inputs
 Analogue outputs
 Analogue registers (byte registers, word registers, double word registers)
 Current program cycle time
 ED state for Moeller easy MFD
The fault message consists of one text, which is permanently allocated to the
value to be monitored. Up to 10 object instances can be monitored altogether.
The fault message can be sent in the following format:
 Via SMS to a mobile phone
 Via SMS to a fixed network telephone (depending on the provider)
 Via SMS to a FAX device (depending on the provider)
 Via SMS to an E-mail recipient (depending on the provider)
2.1.1 Remote Control via Mobile P one or Data Connection
Independent from automatic monitoring, various information regarding the cur-
rent condition of the easy device can be read or set via SMS or a GSM data connec-
tion:
 easy status (RUN/STOP/ERROR). The easy status can also be changed from
RUN to STOP or vice versa.
 Monitoring of the easy object instances. This message can also be per-
formed automatically (refer also to section 3.2.2).
 Setting of the easy object instances. This can be done from a mobile phone
or via a dial up connection. It will enable you to intervene actively in the
process of the easy control program.
2.1.2 Remote Programming via Data Connection
A dial up connection is established with the help of the dialling program “INSYS
Connect” for the remote programming of the easy device. The supplied program
“EASY Soft” by Moeller is used to program the remote easy device. The INSYS GSM
4.2 easy serves as remote terminal of the dial up connection and forwards the
data transparently to the Moeller easy device.
2.2 Possibilities wit t e Preceding Version INSYS GSM
The possibility to control the alarm inputs of the INSYS GSM with pulses, thus
triggering up to 20 fault messages, has been implemented into the device series
INSYS GSM and can still be used. This possibility is not tied to a device and can
therefore be used for all kinds of control types.
Generating pulses or their processing, however, results in the following:

 The controller requires additional memory for the functions to generate
pulses. Compact controllers in particular have a rather limited memory for
control programs.
 Due to additional functions which have no effect on the actual system
function, the control program will be more complex and confusing.
 Programming pulse creation requires effort and time.
 Valuable outputs of the compact controllers are used, because they are
needed for the pulse output.
2.3 Restrictions / Notes
 Since the INSYS GSM 4.2 easy is connected to the Moeller easy device via a
serial interface, a memory can not be used simultaneously with the INSYS
GSM 4.2 easy.
 The password protection of the easy device may not be activated. If it is ac-
tivated, no communication between INSYS GSM 4.2 easy and the compact
controller is possible. However, the INSYS GSM 4.2 easy has its own pass-
word protection, which prevents unauthorized persons without knowledge
of the exact password from remotely accessing the compact controller.
 The CD display needs to be in its original state before the Moeller easy
controllers can communicate via their RS232 interface. This means, for ex-
ample, that if the controller is put into another condition by hitting keys on
the device, or if the control program is manually modified, the user has to
leave all sub menus of the easy device. This is necessary that the INSYS
GSM 4.2 easy can communicate with the easy device.
 As it is possible to intervene in registers of the current easy control pro-
gram with the help of SMS commands via the INSYS GSM 4.2 easy we again
refer to the documentation of the used Moeller easy 800 or easy MFD de-
vices. In the easy device, the storage location for registers can be used
twice; the instances of the registers should therefore be chosen with care
to prevent the registers from manipulating each other.
Recommendation:
Object Instance from
Bit register M 1
Byte register MB 13
Word register MW 49
Double word register MD 49

10 Oct-08
3 Functional Description
3.1 Definitions
3.1.1 Objects, Instances, Object S ort Names
Programming of the Moeller easy takes place via objects. A digital input, a regis-
ter, a counter for operating hours, a comparator, etc. are all examples for objects.
Each object has an object short name. The digital register, for example, has the
object short name "M", the analogue output has the short name "QA".
Several instances of each object are available to the programmer. The easy 500
device, for example, offers 16 digital registers “M”. The programmer can therefore
select the object instances "M1" to "M16".
3.1.2 Alias
As not only the programmer of the compact controller is responsible for mainte-
nance and operation of the Moeller easy device, it may not be clear for “outsiders”
which object instance has which function. Therefore, so-called aliases were intro-
duced for the INSYS GSM 4.2 easy. This offers the possibility to allocate a name
that is easy to understand. If the Moeller easy device controls a waste water sys-
tem, for example, the digital register M1 can be allocated the alias "waste water
pump1”. If an individual wants to activate the wastewater pump via mobile
phone, using an SMS, he does not need to know that the register 1 must be used,
but simply uses the term “wastewaterpump1”, Up to 30 object instances all in all
can be allocated aliases.
3.2 Automatic Actions
3.2.1 Object Instances Monitoring
The values of the easy object instances are monitored to enable a fault message
when values are changed.
Monitoring is performed during polling operation, i.e. the INSYS GSM 4.2 easy will
cyclically read out the easy object instances and can thus detect any changes. Up
to 10 object instances can be monitored altogether.
The query interval can be set to seconds (1 to 255 seconds). These times represent
minimum values. The actual monitoring interval may be slightly larger. If several
values that need to be monitored have been configured, the communication with
the compact controller may have a longer duration than the interval.
If a change of a monitored value is registered, the sending of a fault message is
prompted (SMS, SMS to fax, SMS to e-mail, SMS to fixed network).
For digital values, the following events (adjustable) can cause the sending of a
fault message:
 Change to 0