Ive been using ExportData in a layout for over a year now to export my variables to use in Excel. I have multiple 7 charts on layout exporting over 100 variables. It has worked flawlessly since i started for the most part. I have however had times where a condition in my excel workbook is trigged constantly after market opens and i have always thought it was something with my coding that for the life of me i could not debug. I usually try closing the chart that has the variables that are used in the excel condition which never works. I also try to close and reopen the chart that has the actual ExortData on it which also doesnt work. The only thing that usually fixes it is closing and reopening that instance of IRT. However, today i closed IRT and my excel workbook is still receiving data which comes from the CSV that ExportData writes too. It been over 20 minutes and its still updating with the wrong data with that instance of IRT closed.
Scenario of whats happening... Excel updates every 10 seconds and ExportData writes every 10 seconds also. For some reason every 2-3 runs my sheet would update with incorrect data. The same incorrect data each time. Then 2 runs later it would get correct data again and that would trigger my condition in excel.
Im not sure whats going on here but i only recently started using the 2nd instance of IRT. Since i have, Ive had my original instance of IRT crash some nights and restart while im trying to develop something. Its only crashing due to my lack of RTL skills but when i restart IRT im sometimes notified that the data base is in use already( I believe that was it says but not 100% sure). Same thing has happened when i start 2nd instance at times.
Is it possible that i set something up wrong when i setup second instance of IRT? Or is my issue most likey related to something else and the 2nd issue i mentioned is just random occurrence that is happening at times due to running 2 instances?
Thanks,
Dean
I just found ExportData on a chart that was on a hidden layout i opened earlier. The layout wasnt supposed to be set to hide, That obviously must have caused my issue with my workbook still receiving updates and why i had wrong data every few runs.
Still curious as to why i get that message while reopening 1st instance some times though. Could i have setup up 2nd instance wrong?
Hi Dean,
there is a critical setting when it comes to managing "inactive" layout. As highlighted on the info button,
If needed, more detailed information is available here (The layout toolbar has been adjusted a bit since this video was created, but the principles are the same)
https://www.linnsoft.com/videos/using-layout-toolbar
Eddy
Note : I am 99% sure the installation process of your 2nd instance is fine. If you are running 2 instances at the same time, and if the second instance is crashing (because you did some "experiment" that was not "CPU compatible"), then don't worry about the "database is already in use" type of message (which, I think, is designed to avoid starting twice the same instance). You can usually restart safely the second instance while the first one will keep running normally.
By the way, if you are experimenting a lot, it is always a good idea to do it on a separate instance to split your live trading and data-gathering environment from your chart development & experimentation activities (and, for your "experimenting instance", to make sure that all your inactive hidden layouts are effectively closed).
With today's CPU having 12 or more cores, running simultaneously 3 or 4 IRT instances is not an issue (together with IQ feed, R trader Pro and possibly other trading software)
If you want an extreme reference point, I have been running (simultaneously and over very long periods) up to 10 versions of IRT on a 32-core AMD threadripper without any stability issues.
I actually use hidden layouts already. I just didnt realize that the layout i had opened in my main instance of IRT earlier in the day had been set to hide previously. Sorry for the confusion there. Also, glad to know that message im seeing at times isnt something to be concerned about. Your idea of using a 3rd instance just for development and experimentation make so much sense. When i started using a 2nd instance of IRT for exporting data i should have set up one just for that too.
Thank u,
Dean