APRS returns "range check error"

[Bob Ridgeway]

WXUG gets my data OK (KALSALTA2) but APRS (EW2603) returns "range check error". FTP log and debug log are both off and confirmed in the cumulus.ini file. Just came to mind that its been a while since setting up the account with CWOP and not posting data to it, maybe I'll start a "new account" and see if that works. Anticipating another failure, got any ideas?

[steve]

It's not an error I'm familiar with (regarding APRS). What is the exact full error message, and where are you seeing it? What version and build of Cumulus are you using?

[Bob Ridgeway]

Error log must be turned on to see this. Otherwise Cumulus just clocks along thinking everything is OK. Since reading other posts I've made certain Error log is only turned on when necessary.

See attached the debuglog file from this morning.

debug.log

I am using Cumulus 1.9.4 build 1094.

Is there a particular port on which CWOP receives its data? Because of our network proxy I had to change my HTTP proxy port to 8080 for the upload to WXUG to work. I thought CWOP data used a different protocol, could this be what's causing the problem? Really hope this info helps. I've tried everything I know to do, and at my somewhat short wit's end.

[steve]

I can't tell exactly where in the code the error is occurring - it's a local exception, rather than being returned from CWOP. It's occurring either when trying to send the user and password to CWOP, or while constructing the data string to send to CWOP. It's not getting as far as sending the data to CWOP. It appears that you're generating an 'easyweather.dat' file for Cumulus to read, but I can't see anything wrong with the data that's being supplied that would cause the code to error while constructing the data string.

CWOP uses a TCP connection to port 14580, if that helps.

If you zip up the diags folder and attach it, I'll see if I can see anything in there. If not, I'll have to add some more debug logging to the code which constructs the CWOP data string to narrow it down.

[Bob Ridgeway]

cumulus.001

cumulus.002

cumulus - ~og.003

Sorry, no zip application readily available. These are all the files in the Diag folder. "cumulus.~og" renamed to "cumulus - ~og.003". I really don't see anything in there that helps. I hope you do. Let me know if you need anything else. Would re-downloading and re-installing help, maybe upgrading to build 1095?

[steve]

Sorry, no zip application readily available.

It's built in to Windows.

I really don't see anything in there that helps.

No, neither do I. It's a bit odd that the first file is from 10:39 today, Cumulus keeps the last 10 files, and you were clearly using Cumulus before 10:39 today.

Let me know if you need anything else.

Perhaps a screen shot of your CWOP settings in Cumulus might give a clue. There's not much that can go wrong there, though.

Would re-downloading and re-installing help, maybe upgrading to build 1095?

It's unlikely. It could be that the "easyweather.dat" station type doesn't set something up that is needed by the CWOP upload code - it's a bit of hack and is only really there on a "use it if it works" basis. At some point I should really do a proper "universal" interface for station types that aren't supported directly. I don't know if anyone else using this input method is also uploading to CWOP.

I'll see what extra diagnostics I can put in.

Edit: I've added some more logging to the debug log. Attached is the new cumulus.exe file (zipped), just unzip it into your existing installation and run it as normal, and turn on the debug log.

Edit: I've removed the attachment now as this version is now superseded by the latest official build of 1.9.4, which contains the extra logging.