| |
RN1M > PACTOR 28.01.24 23:08l 58 Lines 1770 Bytes #999 (0) @ WW
BID : 439_RN1M
Read: GAST
Subj: PACTOR 1: LinBPQ+MultiPSK
Path: DB0FFL<DB0FHN<DB0BLO<DB0ERF<OK0NAG<OK0NBR<SR1BSZ<IW0QNL<ON0AR<GB7CIP<
VE3KPG<VE3CGR<R2AKT<RN1M
Sent: 240127/1300Z 439@RN1M.SPB.RUS.EU LinBPQ6.0.24
Hello, OMs
I want to try to raise a port from Pactor 1 for forwarding and winlink based on LinBPQ.
Here are my port settings:
PORT
PORTNUM=9
INTERLOCK=1
ID=14.1023/7.0452 PACTOR 1 +1500Hz
DRIVER=MULTIPSK
CONFIG
ADDR 192.168.0.204 3122 PTT HAMLIB
ENDPORT
In the terminal I enter:
ATTACH 9
MODE PACTOR_1
CONTROLS N N
ALIGNMENT 1500
С BBSCALL
In multipsk there is this error in the log:
14:52:09: Connection accepted by the server socket
14:52:09: Connected to 192.168.0.193
14:52:09: DIGITAL MODE ?
15:45:57: STOP_BEACON_ARQ_FAE
15:46:20: DIGITAL MODE PACTOR_1
15:46:33: CONTROLS N N
15:46:41: ALIGNMENT 1500
15:46:49: CALLSIGN_TO_CALL_ARQ_FAE BBSCALL
15:46:49: SELECTIVE_CALL_ARQ_FAE
15:48:53: Disconnecting error. Socket Error n°10053 : Software caused the connection to abort. A connection that has been made was aborted, usually due to connection or protocol error.
15:48:53: Writing error. Socket Error n°10054 : Connection reset by peer. This occurs when an established connection is shut down for some reason by the remote computer.
15:48:53: Client disconnected
And I still donâ€Öt understand: is Multipsk Paktor 1 in FEC or ARQ mode?
After such an error, multipsk remains in transmission, and LinBPQ is overloaded.
TRX does not switch to transmission via hamlib at all.
Does anyone have experience connecting multipsk in pactor with BPQ?
Or is this a lost cause and not worth wasting time on? :)
When setting up, I am guided by this information:
http://f1ult.free.fr/DIGIMODES/MULTIPSK/PACTOR1_en.htm
https://www.cantab.net/users/john.wiseman/Documents/MultiPSKDriver.htm
I would be grateful for the community's ideas on what more can be done.
73!
--
Sent from Sylpheed 3.7.0 -> LinBPQ
Best regards, Sergey Ievkov <RN1M@RN1M.SPB.RUS.EU>
Lese vorherige Mail | Lese naechste Mail
| |
