Posts made by trader.philipps

@scottpapetti Can you post the full error message from the log and if useful some around? If you use a mac the filename may differ in regards of capital letters maybe .. just a rough guess.

@satoriforex2k18 From what you wrote I understood this:

But be careful with the spread.

That means:

Trailing start: Price has to travel 1000 pips in order to start the trailing
Trailing step: Price has to mover another 500 pips until next SL adjustment
Trailing stop: distance from current price, when adjustment takes place

I use Once per bar as a time filter as it is sufficient for my requirements. You may want to use a different time filter or don't use it.

@l-andorrà Yapp a bit too abstract question.

@Satoriforex2k18 Coming back to your initial question. The link you provided shows from my perspective a regular trailing based on pips. You just have to specify the right numbers to the start and step values.
Or do I misunderstand you?
In that case you can use a regular trailing stop block. Assuming that your TSL should stay 500 pips away from last high (when in profit) you'd specify trailing start 1000 and trailing step 500. Hence price always has room for retracing 500 pips from last high. Is that correct?

@satoriforex2k18 I'd place a "if trade" block before the for each block. Are you sure about 1100 pips? That would be 11000 points!!! It may take a while till that condition is met if ever.

@justintkt Well, the x> or x< means, that the crossover has to take place in the specified candle. If you combine the 2 condition (the cross-over event) it's relatively low from probability perspective. Maybe depends a litte on timeframe, but I think it will mostly the same.
There is a setting "width" that may be fine-tune this, but I never used it and from description you would look for the cross a few candles before rather than the last candle (if condition checks current candle).

I would wish that it means that if you specify a value such as 3 it would mean the cross have to occur with-in the candles n+1, n+2 or n+3! However from field description it probably means n+3 only. In that case you may loop for n+iterator. Maybe someone more experienced with fxdreema may clarify that and maybe give an example.

@justintkt I don't think that's the solution for your problem, but check block 4! It doesn't look right.

^How does your close trades section look like? Maybe you just copied it and don't specify the Filter by Type setting?
Furthermore I'd work woth a For each Trade block before the Close trade block.

Is the setup case given, when price crosses middle line of Bollinger bands and than goes back under (short trade) or vice versa (long trade)?
If not, try to formulate the usecase when the setup is given. The EA needs an algorythm to work with.

@specialfx That's usually the case if you do a division especially with variables and the divisor (is that called like this in English?) is zero. This is not defined in mathematics and hence an error.
example:

//
double dont_do_that = 0;
double result = 12345 / dont_do_that;
//

You can avoid it by testing if in this case "dont-do-that" variable is not zero.

For your EA that means, that it stops working from that point on after the error message.

@ambrogio Yeah, it's a pity that such a great software as fxdreema is laging a good documentation. Or at least I'm not aware where to find it.

@roar Thanks. That is a good start. Is there a way to get the order type as well? As it influence the condition to check.

@gunji80 The only way I know, but I relatively new to fxdreema is if you have a mq4 file available that covers all your old stuff. With this you can create a new project and import the mq4 file.

Try and error. I took a look how the indicator is embedded in fxdreema. Here is an example.

It seems like all you need to do is to use the indicator somewhere and than in the constants declaration you use the same syntax.

That's it!

Here I have something for the advanced folks.

Let's assume I have a moving average. If price is above the MA I assume the price is trending up. If it is below the MA, I assume the price trending down. So far so good.

I want to check the condition now, if since the last trade was closed (eg. long trade) the price ever was closing below my MA. Any idea?

Probably I need some looping and maybe custom code. But any help I appreciate.

@newbietrader Choose at "trail what?" Take-Profit!

Hi folks,

I use an indicator that uses enum as a data type for it's parameters-. As I have mql4 code, I can drag use the indicator in a block (custom indicators) and there I can select that the input is available for optimization. This causes in EA parameter list this output

As I am using constants for the parameters as I want to specifiy the logical order by myself as well as giving it a human friendly label.
I'm asking myself how I can specify a constant that does the same thing. I read a lot here in the forum, but the solutions seem to be quiet old. As an example modification of fxdreema's generated EA source code is not an option.

If enum as constant is possible, please give me an example (eg. screenshot) how to enter it?

The generated enum looks like that:

//
enum enTimeFrames
{
tf_cu = 0, // Current time frame
tf_m1 = PERIOD_M1, // 1 minute
tf_m5 = PERIOD_M5, // 5 minutes
tf_m15 = PERIOD_M15, // 15 minutes
tf_m30 = PERIOD_M30, // 30 minutes
tf_h1 = PERIOD_H1, // 1 hour
tf_h4 = PERIOD_H4, // 4 hours
tf_d1 = PERIOD_D1, // Daily
tf_w1 = PERIOD_W1, // Weekly
tf_mb1 = PERIOD_MN1 // Monthly
};
//

Or that

//enum enMaTypes
{
ma_sma, // Simple moving average - SMA
ma_ema, // Exponential moving average - EMA
ma_mcg, // McGinley Dynamic
ma_dsema, // double smoothed exponential moving average - DSEMA
ma_dema, // Double exponential moving average - DEMA
ma_tema, // Tripple exponential moving average - TEMA
ma_smma, // Smoothed moving average - SMMA
ma_lwma, // Linear weighted moving average - LWMA
ma_pwma, // Parabolic weighted moving average - PWMA
ma_alxma, // Alexander moving average - ALXMA
ma_vwma, // Volume weighted moving average - VWMA
ma_hull, // Hull moving average
ma_tma, // Triangular moving average (TMA)
ma_b2p, // Two pole Ehlers Butterworth
ma_b3p, // Three pole Ehlers Butterworth
ma_s2p, // Two pole Ehlers smoother
ma_s3p, // Three pole Ehlers smoother
ma_sine, // Sine weighted moving average
ma_linr, // Linear regression value
ma_ilinr, // Integral of linear regression slope
ma_ie2, // IE/2
ma_nlma, // Non lag moving average
ma_zlma, // Zero lag moving average
ma_lead, // Leader exponential moving average
ma_ssm, // Super smoother
ma_smoo // Smoother
};
//

@pontedruse I still think what you try to do is quiet complex. Even if you can handle all the money related stuff, you still need to care about persisting those values for the case you need to restart your terminal or just edit EA settings and the EA gets initialized once more.
In addition if you run more than one instance (aka chart) of the EA, there has to be a cross communication between the instances. May I ask you why you make it so complicated? Maybe if I understand the reason, I might think of other solutions.

@technobiz I never used trailing stop, but I think you need a pink block such as "For each Trade" block before it.

@cpxiom Yes, the intention of the indicator is to monitor 3 buffers from a named indicator and display their numeric values as a line in the indicator window!

However, there are indicators that have their buffers not named and you need to guess what each of them mean. Further some indicators have more than 3 buffers and you need to handle the monitoring several times.
Furthermore some buffers are only filled with a value, when a special condition is met. If it's not met, the value is empty.

So my comment just stated that it is a pity that you can only specify 3 buffers to display. I'd wish that the indicator would auto-discover the buffers and display them.