OneFX Aggressive 20% margin (By rkinman)

The user has made his strategy private.

OneFX Aggressive 20% margin Discussion

Jun 10, 2010 at 02:34
1,441 Views
2 Replies
Member Since Nov 17, 2009   31 posts
Jun 10, 2010 at 02:39
Quality was a little low for my liking on this test. I am doing what I can to download a 99% model quality history file. This thing is huge and will take time to get. When I get even better results, I will post them. Same Strategy is used on my live account. So you really can see a difference.
Member Since Jan 12, 2010   3 posts
Jun 13, 2010 at 12:52
hi,
i like tghe SL and TP here, can you share more details about this one or is this perhaps a free ea, would be great to test also. thanks
Member Since Nov 17, 2009   31 posts
Jun 13, 2010 at 17:02
Were using the high and the lows from the daily time frame. Always using points 3 candles back. If a more recent candle creates a higher high or lower low, there is no pending order placed. Orders are set a pip below high/low. When order triggers and price moves a very tight trailing stop triggers when price is X amount of pips in profit. Were looking for very fast breakouts or steady move.

It does get a little more tricky than that. But that is really the basic concept. The original strategy was based on 100sl and 200pip TP. I just decided to scale it down. Im a 8 hour day worker and anything below a Daily TF is out of my realm. I was tired of logging into my VPS from my IPhone every 10mins to see how these trades were doing. Sometimes days! This strategy with the small SL and decent TP really took that burden from me. Trades are from mins, to hours. With trades only triggering every couple of days or so. I don't have to sweat a 7 pip SL 😉
Sign In / Sign Up to comment
You must be connected to Myfxbook in order to leave a comment
*Commercial use and spam will not be tolerated, and may result in account termination.
Tip: Posting an image/youtube url will automatically embed it in your post!
Tip: Type the @ sign to auto complete a username participating in this discussion.