NexusFi: Find Your Edge


Home Menu

 





Obtain Value area values by code (VPOC, VAH, VAL...) in multichart


Discussion in MultiCharts

Updated
    1. trending_up 4,564 views
    2. thumb_up 5 thanks given
    3. group 8 followers
    1. forum 10 posts
    2. attach_file 3 attachments




 
Search this Thread

Obtain Value area values by code (VPOC, VAH, VAL...) in multichart

  #1 (permalink)
Dvdkite
Trieste Italy
 
Posts: 162 since Feb 2018
Thanks Given: 131
Thanks Received: 25

Hello,

I saw by going to format instrument and volume profile that many values like Vpoc, Vah,Val etc. are avalaible when you activate the Volume option with TPO on a chart.

I made some search here and on google but I didn't find anything that helps me to obtain by code all those value and of course use them in a strategy.

There are some free indicators for this purpose (Like the most appreciated from ABCtrading) but they're all readonly so I cannot use those value in a strategy.

Is there any way to access to Vpoc, Vah,Val etc values built in with Multichart?

Thanks

Reply With Quote

Can you help answer these questions
from other members on NexusFi?
Request for MACD with option to use different MAs for fa …
NinjaTrader
My NT8 Volume Profile Split by Asian/Euro/Open
NinjaTrader
NexusFi Journal Challenge - April 2024
Feedback and Announcements
ZombieSqueeze
Platforms and Indicators
 
Best Threads (Most Thanked)
in the last 7 days on NexusFi
Retail Trading As An Industry
58 thanks
Battlestations: Show us your trading desks!
48 thanks
NexusFi site changelog and issues/problem reporting
47 thanks
GFIs1 1 DAX trade per day journal
32 thanks
What percentage per day is possible? [Poll]
31 thanks

  #2 (permalink)
 ABCTG   is a Vendor
 
Posts: 2,431 since Apr 2013
Thanks Given: 481
Thanks Received: 1,623

David,

thank you for your feedback. The value area indicator comes with a function to provide you with the values and documentation on how to call it in your own strategy or indicator.

Apart from that the volume profile information can only be accessed in MC.NET, but not in regular MC unfortunately. The TPO values are accessible in both platforms and you can find a description of the reserved words here: https://www.multicharts.com/discussion/viewtopic.php?t=51318

Regards,

ABCTG

Follow me on Twitter Reply With Quote
The following user says Thank You to ABCTG for this post:
  #3 (permalink)
Dvdkite
Trieste Italy
 
Posts: 162 since Feb 2018
Thanks Given: 131
Thanks Received: 25



ABCTG View Post
David,

thank you for your feedback. The value area indicator comes with a function to provide you with the values and documentation on how to call it in your own strategy or indicator.

Apart from that the volume profile information can only be accessed in MC.NET, but not in regular MC unfortunately. The TPO values are accessible in both platforms and you can find a description of the reserved words here: https://www.multicharts.com/discussion/viewtopic.php?t=51318

Regards,

ABCTG


Hello ABCTG,

as always thanks for your prompt answer. I don't know why I didn't pay attention to your DEMO function...you're right, I saw that's very easy to obtain all the values using your ABC_ValueAreas function.

As I'm new to the use of the Value areas and as I know the calculation should be made during the cash market hours... something like 9:00 to 17:30 here in europe.... in your ABC_ValueAreaPlots you use 9:30 to 16:15...
I know that choices are individual but based on your experience what is the best hour interval to set?

Also I noticed one thing that I cannot figure out. When I apply the Value are DEMO to the dax for example it calculate the same values as in the ABC_ValueAreaPlots, but even if the value numbers are the same the plots are made in a different price level... Am I missing something? Is this a MC bug?

This is the CORRECT ABC_ValueAreaPlots on dax (all correct) :



and this is the DEMO function with plot1 to plot6 enabled:



Can you see that for example the TPOVALo is 12567,50 (in data window) but on the chart I see it at 12500 ???


Here you have BOTH indicators on the same chart ..




Regards,

David

Reply With Quote
The following user says Thank You to Dvdkite for this post:
  #4 (permalink)
 ABCTG   is a Vendor
 
Posts: 2,431 since Apr 2013
Thanks Given: 481
Thanks Received: 1,623

David,

you likely have scaled the indicators differently. Make sure that you set both to be scaled the same as the symbol.

The default settings are just the ES floor session in NY times.

Regards,

ABCTG

Follow me on Twitter Reply With Quote
The following user says Thank You to ABCTG for this post:
  #5 (permalink)
Dvdkite
Trieste Italy
 
Posts: 162 since Feb 2018
Thanks Given: 131
Thanks Received: 25


ABCTG View Post
David,

you likely have scaled the indicators differently. Make sure that you set both to be scaled the same as the symbol.

The default settings are just the ES floor session in NY times.

Regards,

ABCTG

Hello again,

