ML-8 [email protected]

Transcript

MULTILINK 8 INPUTS
8 OUTPUTS
INTERFACE/PERIPHERAL
ML-8
Installation and user manual
Software Ver. 1.02
Manual N°18926 Rev. A
The information in this manual replaces any previously published information. Sicep reserves the right to modify prices and products' characteristics at any time, without further notice.
T.O.C.
Chapter 1
- Warnings............................................................................1
1.1- General information ...........................................................................1
1.2- Limits of use.......................................................................................1
1.3- Connection to the electrical power supply network - earthing..............1
1.4- Disconnection ....................................................................................1
1.5- Buffer battery .....................................................................................2
1.6- Disposing of the packaging ................................................................2
1.7- Disposing of the product ....................................................................2
1.8- Disposing of the batteries...................................................................2
1.9- Receiving the device..........................................................................2
1.10- Storage ............................................................................................2
1.11- Marking ............................................................................................3
1.12- Compliance with EC directives .........................................................3
1.13- Assistance .......................................................................................3
1.14- Shipping the device..........................................................................3
1.15- Warranty ..........................................................................................3
1.16- Repairs ............................................................................................3
Chapter 2
- Technical Specifications......................................................4
TRA-BT887 model power transformer characteristics . . . . . . . . 4
Chapter 3
- Description.........................................................................5
Chapter 4
- Structure............................................................................6
Chapter 5
- Description of the main card................................................7
Chapter 6
6.16.26.36.46.56.66.76.8-
Pag. I
- Operation...........................................................................9
LAN MVSNet connection ...................................................................9
Transmission of a spontaneous alarm (input change or fault) .............9
Inputs.................................................................................................9
Outputs ............................................................................................10
Control channels (system faults) ......................................................10
Radio controls ..................................................................................11
Log function .....................................................................................11
DHCP protocol .................................................................................12
6.9- Remote programming ......................................................................12
6.10- BT-GSM interface ..........................................................................12
6.11- Transmission of control unit reports
Use as a telephone interface ..........................................................13
6.12- Automatic PSTN line exchange function ........................................14
6.13- Input PSTN line exchange function ................................................14
6.14- External PSTN line exchange function for remote assistance.........14
6.15- Remote programming (without optional BT-GSM card) ..................15
6.16- BT-GSM model GSM interface operation .......................................15
6.17- Spontaneous transmissions ...........................................................16
6.18- Polling............................................................................................16
6.19- Remote programming via BT-GSM ................................................17
Chapter 7
- Installation .......................................................................18
7.1- Installing optional devices ................................................................18
Installing the IRS-RT868 receiver for radio controls . . . . . . . . 18
Installing the BT-GSM module (assembling inside the ML-8
peripheral) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.2- SIM CARD installation......................................................................19
7.3- Installing the ML-8 peripheral/interface ............................................19
Chapter 8
- Programming ...................................................................21
8.1- Installing the USB driver...................................................................21
How to identify the USB COM port . . . . . . . . . . . . . . . . . . 21
8.2- MVC programming...........................................................................22
How to perform connection and programming with a serial or USB
connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
System Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Communicator Page . . . . . . . . . . . . . . . . . . . . . . . . . . 25
LAN page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
GSM page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Input page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Output Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Radio Controls Page . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.3- MVC programming: Remote assistance...........................................36
Remote connection to packets on LAN; ML-8 with static IP . . . . 36
Remote connection to packets on LAN; ML-8 with dynamic IP. . . 37
Remote connection via GSM with time-based billing (DATA
connection via modem) . . . . . . . . . . . . . . . . . . . . . . . . . 38
Remote connection via GSM/GPRS with packet-based billing
(GPRS connection); Installer's PC with static IP . . . . . . . . . . 39
Pag. II
Chapter 9
- Special Operations............................................................41
9.1- Restore factory configuration ...........................................................41
9.2- Firmware Update .............................................................................41
Chapter 10
- Appendix 1 Definitions and abbreviations..........................43
Chapter 11
- Appendix 2 Table of Contact ID codes for events ................45
Chapter 12
- Appendix 3 Troubleshooting .............................................46
12.1- Application form repair ...................................................................50
Chapter 13
- Appendix: Certificate of warranty .....................................51
SICEP spa recognizes in insindacabile and intransgressible way the conditions of guarantee brought back in this
manual.
Pag. III
ML-8
Cap. 1 - Warnings
1 - Warnings
This manual is dedicated to the installation, use and maintenance of the
Multilink ML-8 peripheral. It gives the technical characteristics and the procedures to follow for correct installation and programming according to
individual requirements. At the end, there is a table with solutions to the main
problems.
1.1 - General information
The product and this manual must be examined before carrying out any operation.
The information contained in this manual has been checked during the
writing of the manual itself, however Sicep S.p.A. reserves the right to make
changes and improvements to the product described at any time without
prior notice.
1.2 - Limits of use
WARNING
WARNING!
In order to install the ML-8 device safely and efficiently, read the following paragraph carefully.
-
The Multilink ML-8 interface/peripheral may incorporate an optional
radio interface at 868 MHz. Overall, the device complies with the
CEPT/ERC/REC 70-03 recommendation (short range devices) on the
condition that it is in no way altered, including the antenna.
The Multilink ML-8 interface/peripheral may incorporate an optional
low power GSM radio interface. There are place in which the use of
equipment may be subject to restrictions, therefore before proceeding
with installation, consult the Installation chapter on page 19.
1.3 - Connection to the electrical power supply network earthing
Connection to the AC power supply and earthing must be carried out as indicated in chapter 7.3 on page 19. Sicep S.p.A. disclaims any responsibility in
the event of incorrect wiring.
1.4 - Disconnection
As the peripheral does not have a switch, a bipolar disconnector (switch)
with contact opening of at least 3 mm must be envisaged during installation.
Pag. 1
ML-8
Cap. 1 - Warnings
1.5 - Buffer battery
It is advisable to use a rechargeable lead-acid battery in order to ensure operation even in the event of the loss of voltage for short periods. Do not use
batteries with a capacity greater than that indicated in the Technical Specifications on page 4.
1.6 - Disposing of the packaging
The cardboard packaging is classified as 15 01 01 (Directive 09/04/2001).
Dispose of it according to local separate waste collection criteria.
1.7 - Disposing of the product
Overall, the ML-8 peripheral is not MSW (Municipal Solid Waste) but
is composed of electronic boards classified as 16 02 09 and 20 01 36.
Do not dispose of the device as municipal waste, but proceed with
separate collection.
1.8 - Disposing of the batteries
Lead-acid batteries are not classified as MSW and can be classified
as 16 06 01. Dispose of them according to local separate waste collection criteria.
WARNING
WARNING!
The improper disposal of Electrical and Electronic Equipment
(EEE) or any part of it may have harmful effects on the environment
and human health.
1.9 - Receiving the device
Visually inspect the package to check for any damage due to transport. The device is carefully checked and packed by Sicep. If, at the time of receiving the
package, it is damaged, notify the carrier immediately.
Sicep is not responsible for damage during shipping (see warranty conditions).
The package consists of a cardboard box which contains the following items:
- One Multilink ML-8 peripheral/interface;
- A CD-ROM with application software for installation;
- This installation manual*.
* The manual may be provided in electronic format only.
1.10- Storage
Pag. 2
Store the device in its packaging in the environmental conditions
specified in the Technical Specifications.
Maximum storage period: 2 years
ML-8
Cap. 1 - Warnings
1.11- Marking
There is a label on the top of the device
that identifies it. It shows the name of
the manufacturer, the full product identi fi ca tion code, the sup ply data
(voltage, input current), the serial number and the date of production.
1.12- Compliance with EC directives
Sicep S.p.A. declares that the ML-8 interface/peripheral complies with the
essential requirements of Directive 1999/05/EC, on the condition that the installation instructions on in chapter 7.3 are respected.
In particular, the device is declared to comply with the following standards:
EN 60950
EN 301 489-1, EN 301 489-3,
EN 301 489-7*
EN 300 220-1, EN 300 220-3,
EN 301 419-1*, EN301 511*
(art. 3.1.a 1999/5/CE)
(art. 3.1.b 1999/5/CE)
(art. 3.2 1999/5/CE)
* for version with BT-GSM only.
If the optional IRS-RT868 interface is installed, the device complies with the
CEPT/ERC/REC 70-03 recommendation (short range devices) on the condition that it is in no way altered, including the antenna.
A copy of the Declaration of Conformity can be found at the end of this manual.
1.13- Assistance
For any type of assistance, please consult your local Sicep dealer.
To download any free updates of firmware, utility programs or manuals, refer
to the Sicep S.p.A. website http://www.sicep.it
1.14- Shipping the device
In the event that the device has to be returned to Sicep for repair, pack it carefully, preferably in its original box, and attach the repair request form,
completed in its entirety, describing the defect in detail. The form can be
downloaded from the website. For more details, refer to the form above.
1.15- Warranty
Refer to the warranty certificate at the end of this manual.
1.16- Repairs
Refer to the repair request form that can be downloaded from the Sicep
S.p.A. website http://www.sicep.it
Pag. 3
ML-8
Cap. 2 - Technical Specifications
2 - Technical Specifications
Power supply:
Buffer battery:
• 220/230Vac 50Hz / 12 - 13,8Vdc
• Sealed 12V lead acid battery, maximum capacity 2.5
Ah (optional)
Absorption at 230V:
Absorption at 12V:
Inputs:
Outputs:
Maximum available current
from +12V output:
Protection devices:
• 50 mA typical, 60 mA max
• 150mA typical, 250mA max
• 8, 100KΩ, Pull-Up 100KΩ on 3,3V
• 8, Open Collector on GND, 100 mA max
• 350mA
• Anti-opening tamper device, LAN connection control
(polling with operational control centre), GSM signal*,
GSM module tamper device*
Transmission protocols to • NetP (LAN, GPRS*, SMS*)
MVSNet:
Protocols that can be received • Ademco Contact-ID, Ademco 4+2 Express, Ademco
as interface: Fast 4+8+1, Ademco 4+16+1
Configurations: • GSM interface model BT-GSM burglar kit model
IRS-K2
Radio frequency**: • 868 MHz, SRD
Interfaces for • female 9-pin serial connector, type-B USB connector
programming:
Programming software: • Sicep MVC
Dimensions (LxHxD): • 31x20x8cm
Weight: • 1,7Kg without battery,
approx 2.6 kg with 2.2 Ah battery
Environmental operating • Temperature: from -10° to +50° C
conditions: Humidity: from 20% to 80%
Enclosure • IP 41
protection rating:
Container material: • Polycarbonate
* With optional BT-GSM interface
** With optional IRS-RT868 interface
TRA-BT887 model power transformer characteristics
Primary voltage:
Power:
Secondary voltage:
Secondary current:
Insulation:
Safety:
Pag. 4
• 220-230V~, 50-60 Hz
• 25 VA
• 20 V
• 1.05 A
• Class B, 130°C
• Class I (according to EN60950)
Cap. 3 - Description
ML-8
3 - Description
The Multilink ML-8 interface/peripheral is a bidirectional device with 8 inputs
and 8 outputs which uses the TCP/IP protocol on the Ethernet network as its
main medium of communication.
It can send the variations of 8 logic inputs to the terminal, configurable as
needed, and has 8 outputs that can be used as remote controls or to report a
fault condition locally. Additional channels are available to report fault conditions or sabotage (no network, low battery, tampering etc.).
The unit can be equipped with a GSM interface to allow it to be used even in
the absence of the Ethernet network or as an emergency carrier. It is possible to use either the GPRS mode (with a very low cost) or SMS messages.
All traffic is sent to Surveillance Institutes that use the MVSNet management
system.
The unit can also be used as a telephone interface to convert reports from a
generic alarm control unit and transmit them with the TCP/IP (NetP) protocol
to MVSNet control units. It is therefore possible to allow the transmission of
alarms even in cases in which the PSTN telephone connection is not
available.
In this use, the interface can decode four Ademco-compatible protocols:
Contact-ID, 4+2 Express, 4+8+1 Fast (DTMF Ademco Fast) and 4+16+1.
In the operating control unit (MVSNet), the peripheral and interface
functions are managed separately, because:
- as a peripheral, it has its own code;
- as an interface, the alarm is retransmitted with the code assigned to
the control unit, in other words the interface is "transparent".
The ML-8 interface/peripheral can be programmed using the Sicep MVC
software for PCs with a serial or USB connection. This programming is simple and intuitive thanks to the graphic programming pages in Window style.
The parameters programmed in this way can be saved on file and reloaded
onto the PC, in order to build up personalised programming.
It is also possible to access remote programming, with a time-based or
packet (GPRS) GSM connection.
Pag. 5
ML-8
Cap. 4 - Structure
4 - Structure
The ML-8 interface peripheral is composed of:
- Logic card controlled by microprocessor;
- 25 VA power transformer;
- Polycarbonate container for wall mounting.
Accessories:
-
Emergency 2 Ah lead-acid battery
GSM interface model BT-GSM
Burglar kit consisting of IRS-RT868 receiver and BT-KT/2 radio control
Accessories for installation:
-
MVC software for programming from PC via USB / serial connection
P4
DL6
POWER
RESET
RETE
12V
+
- GND
RS 485
DL1
LEVEL
AUDIO
MODEM / LAN
TEST RESET
USB
MODULO GSM
DL3
BT-GSM
BT-MDA / BT-LAN
BATT
DL
TEST
DL
DL4
TAMPER
P3
TRASF.
SPEED
TX/RX
18-24Vac
P6
LINK
DL
DL
DL
OUT OUT OUT OUT GND IN
1
3
5
7
1
IN
3
IN
5
IN GND
7
FUSE
T 500mA 250V
ETHERNET
Pag. 6
2
4
6
8
2
IN
4
IN
6
IN GND L1
8
L2
T1
T2
ML-8
Cap. 5 - Description of the main card
5 - Description of the main card
DL
P41
BATT
DL
DL4
P2
DL3
POWER
RETE
J1
J2
X23
12V
+
- GND
RS 485
X23
TEST RESET
USB
P39
P3
18-24Vac
P6
POWER
LINK
SPEED
TX/RX
DL
DL
DL
1
3
5
7
1
IN
3
IN
5
IN GND
7
P40
ETHERNET
2
4
6
8
2
IN
4
IN
6
IN GND L1
8
L2
T1
T2
Pag. 7
ML-8
Cap. 5 - Description of the main card
Description of the Terminals
IN1..IN8
Inputs, impedance 100 KΩ, Pull-up 100 KΩ on 3.3 V
OUT1..OUT8 Open collector outputs on GND, maximum current 100 mA
T1-T2
Terminals for connecting to the control unit to be sent (simulated line).
Maximum current that can be supplied 26 mA (positive terminal: T2)
L1-L2
Terminals for connection to external telephone line
POWER
Terminals for connection to the power transformer
RS485
Terminals for connecting BUS RS485 (as an alternative to the P6 connector)
Description of the Connectors
P40
P6
P39
Connector for Ethernet (10/100 Mb/s)
Connector for BUS RS485 wire
USB programming connector
P2
Serial port connector for firmware programming/update
P41, P42
Connectors for radio control receiver model IRS-RT868
X23
J1, J2
Connectors for developments
Jumper for firmware update
1-2 Firmware Update
2-3 Normal Operation
Description of the Buttons
RESET
TEST
When pressed, this resets the device. The parameters programmed are not deleted.
Makes it possible to reset the parameters to the default values. To perform the operation,
press the TEST and RESET buttons simultaneously, release the RESET button and keep
the TEST button held down until the Power LED comes on. After the next power on, all the
parameters are reset to default value.
Description of the luminous signals (LEDs)
POWER
Green LED
Indicates that the stabilised voltage of 3.3 V is present and that the card
is correctly initialised.
BATT
Red LED
Low battery. Indicates that the supply voltage has dropped below 10.5
V and the transformer is not supplying current. When the voltage returns
to 12.5V, reactivation occurs.
RETE
Green LED
AC mains presence. Indicates that the 230V AC power supply is
present and the transformer is operational.
USB
Green LED
Indicates the electrical connection of the USB cable to the PC.
LINK
Green LED
When on, indicates the electrical connection of the Ethernet cable.
SPEED
Green LED
When on, indicates that the speed of the Ethernet network is 100 Mb/s.
When off indicates 10 Mb/s.
TX/RX
Green LED
The flashes indicate the transmission/reception of packets on the
network
Pag. 8
ML-8
Cap. 6 - Operation
6 - Operation
The following description assumes that the Multilink ML-8 peripheral/interface has already been configured and that the LAN connection is present.
6.1 - LAN MVSNet connection
When the device is switched on, the peripheral transmits a packet containing its IP address (KeepAlive) to the operational control centre. At this point,
the control centre transmits a polling message every 15 seconds and the peripheral therefore establishes that there is a connection with the control unit.
When, on the other hand, the polling messages do not arrive, the peripheral
sends a KeepAlive every minute, only stopping when the connection has
been restored. These times are fixed.
6.2 - Transmission of a spontaneous alarm (input change or
fault)
If the primary carrier (LAN) is available, the peripheral transmits the report. If
the carrier is not available and the GSM interface is, it attempts to send via
the GPRS connection. If this carrier is also not configured or the peripheral
does not receive a reply, it sends the message by SMS. This priority in the
choice of carriers is fixed.
6.3 - Inputs
8 terminal inputs are available with input impedance of 100 KΩ. The default
setting for the input is NC. In the resting state, it is earthed while when open, it
is in an alarm condition. Conversely, if the setting is NO, the resting state is
open and while the closed to earth state is in an alarm condition. Each input
has a special 100 kΩ pull-up resistor on +3.3 V, but is designed to withstand
input voltages of up to 14 V.
-
Input terminal voltage
Logic State
1,65V ÷ 14V
High
0 ÷ 1,65V
Low
If the input is disabled, it does not generate reports and if polled, it always returns the resting state.
If the input is passive, the changes do not generate reports but when
polled, the actual state is returned.
The Delay parameter defines the minimum time for which the new
state must remain in order for the change to be considered valid. The
default setting is 100 mS.
Pag. 9
ML-8
Cap. 6 - Operation
6.4 - Outputs
8 earthed Open Collector outputs are
available. The maximum current available is 100 mA. If they are used for
piloting relays, it is advisable to protect
them using a diode as shown in the
diagram.
+12Vcc
+
N.C.
OUTPUT
N.O.
Open
Collector
Protection
diode
1N4007
The outputs can be used as remote
controls which can be activated by the operational control centre and can be
programmed as static or impulsive.
It is possible to activate one of the outputs to report one or more system faults
locally. In this case, the associated output cannot be controlled by the operational control centre (if the unit attempts to do this, the peripheral returns the
message Command Refused).
- the "Reversed" parameter is used to invert the resting state and the active one: if enabled, the output is normally active and is deactivated
when commanded.
- The Change State button makes it possible to change the programming state or carrying out an activation test. If the output is impulsive, it
will naturally return to the resting state after the set time.
6.5 - Control channels (system faults)
The ML-8 peripheral/interface has a series of controls to monitor and transmit system faults. All controls, with the exception of No Mains Power and
MvsNET Connection control are activated by inserting a non-zero time in the
field while, in order to also associate transmission in the operational control
centre, it is necessary to enable the relative "Transmission Enabled" flag.
Possible faults are as follows:
- No mains power. The presence of the transformer AC voltage output
is monitored. If it is not available for longer than the set time, the relative event is generated.
- Peripheral tampering. The status of the microswitch that reports the
opening of the container is checked. If there is an alarm, the relative
event is generated.
- Peripheral battery. The 12 VDC supply voltage is checked. If this
drops to 10.5 V, the relative event is generated. When the voltage returns to 12.5V, reactivation occurs.
- No LAN line. The presence of the electrical connection of the Ethernet
cable is monitored. When this fails (cable disconnected or switch/hub
off) for longer than the time set, the relative event is generated.
- No LAN MvsNET connection. As already explained, the peripheral
continuously uses polling packets to monitor the TCP/IP to the
Pag. 10
ML-8
Cap. 6 - Operation
-
-
MVSNet operational control centre. If this fails for at least 4 minutes,
the relative event is generated. This time is fixed.
If the address of the operational control centre is programmed, this
event cannot be disabled. Only reporting to the control centre via a reserve carrier, if available, can be enabled/disabled, using the relative
flag.
No external PSTN line. If an outside telephone line is available, it can
be used as a "last backup carrier" or for remote programming a control
unit. These functions are available when the ML-8 is used as an interface to forward control unit reports.
In this case, the monitoring of the presence of the line can be enabled
by entering a time other than zero. When the line is missing, at the expiry of the time, the relative event is generated.
No GSM line. If the BT-GSM expansion card is present, registration on
the administrator network is monitored. If this is not available for longer
than the set time, the relative event is generated.
GSM module tampering. If the BT-GSM expansion card is present,
the opening of an optional tamper switch to be placed on the P9 terminals on the card is monitored, according to the table below:
Open terminals:
Shorted terminals:
-
Tamper at rest
Tamper in alarm mode
Connecting devices to the RS485. If the BT-GSM expansion card is
present, the connection on the RS485 bus is monitored. In the event of
a failure or sabotage, the relative event is generated, which is immediate (within seconds).
Radio control battery. If one or more BT-KT/2 radio controls are registered, this event indicates that the battery of a radio control has fallen
below the threshold of 6V.
6.6 - Radio controls
The ML-8 peripheral/interface can be fitted with an IRS-RT868 model radio
interface in order to receive BT-KT/2 model burglary radio controls. Up to 16
radio controls can be used, each of which is identified in an unequivocal
manner.
Each radio control has two programmable buttons that can be associated
with the panic or emergency functions or can activate one or two outputs,
static or impulsive. The associated outputs can nevertheless still be
activated by the operational control centre.
6.7 - Log function
All activities of the ML-8 peripheral/interface are stored in a log containing
the last 256 events. The oldest events are gradually deleted.
Pag. 11
ML-8
Cap. 6 - Operation
6.8 - DHCP protocol
The ML-8 peripheral implements the DHCP protocol which, if enabled,
makes it possible to automatically configure the IP address, the Subnet
Mask and gateway address.
A router is required on the network to implement this service.
6.9 - Remote programming
Using MVC software, it is possible to access remote programming in various
ways:
- Via LAN, with ML-8 equipped with static IP.
- Via LAN, with ML-8 equipped with dynamic IP and installer equipped
with static IP.
- Via GSM, with data connection with timed billing.
- Via GPRS, with connection and billing by traffic (see caution).
- From the operational control centre, using one of the methods described above.
The operations to be carried out and the parameters to program according to
the type of connection are described in the MVC Programming section : Remote assistance on page 36.
WARNING
WARNING!
via GPRS, billing is based on the amount of data exchanged, but
because the ML-8 peripheral uses dynamic MVC forms, even in
the absence of changes to the parameters, data exchange is always present, therefore, albeit with different costs, it is always
time-based billing.
6.10- BT-GSM interface
The ML-8 peripheral/interface can be equipped with the BT-GSM model
GSM/GPRS card which makes it possible to use the GPRS and SMS carriers to transmit information, both in the event of a fault or if the LAN
connection is not present.
The BT-GSM card is designed to be inserted into the ML-8 container but can
be used outside it, in all those cases where the installation so requires (e.g.
where the GSM signal is too low). The connection is made with the RS485
bus with four wires and the maximum connection distance is 200 metres.
The card can be used with a SIM card with an M2M contract, in order to reduce operating costs. To use the remote assistance in data mode
Pag. 12
ML-8
Cap. 6 - Operation
(time-based connection) there may be restrictions depending on the operator. Refer to the Installing the SIM Card chapter on page 19
WARNING
WARNING!
The BT-GSM firmware must be version 1.0.2 or later. Earlier versions are not compatible. In that case, as soon as the card is
registered on the ML-8, a warning message is displayed.
WARNING
WARNING!
The BT-GSM card can also handle SIMs where the PIN is activated. If the PIN is incorrect or missing, the ML-8 peripheral makes
only one attempt to enter the code, therefore if the peripheral is reset or switched off and back on again, the PIN code is entered
again. After three attempts, the SIM is locked and must be unlocked using the PUK. In this case, it is necessary to remove the
SIM from the module, insert it in a mobile telephone and enter the
PUK code.
6.11- Transmission of control unit reports
Use as a telephone interface
The ML-8 peripheral/interface is designed to be able to convert and transmit
telephone signals from alarm control units. The telephone cord leaving the
control unit (line) should be place on terminals T1-T2 of the interface.
When the control unit gets a line, the ML-8 interface generates the free line
signal and is ready to accept the call. The control unit can dial any number,
which will be ignored. At the end of the message, the interface will acknowledge receipt of the alarm using the appropriate tone (KissOff).
At this point, the interface will transmit the alarm to the operational control
centre using the primary carrier (LAN) or, if the GSM interface is present,
through a reserve carrier if the primary carrier is unavailable or out of order.
The report received from the control unit is converted and transmitted in full,
keeping the peripheral code of the control unit itself.
The following Ademco-compatible telephone protocols can be received:
- Contact-ID
- 4+2 Express (toni DTMF)
- 4+8+1 Fast (Ademco Fast or SuperFast 4+9)
- 4+16+1 (Ademco Fast extended)
On the simulated telephone line, the interface is able to provide a maximum
current of 26 mA.
Pag. 13
ML-8
Cap. 6 - Operation
6.12- Automatic PSTN line exchange function
When one or more conditions occur that mean it is not possible to transmit
signals through the configured carriers, the ML-8 interface activates the relay bypass and keeps it active for as long at these conditions remain. In this
way, the T1-T2 telephone input is placed directly on the L1-L2 line terminals.
If the telephone line from outside is placed on these terminals, the control
unit is able to transmit its reports in the traditional way.
For this reason, if such a connection is available, it is advisable to leave the
telephone programming of the control unit (e.g. telephone number of the recipient, transmission attempts etc.) unchanged. If, on the other hand, no
such connection is available, to get a line and connect to the simulator,
simply dial any digit.
The conditions that must occur for the automatic line bypass are as follows:
- if the control is enabled, the external PSTN line must be PRESENT;
- if the recipient IP address of the operational control centre is
configured via LAN, the MvsNET connection must have been absent
for at least four minutes;
- if the control is enabled, the LAN must be ABSENT;
- if the GSM module is present and the operational control centre recipient is configured (GPRS IP address or SMS number), the line must be
absent.
If the GSM module is not installed, the first three conditions are
sufficient.
6.13- Input PSTN line exchange function
Input 8 can be enabled to activate the line exchange relay on a time basis.
This happens when the terminal changes from OFF (closed to earth) to ON
(open). The activation time can be set between 1 and 240 seconds.
6.14- External PSTN line exchange function for remote
assistance
If the control unit can be configured via remote telephone assistance and a
telephone line is also available on site, it is possible to use a special manual
function (external PSTN) line control) that makes it possible to bypass the
ML-8 interface in order to access the control unit from outside.
The external line must be placed on the L1-L2 terminals. Programming mode
must be entered from the MVC and the Activate button (General page)
pressed once or several times. Each time the button is pressed, the connection time increases by five minutes and can reach a maximum of 30. After this
time, the external line is released and the control unit returns to normal
operation.
Pag. 14
Cap. 6 - Operation
ML-8
6.15- Remote programming (without optional BT-GSM card)
Remote access via LAN can take place in these two modes of use:
- the peripheral/interface has a static IP reachable from the outside
(public);
- the peripheral/interface has a dynamic IP and the installer's PC has a
static IP reachable from the outside (public).
In the first case, the installer can connect to the ML-8 peripheral/interface via
MVC if it knows the following parameters: IP Address, Peripheral Code,
Password (if programmed).
In the second case, the IP address of the installer's PC must be entered in
the "IP Address/Hostname" field of the peripheral's Communicator page on
the MVC Remote Programming sub-page. The installer can connect to the
peripheral from the PC specified by this address if it knows the Peripheral
Code and Password parameters (if programmed).
6.16- BT-GSM model GSM interface operation
It is assumed that the interface is connected and the peripheral is programmed correctly.
When the GSM interface is switched on, initialisation of the GSM/GPRS
module begins. At this stage, the five "LEVEL" LEDs light up in a backwards
and forwards sequence.
At the end, when registration on the GSM network is successful, the five
LEDs light up depending on the intensity of the signal. The more LEDs are lit,
the higher the signal received.
The frequency of the flashes of the green DL1 LED indicates the registration status:
1 flash approximately every 4 seconds ⇒ GSM registered on the
network
1 flash approximately every second
⇒ GSM being registered.
The red DL6 LED indicates the connection on the 485 bus:
1 flash approximately every 2 seconds ⇒ RS485 connection OK
Slow ON/OFF flashing
⇒ Device not registered,
faulty or the RS485 cable
is disconnected
Pag. 15
ML-8
Cap. 6 - Operation
6.17- Spontaneous transmissions
The management of spontaneous transmissions, in both peripheral and interface mode, takes place automatically with a set priority:
- if available, the peripheral/interface continues to try to send via LAN;
- as the first reserve carrier, it attempts to send via GPRS (the IP address must be programmed in the "IP Address/GPRS Hostname"
field);
- as a second reserve carrier, it sends the message via SMS (the
recipient SMS number must be programmed on the General page and
the number of the Service Centre must be programmed on the GSM
module page).
It is possible to monitor the progress of operations (initialisation, network access, reception, transmission) during MVC programming through the log
window on the Communicator page.
Alternatively it is possible to connect directly with the MVC on the BT-GSM
module via a serial link. This control page (operation log) provides more detailed information, useful in the event of malfunctioning in order to identify
the problem.
6.18- Polling
The management of polling occurs in two distinct modes, depending on
whether the carrier is GPRS or SMS.
In the case of GPRS, the operational control centre must make a call to the
number on the SIM card. Once the peripheral has acknowledged that the
number is not one of the "special" ones, it hangs up and activates the communication via GPRS to the IP of the operational control centre (”IP
Address/GPRS Hostname" parameter), equal to a spontaneous transmission.
In the case of an SMS, the operational control centre must send an SMS
containing the polling message to the peripheral, which only ever responds
to the programmed recipient ("SMS number" parameter).
The numbers considered as "special" are those that, if detected, activate
special functions. In the Multilink ML-8 peripheral/interface, there is currently only one special number, the one programmed in the "Number for
remote programming GPRS / GSM DATA" parameter on the Communicator
page, Remote Programming (MVC) sub-page.
Pag. 16
Cap. 6 - Operation
ML-8
6.19- Remote programming via BT-GSM
When the peripheral detects a call coming from the number programmed as
the "Number for remote programming GPRS / GSM DATA", it checks
whether an IP address is programmed in the "IP Address/Hostname" parameter on the "Remote Programming (MVC)" sub-page.
If the ad dress is pres ent, the pe riph eral hangs up and ac ti vates
communication via GPRS to this IP address, which must correspond to a PC
with the MVC software in TCP/IP mode waiting.
If the address is not present, the device responds in data mode, using the
GSM module as an analogue modem at 9600 bps. This call must be made by
an analogue modem.
Pag. 17
ML-8
Cap. 7 - Installation
7 - Installation
7.1 - Installing optional devices
Installing the IRS-RT868 receiver for radio controls
Refer to the diagram.
- Switch off the ML-8 peripheral.
- Insert the card in the two P41-P42 connectors. The antenna must be
located on the left-hand side (opposite the power transformer).
The control unit will automatically detect the presence of the module the next
time it is switched on.
WARNING
WARNING!
The incorrect insertion of the card may cause damage to it and/or
to the ML-8 peripheral.
Installing the BT-GSM module (assembling inside the
ML-8 peripheral)
-
Refer to the instructions accompanying the module.
Switch off the ML-8 peripheral.
Insert the four plastic spacers supplied in the module fixing holes.
Secure the module inside the container using the two long screws provided.
Connect the RS485 four-wire cable between the connector [5] on the
module and the connector P6 (485) on the logic card of the ML-8 peripheral or, alternatively, use the RS485 terminal block for connection,
respecting the serigraphs shown. In this case, the maximum distance
that can be used is 200 metres. Use a four-wire unshielded cable.
GND
ML-8
-485
+485
RS485
+ - +12
+12
BT-GSM
+12V
+ RS485
- RS485
GND
Pag. 18
ML-8
7.2 - SIM CARD installation
If the Multilink ML-8 peripheral/interface is equipped with a BT-GSM card, it
requires a SIM card, even for data only, enabled for GPRS traffic. Ideal use
requires an M2M (Machine to Machine) SIM. SIM cards of this type are enabled to receive data calls (non-transparent asynchronous 9600 bps).
Be aware that some operators introduce limitations for receiving calls from
landlines, as shown below. This is important if you plan to carry out remote
assistance in connection mode with time-based billing.
- Vodafone operator: connection in DATA mode with a call originating
from an analogue modem on a landline is always possible;
- TIM operator: connection in DATA mode with a call originating from an
analogue modem on a landline is only possible if the SIM card has an
additional number to receive calls from landlines (must be requested);
- Wind operator: connection in DATA mode with a call originating from
an analogue modem on a landline is not possible.
WARNING
WARNING!
The information given above is valid as of 1/10/2010, for use in Italy
with Vodafone, TIM and Wind operators. These operators may
vary these conditions, even significantly, without notice.
The SIM card must be inserted into the appropriate compartment.
WARNING
WARNING!
Before handling the SIM card, ensure that your hands are not
sources of static electricity (it is advisable to touch an earthed
metal mass in order to discharge it). Take great care not to damage
the SIM card and/or the GSM module.
7.3 - Installing the ML-8 peripheral/interface
-
-
Choose the place where the device is to be installed. If it is equipped
with the BT-GSM module, ensure that the level of signal is adequate.
To do this, you can use your own mobile phone or program the device,
power it (even only by batteries) and check that, at the end of the initialisation procedure, at least two yellow LEDs (LEVEL) are lit up on the
BT-GSM.
If it is impossible to remove the BT-GSM card (signal too low), remove
the card and install it in a position where the signal is sufficient. Connect the BT-GSM to the main logic card via a 4-wire cable (as
explained on page 18).
Pag. 19
ML-8
-
GND
Secure the device to the wall using at least three 4 mm diameter
screws.
- Wire the power network as shown in the drawing,
using only the hole located under the terminal
block. Since the device is Class I, the earthing
con nec tion is man da tory. Con nect the yellow/green wire coming from the electrical system
to the relative terminal.
NF
As the device does not have a switch, a bipolar
disconnector (switch) with contact opening of at least 3
mm must be envisaged to interrupt the power supply.
- Sicep S.p.A. will not be held liable in the event of
connections with the electrical mains that are not
made to the highest standards of workmanship.
- Wire the signal cables (inputs/outputs) using the three pre-sheared
holes. It is advisable to short circuit all the unused inputs to earth
(GND).
+12Vcc
+
N.C.
- The outputs used to pilot the relays must be protected with a
OUTPUT
diode connected in parallel to the
relay coils, as shown in the diaN.O.
gram. The diode used may be the
Protection
Open
diode
1N4007 type.
Collector 1N4007
- The +12V output is not protected
and should only be used to power
the device connected to the RS385 bus (BT-GSM). The maximum current that can be supplied without the backup battery is 500 mA.
WARNING
WARNING!
If the BT-GSM card is installed, the 12V buffer battery must be
used.
WARNING
If the device is used as a telephone interface, bring the alarm control
unit telephone output (LINE) to the T1 and T2 terminals.
If you want to bring back the external telephone line to the interface,
connect it to terminals L1 and L2.
WARNING!
Any modifications to the telephone system must only be carried
out by authorised personnel.
Pag. 20
Cap. 8 - Programming
ML-8
8 - Programming
The ML-8 peripheral/interface is programmed using the Sicep MVC software for PCs, locally via a USB or serial connection, or remotely via LAN,
GPRS or GSM with data connection.
Programming locally via USB/serial connection is always possible, while remote programming can only take place if the device has been configured
correctly in order to do so.
8.1 - Installing the USB driver
The first time the USB cable is connected to the peripheral, drivers will be requested for correct operation. These drivers can be supplied on CD. They
are also available on the Sicep S.p.A website.
When prompted, insert the CD into the PC and specify the path for that unit.
NOTICE
N.B. the drivers are the same used for the IRS peripherals/control
units: if they are already installed, they will not be requested.
How to identify the USB COM port
Once the drivers have been installed correctly, the USB connection is seen
as an additional COM port. The number assigned to the port must be entered in the connection window of the MVC program. To find the assigned
number, proceed as follows:
- Connect the device to the PC;
- click on the Start Button ⇒ Settings,
Control Panel ⇒ System ⇒ Hardware,
Managing Peripherals or Devices ⇒ Ports (COM and LPT).
The port we are looking for is called "USB CDC serial port emulation".
NOTICE
N.B. Depending on the operating system installed on the PC, the
steps described may be different.
Pag. 21
ML-8
8.2 - MVC programming
How to perform connection and programming with a
serial or USB connection
NOTICE
Once the MVC pro gram has been launched, click on Connect
.
Set the following parameters:
Direct connection, Auto;
PC port: choose the one
used.
Enter the password only if it has been
programmed. It is not used on the default setting, therefore it can be left
blank.
Press OK.
Once connected, a menu appears on
the left with 8 pages with which it is possible to access all
programming.
At the end, press the Disconnect button
.
The programming pages are all dynamic so, every time a parameter is
changed, press TAB to make the change effective.
N.B. If the USB connection is interrupted without disconnecting
from the MVC, the PC may no longer be able to manage the USB
port correctly. In this case, it may be necessary to restart the MVC
software or the PC.
Pag. 22
ML-8
System Page
r Equipment Code:
(range 1-9999)
Default 100
Enter the numerical code used for the bidirectional peripheral
mode (transmitting the inputs, activating the outputs)
r Password
(range blank-99999) Default blank
Password for MVC programming, which is required for all types
of connection (local or remote). Up to 5 digits are permitted. If
you do not want to use the password, leave this field blank.
Times
r AC mains loss detection
(range 1-99)
def. 60
Time delay in minutes to generate the "No 230 VAC power"
event. This control cannot be disabled.
r LAN fault detection
(range 0-99)
def. 0
Time delay in minutes required to generate the "No network
connection" event. This event is used to detect the lack of electrical connection of the Ethernet cable. Setting 0 disables the
control.
r GSM fault detection
(range 0-99)
def. 0
Time delay in minutes required to generate the "No registration of
GSM module on network" event (only if the optional BT-GSM card
is present). Setting 0 disables the control.
Pag. 23
ML-8
r External PSTN fault detection
(range 0-99)
def. 0
Time delay in minutes required to generate the "No PSTN line"
event. Setting 0 disables the control. This control should only
be enabled if the connection to the external line is present.
r Automatic test
(range 0-99)
def. 0
Time in hours that elapses between two Automatic Test transmissions; enabling it only makes sense if the peripheral does
not have a LAN connection to the operational control centre.
Setting 0 disables the transmission of the automatic test.
r Keepalive LAN
(range 0-240)
def. 10
Time in minutes that elapses between the spontaneous messages sent to the operational control centre via LAN in order to
keep the connection active.
r Bypass from Input 8
(range 0-240)
def. 0
Duration in seconds of the activation of the PSTN line bypass
relay activated on the opening front of Input 8. This function
must be enabled on the Inputs page.
TX system faults section
This section is used to enable the transmission of the relative event to the operational control centre.
Each event is managed if the corresponding time programmed is not set to
zero. The only exception is the LAN MVSNET event (loss), which is always
managed and the time is set to four minutes.
r Output activated on system fault
(range None - Output 1..Output 8)
def. None
Makes it possible to associate the activation of the desired output in the event of one or more system faults.
NOTICE
N.B. The output is activated only if the fault is maintained for longer
than the set time. For the LAN MvsNET connection event (loss), the
time is set at 4 minutes.
Pag. 24
ML-8
Bypass PSTN
r Start (+5min) button
Pressing this button activates the relay that bypasses the internal telephone simulator for 5 minutes. The two terminals T1
and T2 are taken to L1 and L2, respectively. Pressing the button several times increases the connection time in 5-minute
intervals.
r Stop button
Pressing this button disables the bypass relay immediately.
Communicator Page
Surveillance sub-page (MvsNET)
r IP Address/ Hostname LAN
(range 1-32 characters)def. 192.168.0.1
En ter the IP ad dress (for mat xxx.yyy.www.zzz) or the
hostname of the recipient MvsNET system via LAN.
r IP Address/Hostname GPRS
(range 1-32 characters) def. Blank
hostname of the recipient MvsNET system via GPRS.
r TCP Port
(range 0-9999)
def. 9016
Port for the TCP/IP connection. Change only if necessary or for
special uses.
Pag. 25
ML-8
r UDP Port
(range 0-9999)
def. 9001
Port for the transmission of UDP packets. Change only if necessary or for special uses.
r SMS number
(max. 20 characters)
def. Blank
Enter the recipient number for the transmission of SMS to the
MvsNET system.
Communication State Panel
This panel contains indicators and buttons to carry out connection tests to
the MvsNET system.
- Green light: Communication successful / confirmation received.
- Yellow light: Test in progress / carrier busy.
- Red light: Communication failed / confirmation not received
Log Communicator
This window shows the last operations performed by the ML-8 peripheral/interface for diagnostic purposes.
Installer sub-page (MVC)
r IP Address/Hostname (range 1-32 characters)
def. Blank
hostname of the installer's PC via LAN.
r UDP Port
(range 0-9999)
def. 9001
Port for the transmission of UDP packets to the installer's PC.
Change only if necessary or for special uses.
r Number for remote programming GPRS / GSM DATA
(max. 20 digits)
def. Blank
Enter the number to recognise the call from the installer to activate remote assistance mode in GPRS mode (MVC in TCP/IP
mode and waiting).
Pag. 26
ML-8
LAN page
r Automatic
configuration (DHCP)
def. not enabled
If checked, this activates the DHCP protocol for the automatic
configuration of the network parameters.
NOTICE
N.B. The automatic configuration operation may take a few seconds, depending on the type of DHCP server.
r Hostname
def. Blank
Enter the device Hostname, if necessary.
r IP Address
def. Blank
Enter the IP address assigned to the ML-8, if you are programming without DHCP.
r Subnet Mask
def. 255.255.255.0
Enter the value of the subnet mask, if you are programming
without DHCP.
r Gateway
def. Blank
Enter the gateway address, if you are programming without
DHCP.
r Automatic configuration DNS server
def. not enabled
This option can only be activated if DHCP is enabled.
Pag. 27
ML-8
r DNS Server 1
def. Blank
Enter the address of the primary DNS server, if you are programming in manual mode.
r DNS Server 2
def. Blank
Enter the address of the secondary DNS server, if you are programming in manual mode.
GSM page
This page shows different content depending on whether the optional
BT-GSM module is registered or not.
r Add device button
Makes it possible to register the BT-GSM module. After pressing the button, press the Test button on the BT-GSM card.
r Cancel button
Makes it possible to cancel the registration attempt.
r Delete config RS485 button
This button is enabled by checking the appropriate flag. Makes
it possible to delete a faulty GSM module.
Pag. 28
ML-8
r Connection state
Read-only field, makes it possible to display whether the 485
cable is connected correctly.
r Tamper state
Read-only field, makes it possible to display the state of the optional tamper connection to the P9 terminals.
Configuration
r APN
def. web.omnitel.it (Vodafone)
Enter the correct APN depending on the operator. It is also possible to specify an APN not included in the default options.
r SMSC number
def. 393492000200 (Vodafone)
Enter the number of the Service Centre for the transmission of
SMS messages, depending on the operator.
Vodafone
TIM
Wind
WARNING
393492000200
393359609600
393205858500
WARNING!
The information given above is valid as of 1/10/2010, for use in Italy
with Vodafone, TIM and Wind operators. These operators may
vary these conditions, even significantly, without notice. Contact
your operator.
Pag. 29
ML-8
r PIN (range: Blank / 4 caratteri)
def. Blank
Enter the PIN of the SIM, if used.
WARNING
WARNING!
When using a SIM with the PIN activated, if the PIN is incorrect or
missing, the ML-8 peripheral makes only one attempt to enter the
code, therefore if the peripheral is reset or switched off and back on
again, the PIN code is entered again. After three attempts, the SIM
is locked and must be unlocked using the PUK. In this case, it is
necessary to remove the SIM from the module, insert it in a mobile
telephone and enter the PUK code.
Current Modem State Section
This section is useful in order to make an initial diagnosis of the module.
PIN
GSM
Green indicates that the PIN has not been requested or has been accepted
correctly.
Red indicates that the PIN is incorrect or missing.
Green indicates that the GSM is correctly registered on the network.
GPRS
Green indicates that the GSM cell in which the module is registered supports this
protocol.
Initialisation
device
Green indicates that the GSM module is responding correctly to commands and
the initialisation procedure has been completed successfully.
Internet
connection
Green indicates that you are connected to the Internet via GPRS
Remote Host
Connection
GSM Level
Green indicates that a correct data exchange took place with the MvsNET
control centre.
This bar indicates signal strength. If it is green, this indicates that the level is
sufficient. If it is red, this indicates that the level is insufficient.
r Enabled Flag
Unchecking this flag disables, but does not delete, the device.
r REPLACE DEVICE Button
This button is activated only if the device has been disabled
and makes it possible to replace the faulty device with a new
one while keeping the programming of the previous one.
r DELETE DEVICE Button
This button makes it possible to delete a faulty device.
Pag. 30
ML-8
Input page
r Enabled Flag
def. Checked
Makes it possible to disable the corresponding input. Once the
input is disabled, it does not generate reports and if polled, it always returns the resting state.
r Description Field
(max. 18 characters) def. Input 1..8
Enter a brief description of the input.
r State Light
Indicates the logic state of the input: green, input resting, red,
input in alarm mode.
r Mode
(range NC/NA)
def. NC
Establishes the physical state of rest and alarm of the terminal:
NC NA -
resting if connected to GND, alarm if open
(voltage > 1,65V)
alarm if connected to GND, resting if open
(voltage > 1,65V)
r Passive
def. not enabled
If enabled, changing the input does not generate reports but, if
polled, returns the actual state.
r Delay
(range 100/200/500/1000/2000/4000 mS)
def. 100mS
Sets the minimum time necessary to consider the variation of
an input as valid. Makes it possible to increase immunity to interference picked up by the cables.
Pag. 31
ML-8
r Bypass external PSTN control
def. Not enabled
If checked, input 8 is used exclusively for activating the line exchange relay. Activation takes place when the terminal is
opened for the time set on the System page.
Output Page
r Description Field
(max. 18 characters) def. Output 1..8
Enter a brief description of the output.
r State Light
Indicates the physical status of the output (transistor open collector)
Grey - Output not activated
Green - Output activated (transistor conductive)
r Monostable Flag
def. not checked (static output)
If enabled, the output operates in a monostable way and is deactivated at the end of the set time.
r Pulse dur. (sec)
(range 1/5/10/30/60/120/240 secondi)
def. 5
Establishes the duration of activation if the output is programmed as the impulsive type.
Pag. 32
ML-8
r Reversed Flag
def. not inverted
If enabled, this inverts the physical state of the output. The transistor is conductive when the output is resting while it switches
off when the output is active.
r Change state Button
Makes it possible to vary the state of the output. If it is impulsive,
it returns to the rest state at the end of the set time.
Radio Controls Page
On this page, the BT-KT/2 radio controls are configured. To register them,
proceed as follows:
- If the radio control had already been
registered on another system, reset the
configuration (refer to the drawing at the
side):
-
• Hold down the keys
and TEST
for at least 10 seconds;
• when all the LEDs light up, the configuration has been deleted.
Press the "ADD DEVICE" button at the
bottom of the MVC page.
P
P
Press the keys P and
on the
radio control keep them pressed until
the LED
lights up. An audible signal is given as confirmation.
Pag. 33
ML-8
-
Once registered, the entry will appear with KT next to it.
Repeat the operation to register all the other radio controls.
At the end, press the button corresponding to the radio control to configure.
r Map Button
Returns to the radio control map
r Buttons <<>>
These allow you to scroll the list of radio controls without going
from the map every time.
r Description Field
Enter an identificatory description of the radio control.
Battery Section
r Last reading
Shows the last battery voltage value read. This information is
lost when the card is reset.
r State
Indicates the battery state (low if less than 6V).
r Function key P
(range: Disab./Panic/Emergency/Output 1..8)
Associates the desired action with the key P
Pag. 34
ML-8
r Function key
(range: Disab./Panic/Emergency/Output 1..8)
Associates the desired action with the key
r Enabled flag
def. Enabled
Makes it possible to disable the radio control leaving it registered on the peripheral.
r DELETE DEVICE button
Makes it possible to delete a faulty radio control. The button is
enabled when the radio control is disabled (by unchecking its
flag).
Log Page
This page displays the log of the last 256 operations performed by the ML-8
peripheral/interface.
Pag. 35
ML-8
8.3 - MVC programming: Remote assistance
Remote assistance refers to the ability to connect remotely to the ML-8 peripheral/interface in order to change the programming parameters.
Using MVC software, it is possible to access remote programming in various
ways:
•
•
•
•
Via LAN, with ML-8 equipped with static IP.
Via LAN, with ML-8 equipped with dynamic IP and installer equipped
with static IP.
Via GSM, with data connection with timed billing.
Via GPRS, with connection and billing by traffic.
The ML-8 peripheral/interface must already have been suitably programmed. Re mote as sis tance can not be used to per form ini tial
programming during installation.
Remote connection to packets on LAN; ML-8 with static
IP
This mode enables connection via LAN or via the internet, if the network and
programming allow this. The peripheral must have a static IP. This is the
most simple connection.
ML-8 / Router Requirements
-
The control unit must be correctly configured to access the network (IP
address, Subnet Mask, Gateway);
The router that connects the ML-8 peripheral to the network should
have the 8000/TCP port open.
Installer side requirements
-
Pag. 36
The installer must have a PC with internet access;
On the router that connects the PC to the internet, the 9001/UDP and
9016/TCP ports must be open;
The MVC software must be version 1.22 or later;
The following must be known: Peripheral code, password (if used), IP
address of the ML-8.
ML-8
How to connect
-
-
Open up the MVC software and click Connect.
TCP/IP (static);
IP address of the peripheral;
Peripheral code (default: 100);
Password (if used; not
used by default).
At the end of programming, press the
Disconnect
.
button.
Remote connection to packets on LAN; ML-8 with dynamic IP.
-
The control unit must be correctly configured to access the network (IP
address, Subnet Mask, Gateway);
The static IP address of the installer's PC must be entered in the IP Address/Hostname field on the MVC Communicator page - Remote
programming (MVC) sub-page;
The router that connects the ML-8 peripheral to the network should
have all the output ports open.
-
The installer must have a PC with internet access configured with a
public static IP;
9016/TCP input ports must be open;
The following must be known: Peripheral code and password (if used)
of the ML-8.
Pag. 37
ML-8
How to connect
-
Open up the MVC software and wait a few minutes, until the appearance on the bottom bar of the message KeepAlive cp=xxxx where xxxx
is the code of the peripheral to be connected.
-
Click Connect
.
TCP/IP (dynamic);
used by default).
At the end of programming, press the
-
Disconnect
button.
Remote connection via GSM
with time-based billing (DATA connection via modem)
-
The control unit must be equipped with a correctly configured BT-GSM
interface;
The SIM Card inserted in the BT-GSM must be able to respond to
DATA calls. Check the operator requirements as shown on page 19.
Nel campo "numero risveglio GPRS/GSM DATI" deve essere inserito
il numero dell'installatore da cui proverrà la chiamata tramite modem.
-
-
Pag. 38
The installer must have a PC with a GSM or analogue modem with a
serial connection to the PC (or even in emulation, the important thing is
that it is seen as connected to the PC via a COM port). If the modem is
an analogue PSTN, there may be restrictions. Please check the information on page 19 - Installing the SIM CARD.
The following must be known: DATA telephone number of the SIM, peripheral code and password (if used) of the ML-8.
ML-8
How to connect
-
-
Open up the MVC software and click Connect
.
Modem;
PC port connected to the modem;
speed: 9600;
telephone number of the SIM of
the ML-8;
used by default).
Press OK.
The modem gets a line by connecting
to the ML-8 peripheral, which responds on the first ring.
At the end of programming, press the Disconnect
button.
Remote connection via GSM/GPRS with packet-based
billing (GPRS connection); Installer's PC with static IP
-
The control unit must be equipped with a correctly configured BT-GSM
interface;
The SIM Card inserted in the BT-GSM must be able to respond to calls.
Check the operator requirements as shown on page 19.
On the MVC Communicator page - Remote Programming (MVC)
sub-page, there must be the number of the installer from which the ring
will come via modem or telephone. The filed is called "Number for remote programming GPRS / GSM DATA".
On the same page, the static IP address of the installer's PC must be
entered in the "IP Address/Hostname" field.
-
The installer must have a PC with internet access configured with a
public static IP;
An analogue or GSM modem or a telephone* to ring the SIM of the
ML-8; the number it is calling from must be known and should already
Pag. 39
ML-8
have been entered by local programming in ML-8 (Number for remote
programming GPRS / GSM DATA).
WARNING
*WARNING!
this option (awakening ring made by a telephone) can be used only
if the SIM inserted in the BT-GSM is NOT an M2M SIM. Otherwise,
to make the connection, use the "TCP/IP waiting" mode without
awakening ring.
-
9016/TCP input ports must be open;
The following must be known: DATA telephone number of the SIM, peripheral code and password (if used) of the ML-8.
How to connect
-
-
Pag. 40
Open up the MVC software and click Connect
TCP/IP waiting with awakening
via modem;
PC port connected to the modem;
Telephone number of the SIM
inserted in the BT-GSM;
used by default).
Press OK.
.
The MVC software will call the SIM via the modem and will hang up automatically;
Within about ten seconds, the peripheral will automatically connect to
the MVC software in standby mode.
At the end of programming, press the Disconnect
button.
If the SIM inserted in the BT-GSM is NOT and M2M SIM, the activation
ring can also come from a normal telephone and the modem is not necessary. Otherwise, to make the connection, use the "TCP/IP waiting"
mode without awakening ring. The number inserted in the ML-8 peripheral "Number for remote programming GPRS / GSM DATA" must
be one for the phone being called from.
ML-8
Cap. 9 - Special Operations
9 - Special Operations
9.1 - Restore factory configuration
This operation will reset all the parameters to the default value. Any password to access programming is cleared.
Operating procedure:
-
Remove the ML-8 peripheral/interface cover.
Press the TEST and RESET buttons on the logic card at the same
time.
Release the RESET button, keeping the TEST button pressed until the
POWER LED lights up.
Once the button has been released, the POWER LED will go off. When
it lights up again, the operation is complete.
9.2 - Firmware Update
This operation loads a new version of the program into the non-volatile
memory. It can only be performed locally and via the serial port.
WARNING
WARNING!
The firmware update must be performed only when absolutely
necessary and after consultation with the Sicep S.p.A. technical
support.
WARNING
WARNING!
The operation may lead to the loss of the control unit configuration.
Requirements
-
PC with a serial port or PC with a Sicep IF-USB232 adapter
FlashProgrammer software version 1.4.4. or later;
Pin-to-Pin 9-pole serial cable
ML-8 firmware release, .hex format
Operating procedure:
-
Remove the ML-8 peripheral/interface cover.
Move the jumpers J1 and J2 to position 1-2.
Connect the serial cable to connector P2.
Launch the FlashProgrammer program.
Select the NXP LPC2368 device and the COM port used.
Pag. 41
ML-8
Cap. 9 - Special Operations
NOTICE
N.B. if the heading ML-8 is not present in the list of devices, set
BiTech BT-436 (NXP LPC2368).
NOTICE
N.B. If using the IF-USB232 adapter, to find the number of the assigned COM port, refer to the procedure indicated on page 21; in this
case the device is listed in the COM ports as "USB serial port".
-
Pag. 42
Select Baud Rate 115200. The clock value is irrelevant.
Press the Open File button and select the new firmware release
(.hex).
Press the Program Transfer button and wait until the end of the operation.
Bring the two jumpers J1 and J2 to the original position on 2-3 and
press the RESET button.
Cap. 10 - Appendix 1 Definitions and abbreviations
ML-8
10 - Appendix 1 Definitions and abbreviations
APN
Area or system
Operational control centre (or
control centre)
Control unit
Access Point Name. In the GPRS transmission system, this identifies the
name of the network according to the operator used.
Technical term referring to an alarm control unit indicating a grouping of
zones.
Manned location where all reports sent by Sicep peripherals are collected.
Special equipment operated by skilled personnel is found here.
This refers to a generic alarm control unit.
Default
Indicates that the value of the parameters at the time when the device leaves
the factory..
DHCP
A protocol that allows an IP address to be assigned to a device requesting it
automatically via a special server.
DNS (server)
EEprom
Server that makes it possible to convert the name assigned to a device
(hostname) into its assigned IP address.
Indicates a non-volatile device memory.
Event
Any change in an internal or external logic state of a device (peripheral or
control unit). This causes a local action and/or generates an alarm
transmission or reset.
Firmware
Indicates the management software for a device, stored in a non-volatile
memory on the device itself.
Flash
FlashProgrammer
Indicates a non-volatile device memory.
Software per PC sviluppato da Sicep per l’aggiornamento dei prodotti di
nuova generazione.
Gateway
Server that has the task of routing messages addressed to devices that are
outside their local network (LAN).
GPRS
General Packet Radio System, a packet communication system which uses
the normal GSM network
GSM
Hostname
Mobile telephone system with global coverage.
Name assigned to a device on an IP network. It is converted into the
corresponding numerical address by a DNS server.
Multilink Interface
This refers to the ML-8 product.
or Peripheral
IP (address)
LAN
MVC or Sicep MVC
MVS-Net
M2M
Numeric code that uniquely identifies a device connected to a TCP/IP
network.
Local Area Network, indicates a TCP/IP network with a limited number of
local addresses.
Multi Vectorial Configurator, Client software for PCs developed by Sicep for
installing and configuring next-generation Sicep products.
System developed by SICEP for managing the alarms at the operational
control centre.
Machine to Machine, a SIM with a special contract that only allows the
transmission of data and SMS.
Pag. 43
ML-8
Cap. 10 - Appendix 1 Definitions and abbreviations
NETP
PC
Personal Computer. To use the SicepMVC software, it is necessary to have
the Windows® 2000/XP/Vista/7 operating system
PSTN
Public Switched Telephone Network, refers to the normal public switched
telephone line.
RS485
Standard for data transmission in serial mode on two wires. In Sicep devices,
it identifies a system for connecting auxiliary devices via cable, using a bus
that also includes an earthing wire (GND) and a wire for +12V power.
SIM
Subscriber Identity Module, the electronic card provided by a mobile operator
that is inserted in the GSM communicator interface.
SMS
Short Message Service, indicates a protocol for transmission of information
on the GSM network via messages.
Subnet Mask
(address)
Pag. 44
General-purpose communication protocol for transmission of information
between next-generation Sicep peripherals and the operational control
centres.
Numeric code that allows the peripheral to determine whether the recipient of
the messages is within its LAN or not, and if not, the peripheral sends the
message to the Gateway, which will route it correctly.
TCP (port)
Outgoing port needed for the transmission of information to MVSNet.
UDP (port)
Outgoing port needed for the transmission of information to MVSNet and/or
to the installer’s MVC software.
Zone
In an alarm control unit, this indicates a terminal for connection to a sensor
via cable, or to a sensor via radio.
ML-8
Cap. 11 - Appendix 2 Table of Contact ID codes for events
11 - Appendix 2 Table of Contact ID codes for
events
The Contact-ID codes transmitted for system faults are listed below. Unless
specified otherwise, the event is associated with zone 0.
Event
Code
Zone
Description
No LAN
E350
Communicator Fault (generic)
No GSM
E351
Line 1 Fault
No PSTN
E352
Line 2 Fault
Loss of LAN MvsNET connection
E356
Loss of control centre polling
No AC power
E301
No power
Low battery
E302
Low system battery
Tamper
E137
Loss of GSM module on RS485
E333
301
System expansion module: fault
GSM tamper
E341
301
System expansion module: tampering
Panic
E120
101..116
Emergency
E101
101..116
Radio control battery
E302
101..116
Tampering with the control unit
Radio controls:
For the radio controls, the zone identifies the device in this way:
Radio control 1: 101
Radio control 2: 102
...
Radio control 16:
116
Pag. 45
ML-8
Cap. 12 - Appendix 3 Troubleshooting
12 - Appendix 3 Troubleshooting
This table does not attempt to solve all possible faults. It shows the main errors and the respective solutions. If it is not possible to solve the problem,
contact your local Sicep technical support service.
General
PROBLEM
POSSIBLE CAUSE
SOLUTION
The peripheral does not come on
when powered at 230V~
Blown fuse
Check the fuse located in the power
transformer terminal block and
replace it if necessary with one of the
same time (500 mA delayed)
The peripheral does not come on
when battery-powered
Low battery
Replace the battery
False contact on terminals
Check the terminal contacts
MVC programming
PROBLEM
It is not possible to access MVC
programming in direct serial
connection mode (error:
timeout).
programming in direct serial
connection mode (error: AUTH:
Access Denied).
programming in USB connection
mode (error: port not
present/bad port: COM xx)
Pag. 46
POSSIBLE CAUSE
SOLUTION
The serial cable is not connected
correctly or is of the wrong type
Check the cable connection again.
Ensure that a Pin-To-Pin serial cable
is being used. Try replacing it.
Jumpers J1-J2 in the wrong position
(1-2)
Move the jumpers to position 2-3
The serial port used is not the correct
Identify which serial port is being used
one
The connection settings are incorrect
Check the connection settings as
shown on page 22
A non-compatible USB/serial adapter
is being used
Use the Sicep IF-USB232 adapter.
Contact your local Sicep dealer.
Password missing or wrong
Try resetting the password, if it is
activated. If the password is not
known, set the parameters to their
default settings (see page 41)
USB cable disconnected or faulty
connection
Check the USB cable connection
The serial port used is not the correct
one.
Locate the serial port used, following
the procedure on page 21
Drivers are missing or not installed
properly
Try removing and reinstalling the USB
drivers. For installation, refer to the
procedure on page 21
The USB connection has been
interrupted without first logging off.
The driver on your PC has lost its
configuration.
Press the End button on the MVC or
close it down and start it up again.
Reset the peripheral and try again. If
the problem persists, restart the PC.
ML-8
programming in USB connection
mode (error: AUTH: Access
Denied).
Password missing or wrong
programming in USB connection The connection settings are incorrect
mode (error: timeout).
programming in remote
assistance mode, static TCP/IP
mode (error: impossible to
establish the connection.
Incorrect response)
Try resetting the password, if it is
activated. If the password is not
known, set the parameters to their
default settings (see page 41)
Check the connection settings as
shown on page 22
Incorrect IP address
Check the IP address of the ML-8
ML-8 peripheral cannot be reached
Check that the ML-8 side router is
programmed as required on page 36;
check that the PC side router is
programmed as required.
The peripheral has not sent the
KeepAlive message yet
assistance mode, dynamic
TCP/IP mode (error: AUTH:
KeepAlive not received (cp=xx),
wait and retry).
Wait until you see the message
“KeepAlive cp=xxxx” on the bottom
bar of the MVC
The IP address of the installer’s PC
has not been programmed on the
peripheral or is incorrect
From local programming, check the IP
address programming on the
Communicator, Remote Assistance
(MVC) page
The network does not allow
KeepAlive messages to reach the
installer’s PC
Check the settings of the routers on
the peripheral and installer sides (see
page 37 )
assistance mode, time-based
data GSM connection mode
(error: timeout).
Incorrect connection COM port
Find the one used.
The installer’s number is not
configured on the peripheral or is
incorrect
From local programming, check the
programming of the “Number for
remote programming GPRS / GSM
DATA” on the Communicator, Remote
Assistance page
The installer’s IP address is
configured on the peripheral,
therefore the ML-8 peripheral hangs
up and enters GPRS mode
From local programming, remove the
installer’s IP address on the
Communicator - Remote Assistance
page
assistance mode, time-based
data GSM connection mode
(error: busy).
Pag. 47
ML-8
BT-GSM
PROBLEM
BT-GSM module cannot be
registered
POSSIBLE CAUSE
SOLUTION
Incorrect wiring
Check the wiring as shown on page
18
Jumpers J2-J3 on the BT-GSM
module in the wrong position
Make sure the jumpers are in position
near the edge of the card.
Missing or incorrect PIN
The module does not register on
the network. On the MVC GSM SIM locked (requires unlocking using
page, the “PIN” light is red.
the PUK)
The module does not register on
GSM signal level very low. Check the
the network. Only the GSM light
coverage by inserting the SIM into a
is red. All the “LEVEL” LEDs are
mobile phone.
off.
Check the PIN by re-entering it
Remove the SIM from the BT-GSM ,
insert it into a mobile phone and
unlock it using the PUK
Move the position of the ML-8, or
remove the BT-GSM module and
install it in a better position
Ethernet connection/LAN configuration
PROBLEM
POSSIBLE CAUSE
SOLUTION
The LINK LED does not light up
Ethernet cable disconnected or not
securely plugged into the connectors
Check the insertion of the Ethernet
cable
Faulty Ethernet cable
Try replacing the cable
DHCP server is not enabled or not
present on the network. Router not
configured.
Contact the network administrator. If
the router acts as a DHCP server,
check the configuration and make
sure this option is enabled
The configuration may take a few
seconds
Disconnect from MVC. Wait then
reconnect.
The DHCP configuration does
not work
Pag. 48
ML-8
Operation from peripheral
PROBLEM
POSSIBLE CAUSE
SOLUTION
When the LAN connection test
button is pressed, the
communication is not successful
/ The peripheral is polled by the
operational control centre: the
“IP Memory” field is blank on the
peripheral card
The IP address of the Operational
Control Centre is wrong; ports
incorrect
Check the setting of the IP
Address/LAN Hostname (MVC page
Communicator, Surveillance). Check
the settings of the TCP and UDP ports
(contact the network administrator)
The peripheral sends the alarms
correctly but it is impossible to
poll them (error: Access Denied)
MVSNet system, on the peripheral
card the password is missing or
incorrect
Reset the password
MvsNET system: the message
“Peripheral Replaced” appears
The ML-8 peripheral has actually
been replaced or the parameters
have been returned to the default
setting after connection to MvsNET.
Authorise the replacement of
MvsNET* see warning
WARNING
*WARNING!
The Authorise Replacement operation must be carried out responsibly by the Surveillance Institute
Operation from peripheral via GPRS
PROBLEM
POSSIBLE CAUSE
SOLUTION
When the GPRS connection test
button (Communicator page) is
pressed, the communication is
not successful
The IP address of the Operational
Control Centre is wrong; ports
incorrect
Check the setting of the IP
Address/GPRS Hostname (MVC page
Communicator, Surveillance). Check
the settings of the TCP and UDP ports
(contact the network administrator)
APN incorrect
Check the APN (MVC, GSM page)
The SIM telephone number to call is
wrong.
Check the telephone number entered
on the MvsNET peripheral card
The peripheral cannot be polled
from the Operational Control
Centre
Operation from peripheral via SMS
PROBLEM
When the SMS connection test
button (Communicator page) is
pressed, the communication is
not successful
The peripheral cannot be polled
from the Operational Control
Centre
POSSIBLE CAUSE
SOLUTION
Recipient number of the Operational
Control Centre (SMS) incorrect
Check the setting of the “SMS
Number” heading (MVC
Communicator, Surveillance page)
Service Centre number incorrect
Check the programming of the Service
Centre number (MVC GSM page)
The SIM telephone number to call is
wrong.
Check the telephone number entered
on the MvsNET peripheral card
Pag. 49
ML-8
Telephone Interface Operation
PROBLEM
The connected control unit does
not call
The connected control unit does
not call but gets a line
The line exchange relay is
always active
POSSIBLE CAUSE
SOLUTION
Line not detected; incorrect wiring
Check that the cable originating from
the LINE terminals on the alarm
control unit are brought correctly to
terminals T1-T2 on the ML-8 logic
card
Telephone cable connected to the
wrong terminals or not connected
Check that the cable originating from
the LINE terminals on the alarm
control unit are brought correctly to
terminals T1-T2 on the ML-8 logic
card
The control unit connected waits for
the dial tone
Program the control unit to start the
call without waiting for the dial tone
The address for the Surveillance
recipient (LAN) has not been
programmed
Program the address
The LAN control is active but the
connection is not present
Connect the LAN or disable the
control
The IP address of the control centre
via LAN is present but cannot be
reached
Find the reason why the control centre
cannot be reached
12.1- Application form repair
WARNING
WARNING!
In case of breakdowns, anomalies of operation and/or repairs, we
kindly invite you to download the APPLICATION FORM REPAIR
from our site www.sicep.it to the section "Modulistica" and to attach it to the device at the moment of the shipment.
Pag. 50
Cap. 13 - Appendix: Certificate of warranty
ML-8
CERTIFICATE OF WARRANTY
- The
guarantee on electrical and / or electronic products manufactured by SICEP spa is valid for
13months
- Appendix:
Certificate
warranty
24
from the purchase
date, or from theof
date
on the invoice.
- This guarantee does not extend to the software produced and / or sold by SICEP spa, nor does
it cover damages of any kind that may derive from the use of the same.
- Should the products or parts of them prove faulty owing to the quality of the materials used or
-
-
-
-
due to anomalies that occurred during manufacturing, the guarantee limits to the replacement
of said products or parts. The above guarantee includes costs of labor necessary to carry out
repairs.
In cases where one or more parts of the faulty device are missing, the device will be repaired
and returned to the client without integration of missing pieces, excepting when there is an explicit request for integration.
This guarantee does not extend to malfunctions due to normal wear and tear of the products or
their parts (including batteries).
This guarantee does not cover damages caused by negligence, carelessness, accidents or improper use of the products or parts of the same and / or the software. The same applies to
damage caused by atmospheric agents, exposure of the products or their parts, and / or of the
software, to inappropriate environmental conditions, including damages caused, either directly
or indirectly, by excessive temperature, dampness, physical or electrical stress, electrical
blackout or power surges, lightning, static electricity, fires, floods and any other circumstances
that are not ascribable to the direct responsibility of SICEP spa.
This guarantee does not cover damages caused by poor or incorrect installation - or installation
that is not compliant with the relevant instructions or - lacking the same - installation carried out
in an unprofessional manner, wrong or poor maintenance interventions in accordance with
what is indicated in the relevant operating instructions or according to usual maintenance practice, improper or wrong operation, negligence or lack of ability to use the product correctly or
indeed other causes of any kind that are not ascribable to SICEP spa.
This guarantee does not cover any damage originating from faults in assembled components
or parts of the product, although certified in any manner, that it is not possible for SICEP spa to
identify in any way in advance, during or after the manufacturing of the end product in accordance with the normal checking and verification procedures applied for components or
products and external parts of them. Damages or defects ascribable to repair and maintenance
interventions, replacements or changes carried out by third parties not directly authorized by
the manufacturer, or carried out by others employing unoriginal or non-compliant products,
parts of products and / or software that are therefore not guaranteed, not certified and not approved or authorized by SICEP spa, are not covered by this guarantee.
In any case, damages and faults arising from the use of spare parts and accessories that are
non-compatible, unoriginal, non-compliant, uncertified and not approved by the manufacturer
are not covered by this guarantee. Same applies to all damages ascribable to changes made to
the product or parts of the same and / or to the software that are in no way approved by the manufacturer or due to causes of force majeure and / or unforeseeable circumstances.
In order to avoid application of the troubleshooting fee (€30.00 + VAT), the material to be repaired has to be sent carriage-paid to SICEP spa accompanied by the "Repair or change
request form" completely filled in.
SICEP spa reserves the right to make amendments to these guarantee conditions without prior
notice. In any case, the conditions in force at the time of purchase of the electric and / or electronic product manufactured by SICEP spa will be considered valid.
Pag. 51

ML-8 [email protected]

Transcript

Documenti analoghi

Yeastar NeoGate TG Series

liceo scientifico leonardo da vinci

Telefonini_convegno Napoli 2014_1

Liceo Scientifico “A. Labriola - Programma di Lingua e Letteratura

Arc-8c Inglese.vp

CORPORATE PRESENTATION - E

sleep well we take care

The Convergence of Science and Spirituality

The European Community: On the Road to - Augusto Lopez

Parte 4 - Dipartimento di Fisica

Testo gara Eng 12

LinkManager Installation Guide

Consumer electronics - Troostwijk Auctions