Zorro version 2.15 is now available:

http://opserver.de/down/Zorro_215.exe

This version will become the official release when no bugs are found in the next time. Zorro 2.15 features starting, stopping,and communicating with other Zorro instances, new IB order types, more flexible bar generation, and many more. The full list of new features can be found on http://manual.zorro-project.com/new.htm.

Please test everything and report any issues here!

Hi jcl,

What is the recomended procedure to replace actualized Z strategies (Z7 & Z12) and parameters in a case like this where you have new features like BR_WEEKEND replacing WEEKEND so that you need the new 2.15 to run the Z strategies?

a. use the new Zorro 2.15 with new parameters NOW (in the case there are no such major changes you could use the new parameters with the old Zorro version).
b. whait till final release.

I guess you have tested Zorro 2.15 with the Z strategies already and found no bug, so a. wolud be safe. For other own developed strategies, final release is more obvious for me.

You can use 2.15. It passed all tests so far. When a parameter is replaced, the old one is still supported for a long time. Don't use it for new systems, but old system should still work.

Hi JCL,
Now that the weekend parameter is gone from the editable z.ini file, how does one set the weekend parameter, now called the BarMode flag for the edit locked z systems?
For example, it appears that no bar will be created, but will my instance still be logged into the exchange server?
Previously, the system would log out and log back in once trading was ready. This was very useful as the exchange would periodically update their local servers creating log in issues when weekend flag was not properly set.

Hi jcl,

apparently one file is missed. While testing Z7 i get following message:

Error 062: Can't open Z7_29.par (rt:2)
Error 044: Data\Z7_29.par not trained

and the test stops at February 2019.

Is it a missed file? ( Z7_29.par) Or do i have other issue with my setup?

The Z systems have their own bar mode flags, so the weekend parameter is not needed anymore. Explicitly logging off is also not needed - this was required for the old FXCM API, but not anymore for the new one.

AFAIK there is no "Z7_29.par". Such error messages could be caused by mixing up new and old versions.

The manual has an error.

On the bottom of this page is a link to callback():
https://zorro-trader.com/manual/en/hwnd.htm

But it's a bad link. I believe it should go here:
https://manual.zorro-project.com/tick.htm

Thanks, you're right.

Update on my question: Weekend here and my log is now spammed with "Service Unavailable. Please try again messages". As previously mentioned, this was solved by logging the system out and then back in. The other benefit was that sessions were guaranteed to re-authenticate which did not always happen under previous versions of zorro without weekend flag. I am using OANDA API

