MultiBob, a multi symbol NB10.2(a) autotrader

[gaheitman]

If you are have a lot of opening and closing trades, please post a screenshot of your experts tab. MultiBob shows some logging that can be used to pinpoint possible errors. Thank you.

At about 22:30 GMT I started getting a bunch of short-duration losing trades -- see attached. Unfortunately an indi I wrote seems to be spewing out 10-15 messages a second so the Experts tab is running about 6 hours behind!! It's 01:25 GMT now, and the Experts tab is currently dumping messages from 19:25 yesterday. So I can't tell you what's in the Experts tab.

I think I found the issue. The procedures calculateTakeProfit() and calculateStopLoss() are being called before the order is sent, but are accessing OrderMagicNumber() to determine the magic number. That value will either be undefined or will match the previous entered trade. Probably not what we want...

This causes the code to sometimes assign an incorrect take profit level because it thinks it's a different kind of trade. That profit level is on the wrong side of price, making the test I referenced earlier change the take profit to price (unless you have a large stop limit).

George

[Thunder123]

I had open close problem on AUDCHF. See attached screenshots.

[fxarun]

Thanks George.
Spot on.
Instead of using OrderMagicNumber(), I am using tradeorigin to differentiate trades and calculate stoploss and takeprofit accordingly.And I think Its working.

Thanks
Arun

[Baluda]

New version MultiBob v1.1.4 in post 1.
Changes:

• Fixed bug in send trading logic causing incorrect stoploss. TY George
• Implemented new trading hours logic
• Added several improvements in display grid

MultiBob, screen III.png

Notes
1.
Users can now greatly influence the trading hours of the EA. The input string 'tradingHours' takes a comma delimited string of start and stop times for trading. Prefix start times with a '+' sign and stop times with a '-' sign. Use 24H format and a decimal point separator between the hours and minutes. Alternate between start and stop times. Some examples:

• +7.00,-9.30,+14.00,-15.00
• +9,-10,+16,-18.30
• -4.15,+11,-14.30

As you can see, minutes are not required. If the first time in 'tradingHours' is a stop time MultiBob assumes a 0.00 start time.

2.
MultiBob now uses graphic symbols where possible. User inputs can disable this and set colors for those symbols.

3.
Grid line separators are added for better readability. The 'gridLineCount' holds the number of lines between the separator lines. 0 disables the grid lines.

Kicked minor version number.

Enjoy!

Paul

[Eamonn]

Thanks Paul will give it a Whirl !!

[aworex]

Thanks for Paul, been testing it since monday with on all the latest versions on Alpari & FXCM no issues However, is it possible to set a maximum number of opened trades such as a basket limit to avoid margin issues.

[spotdespot]

Thanks for Paul, been testing it since monday with on all the latest versions on Alpari & FXCM no issues However, is it possible to set a maximum number of opened trades such as a basket limit to avoid margin issues.

There already is one. Use the ForexKiwi settings - it will not open trades when margin is below the specified level.

[aworex]

Thanks

[Baluda]

New version MultiBob v1.1.5 in post 1.
Changes:

• Fixed bug in trading hours logic, TY Robert

Use this one if you want to play with trading hours, folks.

Pick up those pips!

Paul

[garyfritz]

Still running v.1.0.2 OOTB, I got some odd errors this morning: a whole series of "Not enough money" errors. According to the alert box, this has been going on for hours. What in the world, I thought, did it blow up a $42k demo account?? No, it's down about $7k but there's still lots of money there. Current margin use is only $15k (with 4 open trades), free margin is $20k.

I can only see the alerts for the last hour or two, but they're ALL for GBPAUD.

Also, I thought it was my indi that was getting the "unknown subwindow number -1 for ObjectCreate function" errors in the Experts tab, but I removed that indi last night and the errors are still coming. I don't know how to tell what's causing them. I'm not 100% sure this setup didn't get them before I added MultiBob. (I have about 10 charts open with NB indicators on them -- DWMPivots, NT TMATrue SlopeHisto MTF, iExposure, Tickets, SlopeValues, NB 10.2_Dashboard, etc.)

Guess I'd better update to v1.1.5 ...