¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. KM4ACK-Pi
  2. Topics

Strange Direwolf YACC and XASTIR error: rig_set_ptt command for channel 0 PTT

 

I've been beating my head against the wall for close to a month now trying to get ANY Direwolf and YACC or XASTIR combo to build a digipeater, Igate combo.
I have an FT-817nd, RPi 3, Yaesu CAT cable CT-62 and the KM4ACK--Build-a-Pi burned into a flashdisk.
Direwolf comes up running and receiving local packet traffic. Here is the startup info:

Dire Wolf version 1.7
Includes optional support for:? hamlib cm108-ptt
?
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:3,0? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3.
Hamlib determined CAT control serial port rate of 38400.
User configuration overriding hamlib CAT control speed to 4800.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
?
Now connected to IGate server noam.aprs2.net (199.204.38.35)
Check server status here http://199.204.38.35:14501
**
When i start XASTIR I get the following error almost right away:

Hamlib Error: rig_set_ptt command for channel 0 PTT
read_block_generic(): Timed out 3.3042 seconds after 0 chars, direct=1
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
read_block_generic called, direct=1
read_block_generic(): Timed out 3.6001 seconds after 0 chars, direct=1
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
read_block_generic called, direct=1
read_block_generic(): Timed out 3.3035 seconds after 0 chars, direct=1
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
read_block_generic called, direct=1
read_block_generic(): Timed out 3.3046 seconds after 0 chars, direct=1
ft817_set_ptt: get ptt cmd failed
?1:rig.c(2932):rig_set_ptt returning(-5) Communication timed out
?
Communication timed out

It repeats very so often, no doubt when trying to do something wit Hamlib.

More often than not the transmitter keys up and after about 12 seconds, goes off. I'm assuming it is the sum total of the times mentioned in the error message. I keep the transmitter at very low power so as not to block the channel 144.390 Mhz.

If I use YACC instead, the error doesn't happen right away, but randomly shows up.

The other thing that happens is that neither app seems to capture my beacons from my FT-5D. Eventually, a "superstation," about twenty miles away picks up the beacon and posts it to aprs.fi, but I never see it posted from my Igate, K1YPP-10.

The Hamlib and controls seem to work fine in FLdigi, FLrig and WSJT-x.

What can I post that will give some clues as to what isn't working properly?

So, what should I look at and what am I doing wrong. I've watched a million videos, mostly KM4ACK, and haven't found anything that seems to cure this...HELP!!!

Dennis, K1YPP
 

If flrig works point direwolf to flrig for PTT?

PTT RIG 2 localhost:4532
 

Thanks Kelly:
I did try that and I get:
Dire Wolf version 1.7
Includes optional support for:? hamlib cm108-ptt
?
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:3,0? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3.
Retrying Hamlib Rig open...

and then Direwolf times out and closes.
I'm assuming that I have to start FLrig first and it does control the frequency, etc. on the FT-817nd.
Is that correct, or do I not start it and Direwolf somehow starts it to use it? I've never used this before.

Dennis, K1YPP
 

Yes start flrig after start direwolf?

k
 

Made no difference, plus, I have to get it running before Direwolf times out.

Thanks

Dennis, K1ypp
 

I've also noticed that YACC doesn't any longer populate the map with stations heard, just my k1ypp-10. That did work, but now, does not. However, XASTIR still populates the map but has that constant error going by in Direwolf. Is this any kind of clue to anything?

Dennis, K1YPP
 

the correct port is 12345 now, so the line should read.. start flrig make sure its working, and open dire wolf after?

PTT RIG 2 localhost:12345
 

I tried the "PTT RIG 2? localhost:12345" and it complained with the error: "Retrying Hamlib Rig open..."

So far, in direwolf.conf I have tried all of the following, or some variation:
#
#PTT COM1 RTS
#PTT COM1 RTS -DTR
#PTT /dev/ttyUSB0 RTS
#PTT RIG 2 localhost:4532
#PTT RIG 2 localhost:7342
#PTT RIG 2 localhost:12345
#PTT /dev/ttyUSB0 RTS -DTR
# PTT is a symlink for /dev/ttyUSB0
PTT RIG 1020 /dev/PTT 4800
#PTT RIG 1020 /dev/ttyAMA0 4800

The only one that seems to work is the /dev/PTT, where PTT is a symlink for /dev/ttyUSB0.

