Software discussion board

The TWSLink won't get erratic. But what could happen is, that you are not able to control which scripts (production, development)
are running in what orchart process. But for your purpose, you need to know this.

So we have isolated the problem: As TWSLink is loaded in this process (or TS loads DLLs in this process), you can only have one TWSLink instance. So a 2nd call of CONNECT disconnects the prev. session (in your case the live connection). Perhaps it is somehow possible to start multiple orchart proces...

Do you have both TS desktops running and how many ochart.exe can you see in the taskmanager ?
Thank you

You don't need TWS running for this. You need to check how to load 2 TWSLink instances. So the TS desktop setup should spawn 2 TWSLink instances, if TS desktops really run in separate processes and the desktop process loads TWSLink. Presumed you run live and paper desktop, you should see 2 TWSLink t...

Sorry, Did not pay attention to the two processes. You should see the process # of Live - Merion Live ----- and Paper -- SPX Paper ----- in C:\trade-commander\twslink2\log You should have twslink logs. Do you see something like p#, so folders beginning with p and a number - the process number ? Or, ...

The important point is: in which of those processes your scripts are running or in other words, TWSLink is loaded. I see 2 processes which are candidates for loading TWSLink: TradeStation Charting TradeStation But i would expect 2 of one of them. So i still guess you mention TWSLink running in 2 sep...

Make sure each TWSLink instance is running in a separate process. If not, then a subsequent call of CONNECT does a disconnect and reconnects to new site. This generates exactly the symptoms you described. Please have a look into the taskmanager. Can you see multiple TS processes? As i ask previously...

Then you do something wrong.
Is it definite, that the 2 CONNECT calls happen in different processes ?
Perhaps i can connect per TeamViewer on your machine, so we can clarify this.

I may misunderstood the word "desktop" in your last post. Ok, desktop means not machine or pc, instead the TS desktop. For me it sounds, you can decide how many desktops you like to open on your machine or computer. If you can do this, open one for development and one for production. As each desktop...

"not sure about your code"

Each TS process can load one TWSLInk. One TWSLInk can connect to one IB account.
A TWSLink license is per machine.

Sorry, don't know how to explain it more clearly.

2 dekstops are a solution. You need a 2nd TWSLink license and your TS costs are doubled, if i understood you correctly.

Ok. Have to think about. Meanwhile, you could get in contact with trade station support and ask them something like that: "I have a DLL plugin used in my TS scripts. Some scripts are for production, some scripts are for development. The DLL connects to a backend that can either be a production backe...

Possible yes, for instance using a custom DLL but eligible ? For me sounds very complicated.

What do you like to accomplish with paper and real trading same time. Can you describe this with few words ?

No. The license you have, basically allows running multiple TWSLink instances each connecting to different TWS. But as one Windows process can only load one TWSLink and one TWSLink instance can only connect to one IB account, you won't be able to connect to paper and real account at the same time fr...

With the normal license, you now can run as many TWSLink instance you like. Each TWSLink instance can connect to exactly one TWS. Each Windows process can load only one TWSLink instance (This applies for all kind of DLL,COM). So, if you run a single TS process, you just can connect to one TWS as you...

This version of TS, which is splitting into multiple processes, is younger than TWSLink. "..of course 32 bit..". After my opinion 32 bit processes are deprecated. As i mentioned, the TS dev Team most likely decided to split the application in multiple process to avoid checking old 32 bit code for 64...

"The problem is, you (Twslink) think in (windows-) processes, a TradeStation user thinks in charts" Exactly. This is the point. Let me think about. The challenge is provide the same clientid for the same group of symbols you trade AND that those groups are always below the same processid. I think th...

Storing in registry is like storing in database. TWSLink can access to odbc databases.
You just need to create your own database for that purpose and sql phrases to store and restore your variables.

As TWSLink is loaded per process, you need a clientid per process

Hello, i am sorry, global variables don't exist across processes. They just exist within process. (32 bit processes run in a virtual windows (syswow64). This windows can't see its host, the 64 bit windows.) To share variables across processes (in the same platform), you could save them to file as st...