Hopelessly confused by TDesk or Desky? Ask here.

[SteveHopwood]

Still here pulling the hairs from my shaved head. I re-downloaded and re-installed fresh Experts. And after clearing the variables again Desky and Tdesk talked but as you can see in the photo it did not complete the transaction as there should have been more trades because the max signal time for desky being set to 5 minutes at the time of this particular snippet. Could it be a server/Empty4 issue rather than the a tdesk/desky issue?

V/r,
Osito

I repeat what I have often written and is clearly stated in the Desky user guide. The largely ignored counter trend trading thingy apart, Desky takes no trading decisions. He reacts only to those signals sent by TDesk

Your Desky isn't taking trades you think he should be? That is because you have TDesk set up incorrectly for your purposes.

TDesk ain't easy. For sure, I do not understand him. I could code Desky because all I needed to do was have him react to signals generated by TDesk.

Try starting with something simple that causes TDesk to generate signals that Desky can respond to - then move out from there. And stick this into your mental cranium until you understand it: Desky will do what TDesk tells him to do. How you get to what TDesk tells Desky to do is down to you.

[tomele]

Still here pulling the hairs from my shaved head. I re-downloaded and re-installed fresh Experts. And after clearing the variables again Desky and Tdesk talked but as you can see in the photo it did not complete the transaction as there should have been more trades because the max signal time for desky being set to 5 minutes at the time of this particular snippet. Could it be a server/Empty4 issue rather than the a tdesk/desky issue?

V/r,
Osito

Hi Osito.

Before I set up a new terminal with your setup, I would be interested in seeing a Desky screenshot.

Stay well
Thomas

[tomele]

Other note:
My UBDs as well as others I have used from the site won't ignoreOpencandle for the life of me unless I have the indicator set to "price_close". I personally like to use other price options but only want the information updated on Tdesk at the close of the candle because Desky will close the trade immediately regardless of check in time. At lease that's my experience. Is that normal for all or am I just assed up all over?

I must admit that I don't understand what you are saying. Do you talk about the price (type) inputs like LONG_Operand_1_Price? They are only relevant if your operand type is "price series" as stated in the "manual" thread: "If the type of operand on the left side of the comparison is PriceSeries, specify the price series to use or "Void" if you don't use prices here". This has nothing to do with custom indicators and I cant see from my code how this input could in any way alter the results of icustom calls.

If I misunderstand you, pleasse explain a bit more.

Stay well.
Thomas

[freakyg415]

Still here pulling the hairs from my shaved head. I re-downloaded and re-installed fresh Experts. And after clearing the variables again Desky and Tdesk talked but as you can see in the photo it did not complete the transaction as there should have been more trades because the max signal time for desky being set to 5 minutes at the time of this particular snippet. Could it be a server/Empty4 issue rather than the a tdesk/desky issue?

V/r,
Osito

I repeat what I have often written and is clearly stated in the Desky user guide. The largely ignored counter trend trading thingy apart, Desky takes no trading decisions. He reacts only to those signals sent by TDesk

Your Desky isn't taking trades you think he should be? That is because you have TDesk set up incorrectly for your purposes.

TDesk ain't easy. For sure, I do not understand him. I could code Desky because all I needed to do was have him react to signals generated by TDesk.

Try starting with something simple that causes TDesk to generate signals that Desky can respond to - then move out from there. And stick this into your mental cranium until you understand it: Desky will do what TDesk tells him to do. How you get to what TDesk tells Desky to do is down to you.

Big Pippin to all. I was hoping I wouldn't get your attention Steve but knowing that Desky is your baby I expected to read those words lol. Maybe I didn't explain my case clearly enough. I read that manual and have been all through this site reading your comments pillaging people who don't know that Desky only follows directions. I took note of that my first few days on the site My set up is simple both indis align take a trade, when they align the other way exit and trade the other way. I thought it was cake and have been racking my head trying to find out my issues. So today I ran two more tests using the exact same set-ups, One works (for now(, and the other is still tradeless, pitcures attached. The only difference... :youknow: THE BROKER. Who would have though. My instructions for Desky and Tdesk were legit and the issues i was having were intermittent with my original broker until i found the magic pill of the moment to get it to work. So for anyone out there having issues such as mine, granted, i'm sure i'm the only lame on here with the issue. Try switching brokers. I was using AAFX Trading, now I am using Trader'sWay and so far so good with Tdesk and Desky communicating.