On the good news front, I did find that somewhere along the line I had turned off the beacon for the Igate. Once I uncommented (#) that, the beacon is now running in both XASTIR or YAAC,
I now see K1YPP-10 showing up in aprs.fi.
However, I don't see K1YPP-7 showing up from my FT5-D sends out a beacon. I am seeing beacons from other stations in the area showing up on the map. They also show up in the little window in the lower-left corner of XASTIR, all except my own, that doesn't show up. If I go out on my deck with the FT5-D and its small antenna, I do show up in aprs.fi via a superstation about 20 miles away, but my Igate just 100 ft away doesn't capture it.
Oh, the big red error message only showed up once in Direwolf when using YAAC, but shows up often when using XASTIR. See the first post for that error.

Here is the current config file for Direwolf:

dennis@raspberrypi:~ $ cat direwolf.conf
?
ADEVICE? plughw:3,0
?
CHANNEL 0
#
MYCALL K1YPP-10
#
MODEM 1200
#MODEM 9600
#
#PTT COM1 RTS
#PTT COM1 RTS -DTR
#PTT /dev/ttyUSB0 RTS
#PTT RIG 2 localhost:4532
#PTT RIG 2 localhost:7342
#PTT RIG 2 localhost:12345
#PTT /dev/ttyUSB0 RTS -DTR
# PTT is a symlink for /dev/ttyUSB0
PTT RIG 1020 /dev/PTT 4800?
#(The one above is the one that currently sorta works)
#PTT RIG 1020 /dev/ttyAMA0 4800
?
AGWPORT 8000
KISSPORT 8001
PBEACON delay=1? every=30 overlay=S symbol="digi" lat=27^15.27N long=082^30.52W power=5 height=15 gain=1 comment="Sarasota FL" via=WIDE1-1
?
#? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?#
#? ? ? ? ? ? ?APRS DIGIPEATER PROPERTIES? ? ? ? ? ? ? ? ? ? #
#? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?#
DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
# tried above with and without TRACE

IGSERVER noam.aprs2.net
?
# You also need to specify your login name and passcode.
IGLOGIN K1YPP-10 12675
?
PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=27^15.127N long=082^30.52W

#PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=T lat=42^37.14N long=071^20.83W
?
# To relay messages from the Internet to radio, you need to add
# one more option with the transmit channel number and a VIA path.
?
IGTXVIA 0 WIDE1-1,WIDE2-1
?
IGTXLIMIT 6 10
?
So, in summary, what I know so far is
-The FT-817nd is responding to Direwolf commands via CAT,
-aprs.fi sees the K1YPP-10 beacons,
-YAAC is communicating with Direwolf, but doesn't show any stations, including my K1YPP-7, but does show ONLY K1YPP-10 on the map
-The big red error message is still there in XASTIR, but seems to be rare in YAAC.
-My local transmit isn't making it through the Igate and doesn't appear to show up in Direwolf at all.

Anyway, that is the quick summary.
I'm open to any suggestions, this is really frustrating.

Thanks
Dennis, K1YPP
Sarasota, FL
 

Step one is rx packet with good success?

so you should be able to ignore PTT and it sounds like you solved PTT anyway.?


The radio sound should be consumed by direwolf and you should see raw packet decodes on the screen with every brrrap. If you don¡¯t see text and hear noises adjust the volume sliders and such till your decode rate is high quality. Volume matters a lot here to be good.?


K
 

Yes, I'm seeing lots of packets and decoding them. The map in XASTER fills right up, the one in YAAC doesn't show any. If I look in the decode texts, it is loaded with stations, except for mine. The audio in Direwolf is running around 50-68. I'm not certain what you mean by "Step one is rx packet with good success" Is that a question, then if so, I would say there are plenty of packets decoding.


It is really odd that YAAC isn't showing any real connection with Direwolf, it doesn't show any raw packets in that list or radio lists, etc. There must be some link missing between YAAC and Direwolf. XASTIR is closer to working correctly. It show stations on the map, and show lots of raw packets. The only thing it doesn't show is my K1YPP-7 packets from my handheld. There must be some parameter that I am just totally missing, but what? My Igate function is picking up my K1YPP-7, yet NI4CE-10, which is I think about 20-30 miles away, does.

If I look at the RAW packets on aprs.fi for K1YPP-10, it mostly looks good, I do see a few dups in red, but I don't think that is causing any of my current problems, I suspect you can see those as well.

Thanks for throwing out suggestions, it is really close at this point.

Dennis, K1YPP

1 - 10 of 10