> For the complete documentation index, see [llms.txt](https://docs.motivewave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motivewave.com/knowledge-base/connection/interactive-brokers-connection/troubleshooting-interactive-brokers-connection.md). # Troubleshooting Interactive Brokers Connection Here are things to double check when connecting Interactive Brokers (IB) with MotiveWave:\ 1\. TWS must be running and you must have a live feed. You can only connect with an IBKR Pro connect and not a Lite account as it does not support API connectivity.\ 2\. TWS must be configured as per the following link: . Pay close attention to the specified port number as this must match the port specific in your MotiveWave workspace.\ 3\. If you are accessing your IB account from multiple platforms then you must specify a Client Id other than 0 such as 3:
4\. If you have more than 100 active tickers then IB will cut off data for excess symbols. You can check your Active Ticker count within MotiveWave via the ***View > Active Tickers*** menu. If you are showing more than 100, then you would need to close charts and/or watchlists to get the number back down to under 100. Another option would be to purchase [Booster Packs](https://www.interactivebrokers.com/en/index.php?f=14193) from Interactive Brokers that will allow you to have more than 100 active tickers.\ 5\. If you are experiencing charts that are not updating, you can also double check to make sure you have Extended Session selected by right clicking on the chart and then selecting ***Extended Session*** via the right click menu.\ 6\. If you have done all the above and it still does not work, then please send email to with a copy of all your log files available via the ***Help > Log Files*** menu. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.motivewave.com/knowledge-base/connection/interactive-brokers-connection/troubleshooting-interactive-brokers-connection.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.