MagicTurtle
07 Sep 2017, 16:13

Thank you for the update,

So I can understand a bit better, could you please clarify what 'requesting a Stop Loss for a position that falls within the margin' entails and how I can avoid this,

cheers

MagicTurtle
07 Sep 2017, 13:03

Hello,

Has there been any updates?

Can you let me know the progress? I'm starting to lose confidence here.

thanks

MagicTurtle
21 Aug 2017, 03:45

Thanks,

I ended up building a ryzen 7, 16G ram desktop which is working out well for the time being,

cheers

MagicTurtle
14 Aug 2017, 04:52

Hello,

Any updates? I asked your colleague at community 10 days ago for an update but he hasnt replied.

thanks

MagicTurtle
28 Jul 2017, 03:56

Hi Paul,

I left it overnight and it was actually executing fine - it ended up having a longer period than usual after I updated the parameters where there was no trades to be made.

So it was actually just me being confused and I'm really happy with the work you did for me :)

Thanks

MagicTurtle
27 Jul 2017, 10:44

Thank you,

I have sent that through, also I am using windows 10 64 bit with Calgo 2.01

MagicTurtle
27 Jul 2017, 06:08

Hello,

It keeps happening and with a number of my trades as well so I can send you my code.

Can you please provide me with an email address where I can send my code? In this instance which is separate from the AUD?JPY example I have a position in USD/CAD which gives the same message

Thanks

MagicTurtle
26 Jul 2017, 04:32

Hello,

Any updates?

Thanks

MagicTurtle
21 Jul 2017, 17:29

RE:

I don't have that anywhere,

Thanks

MagicTurtle
21 Jul 2017, 17:13

RE:

Thanks,

Here is part of the code which should be closing the position:

thanks
 

private bool IsShortCloseSignal()
        {
            if (_sma7.Result.HasCrossedAbove(_sma8.Result.LastValue, 0))
            {
                return true;
            }
            else
            {
                return false;
            }
        }

        #endregion

        #region Position management

        /// <summary>
        /// 
        /// </summary>
        /// <param name="tradeDirection"></param>
        private void ManagePositions()
        {
            
            // Open short
            if (IsShortOpenSignal())
            {
                // make sure there is not a short already open
                if (!IsPositionOpenByType(TradeType.Sell))
                {
                    OpenPosition(TradeType.Sell);
                }
            }

            // Close short
            if (IsShortCloseSignal())
            {
                ClosePosition(TradeType.Sell);
            }
        }

        /// <summary>
        /// Closes a single position for this unique cBot instance
        /// </summary>
        /// <param name="type"></param>
        private void ClosePosition(TradeType type)
        {
            var p = Positions.Find(InstanceName, this.Symbol, type);

            if (p != null)
            {
                ClosePosition(p);
            }
        }

MagicTurtle
21 Jul 2017, 16:21

RE:

MagicTurtle said:

Hello,

I have a bot running where a position should be closed on SMA signals.For some reason I get the error as below and the postion is not closed when i should be. In the screenshot you can see where the cyan coloured sma closed above the purple sma line but I only got the error and the position wasnt closed. Sometimes it works but alot of the time it doesnt. In this instance I closed the position manually.

For some reason it wouldnt let me upload the screenshot so I uploaded to imgur: http://imgur.com/a/wqBwJ

I had a look at this thread /forum/cbot-support/2837?page=2 but I'm not sure it applies since my bot is meant to close it without using a set target.

Can you help me understand this error message and what I can do to ensure my position is closed every time its meant to?

Thanks

 

Here is one of the error messages: "21/07/2017 13:00:01.417 | → Request to amend position PID1447744 (SL: 0.792) is REJECTED with error "TRADING_BAD_STOPS""

and I've sent the troubleshooting info through to the support team referencing this thread,