Posts made by trader.philipps

@paragorundu yepp, just a pity that it's limited to 3 buffers.

@paragorundu I don't think that that might help as it only places stop orders, which doesn't cause an order that has to be filled. I'd say it's absolutely a broker issue.

@ahaziz1958 In addition to @paragorundu approach you can right-klick on the order list and mark comments as selected. Hence another column will be shown displaying your comments.

@monocska3310 If the reasin is as @roar said that the stops are too tight to the market price (you can check stop level in symbol specifications), you might check that value before setting the SL / TP.

You can create a new double variable and on the onInit tab you can calculate it by using a Custom MQL code block.

That might look like this:

And here the code where vd_min_dtoplevel is the variable I specifed before in fxdreema:

//
vd_min_stoplevel = MarketInfo(Symbol(),MODE_STOPLEVEL);

// Print the Minimal Stop level on init of the EA
string msl = "MinStopLevel = "+DoubleToString(vd_min_stoplevel,8);
Print(msl);
//

I found the solution. I do the following in the on Init tab:

The in variables vi_current_timeframe and vi_next_timeframe I defined in variables as integer.

Here the code if someone wants to do the same:

//
int TimeFrames_cust[9] = { 1,5,15,30,60,240,1440,10080,43200 };
int CurrentTimeIndex = ArrayBsearch(TimeFrames_cust,_Period,8,0,MODE_ASCEND);

vi_current_timeframe= (ENUM_TIMEFRAMES) TimeFrames_cust[CurrentTimeIndex];
vi_next_timeframe= (ENUM_TIMEFRAMES) TimeFrames_cust[CurrentTimeIndex+1];
//

@specialfx Okay, I'm not so deep in fractals. However, may I ask you to share that indicator? I like 123 entries yor approach seems to go in that direction.

@specialfx I like the fractals idea. However, fractals as far as I know based on zigzag indicator. That means, a new lower fractal can only be confirmed, if a new high fractal occurs. How does your indicator deal with that? Would it reprint the last fractal until the opposite fractal is available?

Have a look at my indicator. There will be a baseline signal soon, but it doesn't print the last down fractal as it is not confirmed, yet.

@l-andorrà said in successfully created my first ea...based on buy and sell:

That means your indicator is one of those repainting. Are you basing your strategy on a repainting indicator? Did you evaluate the consecuences on backtesting it? Results will not be reliable, I'm afraid.

@l-andorrà I think most indicators repaint on current bar unless they take open price of candle for calculations.

May it be that shift is a variable name that fxdreema internally uses? I was facing the same issue with a custom indicator last night. I changed the variable name in the indicator and all was fine.

@paragorundu said in How to cancel order if it takes too long to open:

Did you check your LAN/WAN connection? You may have connection issues. For example, I had similar issues with WLAN

@rafaelgrecco Good Point. I'm always using VPS with good connection to the broker. Didn't think about someone could run EAs from home :))

Hi folks.

I have an understanding issue. If I want to modify variables in an "for each trade block" it would be sufficient in my case to do the modification once each bar and not each tick when conditions are to be checked. So, if I specifiy after an "for each trade" block a "modify variables" block that is due to run once per bar, will fxdreema create an array for each trade with the specified value or will it store just the variable value that occured on the first trade? The variables I use are related to each trade, but I figured out that modification calling an external indicator slows down backtesting a lot and in that case is not necessary.

It would look like that.

@rafaelgrecco the ordersend function has a time parameter, but I think that is only valid for pending orders and determining the point in time the pending order expires.

int OrderSend(
string symbol, // symbol
int cmd, // operation
double volume, // volume
double price, // price
int slippage, // slippage
double stoploss, // stop loss
double takeprofit, // take profit
string comment=NULL, // comment
int magic=0, // magic number
datetime expiration=0, // pending order expiration
color arrow_color=clrNONE // color
);

Same say the order blocks buy and sell.

Are you trading low liquid assets? Otherwise I'd take the order times and get in contact with broker's support and let them explain you the reason. On order open that may not be an issue if you get the price you want (or could use limit order), but for closing the order that can cost you a lot of money!

@rafaelgrecco I'm not aware of any max ordersend time value. However, you may control the price difference with the slipage settings instead. Or does it matter if you get the same price 10 seconds later?
By the way, which broker are you using? Times appear very long to me.

Hi @money123456 , see the NNFX template thread for the JMA with ATR indicator. However, I'm also thinking about the right way to use fxdreema blocks for the condition.

Usually I'd expected to check closed price of candle ID1 if it is X> JMA value (for long trade). However, I think fxdreema works here a bit different with that condition.

I found this example on EURAUD daily chart.

Candle (1) candle closed under JMA line .. that's okay. Candle (2) opened with a gap and hence fxdreema wouldn't find a valid condition. And finally for fxdreema logic candle (3) would give a valid long signal (ignore ATR linits here).
The candle (3) opened above JMA line and closed above. But the low was below indicator line. I observed that fxdreema would if checked for condition closed price x> JMA value give a valid long signal.

Hence I think that for checking the condition "closed above" intends that the open was below the indicator! Do you agree?
Finally I have no clue yet, how to deal with the gap between candle 1 close and candle 2 open. Uusally I'd expect it to be a valid "closed above" by NNFX meanings. What do you think?

@money123456 I'm not a real MQL4 coder, but I took the challenge to add ATR bands to JMA indicator (token from McGinley). Hence, the work and rights an whatever belong to the people that invented those indicators.
I tested it and looked good. You may easily just check against the Buffers named "Upper ATR Band" or "Lower ATR Band" in a condition block.
0_1567530329424_jma_sl_atr_bands.mq4

Hope that helps you a bit.

@money123456 I have no ready algo, yet. I started fxdreema 1-2 weeks ago so I'm not the experienced one around here.
Here you can see some of my "trials" to give you an idea no1. My project still has a flaw somewhere. Probably I used the flags too heavily :))
But maybe some ideas we can share.

Hi folks, looks like today I'm a little stupid. One of my indicators requires the input of a timeframe. In order to make it flexible, I'd like to calculate the next higher timerframe. For instance if chart timeframe is H1 it should return H4, . for M15 -> M30 and so on.
I create that project Next Timeframe Project and hope that someone can help me.

In details:
I copied a sample code from mql5.com:

//+---------------------------------------------------------------------+
//| subGetNextTimeFrame function - returns the next timeframe |
//+---------------------------------------------------------------------+
int subGetNextTimeFrame()
{
int TimeFrames[9] = { 1,5,15,30,60,240,1440,10080,43200 };
int CurrentTimeIndex = ArrayBsearch(TimeFrames,_Period,8,0,MODE_ASCEND);
return((ENUM_TIMEFRAMES) TimeFrames[CurrentTimeIndex+1]);
}

and put it on "on Init" tab in a custom code block. However, I fail to call that function somehow and receive the error "'subGetNextTimeFrame' - function can be declared only in the global scope".

What am I doing wrong?

OCO order means "One cancels the other" .. You place 2 orders and if 1 of them gets executed the other one gets deleted. Some stock brokers offer that order type. For forex brokers I haven't seen it, yet.

@ambrogio said in TURN Off MT4 Autotrading:

@trader-philipps Perhaps this is simpler: close all the trades of another expert on another chart and prevent it from opening new orders (end the other expert)
@miro1360 some advice?

You may close other expert's orders, but I have no clue how to avoid them to open new ones.

@zackry Thanks! I'm learning so much from those examples!