[Geko]

Post 1 updated with latest DB version.

There are no major modifications in this version.

As suggested, I am going to increment the DB version number starting from now. So, the posted version is now: v 1.01.

vv.png

I have used the same DB name, but if your guys prefer, I can add the DB version in the DB name to make something like this:

! - !-GiG-!--Dashboard-05-v.1.01.ex4

However, to make it easier to install updates, until now, you just had to erase the previous DB version with the new one. If I change the DB name for every single update, if you want to erase the previous version, you will have to change the DB name back to

! - !-GiG-!--Dashboard-05.ex4

I am going to increment the PDF user guide version number also.

[Geko]

I'm all set up for the week ahead. Default colors were hard for me so I made a few changes.

And a suggestion for Geko about the INFOS headings. For me, when I see ADR, I think this is the result of the calculation, usually like this - ADR (14)

And what I'm looking for in the heading is to see how many pips Today; please see the picture.

An excellent EA and I'm sure excited to try it out soon!

Noted for next update as new update already posted

[mrdfx]

Geko I was reading on your CCFp results thread about how you open on LO and you've noticed that on NY open some trades might revers? Do you think then perhaps its better to set the baskets to LO and LC?

I've currently set some to open at LO and some 1hr after like forexpinbar does and all baskets to close at end of NY session. If the NY session might affect the LO baskets performance negatively then maybe its better to close them early.

[Geko]

Good evening guys, during the week-end? when I have modified the code, I have created a glitch. I tried to simplify a few lines of code and I broke the auto GMT thing.

I just fixed it and I have tested on different brokers to make sure it is ok.

Sorry for this inconvenience, please make sure to redownload the DB from post 1 which is v 1.02 now. Without this fix, you might have some issues if you are using the auto GMT mode with sessions open function. You might want to update your file before London Open. Just replace your previous file with this one, and check that the times below the DB are ok.

As I know it was not the best timing to create this glitch, I have also included another tips to make it possible to place a label in the DB to identify easily which settings are applied:

ti.png

[firewight]

Good evening guys, during the week-end? when I have modified the code, I have created a glitch. I tried to simplify a few lines of code and I broke the auto GMT thing.

I just fixed it and I have tested on different brokers to make sure it is ok.

Sorry for this inconvenience, please make sure to redownload the DB from post 1 which is v 1.02 now. Without this fix, you might have some issues if you are using the auto GMT mode with sessions open function. You might want to update your file before London Open. Just replace your previous file with this one, and check that the times below the DB are ok.

As I know it was not the best timing to create this glitch, I have also included another tips to make it possible to place a label in the DB to identify easily which settings are applied:
ti.png

LOL I didnt have a great start thismorning... Loaded the new DB and a bunch of trade went in automatically... It wasnt even the correct session times lol!

[firewight]

Good evening guys, during the week-end? when I have modified the code, I have created a glitch. I tried to simplify a few lines of code and I broke the auto GMT thing.

I just fixed it and I have tested on different brokers to make sure it is ok.

Sorry for this inconvenience, please make sure to redownload the DB from post 1 which is v 1.02 now. Without this fix, you might have some issues if you are using the auto GMT mode with sessions open function. You might want to update your file before London Open. Just replace your previous file with this one, and check that the times below the DB are ok.

As I know it was not the best timing to create this glitch, I have also included another tips to make it possible to place a label in the DB to identify easily which settings are applied:
ti.png

LOL I didnt have a great start thismorning... Loaded the new DB and a bunch of trade went in automatically... It wasnt even the correct session times lol!

AAaaaaaand it just did it again! Quick way to wipe out $10 from my account on Monday morning! Something weird is going on, I have auto sessions set to false, with mon to fri set to false...

[firewight]

Good evening guys, during the week-end? when I have modified the code, I have created a glitch. I tried to simplify a few lines of code and I broke the auto GMT thing.

I just fixed it and I have tested on different brokers to make sure it is ok.

Sorry for this inconvenience, please make sure to redownload the DB from post 1 which is v 1.02 now. Without this fix, you might have some issues if you are using the auto GMT mode with sessions open function. You might want to update your file before London Open. Just replace your previous file with this one, and check that the times below the DB are ok.

As I know it was not the best timing to create this glitch, I have also included another tips to make it possible to place a label in the DB to identify easily which settings are applied:
ti.png

LOL I didnt have a great start thismorning... Loaded the new DB and a bunch of trade went in automatically... It wasnt even the correct session times lol!

AAaaaaaand it just did it again! Quick way to wipe out $10 from my account on Monday morning! Something weird is going on, I have auto sessions set to false, with mon to fri set to false...

OK so I just switched back t demo account, made 100% sure everything was set to false, every day, ever session and also the use session times was false, but trades still automatically were placed...

Capture.JPG

[firewight]

Also, weirdly, under what circumstances will the DB keep putting in trades from 1 signal?

This screen you can see there are multiple trades for each signal. the lot size is 0.01, but there are quite a few trades now, and they keep getting added...

Capture.JPG

[firewight]

Also, weirdly, under what circumstances will the DB keep putting in trades from 1 signal?

This screen you can see there are multiple trades for each signal. the lot size is 0.01, but there are quite a few trades now, and they keep getting added...

Capture.JPG

My test is still going, even after it hits a SL, it opens more and more new trades... The Version 1.0 I tested last week did not do this, but I dont know if its a setting problem or a bug with the new version...

[TheSnowman]

Also, weirdly, under what circumstances will the DB keep putting in trades from 1 signal?

This screen you can see there are multiple trades for each signal. the lot size is 0.01, but there are quite a few trades now, and they keep getting added...

Capture.JPG

My test is still going, even after it hits a SL, it opens more and more new trades... The Version 1.0 I tested last week did not do this, but I dont know if its a setting problem or a bug with the new version...

When I ran it first time last Friday, I had set the Section 5 - Maximum Trades to 10 thinking it was total trades, and it opened a lot of multiple trades on demo.

So now I'm thinking that setting is Trade per Signal

Have you put more than 1 in there?

Other than that, it's work fine for me today at Tokyo Open, I used LOcal Time setting +10:00,-11:00

Good luck

2017-05-29_14-50-39.png