Ajax Translator PRO user manual

Ajax Translator PRO is a plugin for connecting Ajax systems to third-party monitoring software. Acting as a link between the space and a monitoring station, Ajax Translator PRO converts Ajax system events into CMS-supported protocols.

Ajax Translator PRO is an improved version of the Ajax Translator app. While the current Ajax Translator app has limited performance and functionality, Ajax Translator PRO offers improved operability, extended features, enhanced state tracking, and greater configuration flexibility. There is no need to install additional software — all settings are configured directly in the Ajax PRO Desktop app.

How to get Ajax Translator PRO

To get Ajax Translator PRO, fill out the online form on the Ajax Systems website. After submitting the request, you will receive a welcome email. In response to this email, you should provide details about your system setup, register your company in the Ajax PRO Desktop app, and send your Company ID. After that, you will receive an email with the link to download Ajax Translator PRO and your account credentials.

If you have selected the Add a company to the Ajax apps option in the form, your company will be added to the Security companies list in Ajax apps. This will allow you to receive user requests to connect security monitoring directly to Ajax Translator PRO. A user selects your company from the list in the app, taps Apply, and the request is automatically sent to the email assigned to the security company.

System requirements

Differences from Ajax Translator

Ajax Translator PRO is integrated into Ajax PRO Desktop, whereas Ajax Translator is a separate app. Ajax Translator PRO also offers additional features compared to Ajax Translator:

• SIA-DCS codes;

• account numbers in HEX;

• event code customization;

• additional data in the events, such as device or group name;

• ability to add account numbers for video devices separately from hubs;

• URLs for video verification of AI-powered detection events from Ajax cameras/NVRs in the Ajax PRO Desktop widget;

• support for additional event transmission protocols;

• an increased number of spaces connected to the receiver;

• regular feature updates and improvements.

Operating principle

Ajax Translator PRO operates as a TCP client and connects to the monitoring station using the address and port specified in the settings.

Ajax Translator PRO operates only in the store-and-forward mode. Each event generated by a space and transmitted to monitoring software via the Ajax Cloud server and Ajax Translator PRO must be acknowledged. When a space sends an event, it requires an acknowledgement only from Ajax Cloud. The space does not participate in communication between Ajax Cloud and the monitoring station.

Event transmission

When a connection to the monitoring station is available, alarms are transmitted immediately via the selected protocol. Ajax Translator PRO supports the following protocols for transmitting events to monitoring software:

• SIA DC-09,

• Sur-Gard (Contact ID),

• Manitou,

• MASXML,

• Micro Key,

• SoftGuard,

• Sentinel,

• ADEMCO 685.

Transmission channels and formats

Events can be transmitted via Ajax Cloud, via the space’s direct connection to Ajax Translator PRO, or simultaneously through both channels. The following code formats are used to transmit events:

• SIA-DCS for cloud connection only,

• ADM-CID for both cloud and direct connections.

How to directly connect the hub to the monitoring station via the SIA DC-09 protocol

Ajax Translator PRO uses a single transmission network interface and one dedicated port for direct connection to a local network. Ajax Translator PRO supports SP1–SP5 ATS categories.

If Ajax Translator PRO and the monitoring station event receivers are installed on the same computer (local server), they can be connected via a pair of virtual serial (COM) ports. You can also connect separate computers using two physical serial (COM) ports.

Capacity and performance

The Ajax Translator PRO receiver operates with up to 50,000 different spaces. If the number of connected spaces exceeds the recommended limit, divide the receivers into several groups.

Ajax Translator PRO does not impose a fixed limit on the number of events processed per second. The maximum event processing rate is 50 events per second. The actual processing rate depends on the computational performance of the machine running Ajax Translator PRO.

Event storage and retransmission

If a connection to the monitoring station is lost while an alarm is triggered, all stored events are automatically transmitted once the connection is restored.

Security mechanisms

Ajax Translator PRO is protected by security mechanisms that ensure reliable communication and prevent unauthorized interference.

Denial-of-Service (DoS) protection

Ajax Translator PRO implements protection mechanisms against Denial-of-Service (DoS) attacks in communication between Ajax Cloud, Ajax Translator PRO, and the monitoring station.

If the system detects an abnormal traffic pattern (more than 500 invalid messages within 5 seconds), the connection to the monitoring station is automatically terminated. Invalid messages include, for example:

• messages without a sequence identifier;

• messages that cannot be parsed correctly.

When this protection rule is triggered, the connection to the monitoring station cannot be reestablished for 60 seconds.

DoS protection for Ajax Translator PRO is currently based on the cloud infrastructure security mechanisms. The Ajax Cloud server uses AWS Shield Advanced technology to protect its cloud resources from distributed denial-of-service (DDoS) attacks.

Protection against device spoofing

An Ajax system prevents a hub from being spoofed by another device, including identical or counterfeit equipment.

