Custom Indicators/Working with Buffers
-
Well because that's their proprietary information.
You definitely can make EAs with EX4s. You just don't get to see what's behind the curtain so to speak.Ex4's do give you buffer data. What you have to do is put Lopez on a chart in MT4 and open the "DATA WINDOW"(View--data window. Or ctrl-d). That will show you the buffers to use in FxDreema. The buffers in the data window are what you're supposed to enter into dreema in the outputs for a custom indicator. There's 7 of them in Pz Lopez Trend. Buffer 5 is related to opens and buffer 6 is related to closes. Buffer 7 seems to happen when any change occurs at all. 3 and 4 seem to be related to overbought and oversold but we haven't even gotten that far yet. There's no documentation for this, and when we reached out to Lopez himself he just copy and pasted the iCustom function from their website and said to use that
. However, open the data window with the indicator on, move your mouse around the chart and you will see how the numbers change in the buffers.Right now we've automated trades based off Lopez. We just receive errors at different times. Seems like there is very little documentation on these errors outside of a sentence or two.
Don't really know why. Between three different forums no one seems to have a conclusive answer.
But through sheer will we've gotten it to work, to a point.
For example, I just ran a live test and got it to successfully trade and close based on the colors changing in Lopez 6 times in a row before the invalid EX4 error appeared.
Now if an error saying "the ex4 is invalid" appears, wouldn't that mean it shouldn't work or open at all in the first place?
That's where our confusion is right now.As for our previous problem about too many requests, we seem to have found if you use a Tick Time Filter (green node), and limit it to only execute every few ticks, it will trade a bit longer before crashing out with errors. So there seems to be a solution there. I don't understand why a per bar filter wouldn't achieve the same thing (which it doesn't) but the tick node works for now.
So it seems the problem is not getting FxDreema to recognize Lopez, its getting dreema to slow way down and not go nuts executing requests every tick.
-
I don't even know what EX4s and Lopez are

-
I'm trying to post our ea attempt but it's saying
"Sorry, the board attachment quota has been reached."
So here's our file so far on another host:
-
I can see in the code that the indicator is called using only one integer parameter, which is 1 everywhere. There is very little chance for something to go wrong with indicator with only one parameter
Maybe the error comes from the indicator?