Fractalated Bob

[boldtrader]

Hey boldtrader, I would have thought your MPTM settings would be 55/13 with a trail of 34 to stay with your Fib Rules!

LOL.. lets see, I have 17 different bots running, testing, and a hundred other things going on at the same time.. Ya know... sometimes things just slip through.. and multiple eyes are better than one... I missed a setting by a couple.. thanks for the catch.. can't get them all, but still doing darn good.

Cheers

[Gertje]

This is fun!

I set it up on the H1 TF, and within 2,5 hours the first 5 trades closed for 1% profit.


And now I need to wait for over half an hour for 'maybe' the next trade....

[patmontes]

2 global closures on a Monday! Good stuff!!

[SteveHopwood]

2 global closures on a Monday! Good stuff!!

[taipan]

I am using FB and limit my all my trade to max. of 2. This morning, my Global Prime demo traded on EU AND Audjpy sell with 6 positions each (lot size = 0.01). Is there a bug with this ea? I am using v1g. Lot preset to 0.01 and risk percent set to 2.0. Timeframe set to 15 min and Trading TF = 240.

[boldtrader]

I am using FB and limit my all my trade to max. of 2. This morning, my Global Prime demo traded on EU AND Audjpy sell with 6 positions each (lot size = 0.01). Is there a bug with this ea? I am using v1g. Lot preset to 0.01 and risk percent set to 2.0. Timeframe set to 15 min and Trading TF = 240.

Strange.. mine did the same.. but with different pairs.. have 3 nzdusd, 2 nzdjpy, 2 gbpusd, 2 eurnzd, 2 euraud, 2 audusd, 2 audjpy, 2 audchf, and others.. trying to figure out the cause but baffled..

Just began in London session from Sunday to Monday.

Not sure but researching..


Cheers.. BT

[SteveHopwood]

Strange.. mine did the same.. but with different pairs.. have 3 nzdusd, 2 nzdjpy, 2 gbpusd, 2 eurnzd, 2 euraud, 2 audusd, 2 audjpy, 2 audchf, and others.. trying to figure out the cause but baffled..

You will be.

'Empty4' is not a humourously affectionate epithet applied to a magnificent piece of software whose magnificence takes our breaths away.

The term is applied because the platform is rubbish whose appallingly bad coding takes our breath away.

CrapTx has a wonderful little trick up its sleeve, no doubt coded deliberately during the days when the market makers, bucket shop owners and CrapperQuotes all slept together. A sent trade appears immediately in our Orders window, so we think it is an actuality.

It isn't. It is a mirage. The trade is not in the platform's memory until confirmation of the trade is returned from the broker's server. The broker can hold this confirmation for a long time.

So, what happens is this: EA finds a trade trigger; it examines the platform's memory and finds no trade already in place; it yells, "Yippee. Let's party" and sends a trade. The receipt back from the broker is delayed, so the trade is not in the platform's memory. The platform receives a tic. EA finds a trade trigger; it examines the platform's memory and finds no trade already in place; it yells, "Yippee. Let's party" and sends a trade. The receipt back from the broker....................................

In our early days, before the dawn of time i.e. the birth of SHF, we would often awake to find an ea had apparently gone berserk and sent dozens of trades within seconds of each other. Guess what? They all went straight into dd and wiped the account. This never happened to me live, but that was just plain lucky.

Genuine brokers such as our own GP and the guys that Bill trades with do not play around like this, but there can still be a delay caused by latency etc - don't think I actually know what I am talking about here, when talking about technical stuff to do with sending and receiving thigies over the net.

In stepped Matt Kennell with his LibOrderReliable library to replace the usual order sending, closing, deleting and modifying functions that come with CrapQlx. My shells have always included his order sending code, which includes a function to repeatedly check that there has been a receipt returned from the broker's server. I have used this code since before the dawn of time. It has worked flawlessly and seamlessly.

Until now, it appears. Those wretched morons with shit for brains have managed to break this somehow, and I am bloody annoyed. Yet again, we coders have to find a way of making up for a monumental balse-up by those cowboys.

Do me a favour guys: go through your log at the time the trades were sent. Matt's checking code includes lines that sends a message to the log. This one

Code: Select all

Print("Did not find #"+ticket+" in history, sleeping, then doing retry #"+cnt);

is inside a loop that searches the memory for the trade ticket number, so you can imagine the sort of message it prints.

After searching x times, the function sends another message to the log:

Code: Select all

Print("Never found #"+ticket+" in history! crap!");

and gives up. This point has not been reached before.

I think that in view of the multiple trades then we need to get an ea to send us an alert that this has happened and then unload itself. Or maybe sleep for 10 minutes? Any other ideas guys?

Another thing. I am still on Empty4 build 646; don't update to the latest version until you absolutely have to.

Welcome to my world, Bill.

[magft]

I have noticed that for one on the pairs CADJPY, no others strangely out of 26 pairs, occasionally sends 3 trades. I've checked the log and there are no errors what so ever!

Code: Select all

2014.09.30 06:59:46.031	Fractalated Bob CADJPYf,M15: open #19297447 buy 0.10 CADJPYf at 98.106 ok
2014.09.30 06:59:46.015	Fractalated Bob CADJPYf,M15: open #19297445 buy 0.10 CADJPYf at 98.106 ok
2014.09.30 06:59:46.000	Fractalated Bob CADJPYf,M15: open #19297444 buy 0.10 CADJPYf at 98.106 ok

I'm testing on Tradefort build 670, its happened about 3 times now over past few weeks since i started the demo but all other pairs work ok. In the code you only send the trade for a new bar so its its very odd that it sends a trade and the next tick checks again surely it should just wait til the next bar!

Still enjoying watching this EA at work, think i've limited the wins though using a TS but still doing well.

Regards

Mike

[SteveHopwood]

I'm testing on Tradefort build 670, its happened about 3 times now over past few weeks since i started the demo but all other pairs work ok. In the code you only send the trade for a new bar so its its very odd that it sends a trade and the next tick checks again surely it should just wait til the next bar!

This snippet needs removing, I think, starting at line 1594

Code: Select all

//Actions when trade send fails
   if (SendTrade && !result)
   {
      OldBarsTime = 0;
   }//if (!result)
   

because OldBarsTime prevents looking for a trade at line 4278.

Those of you who can, make this change for yourselves. I will put up a fix for the rest of you in a few minutes.

[SteveHopwood]

Fix added to post 1 - V 1h.