VARA FM Broke in Pat 0.13 for the Pi??

[KM4ACK]

Installed Pat 0.13 this afternoon on a pi running Bullseye 32 bit. After starting the VARA FM modem, I attempted a connection and received the following error:

2022/08/23 15:04:19 got a vara command I wasn't expecting: WRONG
2022/08/23 15:04:27 Unable to establish connection to remote: connection failed

Downgraded to 0.12.1 and no longer have the error.

Is there something different that needs to be added to the config file

73, de KM4ACK

[Jim Weisgram]

Does it work with packet (if you have tried it)?

>> Jim

--
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/4e1fd0ab-a56d-4f9e-a0b5-adea00d691fbn%40googlegroups.com.

[KM4ACK]

I didn't try packet. I downgraded when I couldn't get VARA FM to work.

73, de KM4ACK

[jpspoo...@gmail.com]

I got pat v0.13 running on linux mint using packet (ax25). I can successfully connect to CMS via my RMS gateway NX2I-10. Mail is transported just fine. However if I immediately try to send another mail message the transport fails. This is what I see:

this is from axlisten -art:

...NX2I-10 audio level = 74(15/9)   [NONE]   __||||__|
[0.4] NX2I-10>NX2I-4:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)FF<0x0d>
wl2k: fm NX2I-10 to NX2I-4 ctl I00^ pid=F0(Text) len 3 16:41:16
FF
wl2k: fm NX2I-4 to NX2I-10 ctl I10^ pid=F0(Text) len 3 16:41:16
FQ
wl2k: fm NX2I-4 to NX2I-10 ctl DISC+ 16:41:16
[0L] NX2I-4>NX2I-10:(I cmd, n(s)=0, n(r)=1, p=0, pid=0xf0)FQ<0x0d>
[0L] NX2I-4>NX2I-10:(DISC cmd, p=1)

NX2I-10 audio level = 92(16/9)   [NONE]   ___|||||_
[0.5] NX2I-10>NX2I-4:(UA res, f=1)
wl2k: fm NX2I-10 to NX2I-4 ctl UA- 16:41:18

the above is the tailend of the first connection.

in a pat console you can see the end of the first connection and then the failure at the second connection attempt:

NX2I-10 - Linux RMS Gateway 2.5.1 Sep 19 2019 (EL88xv)
NX2I-10 Linux RMS Gateway 2.5.1, The Villages, Florida
INFO: Host Name cms.winlink.org, Port 8772
Connected
[WL2K-5.0-B2FWIHJM$]
;PQ: 07005780
CMS via NX2I-10 >
>FC EM 3HXJO3TEVJNI 382 314 0
Sending checksum 64
FS Y
Remote accepted 3HXJO3TEVJNI
Transmitting [ax25 with attachment] [offset 0]
ax25 with attachment: 100%
FF
>FQ
2022/08/23 16:41:16 Disconnected.
2022/08/23 16:43:11 Connecting to NX2I-10 (ax25)...
2022/08/23 16:43:11 Unable to establish connection to remote: address already in use

[lu...@hearham.live]

That might be this error, which unfortunately doesn't have a good solution... It's a newer Linux bug?

https://github.com/la5nta/pat/issues/352

"Unable to establish connection to remote: address already in use" after first connection #352 - github.com I've got Direwolf running as a software TNC with the -p command, and I run kissattach to connect the Linux AX.25 stack to that port. This works, and when I connect in Pat, my emails are sent an... github.com

---

From: pat-...@googlegroups.com <pat-...@googlegroups.com> on behalf of jpspoo...@gmail.com <jpspoo...@gmail.com>
Sent: Tuesday, August 23, 2022 1:58 PM
To: pat-users <pat-...@googlegroups.com>
Subject: error: Unable to establish connection to remote: address already in use

 

To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/880b3451-d5c6-45ec-980e-85e327720cc9n%40googlegroups.com.

[KM4ACK]