Steve thanks for taking the time to respond. This site ROCKS

V/r
Osito

[freakyg415]

Other note:
My UBDs as well as others I have used from the site won't ignoreOpencandle for the life of me unless I have the indicator set to "price_close". I personally like to use other price options but only want the information updated on Tdesk at the close of the candle because Desky will close the trade immediately regardless of check in time. At lease that's my experience. Is that normal for all or am I just assed up all over?

I must admit that I don't understand what you are saying. Do you talk about the price (type) inputs like LONG_Operand_1_Price? They are only relevant if your operand type is "price series" as stated in the "manual" thread: "If the type of operand on the left side of the comparison is PriceSeries, specify the price series to use or "Void" if you don't use prices here". This has nothing to do with custom indicators and I cant see from my code how this input could in any way alter the results of icustom calls.

If I misunderstand you, pleasse explain a bit more.

Stay well.
Thomas

Thomas,

Good day to you my good sir. There are screenshots in the response to Steve above this one. I'm pretty sure the issue was with the broker's version of empty4 due to the fact that it is now working on Trader'sWays' platform. You can check of course and let me know if you find any deficies otherwise i'll just keep on trucking. The UBD issue however I haven't revisited because I left for the day. I understand how to set up the UBDs the issue when talking about price was the actual indicator applying its calculations to price close, typical, open, etc. I had first assumed that this was irrelevent because UBD is a seperate function in itself of the actual calculations of the indicator. It simply acts as a conduit in order to send the signals to Tdesk. But when I would edit the indicator code and utilize price_close instead of any other calculation method I would get better results. I tested this out from both watching the screen change and orders closing at 6:08 pm when Desky was doing check ins at the close of 30min candles... That didn't add up of course. So I used the UBD refresh time as a work around and just timed the refresh seconds so that they were close enough to the actual candle close. But I'm assuming how they were working on my platform was not the correct way and until I confirm that the issues are gone with Trader'sWay's Empty4 platform I don't know what the issue was. But all of my indicators did this. All updated whenever they wanted. Thanks for your time Thomas.

V/r
Osito

[freakyg415]

Good day to all. I have two last questions for the forum that should shut me up for quite some time so Steve please forgive me for my ignorance once again. My first question is with Desky:
My Entry Signals are opposite of my Exit signals. So knowing that you can close and open at the same time. What is the fastest way to get back in. Setting desky to 1 min with 1 min max signal has been doing double entries, I'm guessing because there is seconds left or something. I probably sound like an idiot lol. But you don't know what you don't know. I am currently using 5m checkins with 5 min max age as a work around
My Second is in reference to Tdesk:
I've been in Tdesk trying to get fancy and Set up re entry signals within the current trade. By doing so I have two indicators that would need to go the opposite direction and return to the the trade direction in order to re enter. So I have both of those on the Veto on Disagree Signals and set to "all" To my understanding for a re entry the trade has to go flat and return. Trying to think through the logic once one of the two indicators return to trade side the trade is again valid, even though I would need both to return. I thought that all rentry signals would require the 100 solo entry signal just like the regular entry however that has not been my experience thus far. Is there a way to accomplish this or am I chasing my own tail here? Maybe a reset on Veto option could be added in the future? Thanks for your time.

V/r
Osito :hi:

[tomele]

I've been in Tdesk trying to get fancy and Set up re entry signals within the current trade. By doing so I have two indicators that would need to go the opposite direction and return to the the trade direction in order to re enter. So I have both of those on the Veto on Disagree Signals and set to "all" To my understanding for a re entry the trade has to go flat and return. Trying to think through the logic once one of the two indicators return to trade side the trade is again valid, even though I would need both to return. I thought that all rentry signals would require the 100 solo entry signal just like the regular entry however that has not been my experience thus far. Is there a way to accomplish this or am I chasing my own tail here? Maybe a reset on Veto option could be added in the future? Thanks for your time.

Hi Osito.

