Data output issue using Raspberrypi v3 B+ and ConsoleWD issue 17.3

you should see a data count of 99 and so then no split out to a smaller count and then you should see the converted to actual data output after that
there are threads in the actual linux section of the forum with outputs of what it should look like

Hi

Sorry, but to me, your answer is too vague.

As far as your reference to the linux section, could you point me to the example you are referring to or provided a search team?

Thank you for your time in trying to resolve the problem.

Best Regards

there is a linux section here on this forum
and there are lots of threads
including some recent ones where people have shown the data output (i.e what it should look like)
you should not be seeing a number less than 99 and splitting out into a smaller number (received number)

not sure how I can make that any clearer

Hi
Am I presuming this is the correct data I should be receiving? http://discourse.weather-watch.com/p/503855

I have as suggested tried the timeout parameter using different values 0 produced “segmentation fault”

30,50,100,150 did not show the correct output format just like 250 reported in my previous post

yes, that is what you should be seeing
and yes, that is the sort of time out values to try, but also try bigger values (e.g 500)
(make sure to restart after making that change and also make sure to check that that value is picked up in the start up messages)

Hi
I have carried out your suggestion even up to 1000.
as you can see below your programme does see the value
pi@raspberrypi:~ $ cd /home/pi/Desktop/consolewdfiles/
pi@raspberrypi:~/Desktop/consolewdfiles $ sudo ./consolewd
Station type raw=31<
Station type =31
Weather station type is a Davis VP
meteobridge user= <
meteobridge ip= 192.168.0.1<
meteobridge pass= <
Davis com method d
Davis time out 500
Davis time out allocated OK
OWW file location= ←
program location= /home/pi/Desktop/consolewdfiles/<-
Davis VP IP data logger port= 22222<
Davis VP IP data logger IP= 192.168.2.3<-
Latitude= 51.3
Longitude= 0.3
Station name =My station
Daily rain startup= 0.0
start up month rain found=0.0<-
Monthly rain startup= 0.0
Yearly rain startup= 0.0
wunderground username =
wunderground password =
wunderground utc =-1
Dir offset= 0
Barooffset= 0.0
Comport is USB to serial
Davis com method d
Yes Revb Davis VP
Davis rain gauge 0.2mm
mysql username =
mysql server =
mysql databasename =
mysql tablename =
Will do mysql metric
mysql time interval = 300
cwop station id =
cwop call sign = -1 // -1 is default (you do not have a Ham call si
cwop latitude=
cwop longitude=
FTP server = =166
FTP username =
FTP port = 21
FTPremote dir =
Will do ftp passive
remote file =
FTP time interval = 60
wu =Y
Will save logfile
logfile metric
Custom file name = wx.html
Custom file name 2=
Custom file name 3=
Custom file name 4=
Custom file name 5=
Tag units in celsius
wind units = mph
baro metric= Y
rain metric= Y
Will run cron files
Custom log out = customlogout.txt
temp offset raw = <
hum offset raw =<
wmr300 channel =1
Modified rain gauge= <
WOW id=<-
WOW pass=<-
PWS id=<-
PWS pass=<-
windfinder id=<-
windfinder pass=<-
meteotemplatepass=<-
meteotemplateurl=<-
univeral update rate 2
utc hour=19
local hour=19
Weather Display vers WD_console_17.3
If use this program,then please consider sending a PayPal donation to [email protected] (Brian Hamilton)
to help with costs, and support, thanks!
www.weather-display.com
Comport /dev/ttyUSB0 opened
setting baud rate to 19200 ->0
ser_read error Resource temporarily unavailable
ser_read error Resource temporarily unavailable
ser_read error Resource temporarily unavailable
waking VP
*****Received count = -----------------------------> 77
requesting data
*****Received count = -----------------------------> 63

You get the purse
then data format as reported in previous posts

so is it worse or better when you change the time out value?

Hi
So you can draw your own conclusions I have attached some examples of the outputs I have been receiving, the examples cover 700,650,600,500,450 &50 timeout counts.

Best regards


Count results examples.docx (33.6 KB)

it looks the same
what I need to do then is try to merge the split data arrival

Yes, that was my view but as you are the expert you may have had a different view on seeing the data.

Thank you for your continuing support

one thing, this time out variable is only used when you have set in the config.txt file
Davis com method=2
what do you have that set as?

oh
I just realised I was setting the time out wrong in the code
and so that is why it made no difference

use a new update, vers 17.4
from the download page, for raspberry pi 3
and then set the Davis timout as 1 to start off with and then go up from there (milliseconds)

if you need the raspberry pi2 version, let me know

Hi again
updated as you can see via the attached. With a delay of 1 the output looked the same as before, for delays of 10 and 20 you will be able to see what I received.


Feedback.docx (19.6 KB)

the higher value (ie 20) made things worse
so it looks like the data read time out is not helping
so I need to look at managing a data split next instead

try another download update
no gaurantee will work, as I can duplicate the issue you are having here

I managed to duplicate the problem and resolve it
with vers 17.4 (pi 3)
download that new update

Hi
sorry, I have not got back but been away I will rerun with updated version over the weekend and get back to you.

Best Regards

it should be better I think you will find (make sure revb is set (I assume its a revb data logger?))

Hi
It’s looking good; my only observations at the moment are that the first record that was logged in Att 1 52018lg file seems to be corrupted and due to anomalies regarding the way the *Received count is displayed i.e. at 17:05:22 and 17:05:23 v two counts loggings at 17:06:08 and 17:06:10, I have provided attachment 2 Test Data, so I can confirm with you that the data format is as you would have expected.

Could you help with the following questions please.

Using this data and a Raspberry Pi version 3 have you produced a graphical interface so it can be displayed in a more friendly way?

The time stamp is incorrect both hours


Attachments.zip (28.2 KB)

re the graphical interface
yes
double click on the wdpi program
and make sure consolewd is set to create the clientraw.txt file