I checked the scaling ... honestly I was just browsing all the available options and when pressed ok and closed the format indicator window levels are now correct... I don't even know How I made that eheh

anyway thanks again.

Regards,

David

Reply With Quote
  #6 (permalink)
Dvdkite
Trieste Italy
 
Posts: 162 since Feb 2018
Thanks Given: 131
Thanks Received: 25


ABCTG View Post
David,

thank you for your feedback. The value area indicator comes with a function to provide you with the values and documentation on how to call it in your own strategy or indicator.https://www.multicharts.com/discussion/viewtopic.php?t=51318

Regards,

ABCTG

Hello ABCTG,

I have a quick question related to the function ABC_ValueAreas.

First of all I succesfully used it inside my signal applied to the FDAX and now I'm trying to set up the strategy to work on the minidax (as I usual do).

So I added FDXM (minidax) on the chart as DATA1 and the FDAX as DATA2. I've added inside the signal "of data2" in every part of code in order to generate signals using the data2 (FDAX) datafeed.

After do that I realized that oDevelopingTPOVAHigh and oDevelopingTPOVALow are calculated on data1 .... and there's no way to keep calculate them on data 2 is it correct?

Of course the values of oDevelopingTPOVAHigh and oDevelopingTPOVALow for the minidax will be similar to the FDAX but I think that trigger signals directly from the FDAX and execute it pn minidax is a better solution...
it seems to work on back test anyway but it need more test for sure to made a comparison with the same strategy simply applied on the big DAX.

Thanks

Reply With Quote
  #7 (permalink)
 ABCTG   is a Vendor
 
Posts: 2,431 since Apr 2013
Thanks Given: 481
Thanks Received: 1,623

David,

you can tie variables and functions to specific data streams. With that you can accomplish what you have in mind.
You can find some examples and further documentation in the FAQs:
https://www.multicharts.com/discussion/viewtopic.php?t=6929

Regards,

ABCTG

Follow me on Twitter Reply With Quote
The following user says Thank You to ABCTG for this post:
  #8 (permalink)
Dvdkite
Trieste Italy
 
Posts: 162 since Feb 2018
Thanks Given: 131
Thanks Received: 25


ABCTG View Post
David,

you can tie variables and functions to specific data streams. With that you can accomplish what you have in mind.
You can find some examples and further documentation in the FAQs:
https://www.multicharts.com/discussion/viewtopic.php?t=6929

Regards,

ABCTG

I know it was possibile and after saw the link that you provided above I think I was missing that I have to DECLARE the variables as data2 , it seems that doing something like this

 
Code
	

        oDevelopingTPOVAHigh			( 0 , data2 ),	
	oDevelopingTPOVALow			( 0 , data2 ),
should solve the problem.

Thank you!

Regards,

David

EDIT OF THE EVENING: (I would like to complete the answer)

 
Code
I discovered that also "data2" after the function is needed :

FunctionValue = ABC_ValueAreas( StartTime, EndTime, CalcMondayToFridayOnly, ProfileTimeInterval, VolumeVAPercentage, TPOVAPercentage, DynArraySize,
			    oDevelopingVolVAHigh, oDevelopingVolPOC, oDevelopingVolVALow, oDevelopingTPOVAHigh, oDevelopingTPOPOC, 	
		 	    oDevelopingTPOVALow, oYesterdaysVolVAHigh, oYesterdaysVolPOC, oYesterdaysVolVALow, oYesterdaysTPOVAHigh,
			    oYesterdaysTPOPOC, oYesterdaysTPOVALow )data2;
with this it is working correclty now.

Reply With Quote
  #9 (permalink)
 ABCTG   is a Vendor
 
Posts: 2,431 since Apr 2013
Thanks Given: 481
Thanks Received: 1,623

David,

you should also tie the function to the data stream that you want it computed on.

Regards,

ABCTG

Follow me on Twitter Reply With Quote
The following user says Thank You to ABCTG for this post:
  #10 (permalink)
Dvdkite
Trieste Italy
 
Posts: 162 since Feb 2018
Thanks Given: 131
Thanks Received: 25



ABCTG View Post
David,

you should also tie the function to the data stream that you want it computed on.

Regards,

ABCTG

I just saw now this ... I came up to this conclusion and edited my previous reply because I didn't see your last reply 😅😅

Thanks,

Reply With Quote





Last Updated on June 18, 2021


© 2024 NexusFi™, s.a., All Rights Reserved.
Av Ricardo J. Alfaro, Century Tower, Panama City, Panama, Ph: +507 833-9432 (Panama and Intl), +1 888-312-3001 (USA and Canada)
All information is for educational use only and is not investment advice. There is a substantial risk of loss in trading commodity futures, stocks, options and foreign exchange products. Past performance is not indicative of future results.
About Us - Contact Us - Site Rules, Acceptable Use, and Terms and Conditions - Privacy Policy - Downloads - Top
no new posts