Incorrect loading Data box "Wind-gust max today" ** Closed **

Hi, in the “Wind-Gust Max Today” box gives me incorrect wind values, I don’t understand why.
I verified with those of the station they are completely incorrect.
Perhaps it is charging the values from the Wu files or I missed some configuration.
How can I do to solve?

Thank you.

Regards.

Could you please post the link to your website?
Nobody here on the forum is clairvoyant.

Thanks

Yes of course it’s always the usual for now: http://max-weather-it.byethost24.com/pwsWD/
As you can see the data from the “Wind-gust max today” box in the attached image the data is incorrect compared to the actual ones.
You can see the direct data of the station: MaxMeteo-Frutti - Weathercloud | Global network of weather stations

How can this solve this?

Thank you.


Image.jpg

Please do something on your attitude and especially on choice of words.
The people on this forum are here to help and learn.
Do you really think you can ask incomplete questions and let others do all the work?
First you should read and investigate yourself.
Try to find the solution, reading other persons questions. Visiting sites of other persons.

And when you can not find it yourself: YOU have to supply all possible information.
Every time before posting, you should ask yourself: what information is needed to let others give an answer.

I am not going to browse your more then a dozen or so posts to try to find the address of your current website. No way Sir.

===

As explained before, a wealth of information is available on this forum.

There is that topic I pointed you to: No High/Lows, where is history and graphs data used for, and ? cron ?
There are readme’s f.i. this pdf: https://pwsdashboard.com/documentation2012/11_cron.pdf
There were two large warnings presented to you when you entered your settings

[center]

IMPORTANT

The Dashboard needs a lot of data, which is mostly not available from your weather-program.
After you entered and saved all your settings please take ample time to read the 1 page document about “Cron-jobs” at the pwsdashboard.com website.

Using a cron-job will give far better response times, prohibit outdated information and will make sure that missing high-low data is calculated.
The cron will also facilitates optional uploading to other networks and having more detailed historical data.

[/center]

sorry was not reported as well as you already knew why I had written another post but it was understood in the sense that I still couldn’t change servers are still stopped on that it was in the sense unfortunately the link and always the same as before as the faulty one Not working, perhaps the translation did not understand the sarcastic ironic value of the phrase … it was not intended for your request request more information. Translations are too literary and misunderstandable unfortunately.
I will try to avoid other misunderstandings.

I hope I have clarified the issue of language that was not my intention to use, I would like to return to the data problem.
I was temporarily performing the handconjob by hand “/PWSWD/PWS_CRON_STATIONCRON.PHP” Thus thinking of recharging data.
However the problem is not that it does not charge the daily data that certainly does not do it because I was missing there I arrived there, but when he loads them, manually, they are wrong, but only those of the wind not those temperature.
Now I have not well understood their operation, but it seems like it is misinterpreting the data downloaded from the Wu server.
Also because I tried to edit data by hand with “/PWS_HIST_UPDATE.PHP?PW=XXXXXX” and these properly save them, though when raising the file /pws_cron_stationcron.php puts the wrong data.
What should I check or check to correct error?
Can they be given under folder / chartswudata /?
Is there any test I can do or file to check to make a cross-checking data?
Do you need some data files like “History” or other Wu data to check if there is a error or not?

Thank you.

Your clientraw weather-file is, as warned by others, incomplete. And those files only have today high-lows.

You are not running a 5 minute cron so there is no history-file kept up-to-date
==> no period high-lows available there.

Result:
Neither your weather-program nor the history has correct high-low values for month and year.
==> You can not use the small blocks with 3 high-low values. As simple as that. No discussion, no other ways.


You can use the samll blocks, BUT change the small blocks to show todays high-values, those values will be used from the clientraw.
Set line 4 in wind_c_small.php and in temp_c_small.php block to comment by adding a # on the first position.

#$my_choice      = 'multi';              // day / month / year

Now lets make an agrement.

  1. First you should upload correct data to your website.
  2. If you want extra high-lows
    => you should run the cron every 5 minutes, that will take some time if you have no experience.
    ==> there are free external cron-servers you could have used already for your current website.
    ===> so please read the documentation.

