The connection between MT and FST works via a named pipe. If we start another instance of FST or MT they interfere each other. I don't know how to workaround this.
I'll experiment later with different named pipes for the different instances. A possible solution is the expert to generate unique pipe name at start up. After that this name to be entered in FST. In that case each couple expert - FST will work with their own pipe.
Any suggestions and ideas are welcome.
I was thinking exactly the same thing. Give the name of the pipe as parameter to the expert, and the same name in FST on startup. Then FST will attempt the connection, if it fails it can show a message that the specified pipe was not found.
Alternatively it might be possible to scan the pc for existing pipes and their names on FST startup, and suggest to the user which pipe/expert wants to connect to. But I am not sure if this can be done because I never worked with pipes before. But I will look it up and post here.
Edit: did a quick search, it's possible to discover existing pipes. http://www.coastrd.com/fcgi-white-paper/enum-named-pipes
I tried the exe and found 2 pips MT4 to FST and opposite way. Seems quite easy. So user configures pipe name in EA as parameter, FST discovers pipes and suggests to the user which one to connect to.