Grid trader 10.1 - adding RSI range restrictions

Following the last 2 videos which used manually set price ranges and trend indicator values to limit trades this video shows the code to use limits based on oscillator type indicators. The indicator used here is RSI but it is easy to adapt.
This video starts with the code from part 10.
If you have come into this video without the earlier code you don't need to see every video in the series to get to the starting point. Some go off into branches, Here is a list to follow to get to the starting code used in this video.
Part 1 - Basic grid code: • Community input grid t...
Part 2 - Add compatibility for MT4: • Community Grid Trader ...
Part 4 - Improve code to remove conditional blocks on buy/sell: • Grid Trading 4: Code i...
Part 9 - Limit trades based on a price range: • Grid trading part 9 - ...
Part 10 - Limit trades based on trend indicator values: • Grid trading part 10 -...
Links:
Playlist for the series: studio.ua-cam.com/users/playlistP...
Join the discord group
orchardforex.com/discord
Looking for a broker? Support the channel by using this link. We receive a commission on your trades from the broker at no cost to you:
orchardforex.com/live-account
If you would like more information on the prop account I referenced (I do get an affiliate fee for any new subscriptions)
xrading incubator accounts: xrading.com/orchard-forex/
and the code is here
github: github.com/OrchardForexTutori...
00:00 - Introduction
01:46 - Creating a new version
02:21 - Input statements
03:48 - Configuration includes
04:01 - Add RSI indicator to main
05:47 - Range check
07:45 - Testing
10:08 - Conclusion

[@a.porteghali7402]

Im still struggling with Risk Management, to find an optimal approach to avoid a critical draw-down. In some scenarios, in the strategy tester, I have been stopped out, while everything seemed to be on right track.
The style of your programming is great and informative. It also helped me to improve some of my C++ coding skills. Thanks a lot.

[@michasz4861]

Thank you so much for your work, it's great to see the process of creating EA. Inspiring.

[@claudiolunardelli1589]

One very interesting thing that I was able to try by modifying the code in a crude way, is to use a CCI to remove the low and high peaks of the prices.
Using it, if it exceeds either 100 or -100, no operations must be entered, but only the target operations must be closed.
One thing I want to try if it goes above -300 or 300 on a 1 hour timeframe is to get inverse to the price.

[@crownpaint5990]

Thanks for ur great work. I think adding trailing TP and SL, two sects of indicators for entry signal and trend filter will make it great

[@billr4267]

I hope our fearless leader and supreme coder/teacher is ok, it’s been a longer than usual time since he’s posted any new Grid insights. Hopefully he’s just on holiday (although I think where he is it’s wintertime?)

[@TheWhippinpost]

How about setting the grid buy or sell distance to trigger at a percentage of ADR (or ATR, whichever)? That way trades can be spaced more dynamically according to an average day's volatility.
So, for instance, one could set a grid distance at 10% of ADR (10-trades).
And then, perhaps, calculate lot-size based on risk, spread over the ADR. So, if a user chose to risk 1% across the ADR, the EA could enter 10 trades with a lot-size 1/10th of the total risk per trade.
Hope that makes sense.

[@DestoTrading]

Suggestion: try reversing the RSI signal, meaning that a Buy signal would be price > RSI level (60 for example).

[@deddyhermanus6980]

I am liking this kind of content very much. Its more easier to digest. :)

[@rabnesbit8287]

Hello. Thanks for these videos, much appreciated. In case you are interested in something new to code, was wondering if you could code the following EA please:
(1) Determine the high and low of the Asian session (user to define start and end time of the session)
(2) At London open, place a pending buy order (price is the Asian session high)and pending sell order (price is the Asian session low).
(3) If the pending buy order is triggered, cancel the pending sell order immediately, and vice versa (i.e one cancel the other - OCO)
(4) Cancel both pending orders if not triggered after a certain period (user defined).
Thank you.

[@grrrrrr1288]

Guess that’s all she wrote folks

[@sophonkururat4636]

for version of MT4 can' work how to do for this? After compiler program MT4 have error of " 'GetData' - function must have a body "

[@hanygad9866]

Hello, can u please make a Video for " Hull Moving Average" for MQL5? Thanks in Advance

[@s36ast1an]

Maybe you would like to check the possibilities of self-adaptive EAs. It's a simple matter. I can share with you code. For example, the signal after the intersection of two MAs, but the parameters of these two MAs are automatically calculated in the Walk-Forward cycle, but inside the EA. Everything is contained in a few lines of code, and the two main functions are virtual trading and optimization (it can be also be brutte force) interesting results :D

[@michasz4861]

Very interesting approach but are the results satisfactory ? Share the EA code for testing if it's not a problem.