Is it possible to increase the grid frequency widget resolution from one digit to 3 digits?
It is measured in 3 digit resolution.
Have you tried creating a custom widget for it?
On mine the default chart is using 2 decimals.
Ok, how did you do this?
On Y resolution it is only possible to enter integers and not 0.1 or 0.01
The widget shows only 0.1Hz resolution, and this is too less to see anything.
Sadly no… Maximum 2 digits.
The logger script that it’s sending info to VRM has something like this defined:
'/Ac/L1/Frequency': {'code': 'g1F', 'whenToLog': 'onIntervalAlways', 'precision': 2},
The same with the battery cell voltages:
'/System/MinCellVoltage': {'code': 'mcV', 'whenToLog': 'onIntervalAlways', 'precision': 2},
Don’t know why they decided to send only 2 decimals instead of 3 for such items that have a small granulation.
Frequency is between +/-3Hz around set grid frequency so you think that’s important the resolution.
The same for cell voltages where 10mV resolution is quite coarse.
Curious might be unique to the EM. Check the frequency widget for the vebus inverter. Thats what I use and it had 2 decimals by default.
In custom ranges you can set the intervals for the chart.
While the numbers will be whole integers the value would render correctly.
So try a manual range or say 49 to 51 with 10 or 20 intervals.
Same in VRM beta.
Ahaaa… Now I get it…
You have a Multiplus, right?
If yes, then the frequency resolution measured by its hardware is 0.128 Hz.
So 0.1Hz steps rounded - if you can say that -, even if software is sending 2 digits.
Although you may have a separate device for metering.
If yes, then - in the light of the above - check it’s reading resolution.
You may try to see it in the dbus-spy, if the representation there mirrors the exact reading and it’s not also rounded.
Question is… next step up or down from 50.008 is ?
For example, for MP2, the steps reported are: …, 49.8208, 49.8488, 50.0768, 50.2048, …
Like I’ve said: 0.128 increments. So roughly, 49.8, 49.9, 50, 50.1, 50.2, etc.
Yes, but did you observed it closely to see values like 50.007, 50.008, 50.009?
In the example given above, you can say that the third digit after the “.” is changing and different each time, but generally speaking, the increment is 0.128, not 0.001.
Yes, just did see in node red 50.002, 50.003 and 50.004, so real 0.001Hz resolution.
How accurate the last digit is, I don’t know.
Would like to see the last 2 (better 3) digits in the widget.
Will Victron look at this issue, or how can I report this issue?
In the new UI debug it shows 0.001 resolution values.
Can the VRM team look why in the widget I only see 0.1 resolution?
Can the VRM team look at the grid frequency widget resolution?
Or is there something I can check/do?
Will the VRM team look at this widget resolution issue?
Is there any update on this issue?
Is the VRM team willing to look and fix this issue?
Is the issue reported at the VRM team, or is there anything I can do myself?
Or what is the way to get in contact with the VRM team?
Silence is just frustrating!!!
I do have a 0.1Hz resolution in the frequency widget, while mine EM540 (one of the advised grid meters) measures in 0.001Hz resolution.
How can I show 0.01Hz or even better 0.001Hz resolution in the wedged?
I only see steps of 0.1Hz (50.1, 50.0 and 49.9), the Y widget scaling doesn’t matter,…
Ok will try tomorrow.
By the way can the VRM team look why the grid frequency in a VRM widget only has a 0.1Hz resolution?
Mine EM540 grid meter measures in 0.001 resolution, can see full resolution in node red and in debug mode (new UI).