It seems as though this might be a configuration issue. My initial config.json entry was:

  "vara": {
    "host": "localhost",
    "cmdPort": 8300,
    "dataPort": 8301,
    "rig": "my-rig",
    "ptt_ctrl": true
  },

but I modified the first line to be:

  "varafm": {
    "host": "localhost",
    "cmdPort": 8300,
    "dataPort": 8301,
    "rig": "my-rig",
    "ptt_ctrl": true
  },

After the changes, I initiated a connection from the command line. Though there is an error, the connection completed and hung up:

pat connect varafm:///WC4EOC-8
2022/08/24 12:17:40 my-rig ready. Dial frequency is 145.050.00 MHz.
2022/08/24 12:17:40 Connecting to WC4EOC-8 (varafm)...
2022/08/24 12:17:40 got a vara command I wasn't expecting: WRONG
2022/08/24 12:17:43 Connected to WC4EOC-8 (vara)
Williamson County TN EMA
[WL2K-5.0-B2FWIHJM$]
;PQ: 96057472
CMS via WC4EOC >
>FF
FQ

2022/08/24 12:18:01 Disconnected.

Rig control still isn't working though.

73, de KM4ACK

[Herbert Crosby]

The qso wasn't over at FQ...which is cms saying bye not the rms gateway and that's part of the problem of the closing stages.

Herbert KD5PQJ

To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/03f22b11-1516-41cb-8aa1-c37f0d8b188cn%40googlegroups.com.

[LA5NTA]

torsdag 25. august 2022 kl. 05:35:24 UTC+2 skrev kd5...@gmail.com:

The qso wasn't over at FQ...which is cms saying bye not the rms gateway and that's part of the problem of the closing stages.

Herbert KD5PQJ

That's an interesting statement, Herbert. Is this defined somewhere? According to the FBB protocol "specification" by F6FBB, the conversation ends with either peer sending FQ. If this is not the case, then how would one know that it's time to disconnect?

If this is not defined properly, we'd might end up with idle connections running indefinitely. Pat's current approach to prevent this is to disconnect after either sending or receiving the FBB terminating command "FQ". I should be valid according to F6FBB's spec, but maybe this is wrong?

Is it your understanding that it's the receiving station's (the "listener") responsibility to terminate the connection?

Thanks!

-- 

Martin / LA5NTA

[Gmail]



After update 0.13 I have as a problem that for Pat:

Ardop hangs and you have to reset de pc

Packet ax25 works very fine

Vara hf is not working was working under 0.12

Vara fm connects but then it is not ending the connection. 

Winlink express is working with vara Fm under 0.13. Was also working under 0.12

With vara hf it does not work was also not working under 0.12 can’t find com port is what he says.

Under 0.12 I used pat for vara hf and for vara fm i used winlink express.

Working with a ic7100 and raspberry pi 4

73 PD7RON

Op 25 aug. 2022 om 05:35 heeft Herbert Crosby <kd5pqj@gmhgf gaail.com> het volgende geschreven:



The qso wasn't over at FQ...which is cms saying bye not the rms gateway and that's part of the problem of the closing stages.

Herbert KD5PQJ

To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/CAG95ni8pdestEDPDRYDyJwCTD4OgAwmp_JyPEvRn05q78M%2BkXw%40mail.gmail.com.

[Chris Keller]

By setting environment variable VARA_DEBUG=1 before running Pat, I think I see the problem causing "got a vara command I wasn't expecting: WRONG": VARA FM doesn't support the "CWID ON". That's an easy fix in the VARA driver

To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/C65F1939-DEC5-431D-A082-EF40A1BC88B7%40gmail.com.

[Gmail]

I have tested the last solution from km4ack but had no luck.

Ardop hangs after one carrier.

Packet works for me

Varafm is coming to an FQ en de last carrier is without modulation.

Varahf is repeating itself the carrier stays on and because of that there is no connection.

Raspberry pi 4 and IC7100

73 Ron

PD7RON

Op 26 aug. 2022 om 22:51 heeft Chris Keller <xyl...@gmail.com> het volgende geschreven: