Holy Graily Bob 'n Dotty 'n SuperSlope

[sesshoumaru]

hi, I put the EA this morning when this weeks started, later I checked and I found this error
2017.01.23 11:34:26.368 Holy Graily Bob 'n Dotty 'n SuperSlope GBPJPY,H4: invalid lots amount for OrderSend function
2017.01.23 11:34:26.368 Holy Graily Bob 'n Dotty 'n SuperSlope GBPJPY,H4: GBPJPY Holy Graily Bob 'n Dotty 'n SuperSlope OP_SELLSTOP order send failed with error(4051): invalid function parameter value Bid = 141.225: Price = 141.139
i'm using the HGIDot-H4 set file just above, but I changed the risk to 1 percent and lotsize to 0 so that it trades with lotsize per risk, but it gives invalid lotsize sometimes. I have several open trades normally, but it has some problem under certain conditions.
or should i just use fixed lotsize?
Thanks!

[traderduke]

faker
Looks great! Any chance you can provide the set file?
Thanks
Ray

I've been a lurker, and mostly done a lot of reading on here - even before attempting on demo... Just so I understood what each bit would mean.

Anyway, I've taken the plunge and have had some fantastic results with this today. I tested out earlier this week with much larger pip for TP; however I wanted to assume I was on a real account so setup the size and such as I would be on live. I also factored in that I do like to take a peak at how it's going through the day, and have opted for the quicker+smaller profits; but it seems that this EA doesn't care for what I want and just keeps giving!

Attached some of the results.

Thanks to everyone who has put in their hard work for this, and who continue to do so.

[UltraMax]

So here's my settings. I told the EA to only close profitable trades and it's still closing negative.

Untitled.png

Also, I'd like to place only one pending trade at a time but the 20/40/60 method has the EA placing pending orders 40 pips away from the price. I'm taking trades off the 1m in the direction of the 15m HGI.


The EA still places trades in either direction of the market based on CSS so it's not sticking to the higher TF hgi rule set in place either. I would also like to close positions from the trend TF and not the trading TF. This would help quite a bit.


If i set it to trade on a grid, it will keep adding pending orders all the way up or down. I only need one order. If i have too many open i will get drawn down too much. So if we could have a setting for 1 order only, pending with an option of how many pips from price, this would greatly decrease drawdown as well.

Untitled2.png

Thanks

[tomele]

Read the manual and the thread.
And pray that you will not get banned.

Although ... going to grab me some popcorn.

[SteveHopwood]

So here's my settings. I told the EA to only close profitable trades and it's still closing negative.



Also, I'd like to place only one pending trade at a time but the 20/40/60 method has the EA placing pending orders 40 pips away from the price. I'm taking trades off the 1m in the direction of the 15m HGI.

The EA still places trades in either direction of the market based on CSS so it's not sticking to the higher TF hgi rule set in place either. I would also like to close positions from the trend TF and not the trading TF. This would help quite a bit.

If i set it to trade on a grid, it will keep adding pending orders all the way up or down. I only need one order. If i have too many open i will get drawn down too much. So if we could have a setting for 1 order only, pending with an option of how many pips from price, this would greatly decrease drawdown as well.



Thanks

Uh-huh.

Another cretin too dim to take on board the instructions in my Welcome message, warning that posting before you have learned what is going on is a bad idea.

I believe I did mention my utter unmitigated loathing of morons who are too stupid to read the User Guides that I produce, and so ask lunatic questions that prove conclusively that they have have not bothered to do so. Ok, so I might have worded it a touch more gently, but you have to be really thick to miss the message.

Long-standing members of SHF read these guides compulsively before asking questions. Then they ask them tremulously and fearfully. Their tremulous fearfulness is often well justified. I tend to get a tad on the shirty side with them.

Before reading on, grasp that I love and embrace, "masterly British understatement". I use it all the time.

Bearing that in mind, ask yourself what I might mean when I write, ".... a tad on the shirty side...." In case of doubt in your mind, "shirty" is a colloquialism for, "irritated".

The above is merely background and is intended as a gentle introduction to what follows.

Whilst I get a tad on the shirty side when somebody with the brain power of a deceased clam asks a question that proves beyond any question of doubt that he/she/it has not been arsed to read the user guide, this is as nought to my malevolent fury when said questioner appears to be questioning the code.

There is long-standing code in my EA's that was contributed a long time ago by programmers whose skills are so superior to mine that they humble me. Old stagers here are still trying to get their heads around the concept of me being 'humbled' by anyone. It has been done.

This code has stood the test of time over and over and over again. Try questioning that and see what happens.

Later code has been pored over by severely good bloop spotters. They did not spot everything, but tomele has spotted the rest and future updates to this and other varieties of Dotty and her relatives will include his spots.

What I am saying here is that the code is as watertight as about 15 resident coding genius's can make it.

You, on the other hand, are an idiot. In future, when something does not behave as you wish it to do then here is what to do: assume you are still a dweeb with the intellect of a squished Tsetse fly that had seen better days even before it got squished and that it is your lack of knowledge and understanding that is at fault.

My best advice to you is to stay quiet until you have grown into long trowsers. SHF is a forum for grownups.

[SteveHopwood]

I have recoded HGBnDnSS using the shell. I have reverted to naming it V1 because of the extensive changes made to the code by Thomas and my inclusion of the sixths and buy-low-sell-high principles. Post one as usual.

[SteveHopwood]

Anybody trading this on demo would have has some peculiar trades - I left a vital conditional out of the trade trigger decision.

Fixed that and have added the updated sixths and buy-low-sell-high stuff. Post 1.

[SteveHopwood]

The latest update is in post 1, with HgiCloseOnYellowRangeWave input implemented in the code.

[traderduke]

The latest update is in post 1, with HgiCloseOnYellowRangeWave input implemented in the code.

Thanks Steve,
One minor question, when the EA is activated it takes the chart to the lowest minimum candle size, on Tallinex platform,is that on purpose?

I've started testing it again, I'll let you know!
Thanks again
Ray

[SteveHopwood]

Thanks Steve,
One minor question, when the EA is activated it takes the chart to the lowest minimum candle size, on Tallinex platform,is that on purpose?

I've started testing it again, I'll let you know!
Thanks again
Ray

The bot only needs to do this if you are using sixths or buy-low-sell-high, but I have missed out a conditional. This applies to all the flavours of DB/HGBnD that I have updated this week, so I will upload fixes tomorrow.

In the meantime, the zooming out does no harm and you can simply zoom back in again. Or you can make your own edit and add the missing conditional.

Go to int OnInit(). The first snippet in the function is:

Code: Select all

   //Zoom the chart out as soon as possible. I do this at the start
   //of GetSixths() as well - does no harm.
   int scale = ChartScaleGet();
   if (scale != 0)
   {
      ChartScaleSet(0);
      //A quick time frame change to force accurate display
      per = ChartPeriod(0);
      int nextPer = GetNextPeriod(per);
      ChartSetSymbolPeriod(0, Symbol(), nextPer);//Change time frame
      ChartSetSymbolPeriod(0, Symbol(), per);//reset time frame      
   }//if (scale != 0)

Copy this over the top of it:

Code: Select all

   if (UseSixths || UseBuyLowSellHigh)
   {
      //Zoom the chart out as soon as possible. I do this at the start
      //of GetSixths() as well - does no harm.
      int scale = ChartScaleGet();
      if (scale != 0)
      {
         ChartScaleSet(0);
         //A quick time frame change to force accurate display
         per = ChartPeriod(0);
         int nextPer = GetNextPeriod(per);
         ChartSetSymbolPeriod(0, Symbol(), nextPer);//Change time frame
         ChartSetSymbolPeriod(0, Symbol(), per);//reset time frame      
      }//if (scale != 0)
   }//if (UseSixths  || UseBuyLowSellHigh)

You can easily see the conditional I missed out originally.