Climax Technology Co MX Users manual
August15,2013
Table of Contents
1. INTRODUCTION..................................................................................................................1
1.1. THE MX MEDICAL AND INTRUSION ALARM SERIES.............................................................1
1.2. WHAT’S IN THE BOX.............................................................................................................. 2
2. SYSTEM OVERVIEW..........................................................................................................3
2.1. IDENTIFYING THE PARTS .......................................................................................................3
2.2. POWER SUPPLY ....................................................................................................................7
3. INSTALLING MX..................................................................................................................8
4. PROGRAMMING MX...........................................................................................................9
4.1. PC PROGRAMMING...............................................................................................................9
4.1.1. Installing USB Driver...................................................................................................9
4.1.2. PC Programming Tool..............................................................................................16
4.2. WEB PROGRAMMING ..........................................................................................................47
4.2.1. Installing the Finder Software ................................................................................47
4.2.2. Programming MX....................................................................................................... 50
4.3. SMS PROGRAMMING..........................................................................................................69
5. DEVICE MANAGEMENT...................................................................................................74
5.1. LEARNING IN PENDANT #1, PENDANT #2 AND OTHER DEVICES.......................................75
5.1.1. Learning in Pendant #1............................................................................................75
5.1.2. Learning in Pendant #2............................................................................................77
5.1.3. Learning in Other Devices....................................................................................... 79
5.2. REMOVING PENDANT #1, PENDANT #2 A ND OTHER DEVICES..........................................80
6. OPERA TION.......................................................................................................................81
6.1. CONTROL PANEL................................................................................................................. 81
6.1.1. Idle Mode...................................................................................................................... 81
6.1.1.1. Answering Incoming Calls........................................................................................... 81
6.1.1.2. Non-Emergency Calls ................................................................................................... 82
6.1.1.3. AC Power Checkup........................................................................................................83
6.1.1.4. Control Panel Low on Battery.....................................................................................84
6.1.1.5. Control Panel’s Battery Disconnected...................................................................... 84
6.1.1.6. Devices Low on Battery................................................................................................84
6.1.1.7. Automatic Check-In Reports....................................................................................... 85
6.1.1.8. Inactivity Timer............................................................................................................... 85
6.1.2. Alarm Activation......................................................................................................... 88
6.1.3. Arming/Disarming the System...............................................................................97
6.1.4. Voice Prompts............................................................................................................99
6.1.5. Walk Test (Range Test)...........................................................................................100
6.1.6. Factory Reset............................................................................................................ 100
7. APPENDIX .......................................................................................................................101
7.1. CONTACT ID COMMUNICATIONS PROTOCOL AND FORMAT .............................................101
7.1.1. Handshake Tones.......................................................................................................101
7.1.2. Placement .....................................................................................................................101
7.1.3. Composition.................................................................................................................101
7.1.4. Message Blocks ..........................................................................................................102
7.1.5. Placement .....................................................................................................................102
7.1.6. Message Composition............................................................................................... 102
7.1.7. Data Tones....................................................................................................................102
7.1.8. Kiss off (Acknowledgement) Tones .......................................................................103
7.1.9. Contact ID Event Codes............................................................................................103
7.2. SIA DIGITAL COMMUNICATION STANDARD.......................................................................105
7.3. SCANCOM EVENT CODES.................................................................................................106
7.4. TUNSTALL TTNEW EVENT CODES..................................................................................107
7.5. CLIMAX CPC DIALECT EVENT CODES.............................................................................108
7.6. FRANKLIN EVENT CODES................................................................................................. 110
1. Introduction
1.1. The MX Medical and Intrusion Alarm Series
Climax’s MX Medical and Intrusion Alarm Series marks a watershed in the
evolvement of medical alarm systems. One of the first of Climax’s wireless
medical alarms to be integrated with an intrusion alarm system, the MX Series
not only provides thorough care for your loved ones at home but also protects
your house and property when you are away. Incorporating various
cutting-edge telecare technologies, the MX Series features a new,
user-friendly three-button design that fully utilizes the flexibility and versatility
of the system. The user can summon emergency help by one press on the red
button and arm his house by one press on the yellow button. Events
happening at home will be reported to the monitoring center via the Contact ID,
Tunstall (TT New), Climax CPC Dialect or 4+2 Franklin communication
protocols. Living under protection and going in and out in peace have never
been easier.
MX Models
Model Alarmcommunicationspath(s) CompatibilitywithEZ‐1orEZ‐2
MX‐2 PSTN EZ‐1orEZ‐2
MX‐3 GSM/3G EZ‐1
MX‐6 EthernetandPSTN EZ‐1orEZ‐2
MX‐8 EthernetandGSM/3G EZ‐1
1
1.2. What’s in the Box
Your MX sample package includes the following items:
z Control Panel
z AC adaptor for the Control Panel
z USB cable
z CD-ROM containing
- MX Installation and Operation Guide
- USB Driver for MX
- PC Programming Tool
- The Finder software (MX-6 and MX-8 only)
2
2. System Overview
2.1. Identifying the Parts
Top View Back View
Side View
3
Control Panel Definitions
Button/LED/Component
1 Red Help Button
2 Red Backlight
3 Green Reset Button
4 Green Backlight
Behavior Function/Indication
Pressed in idle/normal mode To summon emergency help
Pressed once in learning
mode
Pressed for 3 seconds in
learning mode
Dimly lit Idle/normal mode
Blinking 1. Guard time
Brightly illuminating 1. Busy with alarm
Pressed in idle/normal mode 1. To reset the inactivity
Pressed once before the
Control Panel dials out for
alarm reporting
Pressed once during or at
the end of a two-way
communication
Pressed for 3 seconds in
idle/normal mode
Pressed once in learning
mode
On 1. After a non-emergency
Off 1. Idle mode
To select Pendant #2
To delete a selected pendant
2. Pauses during retries of
alarm reporting
reporting
2. After an alarm report
receives a callback and
until the call is hung up
timer
2. For the Control Panel to
report all the fault
problems it is
experiencing via voice
prompts
To cancel the alarm reporting
To terminate the two-way
communication
To make a non-emergency
call
To select Pendant #1
call is dialed out and until
the call ends
2. Busy with status
reporting
3. When two-way
communication is
opened after an
incoming call is picked
up and until the call ends
2. Pauses during retries of
status reporting
4
Button/LED/Component
4 Green Backlight
5 Yellow Button can
serve as:
- Inactivity Button
- Check-in/out Button
- Away/Home Button
- Non-Emergency Call
Button
- Security Button
6 Orange Backlight
7 Green LED (Volume
Switch)
8 Orange LED (Volume
Switch)
9 Microphone
Blinking (on MX-2 and MX-6
only)
Pressed once when serving
as an inactivity, check-in/out
or away/home button
Pressed once when serving
as a security button
Pressed once when serving
as a non-emergency button
Pressed for 3 seconds To enter learning mode
Pressed once in learning
mode
Steady on The inactivity timer is on.
Off The inactivity timer is off.
Blinking The Control Panel is in
Steady on AC power is on.
Blinking twice every second AC power fails.
Pressed once To increase the speaker
Pressed once To lower the speaker volume
Blinking every 3 seconds The Control Panel is low on
Blinking twice every second A device is low on battery or
Off All the conditions signified by
Behavior Function/Indication
The Control Panel has a
phone line fault.
To toggle on/off the inactivity
timer
To arm the system
To make a non-emergency
call
To exit learning mode
learning mode.
volume
battery or is having an
overvoltage condition.
is tampered with.
this blinking orange LED
have been removed.
10 Speaker
11 Battery Switch On/off
12 EZ-1/EZ-2 Lid
13 DC Jack Connects to a DC 12V 2A switching power adapter.
14 USB Port
15 Ethernet Port (On MX-6 and MX-8 only)
16 Phone Jack Marked Connects to a phone line from the wall.
17 Phone Jack Marked Connects to a telephone unit.
5
Button/LED/Component
18 GPRS/GSM or 3G Fault
Indicator (orange)
Behavior Function/Indication
On Failed registration
>
<<NNOOTTEE>
) Registration will fail
when an AC power
failure occurs.
Off Successful registration
19 GPRS/GSM or 3G
Status Indicator (red )
20 GPRS/GSM or 3G Reset
Button
21 SIM Card Base Insert your SIM card in this slot.
Blinking
Pressed for one second
When the GPRS/GSM or 3G
module operates normally
To reset GPRS/GSM or 3G
6
2.2. Power Supply
z Plug the AC power adapter into the Control Panel’s DC jack and connect
to the mains power. Make sure that you use an adapter with the
appropriate AC voltage rating to prevent component damage. An AC-DC
12V/2A switching power adapter is generally used to power the standard
version of the Control Panel.
z In addition to the AC power adapter, a rechargeable battery is installed
inside the Control Panel to serve as a backup in case of a power failure.
z During normal operation, the AC power adapter is used to supply power to
the Control Panel and at the same time recharge the battery. It takes
approximately 72 hours to fully charge the battery.
z If the battery switch is set as OFF, the battery will not be charged when
AC power is connected and nor will it serve as a backup power source
when AC power is missing. You need to switch the battery to ON for it to
be charged when AC power is connected and serve as a backup power
source when AC power is missing.
7
3. Installing MX
Step 1. Choose a suitable location for the Control Panel. The Control Panel
requires the mains power and PSTN (MX-2 and MX-6), GSM/3G
(MX-3 and MX-8) and/or Ethernet (MX-6 and MX-8) connections and
should be easily accessible. It should not be placed in a damp
location such as a bathroom or close to a heat source like a
microwave oven, which could reduce signal strength.
Step 2. Plug the USB cable into the Control Panel’s USB port and connect it to
a PC for MX programming.
Step 3. Connect a PSTN line and a telephone line to the Control Panel for MX
to operate via PSTN (MX-2 and MX-6 only).
Step 4. Insert a SIM card into the SIM card base on the rear side of the Control
Panel for MX to operate via GPRS and GSM or 3G (MX-3 and MX-8
only).
<<NNOOTTEE>>
) It is recommended that you disable the SIM card’s PIN code before you
insert the SIM card into the Control Panel.
) The SIM card will delete its messages whenever the Control Panel is
powered on.
Step 5. Plug an IP cable into the Control Panel’s Ethernet port and connect to
an Ethernet network for MX to operate via Ethernet (MX-6 and MX-8
only).
Step 6. Plug the AC power adaptor into the Control Panel’s DC jack and
connect to the mains power. The Control Panel will emit two beeps to
indicate the system is now ready for further operation.
8
4. Programming MX
4.1. PC Programming
4.1.1. Installing USB Driver
Please first install the USB Driver provided in your CD-ROM on your PC.
>
<<NNOOTTEE>
) It is recommended that you use Windows XP or Windows 7 operating
Step 1. Plug the USB cable into the Control Panel’s USB port and connect it to
Step 2. Insert the supplied CD-ROM into your CD-ROM drive and find the
systems.
a PC.
“USB Driver” folder (you may copy and paste the folder to your
desktop for later use). Click the “Start” button at the bottom left-hand
corner of the screen and then click “My Computer” and “Manage.”
9
Step 3. Click on the “Device Manager” icon and find “MOBIL PERS BASE ISP”
under “Other devices.” Click “Update Driver.”
10
Step 4. When the Hardware Update Wizard window pops up, select “Install
from a list or specific location (Advanced)” and click “Next.”
11
Step 5. Search for the USB Driver folder. If you have copied and pasted the
USB Driver folder to your desktop, tick “Include this location in this
search” and click “Browse.”
Step 6. Select the “USB Driver” and click “OK.”
12
Step 7. It takes a short while for your PC to install the USB Driver. If the
Hardware Installation warning window pops up, please click
“Continue Anyway .”
13
Step 8. When the installation has been completed, click “Finish” on the
Hardware Update Wizard window to close the wizard.
14
Step 9. Please remember the COM port number of MX as shown in the
“Device Manager” section. You will need the COM port number when
doing PC programming.
Now that the USB Driver has been successfully installed, you can
proceed with PC programming of MX.
15
4.1.2. PC Programming Tool
You can easily configure the Control Panel via the PC Programming Tool
provided in the CD-ROM.
Step 1. Find and open the “PC Programming Tool” folder in the supplied
CD-ROM. Click “MPTool_x.xx.exe” to execute the programming tool.
The following configuration screen will be opened.
16
Step 2. Select the following settings in the top section of the configuration
screen and click “Open.”
z Port: Select the COM port generated for MX after installing the
USB Driver (the USB port connected to MX).
z Baud rate: 115200
z Data: 8
z Parity: None
z Stop: 1
z FlowCtrl: None
17
Step 3. Enter SMS Keyword and Access Code and click “Read.” When a
pop-up window shows “Read configuration success,” the
configuration page below will be opened and you can proceed with
the programming of MX.
z SMS Keyword: PROG (default)
z Access Code: 1111 (default)
18
Step 4. SMS Program
Click “SMS Program” to set a SMS Keyword (15 characters max.) and a PIN
Code (4-8 digits) and click “Write.” Please note that the SMS Keyword is
case-sensitive.
<<NNOOTTEE>>
) The version of your MX model will be shown on the top of the screen.
19
Step 5. APN
Click “APN” to set APN Name, APN User and APN Password and click “Write.”
z Access Point Name (APN): The name of an access point for GPRS.
Please ask your SIM card service provider for your APN.
z Username: Offered by your SIM card service provider. Please ask your
service provider for your GPRS username. If no username is required, you
may skip this step.
z Password: Offered by your SIM card service provider. Please ask your
service provider for your GPRS password. If no password is required, you
may skip this step.
20
Step 6. Reporting
Click “Report” to program destinations of reporting, event filters (Event),
reporting formats (T ype), fo llow-on options (Follow-on) and reporting sequence
(Group 1~5) for alarm reporting and status reporting. Click “Write” after you
have completed the settings.
z Destinations of reporting 1~8: Program destinations of reporting 1~8 in
the No. 1~No. 8 boxes.
z Event: Event filters have five options, “All,” “Medical,” “Emergency,”
“Status” and “Burglar.” Event filters are used to process events according
to the categories to which they belong. Please refer to “Appendix 7.1.9
Contact ID Event Codes” to check out the categories to which events are
assigned.
z Type: Select a reporting format for each destination of reporting. The
reporting formats include the following: Speech, CID, Scancom, Tunstall,
Franklin, CPC 1, CPC 2, CID_IP, SIA_CID_IP, SIA_IP, SIA_CID_UDP,
SIA_UDP, CSV_IP, SMS_CID, SMS_TEXT, and SMS_SIA.
z Follow-On: Select a follow-on option for each destination of reporting.
The follow-on options include the following: No, 2-way Voice
communication, Talk only, Listen-in only and Wait (for command). The
follow-on options should be in conformity with the settings of their
corresponding destinations of reporting.
21
z Group 1~Group 5: Groups 1~5 determine the sequence of reporting. The
reporting sequence goes from Group 1 to Group 5.
The procedure and details of programming are as follows:
1. Programming destinations of reporting: You can set 8 destinations of
reporting. To program destination 1, please first enter its reporting
number/setting in the No. 1 box and select its reporting format under “T ype”
as well as its follow-on option under “Follow-On.” Configure destinations
2-8 in the same manner.
The setting of each destination of reporting shall be in conformity with the
destination’s reporting format under “Type.” Examples of reporting formats
are as follows:
- Reporting over IP (Ethernet or GPRS) in CID_IP/SIA_IP/SIA_CID_IP/
SIA_UDP/SIA_CID_UDP/CSV_IP formats: Account@server:port
example: 0001@59.124.123.66:50123
- Reporting over the phone in CID/Scancom/Tunstall/Franklin/CPC 1/
CPC 2 formats: Account@phone number
Example: 0001@(02)27940559
- Speech reporting over the phone: phone number
Example: 0912345678
- Reporting over the phone in SMS_CID/SMS_TEXT/SMS_SIA formats:
Account@phone number
Example: 0001@0912345678
<<NNOOTTEE>>
) The account number can contain 4 or 6 digits. The CMS may also
determine according to its capacity how many digits the account number
can contain.
) You can select the options in the “Follow-On” column (No/2-Way
Voice/Talk Only/Listen Only/Wait) for digital reporting formats, including
CID, Tunstall, Scancom, Franklin, CPC 1 and CPC 2 formats. Please note
that the “Follow-On” settings for all the other reporting formats have to be
“No.”
) If a destination of reporting contains digits in parentheses like
(02)27940559, the Control Panel will not dial the digits in the parentheses
when reporting via PSTN (it will only dial 27940559) but will dial the digits
in the parentheses when reporting via GSM (it will dial 0227940559).
) Jamming reports can be reported via all reporting formats under “Type”
except for the Scancom and Tunstall formats.
2. Programming event filters: Event filters have five options: “All,”
“Medical,” “Emergency,” “Status” and “Burglar.” Event filters are used to
22
process events according to the categories to which they belong. Please
refer to “Appendix 7.1.9. Contact ID Event Codes” to check out the
categories to which events are assigned.
Events are divided into four categories: medical, emergency, status and
burglary. If the option “all” is selected for a destination, all events will be
reported to this destination.
Examples are as follows:
- A device low on battery is a “status” event. If destinations 3 and 7 are set
as “status” and destination 5 as “all” in event filters, this status event will
be reported to destinations 3, 5 and 7.
- A fall sensor being inactive is a “medical” event. If destinations 1 and 6 are
set as “medical” and destination 5 as “all” in event filters, this medical
event will be reported to destinations 1, 5 and 6.
<<NNOOTTEE>>
) Events categorized as “status” do not have follow-on procedure
(2-way/listen in/talk only/wait). Events categorized as “medical,”
“emergency” or “burglary” will have follow-on procedure if you program
follow-on modes for them. The only exception is the home/away events
(the home event code is 3666 and the away event code 1666). These two
events belong to the “status” category but have follow-on procedure.
3. Assigning destinations 1~8 to Groups 1~5: Reporting sequence goes
from Group 1 Æ Group 2 Æ Group 3 Æ Group 4 Æ Group 5. Destinations of
reporting assigned to Group 1 will be reported to first, those assigned to
Group 2 reported to next, and the like.
If you want to assign destination 1 to Group 3, tick Group 3 for destination 1.
Assign destinations 2-8 to the groups in the same manner.
>
<<NNOOTTEE>
) Each group can have more than one destination of reporting. If one group
has more than one destination of reporting, the reporting sequence will go
through all of this group’s destinations before moving on to the next
group’s destination(s).
) The reporting will go through a group’s destinations according to the
numerical sequence to which the destinations are assigned. For example,
when destinations 4 and 8 are assigned to Group 2, the reporting will go to
destination 4 first and then destination 8.
) One complete round of reporting for the system means reporting from
Group 1 Æ Group 2 Æ Group 3 Æ Group 4 Æ Group 5 and going through
all the groups’ destinations. The system will keep going through the
rounds of destinations until one reporting has been received successfully.
If the system has successfully reported to one destination in a group, the
system will consider that it has successfully reported to this group.
23
Therefore, the system will skip the rest of the destinations in this group
and go on reporting to the next group. For example, if destinations 2, 4
and 7 are assigned to Group 3 and the system has successfully reported
to destination 2, the system will skip destinations 4 and 7 and go on
reporting to Group 4.
After the system has completed one round of reporting (going from Group
1 Æ Group 2 Æ Group 3 Æ Group 4 Æ Group 5) and has successfully
reported to one group, it will consider that the event has been successfully
reported and will stop reporting. If the successful reporting takes place in
the midst of a round, the system will still report to the rest of the groups in
the round before stopping reporting. For example, if the successful
reporting takes place in Group 2, the system will no longer report to other
destinations in Group 2 but will still go on reporting to destinations in
Group 3, Group 4 and Group 5 before stopping reporting.
If the system has not successfully reported to any group, it will enter the
retry cycle to repeat another round of reporting.
) If no reporting is successfully received after the system has gone through
the first complete round, the system will take a 5-minute break before
starting the second round of reporting. If there is still no reporting
successfully received after the system has gone through the second
round, the system will again take a 5-minute break before starting the third
round of reporting. The system will never stop the reporting cycles unless
one reporting has been received successfully.
24
Step 7. Non-Emergency Call
z Click “Non-Emergency Call” to program the non-emergency call number
and click “Write.”
z When the Control Panel is in normal mode, you can make a
non-emergency call by pressing the green reset button for 3 seconds or
press the yellow button once (if the yellow button has been programmed
as a non-emergency call button). The Control Panel will emit 2 beeps and
automatically dial the programmed non-emergency call number for
two-way communication.
z During the conversation of a non-emergency call, you can enter the
following DTMF commands:
- Enter (1) to talk only.
- Enter (2) to open two-way voice communication.
- Enter (3) to listen in only.
- Enter (9) to hang up. You can also put the handset back to the base
cradle to end the call.
z During the conversation of a non-emergency call, you can extend the
communication by entering DTMF command (1), (2) or (3).
z At 20 and 10 seconds before the communication time expires, 1 beep will
be emitted via the telephone handset to alert the user. When the
communication time is up, the call will be automatically terminated.
z The communication time of non-emergency calls is conditioned by the
two-way timer function.
Step 8. Setting
25
Click “Setting” to program “Guard Time Normal,” “Guard Time for Fall Sensor,”
“Auto Check-In Interval,” “Auto Check-in Offset,” “Yellow Away/Home Button,”
“Inactivity Timer,” “Inactivity Interval,” “Inactivity Warning Time,” “Callback
Timer,” “Two-Way Timer,” “Supervision Timer Interval” and “Speaker Volume
Two-Way,” “Speaker Volume Talk Only,” “Speaker Volume Other,” Sound
Setting Guard Beep,” “Sound Setting Confirm Beep,” “Answer Incoming,”
“Alarm Length,” “Exit Time” and “Entry Time.”
Click “Write” when you have completed these settings.
Details regarding the settings are as follows:
1. Guard Time Normal:
z Guard time normal is designed for any compatible sensor except for Fall
Sensor (fall detection).
z A voice prompt announcing “help call in progress” will be played every 2-3
seconds during guard time to alert the user.
z If a false alarm is triggered, it can be canceled during guard time.
z An emergency alarm cannot be cancelled after guard time has expired.
z If an emergency alarm is triggered by Fall Sensor, guard time will be
determined by the setting of Fall Sensor instead of the setting of guard
time.
2. Guard Timer for Fall Sensor:
26
zYou can set a guard time period for Fall Sensor. A voice prompt
announcing “a fall has been detected” will be played every 2-3
seconds during Fall Sensor’s guard time.
zIf a false alarm is triggered by Fall Sensor, it can be canceled within the
guard time period.
zThis function is used when a fall is detected.
3. Auto Check-In Interval:
z You can select the length of the interval between auto check-in reports.
z There will be no auto check-in report if you select “Disable.”
z Whenever programming mode is accessed, the Control Panel will reset
the auto check-in timer.
4. Auto Check-In Offset:
z After power is supplied to the
Control Panel, the system will start counting the time for a check-in
report.
z The Control Panel will send a
check-in report once according to the setting of offset time. Afterwards
it will send reports according to the setting of auto check-in reports
unless the Control Panel restarts or the offset time is reset.
z When offset time is reset in
programming mode, the system will recalculate the time for a check-in
report.
z Whenever programming mode is
accessed, the Control Panel will reset the offset timer.
5. Yellow Button:
zYou can set the yellow button on the Control Panel as an inactivity button,
a check in/out button, an away/home button, a non-emergency call
button or a security button.
zAs an inactivity button: The user can use the inactivity button to toggle
on/off the inactivity timer. When the user presses the inactivity button
to toggle on/off the inactivity timer, the Control Panel does not report
event codes to the CMS.
zAs a check-in/out button: The user can use the check-in/out button to
toggle on/off the inactivity timer. When the user presses the
check-in/out button to check out and toggle off the inactivity timer, the
CID event code 665 with the prefix “1” will be sent to the CMS. When
the user presses the check-in/out button to check in and toggle on the
inactivity timer, the CID event code 665 with the prefix “3” will be sent
to the CMS.
27
Loading...