Menu
Sister Sites

Options

Bookmark Thread

First Page First Unread Last Page Last Post

Print Thread

Similar Threads

way to get multiple buffer values with single iCustom call? 23 replies

Wave Entry Alerts - How to get iCustom 18 replies

Need help, I can't get the value of the buffer using Icustom() 5 replies

How to read values of indicators in offline Renko chart 8 replies

iCustom(...) return values don't match contents of the Data window in MT4... 3 replies

Attachments: How to get iCustom values from indicators
Exit Attachments

How to get iCustom values from indicators

  • Post #1
  • Quote
  • First Post: Oct 3, 2012 10:53am Oct 3, 2012 10:53am
I see many people ask this question but how to use iCustom; but so far no clear answers from people about the parameters issue.

The MQL help files are less than useless on the subject.

HOW do we find out what the parameters are?

For example, I wish to code into EAs the attached TMA Slope Indicators the moment the current and previous bar/candle is either side of the zero point. So what I need iCustom to give me is the Slope Value at the close of each bar.

All I can work out is;

iCustom (NULL, 0, "10.2 TMA slope v.1.4B 4.30",6,0) and

iCustom (NULL, 0, "10.2 TMA slope v.1.4B 4.30",6,1).

But what about the parameters? And in particular, what about the parameter that has the Slope Value information I want? How do I list the parameters? They have names or just numbers? Where can I find out how many and what descriptions these parameters have?

Phil
Attached File(s)
File Type: mq4 10.2 TMA slope v.1.4B 4.30.mq4   10 KB | 1,041 downloads
File Type: mq4 10.2 TMA TRUE v2.1 5.2.mq4   8 KB | 989 downloads
The parameters to the indicator go after the 3rd parameter of iCustom. The last 2 parameters to iCustom always go at the end, after the indicator's parameters.
You are in a maze of twisty little passages, all alike.
The list of parameters that you use after indi name must match the number of external variables in the indi.

So 10.2 TmaSlope has 20 external vars which must all be included (if my understanding is correct) ... their values that is. ("Select..", 0,1,50, 12 etc etc)

You can see the list of these vars at the start of the indi code or in the popup when you apply the indi to the chart.

So ... iCustom(symbol, TF, name , the 20 vars values separated by commas, the buffer that you want value from, shift)

HTH

