"Phoenix - FAQ, Stable, User support -Read Post #1" - Page 4

bertbin · #31 (**permalink**) 11-25-2006, 12:18 PM

Quote:

Originally Posted by daraknor

Error 130 is an attempt to set the stoploss too close to the current price. I the code changes are in dialog on the programming forum, I will release them this weekend. Mode1 should not have this error, since it isn't moving the SL around.

Thanks Darak...
At least we have somebody that knows...
Good
Nice WE

daraknor · #32 (**permalink**) 11-26-2006, 08:43 AM

Quote:

Originally Posted by bertbin

Thanks Darak...
At least we have somebody that knows...
Good
Nice WE

I listed the exact change necessary in case anyone else wanted to merge and release, I just wasn't on a computer with the source code at the moment. I waited a day, nobody released, I responded here since the bug hadn't been acknowledged in this thread.
The bug is fixed in the 5.6.6 release I believe (I ran a few backtests and didn't get the error anymore), but we need to test it still.
Phoenix - Development+Suggestions - MQ4 in Post#1
Bertbin, how do you think we can work more closely together?

bertbin · #33 (**permalink**) 11-26-2006, 11:36 AM

Quote:

Originally Posted by daraknor

Bertbin, how do you think we can work more closely together?

No problem. Mail, Pm, skype as you want...

I install yesterday the indicator of Alamandjani showing the buy and sell entries. For me when you put this indicator on usd/chf and eur/usd you see how they are different : that the settings are good for usdchf and bad for eur/usd
Why ? You have a balanced entry signal, more sell, in usdchf (= i am posi on usd chf) and quite only sell in eurusd (= i will never trade on that pair with such settings ! = settings are bads)
At the moment you have entries signal in the same direction of the trend = you got the settings (after you back'test, forward tests, etc...)
It's perhaps a way to find rapidly the new settings for an eventual next opposite trend ?

Now how to know a new trend ? Euuuh no answer for the moment
BUT a bit back to fundamentals : Euro is going high... too high for EZ... and $ want a strong $... Oil is down = good for States... Only unknown thing : China... Well stop for now..
In P5 : when you start to have strong losses (in pips)... If you see my statements of last week, the results start to be equal between gain and losses = something is hapenning

Stupid?

BTW have you see the indicators trend in Here's the new Goblin the link I posted you yesterday ?

(Darak I worked 20 years in advertsiing and, in brain storming meetings, a stupid idea sometimes brings new and/or brillant concept. Or nothing !!! but better to express that idea....That why sometimes, I am a bit... stupid ...Hi ! Hi ! Hi !)

Wackena · #34 (**permalink**) 11-30-2006, 10:25 AM

I noticed this AM that there is a repeated error message in the Experts tab and repeated attempts to OrderModify in Journal.

In the Experts Tab this is the message.

Phoenix 5.6.06.USDJPY,M15:OrderModify-Error # 1

Not sure what this means. In mgl error codes, Error 1 is "No error returned, but the result is unknown." Demo is on North Finance and I guess this could be a server problem.

Anybody else seeing this?

Wackena

Wackena · #35 (**permalink**) 11-30-2006, 03:29 PM

Quote:

Originally Posted by Wackena

I noticed this AM that there is a repeated error message in the Experts tab and repeated attempts to OrderModify in Journal.

In the Experts Tab this is the message.

Phoenix 5.6.06.USDJPY,M15:OrderModify-Error # 1

Not sure what this means. In mgl error codes, Error 1 is "No error returned, but the result is unknown." Demo is on North Finance and I guess this could be a server problem.

Anybody else seeing this?

Wackena

I contacted FDXX about above problem and this is their response.

Quote:

-----Original Message-----
From: NorthFinance Support Team [SMTP:support@northfinance.com]
Sent: Thursday, November 30, 2006 7:32 AM
To: xxxxxx@bellsouth.net
Subject: experts tab

Dear sir

The expert tab contains information about the attached expert,

including opening/ closing of positions, modifying of orders, the experts
own message.

You can find only the latest message in the window.

We have checked the above error message to make sure that it is not an error common from the system and it was regarding an active expert adviser.

For further information about indicators, scripts, ea please refer to
www.mql4.com <http://www.mql4.com/> it is specially designed, to answer
all related enquires

Please do not hesitate to email us for any further assistance

Kind regards,

Gavin

North Finance Support Team
www.northfinance.com

I posted this question on the mql forum.

Quote:

wackena 2006.11.30 15:53edit | delete
I'm getting repeated error message in my FDXX Demo Terminal window expert tab.

"Expert Name".USDJPY,M15:OrderModify-Error # 1

mql error code 1 is "No error returned, but the result is unknown."

Could someone advise what could cause this type error?

Thanks,

Wackena

Irtron was kind enough to give the following response.
reply

Quote:

80 Irtron 2006.11.30 17:31
That usually means that OrderModify() has nothing to do with the parameters it's called with.
I.e all the levels are the same the modified order has already.

Hint: check if the modification parameters are different from existing ones before the call.

I can't check modification parameters as Journal is full of OrderModify-eurjpy and Experts is full of OrderModify-usdjpy-error#1.

Could there be a problem in EA for OrderModify?

Does this code in EA try to OrderModify to same values as order.

Code:

OrderModify(OrderTicket(),OrderOpenPrice(),OrderOpenPrice(),OrderTakeProfit(),0,GreenYellow);

Metatrader may not accept modify an order to its already existing values. There must be at least one value change to process OrderModify command.

Good mystery for me.

Wackena

daraknor · #36 (**permalink**) 11-30-2006, 07:44 PM

Quote:

Originally Posted by Wackena

I contacted FDXX about above problem and this is their response.

I posted this question on the mql forum.

Irtron was kind enough to give the following response.
reply

I can't check modification parameters as Journal is full of OrderModify-eurjpy and Experts is full of OrderModify-usdjpy-error#1.

Could there be a problem in EA for OrderModify?

Does this code in EA try to OrderModify to same values as order.

Code:

OrderModify(OrderTicket(),OrderOpenPrice(),OrderOpenPrice(),OrderTakeProfit(),0,GreenYellow);

Metatrader may not accept modify an order to its already existing values. There must be at least one value change to process OrderModify command.

Good mystery for me.

Wackena

Are you using trailing stops in mode 1, or breakeven in mode 3? If so, what could be happening is the trailing stop code triggers, calls a refresh rates, finds the price has returned to a less profitable level and sends an order modify with the same price data again. To troubleshoot this, please comment the "RefreshRates();" inside the TrailingStop() function code near the bottom and see if you still have the error. Is anyone else getting this?

bertbin · #37 (**permalink**) 11-30-2006, 10:23 PM

MODE 3 both

On FXDD :
2006.11.30 18:16:30 Phoenix_EA_v5_6_06 USDJPY,M15: OrderModify - Error # 1
From 17h32 til now

On Interbak
2006.11.30 17:32:13 Phoenix_EA_v5_6_06 GBPJPY,M15: OrderModify - Error # 1
From 16h25 til now

Wackena · #38 (**permalink**) 11-30-2006, 11:37 PM

Quote:

Originally Posted by daraknor

Are you using trailing stops in mode 1, or breakeven in mode 3? If so, what could be happening is the trailing stop code triggers, calls a refresh rates, finds the price has returned to a less profitable level and sends an order modify with the same price data again. To troubleshoot this, please comment the "RefreshRates();" inside the TrailingStop() function code near the bottom and see if you still have the error. Is anyone else getting this?

Using Mode 3 and BreakEvenAfterPips=0. Error#1 message in Experts tab has stopped. After review of the code, I believe the problem is this OrderModify code.

Code:

if(FirstTrade==true && GlobalVariableGet("FlagMode3Trade2")==1)
    {
      RefreshRates(); //Added by Daraknor 5.6.6
      for(int y=0;y<OrdersTotal();y++)
        {
          OrderSelect(y, SELECT_BY_POS, MODE_TRADES);
          if(OrderType()<=OP_SELL && OrderSymbol()==Symbol()&& (OrderMagicNumber()==MAGICMA02 || OrderMagicNumber()==MAGICMA03))
            {                     
              if(OrderType()==OP_BUY)
                {
                  OrderModify(OrderTicket(),OrderOpenPrice(),OrderOpenPrice(),OrderTakeProfit(),0,GreenYellow);
                  GlobalVariableSet("FlagMode3Trade2",2);
                }
              if(OrderType()==OP_SELL)
                {
                  OrderModify(OrderTicket(),OrderOpenPrice(),OrderOpenPrice(),OrderTakeProfit(),0,GreenYellow);
                  GlobalVariableSet("FlagMode3Trade2",2);
                } 
            }
        }
    }

You can get Error # 1 when OrderModify attempts to replace the values already set with the same values. One or more values must be changed, then modification attempt can be repeated. (Definition of Error #1 - http://docs.mql4.com/trading/errors )

The only order related variable in question to change in code above is OrderTakeProfit(). This value is same as in order and needs to be changed before modify routine can work. I believe the Error # 1 stopped because the signal is now false to modify order and so the error stopped, but will reappear when signal is true again.

Wackena.

Shinigami · #39 (**permalink**) 12-01-2006, 01:15 AM

i'm really new to this so it might sound stupid but... do you HAVE to modify TP? just don't... if that causes errors

Pecunia non olet · #40 (**permalink**) 12-01-2006, 10:02 AM

Quote:

Originally Posted by Ducati

I backtested on Alpari and on FXDD both with Alparis data and I get totally different results with the same settings. This is so frustrating.

Quote:

Originally Posted by Ducati

Anyone know why I have majorly different results on backtesting from different brokers, but with the same data?

A very wild guess: I seem to recall seeing somewhere that Alpari handles Sunday bars differently than FXDD. You might want to visually compare the price plots in both platforms, and especially compare the Sunday bars.

While you're at it, you could also compare a sample of bars numerically; Are the OHLC prices always the same?

How about the spreads in both platforms. Are they the same on the pairs you're testing?

Final wild guess: Could it be related to how the platforms define time of day?

Are you getting completely different entries and exits? Relatively small differences in data can 'compound' in effect over a large amount of data. A sort of intuitive test of whether a system is overly curvefitted to a data series is whether it can survive on a different series. However, generally speaking, I think it would be tough for a system to overcome something like vastly different Sunday bars, or very different platform handling of time of day. (Obviously this will vary depending on the type of system, and I'm generalizing here.)

In any event, after lots of backtesting in Tradestation I've formed the ironclad opinion/rule of thumb that for me, the only meaningful backtests and optimizations are those that are done on the data that you'll be trading on. There are a lot of possible 'gotchas' that can appear if you're testing with data that's different from what you'll be trading on, and some of those 'gotchas' are not immediately obvious. In this game I think you need as many of the odds as possible working in your favor. IMHO, optimizing on your own broker's data is an important step in that direction. [Theres a paradox here: You want your system to perform on unseen, different, future data, but ya gotta try to tune the system on data thats as similar as possible to the unseen future data...]

With MT I'll assume that you'll also want to test and optimize using the platform that you'll be trading with.

I hope some part of this helps!