scalp helper tool
1 2 3 ...

thread: scalp helper tool

  1. #1

    scalp helper tool

    This thread is about little mql
    tool that assist using methodology and trade levels described here:


    https://www.cliqforex.com/trading-sy...r-ea-free.html



    while being AFK.


    I don't want clutter over thread with error reports and queries associated with this tool - that is the reason why new one was launched.


    Main features of the tool include:
    - handling 4 price levels with prescribed TP,SL and risk expressed into account percentage or cash
    - discretionary break even and trailing stops
    - overlooked amount detection - check declared thread for information
    - trading hours - by means of hours and weekdays



    Please keep that in mind this isn't finally tested variant.
    Code is tackling your order so your cash and it has to be analyzed and trusted prior use.
    Thus use at particular risk.


    I invite you to check it on demonstration and report spotted errors using
    toned meaningful posts.


    Whole code will be keept free,possibly updated,
    maybe with source code - it's object oriented code - therefore it requires some time to deal with all include tree to catch.



    Check last posts to download newest version.

  2. #2
    quote Why would a order send be ineffective? (Forgive the lack of information on coding) I would suggest: Rather than market entrance, when price comes inside five pips (user defined) of the degree, the EA puts a limit order. When there is a limit order there, then do nothing. This avoids issues using market orders... order send mistake or possibly multiple transactions in the exact same time - and even avoid things like slippage etc.. . Thank you.
    New parameter Limit orders would call for new implementation of several functions - testing could be neccessary and it takes time.
    Someday . .

  3. #3
    I have a couple questions if you'd be kind enough to answer please: 1 - openLevelNearDistancePips Does this imply in default 1.5, it will take the trade 1.5 pips first, and at 0 it will trade just at the degree? If yes is TP calculated from entrance or the out of the degree? 2 - missedLevelNearDistancePips and missedLevelRetrace Does this mean if market comes in 3 pips and transfers off 10 pips, the trade will be canceled by it? If yes, the 10 pips is calculated from the level or from where price turned off? 3 - How do beTpConstInPips (default -2)...
    1 - openLevelNearDistancePips Does this imply in default 1.5, it will take the transaction 1.5 pips first, and at 0 it will trade just at the degree? If yes is TP calculated from entrance or the out of the degree?
    Yes 0 trade just at the degree.
    Trade TP is figured on current market open price [current bid/ask when we sell/buy] -/ number of pips specified by tp - SL also.


    2 - missedLevelNearDistancePips and missedLevelRetrace Does this mean if market comes in 3 pips and transfers off 10 pips, it will cancel the trade? If yes, the 10 pips is calculated from the level or from where price turned off?
    ==
    10 pips is calculated out of where price turned off -- nearest distance in 3 pips to par price.

    Allow me to describe Buy order check:

    - buy cheapest recent price [this should be altered cheapest recent price is: cheapest price hunted within last 30 bars - this should be changed to n bars from EA beginning or something configurable - when one uses 1H tf or it might produce spurious results]

    - calc missed level price = target price _missedLevelNearDistancePips
    - calc retrace price = cheapest recent price _missedLevelRetraceDistanceFromNearPips
    - buy ask price
    - if cheapest recent price is over target price and below missed level price
    and also current ask price is over retrace price
    level is considered missed



    3 - How do beTpConstInPips (default -2) and beConstInPips (def 8) and tsConstInPips (def 0) work?

    A.
    beConstInPips,beTpConstInPips:
    After order is started price needs to travel beConstInPips pips in favor [go up when u buy] to place SL to beTpConstInPips.
    When beTpConstInPips =-2 that your SL is set to two pips reduction.
    When beTpConstInPips = 0.5 that your SL is set to 0.5 pips
    When beTpConstInPips = 0that is basically split even

    When beConstInPips is set to 0 - no SL manipulation is done.

    B.
    tsConstInPips - this can be trailing stop,
    fires after split even is set,
    and price advances greater than tsConstInPips pips in favor (above open price when buy)
    if 0 - does nothing
    if beConstInPips does nothing



    4 - How does maxSpreadInPips (default 3) work?
    Market Order wont open unless bid ask diference is 3 pips or not.




    5 - What does skippedTicksPriceMoveInPips (def 1.0) mean and how does it function?

    EA is trying to process every tick and employ logic explained in above points.
    _skippedTicksPriceMoveInPips causes above logic to fire only when current bid price mover greater than 1 pip from past processing bid price.
    Missed ticks parameter allow to utilize greater EA cases on given VPS.
    When 0 - it tries to process every tick - and - still misses some of these thanks mt4 ea thread slowness.

  4. #4
    Thanks for the tool. I took a few minutes to think I would have wanted things... and I have a couple ideas. My suggestions to improve your EA: 1 - Choice for EA to draw a line on the chart at the levels (with selection of colors for longs and shorts) two - Choice to add fixed ECN commission fees into the risk (I wish to risk 1 percent total including fees) - (would also need to define how much $ the commission is per lot) 3 - Idea: instead of specifying Long/short for every level, EA automatically checks: if the level is below market - its payable. .
    1,2,3 - todo
    4 - someday todo, market orders have sometimes better price.
    5 - concealed SL? why? 1 big visible initial 100 pip SL and yet another small 10pip concealed SL. I don't have any exp. With hidden SLs.
    6 - code includes many small files, therefore I need to extract subset of my code tree into separate repository such as tfs or bitbucket.
    Subj. To consider.

  5. #5
    Junior Member jj1976's Avatar
    3
    Bez SL a TP.

  6. #6
    Junior Member IsraMx's Avatar
    5
    Idea of hidden SL (or even lage SL which moves down to 12 when price becomes very close) would be to avoid potential stop hunting.

    Thank you for the explanations. Fantastic job.

  7. #7
    Thought of concealed SL (or lage SL which goes down to 12 when price becomes really close) would be to prevent potential stop searching. Thank you for your explanations. Fantastic job.
    Then we have small and large SLs where large one is put on trade.
    Whenever u obtained spike that is a SL hunt and it strikes small SL what to do? Wait until big SL is hit?

    And should price procedures short SL in serene manner - close trade, right?
    --
    What params would describe such process?

    0 big sl is set to _SLPips
    1. _SLHiddenPips - there goes small one, if zero then is ignored
    2. _nSecondsHiddenSLWindow

    if recently n seconds price strike concealed sl and did not return - then close trade.


    --
    or what is?
    Any thoughts?

  8. #8
    Junior Member pilibergado's Avatar
    13
    quote It open orders at selected levels. Set _tradeLevel1,2,3,4 or set to 0.0 if used _tradeLevel1Side to put order side _Risk - to put risk per transaction% _openLevelNearDistancePips put to 0 or 0.5-1.5 - order will be opened 0-1.5 pips ahead of amount _missedLevelNearDistancePips set to 0 or 0. .3 - when price miss amount by 3 pips - degree is invalidated _missedLevelRetraceDistanceFromNearPips - 8-. . .15 minimum retrace distance traveled by price after touching a level - to make order _beTpConstInPips - set 0. . 0.5 also less than zero...
    Thank you so much for your comprehensive reply! I am wanting to trade a London breakout system, therefore I think it will be helpful. Could I PM about it?

  9. #9
    Junior Member IsraMx's Avatar
    5
    quote Then we have little and big SLs where big one is set on commerce. Whenever u made and it strikes SL what to do? Wait until big SL is struck? And if price procedures SL in calm way - close commerce? -- process would be described by What params? 0 sl that is big is placed to _SLPips 1. _SLHiddenPips - there goes one that is little, if zero is ignored 2. _nSecondsHiddenSLWindow if in n seconds price strike sl and did not come back- close commerce. -- or what is? Any thoughts?
    Hmm...

    I think SL in 20, then if price goes -10 pips, move stop to 12.

    If price spikes past 12 - should close immediately... (these needs to be optional).

  10. #10
    Junior Member IsraMx's Avatar
    5
    I think I found another error (or it is the exact same one in another format)

    UsdJpy 116.49 on 9/1/17
    Trade started at 116.481 (0.9 pips better) - went to profit

    Subsequently price went down to the amount after about 10 mins - and also EA took yet another trade
    So basicallyit took the trade again when amount was re-visited after a couple of mins (see attached).

    I feel the EA checks if a degree has been invalidated (price came in 2 pips - went to goal ) - but does not check if amount was actually touched and then went to the goal.

    After price hits a degree and proceeds to profit, then re-visits the amount - if you turn on the EA at this time - it will take the trade.
    The EA should not be carrying this trade (no matter if it traded before) because the trade is over and so the amount is now invalid.

    To mend it: EA checks if price arrived within two pips OR touched the amount - and went to goal (or SL) - if yes then high level amount - no trade.

  •