Topics
Replies

firemyst
04 Oct 2024, 14:42 ( Updated at: 05 Oct 2024, 08:40 )

Have you seen these examples?

https://help.ctrader.com/ctrader-algo/articles/for-developers/how-to-use-custom-indicators-in-cbots/#initialising-an-indicator

One way or the other you have to program it in your bot code, so reference the indicator in your bot instead of trying to read a value from teh chart


@firemyst

firemyst
03 Oct 2024, 07:58 ( Updated at: 03 Oct 2024, 07:59 )

RE: costum indicators not showing

PanagiotisCharalampous said: 

Hi there,

We have released a hotfix (5.0.38). Can you please advise if it resolves your issue?

Best regards,

Panagiotis

Not for me. I had a chart on AUDJPY Renko10. All custom indicators were showing. Then I switched to CADJPY and they vanished.

I tried switching time frames, symbols, didn't help.

Looked in the algo tab to see what logs were displayed, and there were no errors erported for any indicator. All it said is indicator loaded/unloaded.

I couldn't get the indicators back on the chart without restarting cTrader.

I haven't found a way to consistently reproduce them disappearing. So far, it just seems to be randomly.

Version 5.0.38.32023

 


@firemyst

firemyst
03 Oct 2024, 00:20

Hopefully you can get the latest version now and update to 5.0.38.

AGain, it's one of those things that people need to ask how much testing they do before releasing a version as this seems like something that should have been pretty straight forward and catching beforehand.


@firemyst

firemyst
03 Oct 2024, 00:17

I experienced this as well. My cTrader was just updated to version 5.0.38, so hopefully they have that issue fixed now. 


@firemyst

firemyst
03 Oct 2024, 00:14

What's the spread on your US30 when you place the order?

On a few brokers, the spread is larger than the 2-point SL you set. 

If you're doing this in a bot or indicator, you need to check the spread before placing your order. It's not a guarantee since the spread could hypothetically change at any given moment, but it's a good safety check


@firemyst

firemyst
03 Oct 2024, 00:07

Get the position, and then check the stoploss value.

 

if (p.StopLoss.GetValueOrDefault() == 0)

{

    //no stoploss on the position. DO what you want to do.

}


@firemyst

firemyst
02 Oct 2024, 07:48

RE: RE: When a bot was "unexpectedly terminated", cTrader shows the bot as still running

PanagiotisCharalampous said: 

Hi firemyst,

We were able to reproduce this some days ago and we are working on a solution.

Best regards,

Panagiotis

Thank you for the update.

I am going to have my VPS reimaged again since your team no longer needs it now.

 


@firemyst

firemyst
02 Oct 2024, 00:42

cTrader updated to 5.0.36 and the issue still persists.

 

I've left my VPS up if the Spotware team wants to go back in and have a look and see for themselves.

 

 


@firemyst

firemyst
01 Oct 2024, 00:22 ( Updated at: 01 Oct 2024, 06:07 )

you need to put this in the Suggestion forum:

https://ctrader.com/forum/suggestions/

This is technical support, and Spotware doesn't come here looking for suggested improvements to their product.


@firemyst

firemyst
01 Oct 2024, 00:19

Yes, you are.

First of all, you can choose what lines you want displayed on the chart:

 

Second, if you write your own code, just get the symbol's “ASK” price or “BID” price depending on what you want to display.

eg: Symbol.Ask

 

 


@firemyst

firemyst
27 Sep 2024, 01:41

RE: RE: When a bot was "unexpectedly terminated", cTrader shows the bot as still running

zossles said: 

Any updates on this issue? It's affecting us on our VPS as well. cTrader keeps “losing touch” with running bot instances as described in this thread. We discovered this two weeks ago when we were wondering why our bots weren't taking trades they were supposed to. They just “stopped” logging anything, but cTrader still showed them as running.

It's frustrating that now there's at least 2 users reporting this issue, and there still doesn't seem to be any movement on it even though I:

  • sent them emails (Screen captures above in this thread where they acknowledge receipt of the emails) in August on what the issue is and how to reproduce
  • provided them the exact source code I was using
  • provided them full access to my VPS with the bots running where the issue outlined in the emails happens all the time
  • provided them a YouTube video link demonstrating the issue and how I reproduce it

 

 


