Dallasboy 

Thanks ABCTG! Still think there is something I am not yet thinking about.

Dallasboy,

you are welcome. You can add print statements to your code to check the value your variable has on ever bar.
This should give you some insights into what is going on internally.

Something like this might get you going:

 

Code

Print( DateTimeToString( DateTime ), "; BuyBelow: ", BuyBelow ) ;

Regards,

ABCTG

ABCTG,

Thanks and a great idea...never used this before. So inserted your code in mine and compiled, but not seeing anything new on the charts to check the variable on each bar. BTW I'm using MC.

Thanks!

Edit: I see it now in the output window...is there any way to put that in the data window on the chart? And how to expand the decimals? For exmaple, in the EUR it gives me outputs in 1.14 format, how to get it in 1.14000 ?

Dallasboy,

you would have to plot the values to make them visible in the data window, this won't work with a print.
Using plots is also a good way to make things visible on the chart - even values from a system, just look into the SetPlotValue and GetPlotValue reserved words.

You can find the various print options, including how to add more decimals in the Multicharts wiki.

By the way you can show your appreciation for a post here on Futures.io using the "Thanks" button under it.

Regards,

ABCTG

Hi ABCTG,

So I added this to the signal code:

i_setplotvalue(111, BuyBelow);
i_getplotvalue(111);

But when I try to plot (via a Plot1 function), it gives an error you can't plot from a signal study.

Dallasboy,

it's correct that you can't plot from strategies. That's why you can use i_setplotvalue in the strategy to send a value to an indicator on the same chart. The indicator has to use i_getplotvalue to access the value and you can plot this value then using a regular plot reserved word.
Plotting directly from the strategy will not work unfortunately.

Regards,

ABCTG

ABCTG 

Dallasboy, it's correct that you can't plot from strategies. That's why you can use i_setplotvalue in the strategy to send a value to an indicator on the same chart. The indicator has to use i_getplotvalue to access the value and you can plot this value then using a regular plot reserved word. Plotting directly from the strategy will not work unfortunately. Regards, ABCTG

OK, let me get this straight: I put a random indicator on my chart, and within that script I use the i_getplotvalue to retrieve the value from my signal script and then I can plot it either on the chart or data window?

Any chance on how this code would look like?

Dallasboy,

assuming you have this line added to your signal:

 

Code

i_setplotvalue(111, BuyBelow);

Then a simple one line indicator (simply create a brand new one, name it whatever you like) will do it:

 

Code

Plot1(i_getplotvalue(111), "BuyBelow");

Now you simply have to apply both to the same chart and it should work.

Regards,

ABCTG

Hi ABCTG,

Thanks for the help on plotting values! I'm still trying to figure out why sometimes the code doesn't seem to abide by the rules. Again, the way the buy works is to trigger on the value of BuyBelow which is setup and defined by the higher swing lows (see charts). I have keep IOG true and 1 in 4 or so setups does not trigger. In chart "buyissue", you can see 2 well defined buy setups and executions, with the third not triggering...AND, the BuyBelow value is valid and doesn't change.




So, I did turn off IOG and now trade #3 works (chart "buyissue2"), but IOG shouldn't matter in these trades as they setup 2+ bars after the higher swing (BuyBelow).




Again, thanks for your help and advice!

Dallasboy,

I am afraid one can only guess without going through your code and investing some time in debugging it.

As I have pointed out you can use the I_setplotvalue and I_getplotvalue reserved words to check the values that are used for the entries. You can also use Print statements to analyze situations in the code. Check the actual entry prices that are used for triggering the orders, check that the same order is not used again etc..
This will likely be the road you have to take to track the cause down.

Regards,

ABCTG

ABCTG,

Thanks for all your help. Looks like I found the bug...more to learn ;-)