Pactor: Exchange failed: unexpected EOF

[maryan...@gmail.com]

What do I do the get an exchange to work?  I can connect but nothing happens.

Pactor seems to be working -- my script uses these commands:

My calling code:

echo Attempting a connection with <callsign> using pactor
pat connect pactor:///<call-sign>

The terminal displays:

Attempting a connection with K7NHV using pactor
2021/04/06 13:13:37 Unable to get frequency from rig network: dial tcp [::1]:4532: connect: connection refused.
2021/04/06 13:13:40 Connecting to K7NHV (pactor)...
2021/04/06 13:13:42 Connected to K7NHV (pactor)
2021/04/06 13:14:27 Exchange failed: unexpected EOF

The eventlog.json -- shows this:

^%^%^%^%^%^%

{"local_addr":"K7LRK","log_time":"2021-04-07T10:48:07.68516945-07:00","network":"pactor","operation":"connect pactor:///K7IF",

            "remote_addr":"K7IF","success":true,"what":"connect"}

{"auxiliary_addresses":[],"end":1617817731,"error":"unexpected EOF","local_addr":"K7LRK","local_locator":"CN88NK",

            "log_time":"2021-04-07T10:48:51.813932593-07:00","master":false,"mycall":"K7LRK","network":"pactor",                "received":null,"remote_addr":"K7IF","remote_fw":null,"remote_sid":"","

           sent":null,"start":1617817687,

            "success":false,"targetcall":"K7IF","what":"exchange"}

^%^%^%^%^%^%

This is the relevant portion of the config.jsaon

+=+=+=+=

  "pactor": {

    "path": "/dev/PACTOR",

    "baudrate": 829440,

    "rig": "",

    "custom_init_script": ""

  },

+=+=+=+=

eMail in folder: /home/pi/.wl2k/mailbox/K7LRK/out

==================

Mid: WBWNQQAXPLIT

Body: 8

Content-Transfer-Encoding: 8bit

Content-Type: text/plain; charset=ISO-8859-1

Date: 2021/04/06 19:26

From: K7LRK

Mbo: K7LRK

Subject: Hello World

To: SMTP:elc...@hotmail.com

Type: Private

test 1

===================

[Dr. Torsten Harenberg]

Am 10.04.21 um 21:27 schrieb maryan...@gmail.com:

> I can connect but nothing happens.

What I would try first:

can you successfully connect to the remote station K7KHV not using pat,
but only using the terminal command (as described in the SCS manual) and
can you see the welcome message there?

You need to see something like this:

[WL2K-5.0-B2FWIHJM$]
;PQ: ABCDEFGH
CMS via PJ2A >

If not, than there is something wrong in either your audio levels or any
other setting on the radio.

HTH, 73s

Torsten DL1THM

[maryan...@gmail.com]

Torsten and the group:

Still trying to trouble-shoot my connection problem.  You suggested looking for

issues in the radio/modem settings and told me to look for specific responses

from the Gateway

In response I double/triple checked the FSK/PSK/Mic gain settings.  I am using

the method detailed in the SCS manual.  I observe that ALC is not kicking in

during transmission.

Unfortunately, I am still experiencing the problem. I observe transmissions from

my side but never any response from the Gateway.

I wrote emails to several RMS gateways and asked them to look at their log file.

 Here are typical details from N7LOB:

-=-=-=-=-= 

I remembered local vs zulu times, looked back at my session log, and

found this one line at 20:54 zulu time (13:54 local time).

2021-04-24 20:54:31 1.3.37.0 *** scsPtcSession Abort called

(1.3.37.0 is my RMS Trimode version #.) This means there was pactor activity but

it was stopped. No call sign noted.

What seems to have happened is: • Your station called N7LOB. • My station

responded because it heard the N7LOB, so your log said it connected. • But

the exchange didn't continue for some reason. • My station heard your radio

signal strength just fine, but our information was not exchanged, so my log

doesn't show your callsign.

So....your radio is transmitting a good enough signal and is hearing signals

back.

 -=-=-=-=-=

It is not a propagation issue.  The Gateway can “hear” me but does not get

my call.  The Gateway is getting transmissions it cannot decode.  It does not

even request retransmission.  

I recently discovered the environment variable "pactor_debug" and set it to "3".   

Maybe the output will provide some clue to a problem(??).

 

Thanks for any help you can offer.

73

Clark

K7LRK

[Tim B]

I’m having the same issue. What modem are you using? I have the P4 Dragon DR-7400 connected to my iCom 7300. I’m wondering if the problem is that the 7400 is making the connection in Pactor 4 and not stepping back to Pactor 3? Is there a way to limit the 7400 to Pactor 3? I didn’t see anything about it in the pat documentation. In RMS Express there is a selection to limit it to Pactor 3 or less.

73 de KK4FQB 

[Dr. Torsten Harenberg]

Am 11.05.21 um 03:05 schrieb Tim B:

> Is there a way to limit the 7400 to Pactor 3? I didn’t see anything
> about it in the pat documentation. In RMS Express there is a selection
> to limit it to Pactor 3 or less.

you can include

MYLEVEL 3

in the a config file that you upload with the "custom_init_script" flag.
That would limit the connection to PACTOR 3.

Also here, I would suggest to try to contact to the remote station just
with the modem alone (no pat, no nothing), just with a terminal.

If you do not see the welcome message of the remote station: there is
still something with the audio or modem parameters which make the
connection to fail.

My HF station is down for a couple of month due to major works at the
house. I do not even have any kind of antenna at the moment. So I
currently cannot do any tests myself.

73s

Torsten DL1THM

[Tim B]

Hi guys,

I got my P4 DR-7400 working with my iCom 7300 today. I used the information from the Pactor group in the link below. I’ve made 4 connections so far. Thanks for the help.

https://groups.io/g/pactor/topic/scs_pactor_config_with/14354355?20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,14354355#

[Tim B]

Thanks for your input. If I understand correctly, I can build a script file ie. Pactor.sh and make it executable. Then add the path to the custom script line in the pactor section of the Jason file for pat?

Using the SCS manual can I use any of the commands or is it limited in some way?

Thanks,

73 de KK4FQB

[Torsten Harenberg]

Hi Tim,

23.05.2021 00:50:44 Tim B <s.v....@gmail.com>:

> If I understand correctly, I can build a script file ie. Pactor.sh and make it executable. Then add the path to the custom script line in the pactor section of the Jason file for pat?

The "custom_init_script" in the config.json just contains the path to a file (no need to make it executable) that contains commands (one line per command) send to the modem before a connection is being made.

As an example, it might look like this:

MYLEVEL 3
FSKA 310
PSKA 310

>
> Using the SCS manual can I use any of the commands or is it limited in some way?

It's not limited in any way. The driver is "dump" in a way that it assumes that the user knows what he's doing to just sends those commands to the modem - being valid or not. A couple of modem essential commands are being always being sent, including a "MYCALL" command to set the correct call sign:

https://github.com/harenber/ptc-go/blob/v2/pactor/modem.go#L141-L144

Hope this helps!

73s

Torsten DL1THM

[Tim B]

Thanks for the clarification. I’m going to give it a try. 

73 de KK4FQB