Try TT Now

ADL®

ADL FAQs

Find solutions by reviewing frequently asked questions about ADL

Certain questions recur as users go through the process of learning ADL. Before opening a support ticket, look here to see if your question has been answered. For questions about risk management, please review Risk Management in ADL FAQs.
Drag the block onto the ADL Designer canvas and right-click on it. From the right-click menu, select Help… for information about that block type.
Regardless of whether you’re in simulation or production mode, you need to collect workstation log files.
  1. Double-click the Guardian icon in your system tray located in the lower-right corner of your desktop.
  2. From the menu, click Tools | Collect LogFiles.
If you are in production mode, you also need to collect Algo Strategy Engine (Algo SE) log files. Please contact your clearing firm for these files.
You must be permissioned in TT User Setup to deploy algos. Ask your risk administrator to complete these steps:
  1. Log in to TT User Setup.
  2. Click the Users button.
  3. Double-click the appropriate username.
  4. Click the Gateway Logins tab.
  5. From the Gateway column dropdown menu, select AlgoSE.
  6. Find the trader's MemberGroupTrader I.D. (i.e. Gateway Login) and select the corresponding box in the Algo Deployment column.
  7. Click Save.
Once these changes are complete, log out of X_TRADER ®, then log in again. You should be able to deploy algos.
You need to adjust your 32-bit display setting.
  1. In the ADL Designer canvas, click Edit | Preferences.
  2. Un-check the Use Hardware Acceleration box.
  3. Click OK.
You need to adjust your 32-bit display setting.
  1. In the ADL Designer canvas, click Edit | Preferences.
  2. Un-check the Use Hardware Acceleration box.
  3. Click OK.
It depends on the circumstances. For details, please refer to the Disconnects, Crashes, and Restarts section of the Algo Strategy Engine System Administration Manual.

When you enable risk checking in Algo SE, the application performs a complete risk check, which is affected by trades made on all gateways. If your X_TRADER is logged in to gateways that Algo SE is not also logged in to, Algo SE won’t complete the risk check, and it will prevent you from launching algos.

For example, if your X_TRADER logs in to CME-A and Eurex-A gateways, but your corresponding Algo SE is configured only for CME-A, Algo SE will not be able to complete the risk check and will prevent you from launching algos. This wiill hold true even if you only want to launch algos on the CME-A gateway.