Adjust your risk setting to get the lots down to .01 on $2500 for a standard account or .01 on a $250 mini to help prevent "blowout". By the way, you can't blowout your account with the Equity Protection feature set at 50%. At the most, you would lose 50%, not the whole account.

v/r

__________________
Jeff
J Talon Associates
Investment Management

How do you adjust risk setting? Do you mean setting 0.01 lots inside the lot size setting?

Also, what is the multiplier value inside piplite?

Adjust the MaximumRisk value. I set 4 for a $2500 account. That will give you .01 base lots. The multiplier is this:

if(MoneyMangement){

LotSize=AutoLot();
if(LotIncrement>0) LotIncrement=LotSize;
}

Lots = NormalizeDouble(LotSize + (LotIncrement * SellOrders), lotPrecision);

The more orders, the higher the next lot size....

v/r

__________________
Jeff
J Talon Associates
Investment Management

Hi Iron,

Thanks, this is very informative. While I could guess how Blessing work by reading your advance feature document and the settings inside, I find it a little hard to guess how Piplite works. But it is working great so far.

For the maximum risk, if I start with 1500 on a micro account (0.01 lot, 1 pip = 1 cent), should I leave the setting at 4?

Also, can I have two pairs (euro/gbp h1, usd/jpy h1) running piplite together? No magic number to set?

hello to all

For Holyguy7 - mikeduk - Iron:

I ask forgiveness for my English


But I am insisting I think that the filter Marsi is not correct.

The MA is calculated on the actual price of the PAR, should be calculated on the value of RSI

in the backtest released by the Iron version 1.6 is observed that there is only Shell shops throughout the year.

The value of this MA provided between (1.900 and 2.000) aprox. the value of the pair is an average of the price

The value of RSI is between 0 and 100, but has never been below 2,000 -

is like comparing apples with pears

I again ask forgiveness for my English


Orlando

Morning All,

Both Iron and Lordorly have spotted a pretty major problem with the MARSI cross code previously added in v1.6 that when enabled it will only enter sell's and never enter a buy.

The MA on the chart provided by HolyGuy is calculated on the RSI, NOT the PRICE, where in the code the MA was being calculated on the PRICE and not the RSI. This of course meant that the MA value would always be lower than the RSI value and therefore according to the entry rules, never allow a BUY.

I've fixed the problem in this version of the EA, it now calculates the MA on the RSI rather than the price, I've done a fair amount of testing with this this morning and it appears to be working correctly now.

All parameters are the same as they were before.

Iron: Perhaps you can take a look at the changes and if happy merge them into a V1.7 of the branch? I've also added some additional items into the EA's comment section to show the status of each component signal, it was helping me debug and might be useful to others?

Cheers

Mike

Attached Files

Piplite v1.6_MIKEDUK_CROSS_FIX.mq4 (38.7 KB, 173 views)

Hi lordorly, you are absolutely correct, this was overlooked when I added the code originally. Please see my previous post for the fix.

Thanks for highlighting this.

Mike

Hi Gordi,

The time filter simply stops multiple trades within a certain number of seconds (set via the Minimum_Entry_Delay param = the number of seconds to wait).

For example, if you wanted the code to wait 5 min's between trades you would simply set Minimum_Entry_Delay to (60 * 5 = 300) seconds.

The idea being that if the market is moving quickly then we dont want to enter loads of trades quickly.

Hope this helps

Mike

Mike,

I am doing forward testing using piplite 1.5. I did see buy and sell orders.

is there some sort of new code that 1.6 has but 1.5 does not?

Hi Kwkee,

Yes, v1.6 added some new code to check that an MA was above/below an RSI line before entering the market, there was however a problem with the MA calculation (calculated on PRICE rather than RSI) which stopped buy orders.

You can see the spec of the change HERE and the recent change to fix the code HERE.

This version also includes a time filter that does not allow multiple trades within a certain number of seconds. It can of course be disabled if needed.

Cheers

Mike