Only Ajax hubs and video devices can connect to Ajax Cloud and generate system events. The Ajax Cloud server verifies the device’s authenticity before accepting any communication.

Each hub is authenticated through a proprietary handshake process. The cryptographic key required for authentication is uploaded to the hub during manufacturing and cannot be modified during operation.

Ajax Cloud identifies each hub by its unique device ID, which cannot be changed. This ensures that a hub registered in the system cannot be replaced with another device without detection.

The connection between the hub and Ajax Cloud is protected by a NIST-certified cryptographic algorithm.

Learn more about the NIST certification

How to add the Translator receiver

Once you get Ajax Translator PRO:

1. Open the Ajax PRO Desktop app and log in to your account.

2. Go to the Company module.

3. Go to the CMS connection menu.

4. Select the Ajax Translator tab.

5. Click the Add Translator receiver button.

6. Set the required parameters: name, address (IP or domain name), and port.

7. Click the Add button.

You can add up to 10 receivers for a single company. The total limit of 10 receivers applies to Ajax Cloud Signaling and Ajax Translator PRO receivers combined. Only one receiver can run on a machine at a time.

How to bind the space to the Translator receiver

Next, you need to bind the space to the Translator receiver and fill in the account number. To do this, in the Ajax PRO Desktop app:

1. Go to the Objects module.

2. Select the object you want to bind to the receiver.

3. Click Maintenance to view monitoring states.

4. Select the Translator receiver you need.

5. Select the space you want to bind to the receiver.

6. Specify the Account number that is used for messages sent to the receiver. This is not the account number from the Ajax PRO Desktop app, but it can be the same. All spaces bound to one receiver have a unique account number.

7. Click Start monitoring. After that, the Monitoring via <Name> receiver state will change from Not provided to Active.

How to migrate objects from Ajax Translator

An Ajax system allows users to independently export objects bound to Ajax Translator. This app generates a CSV file containing the hub ID and account number of active bindings. The file can then be uploaded to Ajax PRO Desktop to the selected Translator or Cloud signaling receiver.

How to migrate objects from Ajax Translator to Ajax Translator PRO

How to launch the Translator receiver

If at least one Translator receiver is created, Ajax Translator PRO can be downloaded. To do this, in the Ajax PRO Desktop app:

1. Go to the Company module.

2. Go to the CMS connection menu.

3. Select the Ajax Translator tab.

4. Click the button.

5. Select a folder where you want to install the Ajax Translator app. Folder path length is limited to 64 characters.

When the app is downloaded, the senior CMS engineer can specify and launch one of the Translator receivers. To do this:

1. Select the required Translator receiver.

2. Specify the required settings.

3. Click the Launch in Translator app button.

Before launching the app, ensure that the system complies with the requirements and that Java 21 is installed. Launching may take up to a minute. After launching, the Launched on this computer state will be displayed.

States

The states provide information about the receiver.

Settings

To change the receiver settings, in Ajax PRO Desktop:

1. Open the Company module.

2. Click the CMS connection menu.

3. Select the Ajax Translator tab.

4. Select the required receiver and click the icon .

5. Set the required parameters.

6. Click Save.

Receiver events

Ajax PRO Desktop provides a detailed log of system alarms and events, as well as employee actions within the app. Log entries in the Journal module are stored for up to three years. Older entries are deleted. Alarm logs include a timestamp of when the event occurred in the space.

The Company owner, Engineer, Senior CMS Engineer, Head of operators, Operator, and Head of installers have access to the Journal module.

To view receiver events:

1. Select the Journal module from the list of modules in the upper-left corner of the screen.

2. Select the object.

The Journal module will display a list of receiver events:

• Your company’s employee added a new receiver for cloud signaling monitoring.

• Your company’s employee changed the receiver settings.

• Your company’s employee deleted the receiver.

• Ajax Translator PRO lost connection to Ajax Cloud.

• Ajax Translator PRO restored connection to Ajax Cloud.

• Ajax Translator PRO lost connection to the monitoring station.

• Ajax Translator PRO restored connection to the monitoring station.

• Your company’s employee started monitoring the object via the receiver.

• Your company’s employee updated the object’s account number for the receiver.

• Your company’s employee stopped monitoring the object via the receiver.

Set the range and apply it to filter events by time. To generate a report based on the specified parameters, click the report generation button next to the filter name.

Log timestamps and time synchronization

Log timestamps are taken from the local machine where the logs are displayed, provided that its time is synchronized with the server UTC time (the local time zone is also taken into account). If the local machine time differs from the server time, the system displays a notification with instructions on how to correct it.

To synchronize Ajax Translator PRO with UTC time, enable automatic date and time settings on your computer:

1. Go to date and time settings.

2. Check the box to enable time synchronization with the server.

Technical specifications

All technical specifications

Compliance with standards

Additional information

Contact Technical Support:

• email

• Telegram

Developed by “AS Manufacturing” LLC