Thanks so much for RadioMail, it’s a great tool! I’ve got one problem though and I’m not sure if this is just me, or the gateway I’m connecting to, but I seem to get this error each time I’ve tried to download my Winlink Wednesday Net Confirmation. It works fine when I download it over Telnet but downloading it over RF gives me the error. Has anyone else been able to successfully download their net confirmation messages using RadioMail? Other messages send and download fine, it’s only the weekly confirmations that give me this error:
*** Finding device TNC3 Mobilinkd
*** Connecting to WM3M-10 via PACKET @ 145.090 MHz
MMARSI RMS node
[WL2K-5.0-B2FWIHJM$]
;PQ: 18411734
CMS via WM3M >
;FW: KB3UFH
[RadioMail-1.0.2-B2FHM$]
;PR: ********
; WM3M-10 DE KB3UFH (FM18lw)
FF
;PM: KB3UFH 8MUNRI4SS6MU 2365 KN4LQN@winlink.org Winlink Wednesday Net Confirmation (Episode #329)
FC EM 8MUNRI4SS6MU 5562 2365 0
F1
FS +
*** Receiving message 8MUNRI4SS6MU
*** Error: false can't be coerced into Fixnum
Telnet:
*** Connecting to WL2K via TELNET @ cms.winlink.org:8772
[WL2K-5.0-B2FWIHJM$]
;PQ: 70289863
;FW: KB3UFH
[RadioMail-1.0.2-B2FHM$]
;PR: ********
; WL2K DE KB3UFH (FM18lw)
FF
;PM: KB3UFH 8MUNRI4SS6MU 2365 KN4LQN@winlink.org Winlink Wednesday Net Confirmation (Episode #329)
FC EM 8MUNRI4SS6MU 5562 2365 0
I can see a few similar errors on the crash report logs, although I don't see your particular session which is odd. It seems to be occurring when computing the received message checksum.
Could you confirm a few things:
0) You've had this problem more than once, e.g. similar confirmation email but different week?
1) You can receive other messages of similar size (> 5K) from this gateway without problems?
2) When you encounter that problem, did the message start downloading at all (you should see the progress bar creep up) or does the error occur right away?
3) Does the message contain an attachment or is it just a lot of text?
Georges - since today’s Wednesday, it’s perfect timing if you’d like to see the net confirmation email directly; Winlink Wednesday is open to anyone (it’s designed to give people a reason to regularly practice sending and receiving Winlink messages):
Yes. The three yesterday were all Winlink Wednesday confirmations or reminders. I haven’t tried to confirm this issue with messages from other nets, like the Thursday Em-Comm net, or with a mixed batch. But I’ll look.
Just tried to download this week’s confirmation email and got the same error as before, after the progress bar filled up; I’ll download it via Telnet and send you the email directly.
*** Finding device TNC3 Mobilinkd
*** Connecting to WM3M-10 via PACKET @ 145.090 MHz
MMARSI RMS node
[WL2K-5.0-B2FWIHJM$]
;PQ: 16078161
CMS via WM3M >
;FW: KB3UFH
[RadioMail-1.0.2-B2FHM$]
;PR: ********
; WM3M-10 DE KB3UFH (FM18lw)
FF
;PM: KB3UFH IP56J4TRMX1L 2406 KN4LQN@winlink.org Winlink Wednesday Net Confirmation (Episode #330)
FC EM IP56J4TRMX1L 5712 2406 0
23
FS +
*** Receiving message IP56J4TRMX1L
*** Error: false can't be coerced into Fixnum
Thanks Glenn. This issue is driving me insane At least I can eliminate message size as perhaps contributing to some sort of weird problem with frame alignment since now both messages you provided are different length. I've analyzed the code path for packet message reception and could not find anything obvious that would lead to the error.
The only other thing I can think of is that the "MMARSI RMS node" configuration may be different from what I'm using. Is there any way you could find out what software and version they use for their gateway?
I'm considering adding some diagnostic to see if I can gather more clues when this error occurs. Let me know if you'd be willing to get a test build when I have something available. That would help me a lot.
Sure, I’d be happy to help test further! I’ll see what I can find out about the software; looks like MMARSI is the Maryland Military Auxiliary Radio Service (https://mmarsi.org/).
I have a lead. I've looked up some other reports and so far 3 out of the 5 gateways I can identify having problem seems to be running BPQ32. I've reached out to all the gateway operators so they can hopefully confirm what software they are running. If it turns out to be BPQ32, that would narrow down the field considerably and hopefully allow for a repro.
Thanks for your patience. This may take a while but we'll get to the bottom of this.
-