M.
If you think I'm mad, I must be mad
You will call the same parameters as in indicator.
e.g. Indicators parameters:
Inserted Code
extern int xi_Period = 20;
extern int xi_ATR.Period = 20;
extern double xd_ATR.Mult = 2.0;
In EA:
Inserted Code
[size=2]iCustom (NULL, 0, "10.2 TMA slope v.2.1 5.2",20,20,2.0,[/size][size=2]6,0)[/size]
or you can declare your variables at the start of code for easier change of settings:
Inserted Code
extern int xi_Period = 20;
extern int xi_ATR.Period = 20;
extern double xd_ATR.Mult = 2.0;
---------------------------------
[size=2]iCustom (NULL, 0, "10.2 TMA slope v.2.1 5.2",xi_Period,xi_ATR.Period,xd_ATR.Mult,[/size][size=2]6,0)[/size]
Quoting Gvc
You will call the same parameters as in indicator.
e.g. Indicators parameters:
Inserted Code
extern int xi_Period = 20;
extern int xi_ATR.Period = 20;
extern double xd_ATR.Mult = 2.0;
In EA:
Inserted Code
[size=2]iCustom (NULL, 0, "10.2 TMA slope v.2.1 5.2",20,20,2.0,[/size][size=2]6,0)[/size]
or you can declare your variables at the start of code for easier change of settings:
[code]extern int xi_Period = 20;
extern int xi_ATR.Period = 20;
extern double xd_ATR.Mult = 2.0;
---------------------------------
[size=2]iCustom (NULL, 0, "10.2 TMA slope...
Thank you for this; given it has only 3 variables it calls from the indicator I am testing this one first, and it all compiled fine. I'll have to wait and see if my trading logic is correctly coded etc.
Quoting futurespec
The list of parameters that you use after indi name must match the number of external variables in the indi.

So 10.2 TmaSlope has 20 external vars which must all be included (if my understanding is correct) ... their values that is. ("Select..", 0,1,50, 12 etc etc)

You can see the list of these vars at the start of the indi code or in the popup when you apply the indi to the chart.

So ... iCustom(symbol, TF, name , the 20 vars values separated by commas, the buffer that you want value from, shift)

HTH

M.

I also have read that at least all extern vars up to the one I need must be included after the indy name. But I am buggered if I know which ones I need to give me the slope value.

As such the 20 vars would look like this;

double Var1 = iCustom(NULL, 0, "10.2 TMA slope v.1.4B 4.30.mq4", "Select below 0=current tf,1,5,15,30,60,240,1440,10080,43200" , 0, 1, 50, 12, 3, black, 20, 0.4, -0.4, 100, white, 1, 25, 3, 14, 11, 1, 1, 3, 6, 0)

double Var2 = iCustom(NULL, 0, "10.2 TMA slope v.1.4B 4.30.mq4", "Select below 0=current tf,1,5,15,30,60,240,1440,10080,43200" , 0, 1, 50, 12, 3, black, 20, 0.4, -0.4, 100, white, 1, 25, 3, 14, 11, 1, 1, 3, 6, 1)

When I compile this, I get 4 errors, two each reporting "Black variable not define" and "white variable not defined".

When I change these color variables to 0, it compiles OK, but I have no idea if it will work or not.
Try Black / White, not black / white....

Also leave out extern strings.
Black & White should have capital 1st letters

Not checked code to see what the result will give you
If you think I'm mad, I must be mad
Thanks guys for spotting my typo re omitting the Caps for the colours. And I have now omitted the extern string.

double Var1 = iCustom(NULL, 0, "10.2 TMA slope v.1.4B 4.30.mq4", 0, 1, 50, 12, 3, Black, 20, 0.4, -0.4, 100, White, 1, 25, 3, 14, 11, 1, 1, 3, 6, 0);

double Var2 = iCustom(NULL, 0, "10.2 TMA slope v.1.4B 4.30.mq4", 0, 1, 50, 12, 3, Black, 20, 0.4, -0.4, 100, White, 1, 25, 3, 14, 11, 1, 1, 3, 6, 1);

Compiled fine...will test and let you know
  • Post #10
  • Quote
  • Edited 4:14pm Oct 3, 2012 4:01pm | Edited 4:14pm
I played with the TMA Slope using iCustom in an EA a while back.

I don't like the repainting factor, but I did get it to work.

This is the code I used:

double SlopeUp = iCustom(NULL,0,"Slope Indi",20,0.4,-0.4,100,1,1);

double SlopeDn = iCustom(NULL,0,"Slope Indi",20,0.4,-0.4,100,3,1);


When you apply the indi to a chart, and the "Inputs" screen pops up, the only parameters you need to use in the code, are the ones listed there.

In this case, after the normal NULL, time frame, and "Slope Indi" label, the 4 are: the eintPeriod value of 20, the edblHigh1 value of 0.4, the edblLow value of -0.4, and the ATR period of 100.

The next number 1 and 3 in my lines of code, indicated the buffers I wanted the indi to reflect. If you want it to reflect something different, use the buffers from the indi that corresponds with the values you want it to return. The last number is the shift of course, and since the TMA indi is a histogram, and it repaints, that's where it runs into trouble a bit. If you need more values returned, simply call another variable name, reuse the indi code line, and change the buffer number to identify the values you need it to return. I needed two, so I used the up, and the down, which was buffer 1, and the 3 I posted above.

Also, keep in mind, those buffers start at 0, not 1. Until I realized that, I was using the logical 2 and 4 like a total noob...

Hope that helps you some!

Cheers.
No way I'll wreck this... It's a beer truck!
Quoting dancingphil
Thanks guys for spotting my typo re omitting the Caps for the colours. And I have now omitted the extern string.

double Var1 = iCustom(NULL, 0, "10.2 TMA slope v.1.4B 4.30.mq4", 0, 1, 50, 12, 3, Black, 20, 0.4, -0.4, 100, White, 1, 25, 3, 14, 11, 1, 1, 3, 6, 0);

double Var2 = iCustom(NULL, 0, "10.2 TMA slope v.1.4B 4.30.mq4", 0, 1, 50, 12, 3, Black, 20, 0.4, -0.4, 100, White, 1, 25, 3, 14, 11, 1, 1, 3, 6, 1);

Compiled fine...will test and let you know
Just looking at this, the only difference is the shift of one bar. The current open bar, and the last closed bar. Is that what you were after?

Because that will give you some troubles. Var1 is a moving target.
No way I'll wreck this... It's a beer truck!
Quoting Bruce Flea
Just looking at this, the only difference is the shift of one bar. The current open bar, and the last closed bar. Is that what you were after?

Because that will give you some troubles. Var1 is a moving target.
Thanks for your two replies.

What I am trying to do is make a trade happen when it crosses the zero line. So I do need shift 0 and shift 1 to be on opposite sides of the zero line. And to overcome the repainting issue, I want these values to be known at the close of the shift 0 bar, using a "true value" version of the TMA.

With trades closed and reversed at each cross of the zero line, I want to understand the average cost of this flip-flopping of the TMA.

In theory, I should get this with;

extern int xi_Period = 20;
extern int xi_ATR.Period = 20;
extern double xd_ATR.Mult = 2.0;
---------------------------------
double Var1 = iCustom (NULL, 0, "10.2 TMA slope v.2.1 5.2",xi_Period,xi_ATR.Period,xd_ATR.Mult,6,0);
double Var2 = iCustom (NULL, 0, "10.2 TMA slope v.2.1 5.2",xi_Period,xi_ATR.Period,xd_ATR.Mult,6,1);


While I wish this was a histogram version of TMA so that I can visually see the cross of the zero level; it's an on chart 3 MA lines version.

The experiment is about finding out in transaction cost in terms how many times the TMA flips flops over the zero line before it finally sets off in a new direction, or reconfirms its past direction.

Thanks, Phil
  • Post #13
  • Quote
  • Last Post: Oct 3, 2012 6:38pm Oct 3, 2012 6:38pm
I see where you're headed now. And I have a slightly different version of the 10.2 TMA, which leads to the difference in parameters, but it looks like you've got it going on now.

I also looked the the TMA True indi. I still think the repainting thing will cause you some headache, but it's always worth trying

Best of luck with it!
No way I'll wreck this... It's a beer truck!
0 traders viewing now