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

Hi,
Thank you for the feedback, yes I have experimented with that comms setting if you set it to 1 you get:-
requesting data
requesting data
and so on

which is the same as documented by "senapsys"within http://discourse.weather-watch.com/p/476748

I will see if I can improve the situation and get back to you

I have tested here
it works great
(after initial start up where its a bit slow to get going)
then after the first data has arrived, its synced up and flys along nicely
maybe try updating the silicon labs usb driver you have?

Hi
Thank you for the feedback, I have done a sudo apt-get update and sudo apt-get dist-upgrade, however as you can see by the attachment still having problems. What is my route to doing any form of diagnostics and what data stream should I expect?
The only positive at the moment is another person had the same issue.


Test after update.txt (24.9 KB)

I will check my code and see if I can get it to handle split data better

Hi
Have you a timescale for when you would be able to revisit your code?

Best regards

it certainly is not a widespread problem
have you waited to see if the data gets in sync OK?
since I can not duplicate the problem here is not easy

but I will review the code and see if I can make an improvement that might help and let you know

Thank you for the update, I have left it running for ~5 minutes and the output is as per my post.
what output format should I be seeing?
can you suggest any debugging technique that I can do at my end to help you?

try a new update (vers 17.3)
for raspberry pi3 version
and then in the config.txt
add
Davis timeout=250

and then try making that time out value a different number (e.g start at 0)
(restarting the program each time)
and see if that helps

any news?

hi
I will be working on this over the weekend and get back to you with any feedback

Hi
I have a problem with just launching the new version of the program in that in the past I have been able to try to test out via using:-
cd /home/pi/Desktop/consolewdfiles/
sudo ./consolewd

However I am now getting the following status:-
pi@raspberrypi:~ $ cd /home/pi/Desktop/consolewdfiles/
pi@raspberrypi:~/Desktop/consolewdfiles $ sudo ./consolewd
sudo: ./consolewd: command not found
pi@raspberrypi:~/Desktop/consolewdfiles $

I have also tried out as per your readme but get the same status:-

pi@raspberrypi:~ $ cd /home/pi/Desktop/consolewdfiles/
pi@raspberrypi:~/Desktop/consolewdfiles $ sudo ./GoWdconsole.sh
sudo: ./GoWdconsole.sh: command not found
pi@raspberrypi:~/Desktop/consolewdfiles $

I have reverted back to the previous version and using the same commands as I normally use

cd /home/pi/Desktop/consolewdfiles/
sudo ./consolewd

I am able to get the programme to respond as you’re aware of. Thus what am I overlooking to do correctly?

that problem usually happens when you are running e.g version for rasberry pi2 on rasberry pi3

Thank you, you were spot on.
I have attached a file of the data I am receiving with a timeout of 255. Before I start to alter this parameter as you have asked me to, could you provide me with an example of the data format run that I should be receiving?
Thank you


Test after update.docx (20.9 KB)

Sorry should have said timeout 250

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)