check sum failure

68 views
Skip to first unread message

Ed Fardos

unread,
May 8, 2020, 12:10:44 PM5/8/20
to pat-users
email with attachment, recently switched ardop from max=500 to max=2000,  tried twice, different gateways, same errror:

Bad checksum generated by pat?



2020/05/08 08:32:54 Connected to KD6OAT (ardop)
RMS Trimode 1.3.30.0
KM6LYW has 44 minutes remaining with KD6OAT
[WL2K-5.0-B2FWIHJM$]
;PQ: 99045775
CMS via KD6OAT >
>FC EM G6EZPYUEQKLJ 7251 7056 0
Sending checksum D6
FS Y
Remote accepted G6EZPYUEQKLJ
Transmitting [winlink with attachment image] [offset 0]
*** Error check failed on receiving B2 message. [Check sum failure - failed to assemble correct binary image] - Disconnecting (174.23.52.85)
2020/05/08 08:39:46 Exchange failed: Error check failed on receiving B2 message. [Check sum failure - failed to assemble correct binary image] - Disconnecting (174.23.52.85)
2020/05/08 08:39:47 QSX ardop: 14074.000

Martin Hebnes Pedersen

unread,
May 11, 2020, 3:30:05 AM5/11/20
to Ed Fardos, pat-users
Hi Ed,

Are you able to send the message via telnet or any other transports?

The error indicates that the receiving CMS are unable to decode the lzhuf compressed binary, either because of corruption in the underlying transport stream or due to some lzhuf incompatibility issue between Pat and the CMS.

Early versions of ARDOP did have some issues that lead to corruption in some cases. What version are you running?

Please keep the errornous message file (G6EZPYUEQKLJ.b2f), it might be important for further debugging.

Thanks!

-- 
73 de LA5NTA / Martin
-- 
Martin


--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/93aa40d4-2f4e-2d3a-a12c-b12fd2269b46%40gmail.com.

Ed Fardos

unread,
May 11, 2020, 10:16:13 AM5/11/20
to Martin Hebnes Pedersen, pat-users
sorry message deleted, didn't try telnet, wish I did now.

ARDOPC Version 1.0.4.1j-BPQ

subsequent emails haven't had a problem, so it was a one-time glitch at this point.
> To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com <mailto:pat-users%2Bunsu...@googlegroups.com>.

Torsten Harenberg

unread,
May 11, 2020, 10:58:22 AM5/11/20
to pat-...@googlegroups.com
Hmm.. I just had that as well connecting via Packet Radio:

2020/05/11 16:55:54 Connected to PJ2A (pactor)
PJ2A - Linux RMS Gateway 2.5.1 Sep 28 2019 (FK52nd)

Welcome to the PJ2A Winlink 2000 RMS Gateway. VERONA Radio Club,
Curacao, Dutch Caribbean
INFO: Host Name cms.winlink.org, Port 8772
Connected
[WL2K-5.0-B2FWIHJM$]
;PQ: 56687417
CMS via PJ2A >
>FC EM T2JYZDQLCZA3 298 247 0
Sending checksum 53
FS Y
Remote accepted T2JYZDQLCZA3
Transmitting [test mail with DR-7800] [offset 0]
test mail with DR-7800: 100%
*** Error check failed on receiving B2 message. [Received data stream
not a correct format] - Disconnecting (93.244.113.115)

The is the BETA of the new P4 Dragon driver, but strange nevertheless. I
wouldn't expect packet losses here.

73s

Torsten


Am 11.05.20 um 09:29 schrieb Martin Hebnes Pedersen:
> Hi Ed,
>
> Are you able to send the message via telnet or any other transports?
>
> The error indicates that the receiving CMS are unable to decode the
> lzhuf compressed binary, either because of corruption in the underlying
> transport stream or due to some lzhuf incompatibility issue between Pat
> and the CMS.
>
> Early versions of ARDOP did have some issues that lead to corruption in
> some cases. What version are you running?
>
> Please keep the errornous message file (G6EZPYUEQKLJ.b2f), it might be
> important for further debugging.
>
> Thanks!
>
> -- 
> 73 de LA5NTA / Martin
> -- 
> Martin
>
>
> fre. 8. mai 2020, 18:10 skrev Ed Fardos <edfa...@gmail.com
> <mailto:edfa...@gmail.com>>:
> <mailto:pat-users%2Bunsu...@googlegroups.com>.
> --
> You received this message because you are subscribed to the Google
> Groups "pat-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to pat-users+...@googlegroups.com
> <mailto:pat-users+...@googlegroups.com>.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/pat-users/CAAUuLGn2vc-MUo9jZkt95Pq3_KhcEbu1ZQNsjSYkAwb-XDjvtQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/pat-users/CAAUuLGn2vc-MUo9jZkt95Pq3_KhcEbu1ZQNsjSYkAwb-XDjvtQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.

