Hello Veeresh,

Thank you for your post(s).

I have been investigating into this issue, and it appears that this is being caused by the lack of a data context existing on the XamRadialGauge. The binding errors are not showing in the Visual Studio output window on my end, likely because the XamRadialGauges exist in a separate project file, but if you add the following line of code just after the InitializeComponent() call in your TileControl control's code-behind, it appears that all of the gauges are rendered correctly.

InitializeComponent();
this.DataContext = new TileControlViewModel();

Doing this allows the bindings on your XamRadialGauges to resolve correctly and allows the gauges to render.

At the moment, I am rather unsure why WPF will seemingly only allow 20 gauges to render, to be honest. I have also a sample project of my own that is based upon yours, in which if the values that are bound in your project are hard-coded, the first 20 gauges render correctly, and the rest of them will not render until the page resizes and WPF forces the controls to redraw. Even stranger, the page appears to need to resize horizontally for this to happen. However, if these are bound to a data context's source property, then all of them appear to render correctly.