Graham, thanks for the live account especially the full access to look at history etc I hate it when people lock half the stuff and think what is the point showing it if your going to hide all the data... Anyway, can I ask if you have it set on 12hr trading as in takes one trade every 12hrs and if so what time does this generally occur on your platform? I have bought this too and just downloaded the upgrade to 1.1 version but since using this it has crashed my meta trader a couple of times last week on demo account and I think this is happening when it has opened 2 trades same pair and is trying to close them both when its acheived its target profit target as a sum of both the trades, have you had any on these problems? Can I ask if you have also adjusted the profit target to take account of using £ instead of $ I know its not in the manual but read about it on thier website?
You also mention that you have adjusted the DD to 25%, for black swan events, I think its normally set at 30% how did you change this setting?
My leverage is 1:500 do you think it will make any difference?
Sorry about all the questions but I will be going live next week too and will put mine on here too as I am impressed so far with the demo.
Thanks for the post. These are my current settings:
Initial Balance: 1,000 (this NOT adjusted for £) Order Stop: 60 Target Profit: 2.53 (this is adjusted for £) Frequency: 4 (every 12 hours which is 11am/pm on Alpari UK at the moment due to BST) Manual Trend: False Trend Derecttion: 0 Lot Size: 0.01 Risk Percent: 1.0 Max Total DD: 25.0 (=25% of £1,000 (initial Balance)) Slippage: 5.0
I am currently running the original v1.0 of the software for 2 reasons. 1. The main issues that people seen to be ahving are on accounts that suffixes on the PAIR names. I am running the EA on the same Broker as Andrea and therefore do not anticipate any issues. 2. I have open trades that are currently in a loss and I do not want to close them and I d not want to risk upgrading with the trades open, just incase v1.1 does not pick up on the open trades and deal with them properly.
I will wait for the trades to close (hopefully in profit 😄) and upgrade to v1.2 once it has been tested. I like the idea of v1.2 using compounding 😄
I am not entirely sure why there are 4 trades on the £/JPY but having read the manual and Andrea's comments on the blog https://www.forexcrescendo.com/blog/ I am happy that it is working correctly. See page 5 of the user manual for an explanation of when trades are opened.
The thing I like is that it will close ALL of the orders on a particular pair, once it has reached the Target_Profit between ALL of the open trades. So the price on £/JPY does not have to rise as high as 132.577 in order to close the 4 trades. Between them they need to make a nett gain of £2.53 (plus spread, swap and slippage)
I am a great believer of 'if it aint broke, don't fix it' So I will not be messing with my setings. I am happy to let let it run for a few weeks to see waht it can do 😄
I look forward to seeing your live account when you decide to take the plunge. Please send me a link and details of your settings?
Happy Trading 😄
(where abouts in the UK are you? I a live just south of Bristol)
Initial Balance: 1,000 (this NOT adjusted for £) Apparently this should be adjusted too according to the website
Order Stop: 60 - found out this is the reason for there being 4 trades so there must be at least 60 pips between the £/Y trades as when it calculates again if its greater than 60 will add another in the same direction.
Lot Size: 0.01 Risk Percent: 1.0 - I see you using the MM setting so is it not trading 0.1 lot I will have to check back when finished sending thsi response.
Max Total DD: 25.0 (=25% of £1,000 (initial Balance)) I see you have reduced it? if it hits 27% and not 30% you will ask yourself why you changed it to 25% hehe..
(where abouts in the UK are you? I a live just south of Bristol) - I am from Manchester work all over the country hence have to use a VPS and waiting until MT5 is out so I can use it on my Iphone!! Do you use a VPS?
One other thing, I was thinking of starting it running trading in the long direction so that the first trades on £/Y will be long, reason being I do see the JPY being corrected soon (could that be our black swan event)? so if its trading in the right direction then great!
Will try have it live before the end of the week, good luck with the 4 trades open hope it turns out ok.
Update: I have temporarily stopped the trading on the GBPUSD waiting for the GBPJPY to come back into profit (fingers crossed 😄)
Once all open trades are closed I will update to v1.2 and re-start my trading with the recommended settings. I have read on the Crescendo blog that some people have experienced their open trades being closed when updating. I don't want to take the chance with my 5 open trades.
I havent gone live yet I am wondering what happens when my demo keeps buying and it keeps going in the opposite direction will it ALWAYS buy or at some point in time will it sell too?
Funny thing happend on my VPS too I opened it and found MT was minimised and would not open to full screen so I closed it then re-opened it and found 2 trades on G/U had closed both for a loss any ideas?
I'm not sure what happened to your MT4 and your 2 trades?? Which version of crescendo are you running?
As for the direction of the trades. Crescendo will keep opening trades in the same direction until the collective value of all the open trades = [profit target]. Once the [profit target] is reached then crescendo will wait until the next [market watch] time at which point it will then decide which way it trade (i am not sure of the parameters that determine this but it is related to a longer time frame, to try to determine the trend). Once it opens a new trade ALL new trades will be in the same direction again until [profit target] is reached by the collective profit of those open trades (it means some will close in profit and some may close at a loss, but the total nett profit of those trades will be [profit target] then ALL trades will be closed.
I am still waiting patiently for the GBPJPY pair to recover from a massive down trend, The pair has almost reached an all time low, so fingers crossed it should recover soon. When the trades close I will upgrade to the latest version and then restart the trial.
Part of me really wants to believe in this EA and the other part is saking 'Why on eatrh would you use a system that allows your account to risk £300 to make £2.80 ????????'
The more i think about it the more crazy it seems.
I am determined to wait until the GBPJPY pair recovers but it look slike it may be some time. Once it does I think I am going to have to seriously consider if I will continue with Crescendo.
I am currently testing a great manaul trading system that gives me good entry points that I manage with a special EA that automatically allows me to place a pending order with 2 profit targets. The EA moves my stop to break even at TP1 and close half of the trade. the rest of the trade continues to TP2 or close at the break even position.
This is proving very easy to manage by checking in on account just once or twice per day ie 6am and 8pm. I am only demo trading at the moment because my live money is tied up waiting for Crescendo to recover. I'll let you know how it goes.
I hope you have better luck with Crescendo that I am at the moment :)
I was wondering if anybody has ever had their VPS lock up and therefore cause all the platforms to reload using AutoBoot and if this would cause any challenges for an EA like Crescendo that uses a basket closing feature?
In other words, I wonder if the platform closing and reloading if that would interfere with the ability of the EA to do it's job or cause the EA to lose any data as far remembering what the basket total was last etc. etc.?
Thanks for any help you may offer on these type of scenarios?
I have a VPS running 24/7 and have set up AutoBoot to restart Metatrader automatically. As far as I am aware Crescendo will pick up the basket of trades when the EA reboots and carry's on moitoring the success of all of the trades that are in place (although this has not, touch wood, happened to me yet)
My VPS seems very relaible. I am with Commercail Network Services if that is any help.
I think something may have happened with the basket monitoring some how because I have older orphan trades that are still open and newer trades that have closed already.
And to make things more mysterious, I looked in the log and noticed that a transaction tried to close even though the basket was still with around -$400 DD for each pair.
Here are the entries from the log: 14:10:08 HullMA GBPUSD,H1: loaded successfully 14:10:08 HullMA GBPUSD,H1: initialized 14:10:08 HullMA GBPJPY,H1: loaded successfully 14:10:08 HullMA GBPJPY,H1: initialized 14:11:01 Crescendo_v1 GBPUSD,H1: initialized 14:11:01 Crescendo_v1 GBPJPY,H1: initialized 14:11:01 Crescendo_v1 GBPUSD,H1: close #35873666 sell 0.10 GBPUSD at 1.59448 at price 1.62568 <-------------- 14:11:09 Crescendo_v1 GBPUSD,H1: invalid price 1.62568000 for OrderClose function <---------------------- 14:11:09 Crescendo_v1 GBPUSD,H1: invalid price 1.62568000 for OrderClose function 14:40:41 Crescendo_v1 GBPJPY,H1: loaded successfully 14:40:41 Crescendo_v1 GBPJPY,H1 inputs: note0='AUTHENTICATION OPTIONS'; username='xxxxx'; password='xxxxx'; note1='STRATEGY SETTINGS'; initial_balance=3000; order_step=60; target_profit=4; frequency_note='0 - always; 1 - every hour; 2 - every 3 hours'; frequency_noteb='3 - every 6 hours; 4 - every 12 hours; 5 - every 24 hours'; frequency=4; manual_trend=false; trendnote='1 - long; -1 short'; trend_directi0; note2='MONEY MANAGEMENT'; lot_size=0.01; risk_percent=0; max_total_DD=30; slippage=5; note3='EA SETTINGS'; GBPUSD_Magic_Number=130907; GBPJPY_Magic_Number=300610; suffix=''; 14:40:41 Crescendo_v1 GBPUSD,H1: loaded successfully
Notice how it tried closing transaction #35873666 twice or at least there are two entries with the same time from above:
14:11:01 Crescendo_v1 GBPUSD,H1: close #35873666 sell 0.10 GBPUSD at 1.59448 at price 1.62568 14:11:09 Crescendo_v1 GBPUSD,H1: invalid price 1.62568000 for OrderClose function 14:11:09 Crescendo_v1 GBPUSD,H1: invalid price 1.62568000 for OrderClose function
Here are my stat pages for this account: (They are both the same account but with different stat companies in case you prefer or are used to seeing one versus the other.)