WinRPR uses WA8DED Host Mode, and with that the monitor does not
differentiate between TX and RX frames.
When you tried KISSHF did you enable KISS mode in the WinRPR config?
73, John
On 13/03/2025 03:24, Lee Bengston via
groups.io wrote:
toggle quoted message
Show quoted text
1) The WINRPR driver works, but QtTermTCP shows the same
(Rx) color in the monitor for both transmit and receive. I
don't see that on any other ports. It's a minor but strange
thing. Despite not showing the right color for transmit, the
radio does get keyed, and transmit works.
2) When advised to try the KISSHF driver, I did, and the
correct color is displayed in QtTermTCP for transmit, but the
radio is not keyed.
My current port is as follows. When I change to use the
KISSHF driver, the line DRIVER=WINRPR is replaced with
DRIVER=KISSHF, and the KISS related parameters are
un-commented.
PTT is handled via CAT commands. BPQRemotePTT and com0com
are running on a Win10 desktop with WinRPR. LinBPQ
communicates with WinRPR over the network.
PORT
?PORTNUM=8
?INTERLOCK=1
?ID=WinRPR, INFO for details
?DRIVER=WINRPR
; QUALITY=0
; FRACK=6000
; RESPTIME=6000
; RETRIES=12
; MAXFRAME=1
; PACLEN=60
; TXDELAY=300
; SLOTTIME=100
; PERSIST=128
?CONFIG
? ADDR 192.168.200.6 8001 PTT CAT
? FORCE ROBUST ? ? ? ? ? ?; RP Only
? USEAPPLCALLS ? ? ? ? ? ?; Accept connects to all APPLCALLS
? Z 0 ? ? ? ? ? ? ?; No Flow Control
? Y 1 ? ? ? ? ? ? ?; One Channel
? E 1 ? ? ? ? ? ? ?; Echo - Restart process needs echo
? BEACONAFTERSESSION
ENDPORT
The pertinent
rig control statements are as follows:
?RADIO 1
?Remote YAESU FTDX10
HAMLIB=4532
LinBPQ sends CAT
commands to WinMorControl on the Win10 desktop including the
command(s) for PTT. That works not only with WinRPR &
the WINRPR driver, but also with QtSoundModem and VARA.
73,
Lee K5DAT