If those 2 points are OK, then and only then you start asking questions again.

I did all operations only that the site cronjob does not allow me uploads every 5 minutes but I can select minimum execution 1 hour.

  1. I have discovered that if you delete the “History TXT” file then they re-appear the /PWS_CRON_STATIONCRON.php the data is loaded correctly.
    But if you start /PWS_HIST_RECREATE.PHP?PW=XXXXXX and then restart /PWS_CRON_STATIONCRON.PHP The data returns incorrect. So the problem and reading Wu data.

  2. If I use method “Save the Daily Data for the Charts” everything is ok.

  3. I also noticed another thing, using data loading method “clientraw.txt” provided by Foshkplugin also generates incorrect values ​​in historians.
    Using loading from Ecowitt Direct update of historians takes place correctly.

So the problem was in the data loading file in real time.
Evidently the file generated by Foshkplugin “clientraw.txt” must have something that does not like the “wind_c_small.php” script.

I will continue to take trials, thanks.

Regards.

Hi!

Evidently the file generated by Foshkplugin "clientraw.txt" must have something that does not like the "wind_c_small.php" script.
As already mentioned, the clientraw.txt generated by FOSHKplugin does not contain all the fields that are normally present.

I don’t know which fields PWSDashboard is accessing exactly, but the hourly values for min / max wind speed (fields 51…70 and 80…89) are NOT contained in the file generated by the FOSHKplugin.
This is simply due to the fact that these values are not calculated by FOSHKplugin.

The other wind speed-specific fields are actually set correctly by FOSHKplugin. However, there can also be a conversion error - the speeds in knots are expected there.
Wim, can you quickly tell from which fields you are pulling the data?

@Maximux:
If you have the opportunity to use the Ecowitt format directly, you should do that! No other format gives you access to all of your measured values.

Regards, Oliver

The clientraw fields which are generated by FOSHKplugin are correct.
I always check new clientraws with the clientraw parser Clientraw - Script developers info
That script is maintained since 2008. When Brian Hamilton adds new fields those are added as soon as a new clientraw is available.
=> no problem with the FOSHKplugin , the windspeed was in kts as it should be.

. . . . . .

The history file uses the default UOM’s as set in easyweather. Not the UOM’s as used in the file.
=> If there is a problem I can be contacted directly and will check a.s.a.p. as this is a “kernel” part of the dashboard.

As the OP is doing all kind of tests I re-checked this morning what could cause wrong data in the history.

  1. No roll-over just after midnight when todays high-lows are cleared, yesterday is filled a.s.o. ==> 99% that this was the case
  2. Switching to another UOM in the easyweather settings and not deleting the history.
    => The scripts then use the history data generated for the old UOM as using the new UOM. Switching km/h ↔ m/s is an 3.6* error

@all When you are changing a default UOM:
=> make a print / pdf, delete history,
==> recalculate the values and insert in the history with the history update script
==> or regenerate the history if valid WU data is available.

@all Use the debug console . . ./pwsWD/PWS_module_test.php when there are problems with data or scripts.
You can test all blocks/popups and read all uploaded file-contents in a “human-readable” way .
I attach a screenshot of how you can inspect which fields are used from the uploaded file example of a clientraw file.

Wim


Mine wanted to be just a statement a clarification, to indicate the relative problem you have historical values, that clientrawtxt file can be used in some cases, the data is well detected in almost all its program functions except the historical values of the checked boxes from “WIND_C_SMALL.PHP” that misunderstands some data reported in the file.
I have only found that using ClientWTXT from incorrect values while Ecowitt file no.
I did test with /pws_module_test.php and here values that marks in the historic box there are no.
On the Test screen of the ClientRaw file is all correct. Perhaps it would be a united united problem K-nodes, km, miles etc. Use in files.
So it may be that those values are different perhaps because they are displayed in a different measurement unit … it may be, I don’t know …
However the thing imported and that you are understood that the problem of the box in question was in the fact that I used the clientraw file.