Trading Systems Leaders in this forum (automated trading systems) are winning more than 3000 pips in a month (30000$ investing one lot every time). Click here to register and get more information
Today, I conduct some 3 months backtests for EURJPY and play around with the MaximumRisk, DecreaseFactor and the MM.
With the MM=true, adjusting the DecreaseFactor will have a little change in the result but the number of consecutive loss doesn't. Can anyone tell the actual function of this DecreaseFactor?
An updated version of Phoenix 5 (version 5.6.02).
- we now have the follwing pairs: USDJPY, EURJPY, GBPJPY, USDCHF, GBPUSD.
- to avoid mistakes in choosing the right mode, there is now only one parameter for this : PhoenixMode. Classic mode=1, SencondTrade mode=2 and 123 mode=3 (thanks Herbert).
- MicroAccount was still not working. Changed the code as suggested by lgvh.
May I suggest to have the code changed to set Phoenixmode=1, 2 or 3 instead of the 3 booleans for mode switching, which can be set to true at the same time by accident or without knowing?
Regards
Great idea Herbert! Thanks.
I was actually thinking of taking advantage of this "feature" and run them in combination to see how they would perform. Just for curiosities sake ;-)
If you go to have a look of the trading platform's directly, (fxdd-metatrader)\config\***.srv, you may see 2 *.srv files, one is *-live.srv and the other is *-demo.srv. Therefore, it is hard to say the datafeed for the Live & Demo are the same.
Of course, many other brokers do the same.
I just have to take their word for it. Once I open my account there then I'll be able to really validate their claims.
I'm not sure what you mean with "Phoenix may open 5 trades for 1 currency". If that's the case then I think you have more than 1 Mode set as True. You have to set only one of the three modes set as True.
I'm not quite sure if the "5 trades per currency" is valid, but I guess one of the reasons why I brought up the MM side of things is that "ideally" I'd like the Risk parameter to represent my potential for loss on one signal (wheatver it be 1 trade or 2 or 3 trades).
So for example in mode 1 if we have a signal and a setting of Risk of 1%, to me that would mean that I can loose at most 1% of my account value on this particular signal.
Another example, in mode 2 where there may be two trades as a result of the one signal, then most likelly it would be preferable to split the 1% into 2 parts and risk each part on each trade. (though this is a bit slippery in this case since if I'm not mistaken the second trade doesn't come into play untill the first trade is set at BE and in profit already)
Hopefully I'm not confusing things here, but that was my intention initially.
- MicroAccount was still not working. Changed the code as suggested by lgvh.
Manual for Phoenix is updated.
The modifications I suggest had been tested with the competition version, now I review in full the new code, here follows the necesary modifications for thes new version:
1- There is some compatibility problem with the variable name "MicroAccount" with the compiler, I rename it to "Micro_Account" (must be done in all code)
2- In addition to the original sugested corrections it is necesary to change
int CheckOpenTradeMode123()
{
int Signal = 0, err = 0, total = OrdersTotal();
double lots123 = NormalizeDouble(LotsOptimized()/3,1);
if(lots123 < 0.1) {lots123=0.1;}
to
int CheckOpenTradeMode123()
{
int Signal = 0, err = 0, total = OrdersTotal();
double lots123 = NormalizeDouble(LotsOptimized()/3,1);
if(lots123 < 0.1 && Micro_Account==false) {lots123=0.1;}
if(lots123 < 0.01 && Micro_Account==true) {lots123=0.01;}
I'm sorry to post the corrections without test the new version , I just saw the LotsOptimized() function that was the same (with the exception of the change of the variable name AccountIsMicro) and I posted in a hurry the code that worked for the previous version. Excuse my English, hope you understand
The modifications I suggest had been tested with the competition version, now I review in full the new code, here follows the necesary modifications for thes new version:
1- There is some compatibility problem with the variable name "MicroAccount" with the compiler, I rename it to "Micro_Account" (must be done in all code)
What was exactly the compatibility problem with the variable "MicroAccount"?
I'm not sure what you mean with "Phoenix may open 5 trades for 1 currency". If that's the case then I think you have more than 1 Mode set as True. You have to set only one of the three modes set as True.
Yes Hendrick,
It is true that Phoenix 5 can open up to 5 trades at once, if we switched on all the modes. But I guess it is not tested yet (?)
However I like when seeing combination of the modes, compare to combination of the currency pair. Seeing your success trade on championship, I think better to concentrate on USDJPY rather than concentrating on other pairs.
See this result? it is an amizing Phonex 5, can turn $1000 to $1 million within 6 months of trade. I am using mode 1 and mode 3.
The risk is 0.3, using 2 modes it will consume 60% of the free margin.
It is very great in backtest, but Let's see how it perform in forward test.
It is true that Phoenix 5 can open up to 5 trades at once, if we switched on all the modes. But I guess it is not tested yet (?)
However I like when seeing combination of the modes, compare to combination of the currency pair. Seeing your success trade on championship, I think better to concentrate on USDJPY rather than concentrating on other pairs.
See this result? it is an amizing Phonex 5, can turn $1000 to $1 million within 6 months of trade. I am using mode 1 and mode 3.
The risk is 0.3, using 2 modes it will consume 60% of the free margin.
It is very great in backtest, but Let's see how it perform in forward test.
Well Fikko. So you've just discovered how to become a millionaire in 6 months with Phoenix. Thought I could keep this a secret for myself .
Problem is, I just changed the code in version 5.6.02 to prevent this. So what should I do? Change it back to the old settings or what? Anyone?
, I just saw the LotsOptimized() function that was the same (with the exception of the change of the variable name AccountIsMicro) and I posted in a hurry the code that worked for the previous version. Excuse my English, hope you understand 
.
Linear Mode
