Rhino Ilan - Scalper (stopped) (By forex_trader_165856)
The user has deleted this system.
Rhino Ilan - Scalper (stopped) Discussion
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 10, 2015 at 16:30
103.00 (+82.7) pips today across many pairs
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 12, 2015 at 11:21
Only for purchase outright and you can invest with your own trading account. There is no need for PAMM with my products. https://redrhinofx.com/vortex-scalper-pro/
5 Signals today and 2 reached full takeprofit of 20 pips.
5 Signals today and 2 reached full takeprofit of 20 pips.
Member Since Nov 06, 2014
114 posts
Feb 12, 2015 at 11:32
Does the EA enter trades with an ideal spread? Spreads can change rapidly on some currency pairs and how does this EA handle this?
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 12, 2015 at 11:45
An ideal spread. Interesting. I can collect the spread data for an average and only have it enter when the spread is equal or below the average. I have also coded the use of 1 Real and 1 Demo account with the 1 account license and I'll consider adding the monthly subscription option over the weekend. Thanks for the suggestions.
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 13, 2015 at 06:41
1 Loss today, and a lot of wins. The AUDUSD Sell could have been profitable if using a conservative setting with the MoveToBreakeven setting = True. Live and learn
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 13, 2015 at 06:50
https://www.mql5.com/en/charts/3021051/audusd-m15-fxopen-investments-inc
Move to Breakeven after 30 mins would have been sufficient and up to 4 hours.
https://www.mql5.com/en/charts/3021063/gbpusd-m15-fxopen-investments-inc
Here is an example of how the Move To Breakeven works successfully on the GBPUSD Short.
I also got the LONG GBPUSD that VTP EA fired off today 😎
Move to Breakeven after 30 mins would have been sufficient and up to 4 hours.
https://www.mql5.com/en/charts/3021063/gbpusd-m15-fxopen-investments-inc
Here is an example of how the Move To Breakeven works successfully on the GBPUSD Short.
I also got the LONG GBPUSD that VTP EA fired off today 😎
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 14, 2015 at 17:22
Make no doubt I do get the same trades as Vortex trader Pro ., Here are the GBPUSD trades .
You can get the same results as VTP by disabling the BreakEvenAt = False;
You can get the same results as VTP by disabling the BreakEvenAt = False;
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 14, 2015 at 17:26
(edited Feb 14, 2015 at 17:28)
The reason for some trades close out at 1 pip is because the Trade Duration has gone beyond the expected range and will try to cut a bad trade instead of hanging on for an average of 10 hours as does VTP. VTP GBPUSD trade had a duration of 8h 15m for 2 pips, while VSP made 1.1 pips within 36minutes.
Also I don't Average/Grid with another trade. VSP has the option within the parameters however I am using only 1 trade per signal
Also I don't Average/Grid with another trade. VSP has the option within the parameters however I am using only 1 trade per signal
forex_trader_165856
Member Since Dec 03, 2013
631 posts
Feb 14, 2015 at 19:30
42 trades in 1 week with 324.7 pips. Pip Expectancy is 7.7 pips. Only 1 losing trade out of 42 and it would take on average 14 trades to recover the loss from 1 trade.
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 16, 2015 at 14:07
79.50 Pips on a Monday with Vortex Scalper Pro. Off to an excellent start.
Wouldn't be wise to have a recovery module built-in?
It already does, Allow a 2nd order and enable BreakevenBasket == true .
Wouldn't be wise to have a recovery module built-in?
It already does, Allow a 2nd order and enable BreakevenBasket == true .
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 17, 2015 at 17:31
47 pips overall despite a -110 on EURJPY. I am already thinking about some new features. Maybe you are seeing what I am seeing.
Feb 17, 2015 at 17:50
(edited Feb 17, 2015 at 18:00)
Frank Wright (RedRhino),
I think you're integrating RevEnginePro indicator in Vortex Scalper EA to improve entry accuracy at 15M timeframe to filter out bad entries and improve better timing for entries.
I'm looking forward to seeing the improved results with this update.
I think you're integrating RevEnginePro indicator in Vortex Scalper EA to improve entry accuracy at 15M timeframe to filter out bad entries and improve better timing for entries.
I'm looking forward to seeing the improved results with this update.
Member Since Nov 06, 2014
114 posts
Feb 17, 2015 at 21:24
When will these new features be implemented?
RedRhino posted:
47 pips overall despite a -110 on EURJPY. I am already thinking about some new features. Maybe you are seeing what I am seeing.
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 18, 2015 at 13:49
Ive already include the RevEnginePro indicator within the closing logic of Version 1.0 of Vortex Scalper Pro to close a bad trade before reaching the stoploss. This setting wasn't on. My new idea is to use a combination of if,then conditions to activate a new feature that I'll add within a week to version 1.1.
The new feature will not be to filter the entry logic condition but to manage a losing trade better aka reduce stoploss values to boost RR ratio. I did a visual backtest with the new feature ( already coded the feature) yesterday to clarify the idea and it did improve the backtest on EURJPY but I'll need some time to refine it.
The new feature will not be to filter the entry logic condition but to manage a losing trade better aka reduce stoploss values to boost RR ratio. I did a visual backtest with the new feature ( already coded the feature) yesterday to clarify the idea and it did improve the backtest on EURJPY but I'll need some time to refine it.
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 18, 2015 at 15:27
48 pips so far this day. AUDNZD holds a long while two Shorts entered and exited at profit. Trading 20 pairs creates a lot of action and a nice diversified portfolio. Also the logic and settings are the same for all pairs, I can't wait to get all 20 pairs optimized to their own specific behavior.
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 20, 2015 at 13:19
Turn NoOptimizing24H to false, turn FindFinding to True, and Optimize StartTime with min 0, step 1, max 23
You will find the best trading time for that currency pair. Since FX is a 24 market and each Currency/Central Banks come online from their own timezone it would be sufficient to start there.
Then optimize the ATR setting since every currency pair has their own daily range.
Next you can start fine tuning MaxProfit MaxStoploss to find a suitable RR ratio. That will get you in the profit zone! Thanks for your question.
You will find the best trading time for that currency pair. Since FX is a 24 market and each Currency/Central Banks come online from their own timezone it would be sufficient to start there.
Then optimize the ATR setting since every currency pair has their own daily range.
Next you can start fine tuning MaxProfit MaxStoploss to find a suitable RR ratio. That will get you in the profit zone! Thanks for your question.
forex_trader_149646
Member Since Sep 09, 2013
471 posts
Feb 20, 2015 at 13:20
More fine tuning can be completed with the MAFast parameter , WPR, CCI parameter. These settings are the indicators that fire the Entry and Exit logic. When optimizing these setting, I would pick 6 months - 12 months of data to find a good setting, then backtest using the same setting on data that you didn't optimize on. This is called Walk Forward Test and allows optimizing for a specific market condition and then you get to see how it can do on data that you didn't optimize the parameters on. You would get the best feel for how your setting will perform tomorrow trading live.
forex_trader_165856
Member Since Dec 03, 2013
631 posts
Feb 22, 2015 at 15:39
EuroGroup Meeting volatility took Vortex Scalper Pro for a ride to losses, but that was expected. There are some news releases that can't be programmed into the code where the user needs to turn off the system manually.