C. Matthew Curtin

unread,
Jun 18, 2020, 8:59:36 AM6/18/20
to Torsten Harenberg, pat-...@googlegroups.com
I've encountered the same issue and started to isolate it. It seems to happen when I've got an attachment, but not every time, and sometimes when I attach a file it will work, the same file attached to another message body will fail, but that same message body will work without the attachment. Furthermore, the message that fails to transfer with ardopc (1.0.4.1j-BPQ, built from source) successfully transfers by telnet.

I'm quite new to Winlink but given that the same b2f fails on one transport but succeeds on another, I think we can probably safely conclude that this isn't a Pat problem, but an ardopc problem, or is a problem with the receiving side's transport:

KC8YJJ (ardop)
RMS Trimode 1.3.31.0 "ON JUNE 30, 2020, Winlink VARA HF RMS stations will switch to use VARA HF 4.0, which is incompatible with earlier versions. Client stations should pr

I've experienced this issue with multiple RMS gateways, but I think (have not confirmed...don't have logs going back that far) that they're all running that version of RMS Trimode.

I'm going to start looking more closely at my build of ardopc. My test system here is 
Linux kali 5.6.0-kali1-amd64 #1 SMP Debian 5.6.7-1kali1 (2020-05-12) x86_64 GNU/Linux

Is anyone having this problem with anything other than ardopc, or with ardopc on another platform?




To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/f87ce544-81ec-8859-fd5c-f563e7b85973%40gmail.com.


--
C Matthew Curtin  Columbus Ohio USA

LA5NTA

unread,
Jun 18, 2020, 11:09:18 AM6/18/20
to pat-users
This is excellent news!

Since you're able to confirm that CMS decodes the message successfully when connecting over telnet, it clearly isolates the problem to the transport layer. It might be a bug in ARDOPc, but it could also be a bug in the ARDOP interface implementation of Pat.

You can enable debug logging for the ARDOP driver for Pat by setting the environment variable ardop_debug=true when running Pat. Simply run `export ardop_debug=true` in the terminal before starting Pat (in the same terminal session).

If you're able to catch both the ARDOPc log output and Pat log output (with ardop_debug=true) when the error occurs, that would be very helpful.

Thanks!

-- 
73 de LA5NTA / Martin

C. Matthew Curtin

unread,
Jun 18, 2020, 12:33:40 PM6/18/20
to LA5NTA, pat-users

OK I've got the log data. I haven't trimmed anything because I want to be sure not to lose anything that might be relevant. I made several attempts to get a good connection. You'll see in the ARDOP log that I could not reach several RMS Gateways, one I did reach and started sending but got an "Unexpected EOF" in the middle (quality was poor), then I did get a good connection and the entire message moved when talking to NS0A on 40m and got the checksum error we're focusing on. I then sent the message by telnet transport and it did go through.

I'm attaching the ARDOPDebug log, ARDOPSession, and the pat.log.


--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
ARDOPSession8515_20200618.log
ARDOPDebug8515_20200618.log
pat.log

C. Matthew Curtin

unread,
Jun 22, 2025, 6:06:45 AMJun 22
to LA5NTA, pat-users
Following up on an ancient problem for the sake of posterity since someone, someday will find this in an archive when dealing with the problem. :)

I confirmed that this was not a pat problem, but an ARDOPc problem. ARDOPc also had trouble with version 6 Linux kernels.

I found a reliable fix with a move off of ARDOPc and to ardopcf, a fork that's made it much easier to build and to maintain. https://github.com/pflarue/ardop



On Thu, Jun 18, 2020 at 11:09 AM LA5NTA <martin.h...@gmail.com> wrote:
--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages