Trading Robot Between TradingView and Interactive Brokers

In this section, We will start by taking a top-down approach to understanding the architecture of an automated trading system

1. A high-level overview of automated trading systems

2. Examining the trading robot itself

3. The brain of the trading robot and its role and architecture

In this section, you will learn How to Set Up TradingBoat Docker in 5 Minutes.

• Firstly, I will explain the reason why I’m using Docker technology for this training.

• A Step-by-Step Guide on how to install a docker and how to run

• You will learn how to access the docker container in two interfaces:

  • Use a web browser to access HTTP server inside the container

  • Use a VNC viewer to access VNC server inside the container

To access TBOT on TradingBoat from outside the network, a door key and the receiver address are required: two pieces of information are needed for TradingView to access TradingBoat.

In this section, we will explore two important aspects of TradingBoat's web interfaces:

• TVWB provides the webhook key for TradingView's PineScript TBOT library.

• NGROK provides the endpoint URL that TradingView's alert messages are sent to.

In this session:

• Learn how to set up Alert Messages under TradingView's Alert Settings

• Verify if alerts arrive at your Docker (TradingBoat)

• Confirm if alert messages are converted into Interactive Brokers' orders

The simplest way to track orders from TradingView's message to IBKR is by using the Web Browser Interface. On this video, there are four important components of the interface:

1. Alerts: These are webhook messages received by TBOT on TradingBoat from TradingView. The important columns to search for a specific alert are TBOT_TIME and ORDERREF.

2. Orders: This table displays order history, open orders, and portfolio from IB Gateway. Orders that are shown on the Orders Table are equal to those on IB Gateway.

3. TBOT: This is the inner JOIN table between Alerts and Orders used to track the transition between webhooks and orders.

4. Errors: This table displays error messages coming from IB Gateway or TWS.

In this section, we will demonstrate how to generate alert messages from TradingView to send to TradingBoat. We will be using a simple PineScript strategy in conjunction with a specialized PineScript Library that creates a JSON message.

The Web Interface we saw at http://127.0.01:5000 is a read-only interface. To configure multiple software components inside Tradingboat Docker, we can use environment variables that can be found in the provided materials.

As demonstrated in the accompanying image, you can manage multiple software components, such as Redis, TBOT, IB Gateway, TVWB (Flask), and messaging apps.

This video will guide you through using the DOTENV file, tbottmux utility, and controlling individual applications within the Docker environment.

TradingView's PineScript language allows users to create trading algorithms that can be tested and implemented in the markets.

By employing the PineScript TBOT library, users can send their algorithms' outputs to TBOT on TradingBoat using pre-defined JSON format messages, enabling efficient communication and streamlined automated trading systems.

Understanding the JSON data format and the architecture of the TBOT system is crucial for effectively utilizing the PineScript TBOT library in TradingView.

• JSON (JavaScript Object Notation)is a user-friendly data format used to transfer information between applications, websites, and servers due to its simplicity and wide compatibility.

In this section, we will examine the JSON data format employed by the PineScript TBOT library and TBOT on TradingBoat.

Thank you for spending time with me. I hope that this trading guide provides you with a useful reference to explore TBOT on TradingBoat further so that you can take advantage of it.

TBOT on TradingBoat can be easily deployed to cloud computers and should serve as a reference platform that can be further customized.