[So,

time to time is a problem with *fac. Train mode not correct close the file.


After close Zorro with net run is all OK

( sorry for czech )

- Service unavailable: this message is suppressed, so you should normally not get it at all regardless of the logoff flag. Please contact Support with the log.

- Fac file locked: Did this also happen with earlier versions? Under which circumstances?

A new version 2.15.2 was uploaded to http://opserver.de/down/Zorro_215.exe. The heatmap bug was fixed in this version.

I just tried emailing support but the logfile was too large to attach. I copy and pasted logfile snippets and information for support

FYI, log files usually compress very well into zip files. Also, consider sharing large files via a service, such as Google Drive or Microsoft OneDrive.

Good suggestion Andrew!
For anyone's interest, support came back and issued a new Oanda DLL that will hopefully suppress the messages I'm receiving.

Hi jcl,

I have just tried to test the Z12 with 2.15. However, this seems to become an S only feature? Is this a bug or intended change? I have also found out testing Z9 requiring S license.

Yes, Z12 and Z9 run with Zorro S only. But you can test Z1 and Z2 - Z12 is a combination of them.

Hi jcl,

about the new feature " Zorro instances can now start, stop, and communicate with each other."

I have two Zorros 2.15 trading in an AWS, a Z12 and my own script. I see that the seccond Zorro (my own script) starts trading and then seams to log-off, but the Trading Status page continues to deliver new updates every minute. So i understand the seccond Zorro gets price information from the first one, since they are both connected to the same broker, but different accounts (Dukascopy).

What hapens when one of the Zorro freezes or crashes? Any conflicts if BarPeriod are different? Guess not since it works.
What about placing orders? Will the seccond instance re-connect, place orders and then disconnect again? How does this works?

From the manual under "Integrating Zorro processes" i get very few infos on this. Is there any more detailed information on this feature?

A suggestion woud be to include another color on the Zorro indication square, green when connected, red when offline and another one to specific say it gets data from another Zorro. Otherwise, as in my case, if you look at the Zorro instances one of them seams to be disconnected. There is no error message but the square is red.

By default the Zorros are not connected. For this you need code to establish the connection with the commands described in the manual. The minute update of the status page is a HTML effect.

Indeed... after a while the square was green again and they are independently working as usual.

But, what was that period of time where one of the instances was disconected? hmm, will keep an eye on it and report any other issue/effect i can see.

12.07.2019: this was a behaviour related to the new BarMode, specifically BR_LEISURE in combination BR_SLEEP and BR_LOGOFF. In this way Zorro trades only between StartMarket and EndMarket which by default are 9:30 to 16:00 only, and i was looking outside these hours. My intention with the script is also to trade longer times, so i need to modify my script again.

Problem with chart viewer:

begin with the 2.15.2 I have problem, I see not bottom of chart.



note: repeat with workshop4.c

Does it happen with a special script, or with all scripts? If with a special script, can you post it?

It happens with any script, which plots an indicator or other data below the price curve. At least for me it does. An example script, as already said is Workshop 4.

I see the same behavior. Selecting Workshop4 and hitting "Test" results in a chart window with the MMI plot mostly cut off.

Thanks, we'll look into that. It seems to happen only on some PCs.

Update: We found the problem. It should not happen with the latest version, 2.15.3. The download link:

http://opserver.de/down/Zorro_setup.exe

This is now the official release.

Looks like it's fixed for me. Thanks!

So,

I dont know, if is a problem with 2.15 but:



have output:


unixtime is less by -1

workaround:
string cOutput=strf("\nUnix: %d TimeDate: %s StrDate: %s",utm(wdate(0))+1,datetime(),strdate("%Y-%m-%d %H:%M", wdate(0)) );

This is caused by data type conversion: DATE is a double float and the unix time is an integer. The correct fix would be rounding to the next full second:

utm(wdate(0)+0.5/(1440.*60.))

I've put a notice to the developers for doing that on the next occasion. It is not related to 2.15.

What I do miss a little bit with 2.15 is the Zoom Out function in the Chart viewer of previous versions. Now I can always only click on "Total" to see the entire chart again. Makes navigating large charts more cumbersome.
I have attached two pictures to show the difference.
Are there any plans of allowing to gradually zoom out again in the future?

Nothing has changed with zooming. Only the text on the button.

edit: is OK, bug is not in Zorro but in my script

I have new problem with Zorro 2.15.0 S. If running on the WIN server 2012 I see this ( picture ). First instance is OK, but If start second and more is a very slow.

plotWeek() function may have some problem.
Please check the attached file.

What's the problem?

I think blue bar need to be drawn first. Red bar interrupted by blue bar.

That makes sense, but it's just the order of plot commands in the script - has nothing to do with 2.15.

I'll put a notice to the developers to draw the blue bars first.

I this problem already send but still is on table. With Zorro 2.15.3 and win server 2012, I see in the "task manager" Zorro "not responding". I trying use lock() and unlock() but no change. If running only one instance, all is OK.


I found the same problem with older version:

https://opserver.de/ubb7/ubbthreads.php?ubb=showflat&Number=474020#Post474020

There can be many reasons why two scripts lock each other or get nonresponsive. For instance by an infinite loop or when they write in the same file. Or the server has not enough resources. If you can't find the problem on your own, explain the details and post the script, but please in a different thread. This one is for Zorro 2.15 only.

Hi jcl,


With the weekend parameter we had two holidays included by default:
"December 25 and January 1 count as weekend. Other holidays are not automatically included, but can be taken account of in the script."
25.12. is also included in the new bar mode on Z strategies, but apparently the 1.1. is not...
Tested with Zorro 2.20.2:
Z2 tried to open several positions during New Year's Day and wanted to close one position here. After the market opened again at 23:00 it immediately closed that position under very bad conditions (huge spread due to just opened market). The positions it previously wanted to open on 1.1. it didn't try again after the market opened, though.
Is there any way to specify the holidays / marked closed periods for the Z strategies? Or is it just a bug in the bar mode flags or the usage in the Z strategies scrips that will be fixed in the future?
Thanks.

Hi,

I had the same experience on 01.01.2020 with Z12 and Z2.
Also my own scripts, that contain BR_WEEKEND had the same issue.
I now added BR_LEISURE in my script, will this perhaps resolve the problem? (of having Zorro activity in a closed market period?)

Thanks.