CWOP OK from WD on desktop but not OK from consolewd

Hello Experts

the CWOP update works from the desktop computer WD software, this is the raw data:

EW3457>APRS,TCPXX*,qAX,CWOP-4:@221757z4650.97N/00734.37E_045/000g000t077r000p000P000b10263h51.WD 10
EW3457>APRS,TCPXX*,qAX,CWOP-4:@221758z4650.97N/00734.37E_045/000g000t077r000p000P000b10263h51.WD 10

http://www.findu.com/cgi-bin/wx.cgi?call=EW3457

but the raspberry PI is sending it in a different format which doesn’t goes through
the raw data from raspberry pi`s consolewd looks like this:

irox read -1
status 0
cwop sending EW3457>APRS,TCPIP*:@221822z4650.97N/00734.37E_045/000g000t076r000p000P000b10263h52.WD 59
irox read -1
status 0
irox read -1

Checking the ethernet interface on the raspberry pi with WireShark, I see only a dns query towards CWOP.

Any idea what I should do to fix the update towards CWOP from Raspberry Pi - consolewd?

Many thanks

Not sure what the current status is with the CWOP servers, but they mentioned on the listserv that “TCPXX*, qAX.” should actually be “TCPIP*”. Last I heard not all their servers were requiring this change, so depending on what server you connect to in the rotation might explain why your data is not showing up.

Norcaldan,thats not the problem

because the info posted above shows consolewd is sending as TCPIP

(the raw data posted for the desktop version is how it looks like once it gets to the servers…its not sent like that)

or it could be that its not connecting correctly to the cwop servers
I will do some testing here

Thank you Brian, I am waiting for your test result on this. I am running your latest consolewd on my Raspberry Pi.

do you happen to be using a call sign in the windows version?

ps, I did test initially for CWOP and it worked OK
how do you have the CWOP settings set in the config.txt?
e.g server, port, etc?

oohh, then It is my mistake, as I don’t have any server and port set in the config.txt.

Here is what I have in the config.txt that relates to CWOP:

Do CWOP updates=Y //every 10 minutes
CWOP station id=EW3457
CWOP ham call sign=-1 // -1 is default (you do not have a Ham call sign)
CWOP Latitude=4650.97N
CWOP Longitude=00734.37E

I thought these CWOP settings were enough to make it work. How and what should I specify for the server and port here in the config.txt?

By the way I also have a hamradio callsign, so I am interested to use that for CWOP as well.

Many thanks

my bad…I thought there was settings for that…
I will add some debug code to the croncwop program

so we can see what is happening /not happening on your setup

OK, no problem at all, please just let me know when I can test your update on CWOP with Raspberry Pi. Thank you

In the mean time I am testing the stability on the Raspberry, I installed the latest wheezy image on it and did an update and only a FTP server is running on it plus the consolewd. It seems to be stable but only I have been using it for a few days so far.

OK, I have fired up my raspberry pi

the server to use is from the wdconsole.ini file
i.e
[Aprs data send]
the server to use=

if blank then cwop.aprs.net is used
the port is fixed at 14580

if you go
./croncwop

what shows up?

Hello,

it looks like this:

pi@raspberrypi ~/WX $ ./croncwop
status 0
connected to CWOP server Ok
status 0
cwop sending user EW3457 pass -1 // -1 is default (you do not have a Ham call si vers wxdisplay WD_console_8.9 59
status 0
cwop sending EW3457>APRS,TCPIP*:@261431z4650.97N/00734.37E_045/000g000t076r000p000P000b10221h45.WD 59
status 0

config.txt:

Do CWOP updates=Y //every 10 minutes
CWOP station id=EW3457
CWOP ham call sign=-1 // -1 is default (you do not have a Ham call sign)
CWOP Latitude=4650.97N
CWOP Longitude=00734.37E

wdconsole.ini

[Aprs data send]
station id=EW3457
WD version=WD_console_8.9 59
ham call sign=-1 // -1 is default (you do not have a Ham call si
latitude=4650.97N
longitude=00734.37E
the server to use=cwop.aprs.net
data=EW3457>APRS,TCPIP*:@261431z4650.97N/00734.37E_045/000g000t076r000p000P000b10221h45.WD 59

and even if I modify the data= in the this file to
data=EW3457>APRS,TCPXX*,qAX,CWOP-4:@261431z4650.97N/00734.37E_045/000g000t076r000p000P000b10221h45.WD 59

it doesn’t work neither.

so It still doesn’t go through : http://www.findu.com/cgi-bin/wx.cgi?call=EW3457

re the longitude, where do you live in the world?

This is my location:
http://www.findu.com/cgi-bin/find.cgi?call=EW3457

Near the place where the IROX is made in Switzerland.

But the CWOP is still only working from my desktop WD, not from my raspberry pi.

humm, its not getting through from here either, in testing, using your settings files
I will test again to my CWOP number

I have fixed it
needed to be using port 23 instead
download a new consolewdpi update
http://www.weather-display.com/downloadfiles/consolewdfilespi.zip

(updated consolewd and croncwop files)

Thank you very much for the fix. Now it is working fine with the CWOP weather station ID.

If I want to use my hamradio callsign, what should I modify?
I just entered it in the config.txt after CWOP ham call sign=
and also into the wdconsole.ini but I can not see it on the APRS.FI.
Do I need to add something else in the config in that case?
It would be great to use with hamcall as well.

I had a problem with CWOP/aprsnetwork not updating properly. I figured out that my virus software was disabling the croncwop,exe therefore not letting data be sent. I disabled AVG virus protection, reinstalled the latest update from weather display and now everything is working properly

sometimes the virus checker is the virus