Central units

The number of ReX range extenders connected to the Ajax security system depends on the hub model:

Only hubs on OS Malevich 2.8 and higher support the connection of several ReX.

Alarms are communicated within 0.3 seconds.

In the event of a loss of connection between the hub and ReX, all devices connected to the range extender also lose connection with the hub.

By copying the system information from the hub, ReX creates an autonomous group of devices and responds to events instantaneously. If ReX continues to communicate with the connected devices when the connection with the hub is lost, ReX assumes the role of the control panel: it will receive an alarm signal from the detector and activate the siren.

Users can manage the security modes of ReX and of the devices connected to the range extender only after the connection between the range extender and the hub is restored.

ReX functions at a distance of up to 1,800 meters from the hub and can double the radio communication range between the Ajax devices and the hub.

The communication range between ReX and a paired device is limited by the radio signal range of the device (the relevant parameter is indicated in the device’s specifications on the website and in the User Manual).

You can significantly expand the coverage area of the Ajax radio network using several ReX in the security system. However, keep in mind that ReX can only be connected directly to the hub and connecting one range extender to another is not supported.

The number of ReX connected to the security system depends on the hub model.

No. ReX expands the security system’s radio communication coverage, thereby enabling the installation of Ajax devices at greater distances from the hub or in locations where a reliable signal reception from the control panel cannot be ensured.

ReX expands the hub’s radio communication coverage.

ReX receives hub signals and transmits them to the devices connected to the range extender. It also transmits signals received from the devices to the hub. Two-sided connection is provided by the Cargo protocol operating over the Jeweller radio protocol.

Unlike regular range extenders that only re-broadcast signals, ReX controls the functioning of the security system devices. By copying the system information from the hub, ReX creates an autonomous group of devices and responds to events instantaneously. If the hub disconnects from the network for whatever reason, ReX receives an alarm signal from the detector and activates the siren.

ReX does not increase the number of devices connected to the hub!

Tamper is a miniature button on the device board. It is released when the lid is opened as well as a result of an attempt to unfasten and/or lift the device from the surface, which initiates an event.

When the tamper is released, the Hub sends push notifications and SMS messages (if this type of notification is enabled) to all users of the security system and also communicates the event to the central monitoring station of the security company.

If the tamper is released, Ajax applications display the Open status in the Lid field of the device menu. In addition, a malfunction badge appears on the device icon.

The maximum distance between the Hub and the detector can reach up to 2000 meters in open spaces. Walls, ceilings and other structures between Hub and the detector, reduce the range of action several times. In this case, the maximum distance depends on the material, thickness, and configuration of the walls.

The Hub will be receiving new software features as long as its electronic components can support their functioning. Once its development potential is exhausted, the software will be updated to ensure compatibility with the Ajax server and applications.

We are working currently on the new features for all Ajax central units: the standard Hub, the advanced Hub Plus and Hub 2, that supports detectors with photo verification.

The aim of developing Ajax is to provide current and future owners of our systems with greater opportunities. New products of the Ajax range will be operated under the control of Hub, Hub 2 and Hub Plus if such support can be ensured by updating the control panels software. In the future, the capacities of the new devices might require other hardware components of the central unit, and a new control panel will be needed to run them.

The Ajax control panels have different purposes. The standard Hub provides a basic set of features ensuring integrated security of an apartment, a house, a store or an office. The advanced Hub Plus has unique communication capacities: the control panel is equipped with Wi-Fi and Ethernet modules and two 2G / 3G SIM card slots, and it can ensure security of large facilities, which is attributed to its 150 detectors, 25 groups, 99 users, and 50 cameras, works up to 16 hours from backup battery. For the time being, less than 50% of the Hub Plus hardware capabilities are utilized. Future software updates will uncover the full potential of the device.

We are developing Ajax to provide our customers with more opportunities and increase the level of security and resilience of the system. This process cannot affect negatively the user experience and limit the existing opportunities. The central units of all generations will be supported by the Ajax servers and applications.

The type of SIM card used is Micro-SIM.

SIM-card must be inserted with the front part (with the operator’s label) towards the cavity marked with the Hub:

In order to allow automatic updating of the firmware of the Hub, select the Hub in the device list, go to the settings , select Service and turn on the option Automatic software update.

Auto-Update is turn on by default.

Press the power button (the Ajax logo will turn off) and hold for 30 seconds, until the logo is flashing red. This will remove all detector connections, room configurations, and user setting. User accounts will remain connected to the system.

Most likely, several users are receiving SMS alerts. For example, if three people receive SMS alerts, then each notification is sent out three times.

No, Ajax Hub can work without port forwarding.

Yes, as long as the test shows a good enough radio communication. But you will still need to secure the Hub on the table with the provided screws. This is required to ensure the alarm will work if an intruder tries to dismantle Ajax Hub.

To make SIM card work properly, please do the following steps:

• SIM card shall have some money on its account or free Megabytes for using the Internet
• SIM card shall support 2G Internet
• The pin-code request shall be removed

Detectors’ LED indication turns only in armed mode in case of alarm. While detector is disarmed, it won’t blink with the LED in case of actuation.

The functioning of the detector may be checked using the Detection Zone Test

Check if both LEDs are lit on the Ethernet port when the cable is connected. If they aren’t, connect another Ethernet cable. If they are, check your router settings. It should be set to DHCP mode.

The system uses our own two-way protocol, Jeweller. The protocol allows Ajax Hub to monitor securely all network devices up to 2,000 meters away in open space, helps to identify detector failures and radio jamming, and carries out radio and detection zone tests.

The server will notify you of any connection failure with a push-notification. If you’ve activated SMS alerts, the Hub will send an SMS alert. Also, in the Ajax application, the icon of your hub will become gray.

GSM and Ethernet (main channel). If one channel is temporarily unavailable, the system automatically switches to the other.

You will receive a push-notification. If you’ve activated SMS alerts, you will receive an SMS alert.

Yes. The battery inside the hub will provide for up to 16 hours of the system operation. In the case of switching to backup power, a push-notification and an SMS-message will be sent.

The system works on Ethernet / Wi-Fi with GSM connection as a backup communication channel by default. You can not change the priority of the channels.

The hub update does not exceed 1 megabyte.

The user identifier is a unique number which is assigned by the hub to the specific user being added.

If the user has several hubs, they will be assigned their own unique number in each hub

Your own user identifier can be found in the profile settings (Hub Settings User settings ).

Your identifier and combinations for using the keypad personal password are displayed in the settings menu.

Data is protected using “rolling code” encryption and authentication. Your information remains safe by making it virtually impossible to de-encrypt system data.

To delete a group:

At the moment, it is impossible to delete all groups from the hub. To completely remove all groups, the hub must be returned to the factory settings!

To disable the group mode, go to groups settings (Hub Settings Groups) and deactivate the group mode.

The ID of the group is a number of the group, which is necessary for arm separate groups from the keyboard.

The group number (ID) is displayed in the group settings (Hub Settings Groups)

In hubs with the firmware version OS Malevich 2.6 and latest hub administrator can limit the user’s access to the following functionality:

• Night mode activation (perimeter security)
• Panic Button
• View cameras
• Turning on/off automation devices
• View devices and rooms
• View notifications

All these settings you can find in the user’s settings (Hub Users User settings ).

The rights to the group, viewing notifications, devices and rooms can only be removed from the user account!

The second IP address is a backup in case of direct connection to the Central Monitoring Station (CMS).

If the main IP address is not available, the hub uses the second IP address to send events.

When the Hub communication with the server fails (the Ajax logo lights red), the security system continues autonomous operation responding to all events, executing the enabled scripts, and activating the siren when applicable.

The events during the communication failure are recorded in the Hub buffer and are delivered to the Ajax applications when communication with the server is restored.

The Hub buffer can store up to 130 events

Since the Ajax applications communicate with the Hub via the server, you cannot operate the Hub via applications in the case of Internet connection failure.

If the Hub connection to the GSM network is active, it continues calling and sending SMS to users — if these notification methods are enabled.

The direct connection (Monitoring Station tab) is the channel used to transmit hub events directly to the Central Monitoring Station (CMS) of the security provider, bypassing our server.

When direct connection is used, all events are communicated directly to the security company’s central monitoring station without affecting the functioning of the Ajax apps. If the direct connection is lost for any reason, the server acts as a redundant communication channel.

By default, the hub is set to ping detectors every 36 seconds and to signal an alert after 30 undelivered pings. Under these settings, it will take about 18 minutes for the system to recognize a communication failure. You can adjust these settings in the hub settings → Jeweller.

At the moment, such an opportunity is not provided, since the equipment of other manufacturers uses other frequencies and communication protocols with the control panels.