I understand what you want to accomplish - a different logic for entering and exiting the VETO state. I don't think I will go that route. There are too many ideas to further complicate TDesk's signal processing and I like it as it is.

Another project in my pipeline might come to your rescue though. I am planning to provide a framework that will make it VERY easy for those with at least a minimum of coding knowledge to create their own TDesk indicators. The framework will even enable to combine existing indicators into a single signal having its own logic. This should exactly solve your problem.

So if you are not already in the group mentioned, time to start learning some basic MQL ...

Stay well
Thomas

[freakyg415]

I've been in Tdesk trying to get fancy and Set up re entry signals within the current trade. By doing so I have two indicators that would need to go the opposite direction and return to the the trade direction in order to re enter. So I have both of those on the Veto on Disagree Signals and set to "all" To my understanding for a re entry the trade has to go flat and return. Trying to think through the logic once one of the two indicators return to trade side the trade is again valid, even though I would need both to return. I thought that all rentry signals would require the 100 solo entry signal just like the regular entry however that has not been my experience thus far. Is there a way to accomplish this or am I chasing my own tail here? Maybe a reset on Veto option could be added in the future? Thanks for your time.

Hi Osito.

I understand what you want to accomplish - a different logic for entering and exiting the VETO state. I don't think I will go that route. There are too many ideas to further complicate TDesk's signal processing and I like it as it is.

Another project in my pipeline might come to your rescue though. I am planning to provide a framework that will make it VERY easy for those with at least a minimum of coding knowledge to create their own TDesk indicators. The framework will even enable to combine existing indicators into a single signal having its own logic. This should exactly solve your problem.

So if you are not already in the group mentioned, time to start learning some basic MQL ...

Stay well
Thomas

Hey Thomas,

Tracking all. Glad to know I wasn't going crazy trying to accomplish the impossible and failing lol. In the meantime, I'll try to adjust the indicator to show what I need in one swoop. Then I can use one indicator as the veto and get re entryies. Your project should be awesome to those of us who aren't legit with mql4. I'm familiar with pinescript and it's similar ... sometimes. But they are definitely not the same. Either way, I'll get her done. I'm not one who like to wait so i'll get crackin on that and try to fix my own issues. Thanks for your time. Happy Holidays from the US.

V/r
Osito :hi:

[RMSSC]

Good Morning,

I really need your help, the new implementation of the trailing stop in conjunction with break even, in my case it is not working as I expected, I am probably doing something wrong which is the most certain because I doubt there are any code errors.
In the images below shows how I have configured it.
What I imagined this configuration to do was the following:
1º Reaching a profit of 40 pips, a stop loss of 30 pips is created by the break even, which in fact does so in an exemplary manner;
2nd When creating the 30 pips stop loss and reaching 40 pips or higher the trailing stop starts to follow the price at a distance of 15 pips increasing the stop loss, I am not getting this done, except in some trades , but for most it didn't
So I asked a charitable soul to elude me because for weeks I have tried to change the settings and I have not been successful.

Now I have a question for Thomas, on tdesk the news report has stopped appearing, will it be a problem on my part? It had never happened to me and this happens to me on all active platforms.

Cheers,
RMSSC :hi:

[RMSSC]

Good Morning,

I really need your help, the new implementation of the trailing stop in conjunction with break even, in my case it is not working as I expected, I am probably doing something wrong which is the most certain because I doubt there are any code errors.
In the images below shows how I have configured it.
What I imagined this configuration to do was the following:
1º Reaching a profit of 40 pips, a stop loss of 30 pips is created by the break even, which in fact does so in an exemplary manner;
2nd When creating the 30 pips stop loss and reaching 40 pips or higher the trailing stop starts to follow the price at a distance of 15 pips increasing the stop loss, I am not getting this done, except in some trades , but for most it didn't
So I asked a charitable soul to elude me because for weeks I have tried to change the settings and I have not been successful.

Now I have a question for Thomas, on tdesk the news report has stopped appearing, will it be a problem on my part? It had never happened to me and this happens to me on all active platforms.

Cheers,
RMSSC :hi:

Is there a kind soul who can help me with this problem?
I would really appreciate it, because all the attempts I made, I was unable to come up with any solution .
It is true that I am doing something wrong.
Cheers,
RMSSC :hi: