Yes. I always test with real $. This way I won't feel riled when my profits were only virtual money.

Wow! I hope to someday have your confidence of always making profits!

In the meantime, a Trade started at 02:23 UTC yesterday produced its 1st plot at 00:00 UTC today - ~22 hours later - and hasn't updated the plot since. I plan to run another test Trade today.

Is there a reason for the 00:00 1st plot and the 24 hour cycle? My speculation is that as Trading continues plotting time will increase and at some point overwhelm the strategy - therefore restrict it to 1x/day and at a quiet hour...

Thanks.

Well, I didn't expect to report on the beta so soon, but here it is: Unzipped to Zorro folder & ran Zorro. 1st problem is Zorro now defaults to MT4 and have to manually change it to FXCM.

Did Trade & trades resumed. Printed 1 bar and then an Internet glitch hit. Box went red. Internet came back and box went grey. After ~10 minutes of grey & Offline, clicked Stop, No, No. Zorro hung. Clicking red X a few minutes later gave not responding error. Force closed. Restarted. Again had to manually change from MT4 to FXCM. So far this 2nd Trade is OK.

HTH.

I can not comment on the MT4 default, as Zorro has no broker default. But if the FXCM API problem happened with the beta as well, it seems to be unrelated to the API version. I also heard from FXCM that they can not confirm such problems, neither with this nor with the previous beta.

Maybe the continuing FXCM problem is in fact an issue of your PC? Do you have the possibility to test on a different system?

Also, can you post the diag.txt from the situation when Zorro hung? Maybe we can then see which API function it was and forward the info to FXCM.

Thanks jcl. It of course could possibly be a problem with my PC or its configuration. But I don't have another PC readily available...

Re. diag.txt, I can't find one containing the issue - perhaps buffers weren't flushed when Zorro crashed? Also, I'm seeing multiple diag.txt's - with and without asset names in the filename. What is the difference between them and which diag.txt(s) should I be looking for?

None of them appear to be time-stamped. Would it be possible to create separate time-stamped files rather than appending so it would be obvious which file related to which strategy run?

Thanks.

Under Windows, you can see the time stamp of files in the Windows explorer. So when you know at which time the crash happened, you can identify that file and post it here. It does not matter if Zorro crashed, its content can nevertheless give some info.

If a script uses only a single asset, the asset name is added to the file name. This way you can see with which asset it was generated.

Thanks jcl. Yes, I'm aware of Windows timestamp & use it. Nevertheless, couldn't find an appropriate *diag.txt for this issue. Perhaps too aggressive cleaning up...

Re. *diag.txt names, I've seen a strategy that uses only a single asset produce *diag.txt's both with and without asset name. Why would that happen?

Thanks.

If the script is the same, the diag.txt name should also be the same. But maybe you've changed the script by adding or removing a asset() function or a loop() function?

Don't think so. No loop() and only 1 asset().

I'll try to watch this closer and advise if I come up with anything.

Thanks.

Hi jcl. If I get agressive and upgrade Real trading to the 1.32 Release this weekend, would you advise also adding the newer FXCM API beta? Or leave that just for test Demo Trading for now?

Thanks.