Flying Slope auto-trading EA

[sandybeach]

Hi Mike,

Initially FS was working really well here. I have had lots of problems with trying to keep the platform it is on working, it seems to lock up and go to "not responding" so much of the time, and I have not been getting any trades. I will try it again this week on a different platform, and also maybe not so many pairs to try to find out what is causing the probs.

Cheers
Marlene

[bshoe24]

Hi Mike,

Initially FS was working really well here. I have had lots of problems with trying to keep the platform it is on working, it seems to lock up and go to "not responding" so much of the time, and I have not been getting any trades. I will try it again this week on a different platform, and also maybe not so many pairs to try to find out what is causing the probs.

Cheers
Marlene

Hi,

I don't ever post not usually having anything worthwhile to contribute but, i might have a contribution for a change for you to try. You may be having a problem i have seen for a little while. For some time now i have been testing Steve's and others generous offerings here (many thanks to all by the way). I have tested this EA and others and i have seen the "not responding" hangs many times - most of the times on startup of the terminal. What i have found is that the "ChartBars" function check where it checks for enough history for all the pairs seems to hang very often or at least it has for me. The hangs i've seen seemed to correspond with the history check you see flash by on the chart screen at the beginning of running the terminal. Though i'm not a coder i can read code reasonably well so i removed the "ChartBars" function (it's in two areas), recompiled, and my problems went away. I never again had any problems with this or the other EAs that i had the exact same problems. I couldnt tell you why this sometimes hangs the terminal and sometimes doesnt - even though i have ran the "Load history" scripts. I just remove that part of the code from any EA i download including new updates to EAs. I also always run the Load History scripts/EAs that have been shared here to make sure i am loaded up as correctly as possible.

I can't promise this is a fix for your exact problems but, you might consider trying it. If you want to try it load the EA mq4 up in the Metaeditor and remove the Chartbars function (in both areas) and then recompile and restart the terminal. Hopefully this helps if you are encountering the problems i was.

[cuzgeorge]

I can't promise this is a fix for your exact problems but, you might consider trying it. If you want to try it load the EA mq4 up in the Metaeditor and remove the Chartbars function (in both areas) and then recompile and restart the terminal. Hopefully this helps if you are encountering the problems i was.

Hi Bshoe24,
i was wondering if you now are managing to get FS to trade with your changes. I believe FS needs to look back at the charts for a history and there might be an issue at this point.?

I'm looking into this right now and will post what i find.
regards
CuzGeorge

[cuzgeorge]

Hi Gary , George and all,
Here are the first and last versions of FS.

If you have the time, use this to compare why the original would trade but the updates fell behind.

http://www.text-compare.com/ - (Thanks Gary)

For those who don't know,
1- open the editor you use and open each of the EA's into their own tab.
2- select the first tab and select all the code, right click in the highlighted area and 'copy.'
3- Navigate back to your browser where you opened text-compare and 'paste' into the one side.
4- repeat 2 and 3 for the second EA, remembering which one you put into which side, hehe
5- hit the 'text-compare' button and voila!, all differences are highlighted.


I cant see whats wrong myself, ' swoosh' over my head. There are many changes from the original, and the orig still has the 'is demo' cretin warning.

I've had to remove this EA to allow for others but would love to get back into this one. I dont see the problem with the code for the chartbars history as mentioned by BSheo24, but it possibly eats up CPU power. Might be luc and mq4 having a party again.

I had a few trades as posted before, but then all went silent with latter versions.

Hope this helps, and thanks to all for their contributions and time,
cuzgeorge

EDIT; I lied, i found FSv1l hidden on a 6 charts on demo with another EA . I'm going to revert back to the original version for now and see how FSv1 trades again from the beginning. V1 did'nt have much chart time but it did trade for me. Sorry for the edit here, Just noticed my mistake.

[bshoe24]

I can't promise this is a fix for your exact problems but, you might consider trying it. If you want to try it load the EA mq4 up in the Metaeditor and remove the Chartbars function (in both areas) and then recompile and restart the terminal. Hopefully this helps if you are encountering the problems i was.

Hi Bshoe24,
i was wondering if you now are managing to get FS to trade with your changes. I believe FS needs to look back at the charts for a history and there might be an issue at this point.?

I'm looking into this right now and will post what i find.
regards
CuzGeorge

I'm not currently testing it and havent been in a while (because i can only test so much) so i can't help on the actually trading of the EA. I was mostly just trying to help with the "not responding" hangs if someone was having the problems i had. As i said removing the Chartbars stuff resolved that for me. I never had another hang after remvoing it from the code and recompiling. As far as being sure of having proper history i always run "Loadhistory" and "ForceLoadHistoricalData" scripts that i got from this forum in lieu of having the checks in the EAs.

[cuzgeorge]

I can't promise this is a fix for your exact problems but, you might consider trying it. If you want to try it load the EA mq4 up in the Metaeditor and remove the Chartbars function (in both areas) and then recompile and restart the terminal. Hopefully this helps if you are encountering the problems i was.

Hi Bshoe24,
i was wondering if you now are managing to get FS to trade with your changes. I believe FS needs to look back at the charts for a history and there might be an issue at this point.?

I'm looking into this right now and will post what i find.
regards
CuzGeorge

I'm not currently testing it and havent been in a while (because i can only test so much) so i can't help on the actually trading of the EA. I was mostly just trying to help with the "not responding" hangs if someone was having the problems i had. As i said removing the Chartbars stuff resolved that for me. I never had another hang after remvoing it from the code and recompiling. As far as being sure of having proper history i always run "Loadhistory" and "ForceLoadHistoricalData" scripts that i got from this forum in lieu of having the checks in the EAs.

Thanks bshoe24,
and your post is very informative. Troubleshooting is the first step towards finding a solution. Much appreciated and i'm sorry i cant solve the problem of no trades.
regards
cuzgeorge

[sandybeach]

Thanks so much for the feedback everyone, I will def try what you suggest bshoe24, and see if it helps the issue here.

Cheers
Marlene

[SteveHopwood]

I have returned to this ea, and V 1j is in post 1.

Note my warning in post 1 about not using this live yet.

I was trading it live for a while. Just before the August slowdown, I made some changes to the code and took it off my live account for safety. On demo, it did not take a single trade throughout August, or for the first two weeks in September, so I removed it.

When I looked at the code tonight, I saw a bloop in the Htf Slope code that would have stopped most long trades.

In Crapergy testing, FS would take and close a trade, then shut up shop. The problem turns out to be in IsTradingAllowed(). The call to TooClose() in IsTradingAllowed() stopped further trading. There is something wrong in TooClose(), but blowed if I can see what. The only way to allow a resumption of trading is to comment out the call to TooClose().

Hey ho.

[zkucera]

In Crapergy testing, FS would take and close a trade, then shut up shop. The problem turns out to be in IsTradingAllowed(). The call to TooClose() in IsTradingAllowed() stopped further trading. There is something wrong in TooClose(), but blowed if I can see what. The only way to allow a resumption of trading is to comment out the call to TooClose().

Hi Steve,

I think the problem is in the following line:

Code: Select all

if (OrderCloseTime() - TimeCurrent() < (MinMinutesBetweenTrades * 60))

OrderCloseTime() - TimeCurrent() is always < 0 so the function always returns True.

Cheers,
Zeljko

[SteveHopwood]

In Crapergy testing, FS would take and close a trade, then shut up shop. The problem turns out to be in IsTradingAllowed(). The call to TooClose() in IsTradingAllowed() stopped further trading. There is something wrong in TooClose(), but blowed if I can see what. The only way to allow a resumption of trading is to comment out the call to TooClose().

Hi Steve,

I think the problem is in the following line:

Code: Select all

if (OrderCloseTime() - TimeCurrent() < (MinMinutesBetweenTrades * 60))

OrderCloseTime() - TimeCurrent() is always < 0 so the function always returns True.

Cheers,
Zeljko

Oh crap. Thanks. I had this solved at one point and have clearly unsolved it.

For those of you unable to correct this Baby Pips level bloop, the fix is in V 1k in post 1.

Thanks again Zeljco. Your contributions continue to be magnificent.