Connecting to Rithmic

This guide provides instructions on how to connect an account via Rithmic to ATAS.
There are 2 ways to connect your Rithmic account to ATAS - directly and via RTrader Pro. Instructions for each of them are given below.

• Connecting Rithmic account directly to ATAS
• Connecting a Rithmic account to ATAS via RTrader Pro
• An important feature of Rithmic connection.

For APEX accounts check  additional connection recommendations

To configure the Rithmic connection to the ATAS platform,  in the platform's main window, click on Connections - Add - Rithmic, and then click the Next button

Next, windows for signing an agreement will open:

OCO (One Cancels Other) orders for connection are simulated locally on your computer. This means that the platform must be connected to your broker for OCO orders to work properly. If you get disconnected and one of the OCO orders is executed, the other orders in the group WILL NOT BE canceled! If you are okay with that, click I Accept, Please continue.

Connecting Rithmic account directly to ATAS

The account must NOT be connected to RTrader Pro or another platform

1. Enter your Rithmic account login and password

2. Select a server depending on the account type and broker

3. If necessary, activate the checkbox next to Aggregated quotes - in this case Rithmic will send symplified market data, which reduces the load on the CPU, but at the same time reduces the speed of updating this data.

4. Uncheck the box next to Connect via RTrader Pro

Connecting a Rithmic account to ATAS via RTrader Pro

Only one Rithmic account can be connected to ATAS via RTrader Pro
ATAS and RTrader Pro connector settings must match

1. Log in to RTrader Pro by activating the Allow Plugins [ON] and Aggregated Quotes [ON] functions

2. In the settings of the Rithmic connector in ATAS, check the boxes next to Aggregated Quotes and Connect via RTrader Pro

3. If necessary, activate the checkbox next to Aggregated quotes - in this case Rithmic will send symplified market data, which reduces the load on the CPU, but at the same time reduces the speed of updating this data.

After configuring the connection, it will appear as a separate line in the list of connections.

You can read about the settings of this window at the following link: Connection Settings Window

1. Add - add a new connection.

2. Type - connection source.

3. Name - connection name which you can set yourself.

4. Status - connection status.

5. Quote Provider - option to select a quote provider (this connection will be used as a quote provider).

6. Auto-Connect - if you want the connection to automatically occur when the platform is launched, you need to enable this option.

7. Connection settings button.

8. Remove connection from the list button.

9. Connect/Disconnect - connect/disconnect the connector.

An important feature of Rithmic connection.

Often the Rithmic connection is quite sensitive to the communication channel and CPU load. If the CPU is heavily loaded or there are problems with the communication channel, the Rithmic connection may become unstable.

There may be the following connection problems:

1. If you enable the plugin connection and then try to connect without the plugin, it will not work until the application is restarted.

2. If you create 2 connections, one with the connection via plug-in, and the second - without, the second one will not connect.

3. If one of Rythmic servers is unavailable, the connection may be waiting for a long time. You connect, a minute passes, you get an error, then you change the server and connect again->you will ned to wait a several minutes until the previous connection closes completely.

4. Connection lost. In this case, ATAS will pop up the notification.

5. Potential connection loss. This is a kind of intermediate state between connected and broken connection. At such moments, Rithmic sends messages like: ‘PnL Connection - Heartbeat has been quiet for XX seconds’ . Instead of a PnL connection, there can be Trading Connection, History Connection, etc. These messages indicate that there was no data exchange with the corresponding Rithmic connection (PnL, trading, historical, etc.) for a certain number of seconds. For a trader, this can mean the following:

   1. If there are problems with the PnL connection: perhaps the price, volume, direction of positions (which were received before from a working connection) in ATAS may be different than others on the Rithmic servers.

   2. If there are problems with the trading connection: submitted orders may be sent to the Rhimtic servers, but their statr may not be recieved back to ATAS

6. That means, if there are problems of this type with Rithmic connections, ATAS cannot guarantee if the displayed information is correct. Therefore, ATAS provides 2 mechanisms to protect a trader from such situations:.

   1. When receiving messages likePnL Connection - Heartbeat has been quiet for XX seconds , ATAS displays a pop-up window in which it displays the text of this message.

   2. If user tries to place orders or change the position after recieving those messages, ATAS will require confirmation of the operation, which will indicate all messages from Rithmic that were received earlier:
      
      

In this case, the user will need to decide for himself whether to execute this order or not.
Similar messages are issued if the user trades through a Portfolio Group,
which includes the Rithmic account that received the message data.