@firemyst

firemyst
25 Sep 2024, 07:01

People would probablyt be more inclined to help you if you used the “insert code block” option and pasted in nicely formatted code instead of what you have.


@firemyst

firemyst
24 Sep 2024, 00:27 ( Updated at: 24 Sep 2024, 05:37 )

And sizes for Renko Charts, Range charts, etc.


@firemyst

firemyst
24 Sep 2024, 00:26 ( Updated at: 24 Sep 2024, 05:37 )

And try to get somewhere close to how they are implemented in ThinkMarkets ThinkTrader as no other platform comes close to the exception way they've implemented their alerts.

They're all cloud-based, and can be set for any indicator and any option (price cross, indicator cross, indicator levels, etc).

I use ThinkTrader solely for this purpose because they're so excellently done, and being cloud based with push notifications (so they work on desktop, mobile, web, etc) it doesn't matter how we're logged into the app - we get notified:

https://www.thinkmarkets.com/au/thinktrader/

 

https://support.thinkmarkets.com/hc/en-gb/articles/11615031550481-How-do-I-set-an-indicator-alarm-on-ThinkTrader-mobile-app

https://support.thinkmarkets.com/hc/en-gb/articles/11614991310865-How-do-I-set-a-price-alarm-on-ThinkTrader-mobile-app

 


@firemyst

firemyst
24 Sep 2024, 00:15 ( Updated at: 24 Sep 2024, 05:37 )

You need to post this in the Suggestions forum. This is technical support, and Spotware doesn't come here to see what users are requesting for new features.

 

https://ctrader.com/forum/suggestions/

 


@firemyst

firemyst
22 Sep 2024, 01:01

You already can. Just create a new alert:


@firemyst

firemyst
18 Sep 2024, 05:47

Could part of your problem is the mdiEma values are based on the calculated values of the MdiSmooth;

But then your MdiSmooth values are based on your mdiEma.

You seem to have an infinite recursion. It's like asking, what came first, the seed or the plant?


@firemyst

firemyst
17 Sep 2024, 00:55 ( Updated at: 17 Sep 2024, 05:17 )

Yes. You can have multiple timers.

https://ctrader.com/forum/cbot-support/24285/

 


@firemyst

firemyst
17 Sep 2024, 00:52

I hope you're not expecting a response and just posting a general statement because you've posted no screen shots, haven't mentioned the time it happened, or anything else.

 


@firemyst

firemyst
13 Sep 2024, 09:51 ( Updated at: 13 Sep 2024, 09:56 )

RE: RE: When a bot was "unexpectedly terminated", cTrader shows the bot as still running

firemyst said: 

PanagiotisCharalampous said: 

Hi firemyst,

I did not write that this does not happen, I wrote that we are not able to reproduce the "unexpectedly terminated" message on our machines on your VPS either. If we cannot reproduce it, then we cannot easily spot the problem. Also we cannot spend unlimited hours waiting for one user's problem to happen again. If you are able to isolate exact steps that will allow us to consistently reproduce this behavior, we are happy to have another look. Else it is a low priority issue and we will fix it if we stumble on it in another occasion. 

Best regards,

Panagiotis


 

I explained how to do it in the video that apparently nobody from Spotware is willing to watch from start to finish.

I also sent them this email, dated August 20th, that I was acknowledged because they responded to it:

 

Proof of the acknowledgment of having received the email. THe “unexpectedly terminated” doesn't always happen, but what DOES always happen is the bots will “lose” their connection to cTrader. I've left the windows open in the VPS showing this. AUDCAD pair. cTrader says the bot is still running, but it's obviously not doing anything because it's no longer logging anything in the “OnTick” event. This is easily reproducible in the steps I've outlined in the above email screen capture. It happened for your team as well – just look at the logs from when they started the bots. They should see several bots are still running, but cTrader “lose” them because they are no longer responding/logging.


@firemyst