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 Connections – Add – Rithmic, and then click the Next button.

Next, windows for signing an agreement will open:

OCO (One Cancels Other) orders for this 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 simultaneously.

1. Enter your Rithmic account login and password.

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

3. If necessary, check Aggregated quotes—in this case Rithmic will send simplified market data, which reduces CPU load but also lowers the speed of data updates.

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. Also, ATAS and RTrader Pro connector settings must match.

1. Log in to RTrader Pro by activating the Allow Plugins [ON].

2. In the settings of the Rithmic connector in ATAS, check Aggregated quotes and Connect via RTrader Pro.

3. Remember that checking Aggregated quotes means Rithmic will send simplified market data, which reduces CPU load but also reduces the speed of updating 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, enable this option.

7. Connection settings button.

8. Remove connection from the list button.

9. Connect/Disconnect – connect or 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 plugin, and the second without— the second one will not connect.

3. If one of the Rithmic servers is unavailable, the connection may be waiting for a long time. You connect, wait about a minute, receive an error, then change the server and connect again. You will need to wait several minutes until the previous connection fully closes.

4. Connection lost. In this case, ATAS will display a notification.

5. Potential connection loss. This is an intermediate state between "connected" and "disconnected." Rithmic sends messages like "PnL Connection – Heartbeat has been quiet for XX seconds." Similar messages can appear for Trading Connection, History Connection, etc. They indicate there was no data exchange for that specific Rithmic channel for the stated period. This can mean:

   1. If there are problems with the PnL connection, the price, volume, or position direction in ATAS (previously taken from an active connection) may not match what is on the Rithmic servers.

   2. If there are problems with the trading connection, submitted orders may be sent to Rithmic but their state may not be received back into ATAS.

6. In such cases, ATAS cannot guarantee that the displayed information is correct. Therefore, ATAS provides two mechanisms to protect a trader:

   1. When receiving messages like "PnL Connection – Heartbeat has been quiet for XX seconds," ATAS displays a pop-up with the text of this message.

   2. If the user tries to place orders or change a position after receiving those messages, ATAS will require confirmation, listing all Rithmic messages that appeared previously:

      

In this situation, the user must decide whether to execute the order. Similar messages are shown if the user trades through a Portfolio Group that includes the Rithmic account which triggered the data message.