FXQU_A1 broker limits hit.... Again

Time to adjust the approach with the accounts.  I have hit the trade limits again.

I will changing things up this weekend... New approach... More later

FXQU_A1 update... Smaller timeframes

V1.80 was deployed last night to now give the option to stop new trades opening if the same direction and timeframe was already opened. Also some cosmetic changes such balance, equity etc is displayed.

Tough going at the moment with single direction of the usd pairs.. I have switched my second live account Ruby to very small time frames however the already opened large time frames will need to eventually close out.

FXQU_A1 A2

OK so I plan to switch the second live account (Ruby) over to the A2 model which looks at very small timeframes... This way I will have two accounts covering small and large timeframes.

No new versions deployed..

FXQU_A1 re-factoring

Latest version is v1.78  ...  I had to refactor the engine to cater for broker limits (max trade numbers).  This meant some prolonged testing periods across all the robots - it also meant that a minor bug crept into the deployed code.  This is now fixed however I am monitoring the internally generated messages created during the robot execution window.

FXQU_A2 update

Since mid December the robots have been pushed... Constantly trying to manoeuvre through positions to get the best outcome in a one directional market.

I have changed the FXQU_A2 account to very small time frames as of this morning.

Latest version is v1. 77

I had to recode some data blocks that reduce the level of broker server messaging following a warning from IC markets.... Apparently 2000 hits per day is a lot... Unfortunately that's not a lot for FXQU_A1!

FXQU_A1 update.. Dynamic throttling change

New minor version released v1. 74... This was to all robots.  Key change was a slight mod to the dynamic throttling algorithm.

The robots are currently attempting to recover from the long usd downward run and are positioning up appropriately.

FXQU_A1 update.. Limits hit

With the strong directional decline of the usd pairs I noticed some trades were not completing. Further investigation showed the robots were hitting the Max allowed number of trades per account (in line with broker guidelines) . I have changed the code accordingly and have deployed the latest version 1.72 across the robots. 

Overall the next week or two the new version will be fully flushed through the trades.