The automatic update is optional and can be disabled. To do this, go to the service settings of the hub (Devices Hub Settings   Service) and disable Firmware Auto-Update.

The Ajax Cloud service enables the user to manage the security system through specific applications remotely, it sends push notifications about alarms, and monitors the status of the equipment (attributed to regular hub – server communication sessions).

The loss of communication with the equipment means the weakening or complete disabling of the protection that the users and the security company must be aware of

The Ajax Cloud service can communicate with the hub through several independent channels: Ethernet, 2G/3G, and Wi-Fi. An alarm is sent if the hub loses connection with the Ajax Cloud service simultaneously via all communication channels.

Why the connection between the hub and the server may fail?

• Failure of the communication service provider’s network equipment or the relevant equipment located at the protected facility.
• The services of the communication service provider have not been paid for.
• The hub has been turned off (the hub sends a corresponding notification before turning off).
• The hub does not have an external power source and the backup battery is discharged (the hub notifies the users and the security company of the critical battery level before turning off).
• Hardware failure of the hub.
• Sabotage of the system: wired communication channels have been cut off and the radio has been jammed or the hub has been disabled.

If the connection between the hub and the Ajax Cloud service is lost, it is recommended to check the connection of the hub to the internet. If the hub is connected to the monitoring station of the security organization, contact the security company and discuss further actions.

Change the SIM card is possible, while you need to clarify the tariff, tariff conditions and APN data from the operator whose SIM card you plan to use.

After changing the SIM card, you need to make changes to the GSM connection configuration in the Ajax application.

The number to top up is on the plastic card holder of the SIM card, included in the box. Top up like any other mobile phone account.

You need to click on the Number field, enter the balance check USSD code (available from the mobile phone service provider).

After entering the number, click “Check balance”. It takes about a minute to complete the request. After the query is executed, you will see the status of the SIM card account.

The hub consumes mobile traffic regularly to check the functioning of the GSM channel and its availability as a backup communication channel.

The volume data depends on the settings and the number of devices assigned to the Hub. Working in the regular mode without alarms, the Hub uses up to 30 Megabytes per month.

The loop (zone) number is required to add a guarded facility to the CMS along with descriptions of all devices connected to the hub.

The loop (zone) number is available in the settings after activating the group mode in the Ajax application:

Having selected a group, you will see a list of its devices. Each device has a Device No. (or DeviceIndex in Ajax PRO Desktop) that corresponds to the loop (zone) number. A number is assigned when a device is attached to the Hub. The first added device has the first loop (zone) number.

After a device or a detector is removed, its number will be assigned to the next added device. However, the numbering of other devices will not change.

Monitoring Station — is a function used by security companies to configure a Direct Connection to the Hub with the CMS. When the Direct Connection is enabled, the Hub will send events directly to the IP and the port specified in the settings (without the participation of our server).

In the Ajax app, select the «Devices» tab . Information about the firmware version and device ID is located at the very bottom of the tab with the device parameters.

Go to the hub settings (Ajax Application Devices Hub Settings ).

In the GSM tab, select SIM card, enter the balance check USSD code (most often *111#), and click on the Check Balance button.

It is possible. In the Ajax Security System application, on average, you can add up to 50 Hubs. Such an amount can withstand the average user’s smartphone, the number of the attached Hubs is not limited and depends only on the phone characteristics.

However, we do not recommend using the Ajax Security System application to monitor a large number of objects, for these purposes there is a solution for professional installers, Ajax PRO: Tool For Engineers.

The detection time of communication failure with the server depends on two parameters in the Hub settings (Hub Settings Service):

• Server Ping Interval. The period of the pings by the Hub to the Ajax Cloud server, is set in the range from 10 to 300 seconds. The recommended and default value is 30 seconds.
• Connection Failure Alarm Delay. This is the delay required to reduce the risk of a false event of loss of communication with the server. The delay can be adjusted from 30 to 600 seconds. The recommended and default value is 300 seconds.
  

  The connection delay is activated after 4 failed pings.

The time until the message about the loss of communication between the Hub and the server is generated is calculated by the formula:

(Ping interval * 4) + Connection Delay

With the default settings, the server records the loss of the hub after 7 minutes:

(30 s * 4) + 300 s = 7 minutes

Reducing the time of registration the loss of communication with the Hub can be achieved by reducing the values ​​of the ping interval and the connection delay. But this increases the likelihood of a false event of loss of connection with an unstable Internet connection.

Go to the Device tab , select the device you want to check.