Cumulus Support

I just upgraded from v1.9.4 build 1085 running on WinServer 2003 to a RPi 2 last night. I have everything working fine on the RPi so far with the exception of APRS/CWOP reporting.

If I go to www.findu.com it says (as of now) that I haven't reported any data since last night when I shutdown my old install:
"Last report from DW9477 received 21 hours 6 minutes 38 seconds ago"

I turned on debug logging in CumulusMX and it looks like the CWOP update is working w/o any errors:
2015-09-19 13:30:00.789 Updating CWOP
2015-09-19 13:30:01.020 Sending user and pass to CWOP
2015-09-19 13:30:04.064 Sending: DW9477>APRS,TCPIP*:@192030z3901.100N/11942.33W_341/001g004t081r000p000P000h14b10184eCumulusDsVP
2015-09-19 13:30:06.342 Reading reception stats
2015-09-19 13:30:06.643 0A-0D-4F-4B-0A-0D-31-32-35-32-34-20-37-39-20-30-20-32-36-33-34-20-34-32-0A-0D-00-00-00-00-00-00-00-00-00-00-00-00-00-00
2015-09-19 13:30:06.644 12524 79 0 2634 42
2015-09-19 13:30:06.744 Sending command LPS 2 1 - pass 1
2015-09-19 13:30:07.085 End of CWOP update

I read some info on APRS/CWOP and found out there is a Packet Checking page at http://wxqa.com/activecwd.html. Item 3 has a link to show packets arriving at APRS. When I check this, it shows my last incoming packet:
DW9477>APRS,TCPXX*,qAX,CWOP-3:@191950z3901.100N/11942.33W_282/003g009t078r000p000P000h17b10189eCumulusDsVP
6/84 data packets and 0/0 duplicates; 636/8904 bytes

In item 4 on the same page, there is a description of the findu.com database and it says:
A listing of faulty packets received by findu.com is also available. If your packets appear in this listing, to find the problem you may want to compare with the packets in CW Weather packets or DW Weather packets or EW Weather packets

When I click on the faulty packet link, I find my station listed:
Call - Count - Last Bad Packet
DW9477 88 DW9477>APRS,TCPXX*,qAX,CWOP-3:@192030z3901.100N/11942.33W_341/001g004t081r000p000P000h14b10184eCumulusDsVP

So does this mean MX build 3030 is building a malformed packet or that I have something wrong in my configuration that is causing a bad packet?

Just found this page that lists every one of my new MX packets as having an error:

http://www.findu.com/cgi-bin/errorlist. ... 77&last=24

MCQ wrote:Just found this page that lists every one of my new MX packets as having an error:

http://www.findu.com/cgi-bin/errorlist. ... 77&last=24

Compared to where your station is registered, the data the station is sending doesn't match. That will cause errors.

You're station is registered at 3902.00N Latitude in LORAN units. You're sending 3901.100N in those packets. That will be enough to cause errors. You need to change your location in the settings of MX to reflect that. Or if you are actually at that position, you'll need to re-register and correct it, and that will take a bit to update from past experience.

You can also use this site and it will tell you of any errors.

http://weather.gladstonefamily.net/site/D9477

You notice down in this page an error:

This report was not parsed as a valid APRS message: Invalid uncompressed location

Make sure that in the location part of the main settings page, you have the right Lat/Long. CW is expecting the longitude at the top of the Gladstonefamily page I have provided. If it doesn't match, there's your issue. If it does, then something else is afoot.

OK - I figured this out and I believe I found a bug in MX build 3030.

I looked at my last good packet vs. the bad packet list and found the same as BigOkie:
DW9477>APRS,TCPXX*,qAX,CWOP-6:@182320z3902.00N/11942.33W_326/008g013t078r000p000P000h16b10164eCumulusDsVP
DW9477>APRS,TCPXX*,qAX,CWOP-3:@191950z3901.100N/11942.33W_282/003g009t078r000p000P000h17b10189eCumulusDsVP

I thought for sure I set this correctly in my Station Settings, so I went to that page and found:


I edited it to this (color changed to black) and saved the page and got a 'settings saved' popup:


I restarted MX and waited for a CWOP update and got another bad packet. Here it is, just like the last:
DW9477>APRS,TCPXX*,qAX,CWOP-3:@192140z3901.100N/11942.33W_015/003g009t082r000p000P000h13b10172eCumulusDsVP

I open the Station Settings page again, and my Latitude is back to what it was above in red -> 39 - 1 - 60.

I open Cumulus.ini and find the LatTxt is correct:
[Station]
Type=1
Model=
ComportName=/dev/ttyUSB0
Latitude=39.0333333333333
Longitude=-119.705555555556
LatTxt=N 39° 02' 00"
LonTxt=W 119° 42' 20"

I manually edited the Latitude in Cumulus.ini and changed it to 39.04 and then restarted MX. Now when I go in to Station Settings, I get a black setting:


APRS/CWOP reporting is now working with the incorrect latitude.

So, it looks MX really dislikes having a zero in the seconds field and when you save that setting you get an acknowledgement instead of an error. It also squawks if you enter a double-zero in that field throwing this error: "This value is not an integer."

Thanks - I can reproduce this, I'll fix it in the next build.