开云体育

Hello Lynn,

alsamixer -c 1

direwolf receives with this setup with no issues.? But when it tries to transmit, I see the red/pink/magenta [0H] line with the packet, but the SignaLink PTT light doesn't go red and the radio doesn't key up.? The Rx volume control on the SignaLink does affect the audio level of the receive packets.? But I find it strange that alsamixer only shows one control.

Signalink units have limited controls via alsamixer as some of their controls are ONLY available via hardware POTS on the front of the unit.? There is the F3 view to set playback levels and F4 view for microphone levels.?? The key setting here is that you must increase your playback levels higher and higher until the TX LED on the Signalink lights up.? Unless you can get that LED to light up, you aren't keying the radio.

Another test you can do is connect a set of headphones to the back of the Signalink and see if you can hear the transmitted audio you expect to be coming from Direwolf.? If you don't hear anything, you have some form of a configuration error.

I have a DINAH audio interface on a different Pi and alsamixer shows two controls, one for Speaker and one for Mic, and a 3rd for Auto Gain Control.? The Pi with the DINAH and direwolf has no trouble keying the transmitter, both the IC-706MKIIG or an Alinco DR-135 both using the same 6 pin mini-din connector

These use different sound chips and have different controls.? If I was to recommend it, I would recommend to use the DINAH over the Signalink.

--David
KI6ZHD

开云体育

Greetings,

I'm trying to get direwolf on a Raspberry Pi to use a SignaLink USB as the audio interface to an IC-706MKIIG.? I've used this SignaLink/radio combination from Windows for many years, but would like to try it now from a Pi.? Here's what I'm seeing so far (removing the devices that aren't the SignaLink):

lsusb
Bus 001 Device 004: ID 08bb:29c6 Texas Instruments PCM2906C Audio CODEC

aplay -l
card 1: CODEC [USB AUDIO? CODEC], device 0: USB Audio [USB Audio]
? Subdevices: 1/1
? Subdevice #0: subdevice #0

alsamixer -c 1

direwolf receives with this setup with no issues.? But when it tries to transmit, I see the red/pink/magenta [0H] line with the packet, but the SignaLink PTT light doesn't go red and the radio doesn't key up.? The Rx volume control on the SignaLink does affect the audio level of the receive packets.? But I find it strange that alsamixer only shows one control.

I have a DINAH audio interface on a different Pi and alsamixer shows two controls, one for Speaker and one for Mic, and a 3rd for Auto Gain Control.? The Pi with the DINAH and direwolf has no trouble keying the transmitter, both the IC-706MKIIG or an Alinco DR-135 both using the same 6 pin mini-din connector.

Any/all things to check would be welcome, especially if someone is actually using a SignaLink USB with direwolf on a Raspberry Pi!

开云体育

Hello VK8MT,

How did you install direwolf?? Did you get the program from the Raspberry Pi OS repos or did you manually download it from somewhere else?? Anyway, can you send the list the output from the following command?

?? dpkg -l | grep -e direwolf -e hamlib

--David
KI6ZHD

Hi

I'm get the error described on page 21 of the User Guide, 'direwolf: error while loading shared libraries: libhamlib.so.4: cannot open shared object file: No
such file or directory.? The issue is that I don't understand the resolution which states the following: -

One solution is to define an environment variable.
export LD_LIBRARY_PATH=/usr/local/lib
You will probably want to put this in your ~/.profile, or similar, file that gets run when you log in.

I don't know how to do this.? Any help would be greatly appreciated. This is on a fresh install of raspbian, (Release date: April 4th 2022 System: 32-bit).

THanks?

?

开云体育

Hello Neil,

I have read your suggestions carefully, and I have some updates, responses, and questions.

Rob already provided a set of initial answers to your packet questions so I won't duplicate the answers here.? That said, here are some "intro to packet radio links" that might help you learn more:

??

What does 'callsign+SSID' mean?? In my previous experience, I just knew about callsigns, and the number at the end(e.g. n8ssw-1 usually was the mailbox) which I always assumed was just a different radio(or service) being operated under the same callsign.

I will add to Rob's previous reply that the different SSID numbers really depend on what frequency you're on as different system might have different defacto standards.? The APRS network has the following SSID standards:

??

As a counter example, here in Northern California on 145.050, we have the de-facto SSID standard of:

?? 0 : keyboard to keyboard SSID
?? 1 : PBBS
?? 2 : generally not used
?? 3 : generally not used
?? 4 : generally not used
?? 5 : node or digi
?? 6 : generally not used
?? 7 : node or digi
?? 8 : generally not used
?? 8 : generally not used
? 10 : generally not used
? 11 : generally reserved for netrom connections that automatically count from -15 downwards per hop
? 12 : generally reserved for netrom connections that automatically count from -15 downwards per hop
? 13 : generally reserved for netrom connections that automatically count from -15 downwards per hop
? 14 : generally reserved for netrom connections that automatically count from -15 downwards per hop
? 15 : generally reserved for netrom connections that automatically count from -15 downwards per hop


On Winlink frequencies like 145.630, you typically only see:

? 10 : winlink station

What does 'DIGI addressing' mean?

I did not think to try the APRS frequency.? I don't know much about APRS and assumed that it couldn't be manually interfaced.

It really depends on what equipment aka TNCs are being used. Unless the operators explicitly disabled the functionality, most TNCs will still have many of the basic NODE functionality still available.? To find out if anything is really there, you will have to make packet connection attempts to every SSID up to say SSID 11 to see if something will answer back or not.? It's a tedious thing but if you write it down, you can use this in the future to run tests, hop around on the APRS network, etc.

One of the biggest headaches that I have is not having two of anything making loopback tests difficult.? More on that later.? I don't have two serial ports.? I don't have two available sound cards.? I don't have two sets of cables.? Maybe there is a lesson here.

To be honest, there *is* ways to create ALSA loopback interfaces but it's 1) rather complex and 2) pretty useless.? Even if you had an emulated soundcard, how would that prove to you that you had a working station?? Yes, you might be able to prove that the Linux AX.25 stack is functioning but 99% of people's issues are on physical soundcard's audio levels, issues interfacing to the RF radio, dealing with RFI issues, etc.

In the meantime after some begging, I eventually found two TNC's that I could use to test: a Kantronics KAM+ and an AEA PK-900.? I couldn't read anything but gibberish from the KAM despite trying every combination of baud, data, parity, and stop bits(even a factory reset couldn't help).? I could talk to the PK-900 over the serial port, but I lacked proper interface cables for this TNC with any of my radios.

Did you follow the KAM+ manual on what it's default serial port speed is?

Eventually I discovered that I could put direwolf on VOX, use my single serial port to talk to the PK-900(formerly used for RTS PTT with direwolf), then use a 3.5mm audio jack cable to connect audio out to the input audio of the PK-900.? This only allowed one-way communication, but it worked.? I was able to connect and send text to the PK-900 thus verifying that direwolf can transmit. Eventually the PK-900 bombed complaining about unacknowledged packets, but it was a successful one-way test.

Ok.. that's a positive step though using VOX beyond anything but a test is not recommended due to all kinds of timing issues.?

1. I was trying to connect to stations that just ignored me completely(not even a NAK?)

Either this or the remote stations cannot decode your packets because:

?? 1. Maybe your antenna is not in a good location : ideally it's on top of your roof and is as high as possible.? Don't even try to do packet radio with an antenna that's inside your home as there will be too much signal attenuation from your home's structure, too much interference from other electronics in your home, etc.

?? 2. Maybe your antenna doesn't have enough gain to focus the RF signals to the remote station(s).? Basic ground plane / J-pole / etc antennas will work but they aren't good performers.

?? 3. It's not clear what radio you're running but ideally it's a quality radio with a good receiver and you're transmitting at at least 25 watts

?? 4. Your audio levels in/out of your radio need to be reasonably close to correct.? It's better to be too low than too high as distortion will destroy the AFSK modem tones and nothing will be decoded on either station

2. My output audio level is sub-optimal and results in a signal that can't be decoded.

I read the webpage on tuning the AFSK audio.? I am using a Asus Xonar usb sound card.? In linux, the alsamixer program doesn't give me a continuum of values.? For example, some gain controls can be 100, 50, or 0 with nothing in between.? So I will have to play a bit to see if I can tune better.? But I was led to believe that 1200 bps packet was pretty insensitive to volume levels.? But I'm trying to find a local who has a FM deviation meter.? Or if I were confident that audio level was the only problem, I could just diddle with the settings until things mostly worked.

1200bps AFSK packet radio is pretty forgiving but I wouldn't say it's insensitive to volume levels.? They need to be roughly right both on RX and TX.? I'm not familiar with that sound card but if the LInux driver for it lacks the granularity that you would expect, I would recommend to get a different soundcard.? You can get a Syba USB sound device for $9 which is known to work well with DIrewolf.? There are also many other sound devices that have more features, etc. if you want to afford them.? Here are some ideas:

??

On the topic of open squelch and DCD.? The old TNC's didn't have a sophisticated carrier detect, and I had been bitten by the problem of an open squelch preventing transmit.? I thought that I saw the same behavior in direwolf.? It turns out that it wasn't quite the case.? What seemed to be the problem was a nearby mobile phone charger confusing the carrier detect in direwolf which was avoided by using the squelch.? After removing the charger, direwolf will transmit even with an open squelch.

Yeah.. the whole interference due to local electronics is a major pain for new HAMs.? Great to hear you found the source of interference for that specific frequency but as you move around to other possible packet frequency, you will have to do it all over again.? This is where I recommend to buy an inexpensive RTL SDR which can show you 2.5Mhz worth of spectrum at a time which makes it very easy to see how RF quiet or noisy your home really is.? By using a simple loop antenna, it can be a fantastic tool to locate interference generators.

On the whole, this has been an interesting and soul-searching adventure.? In order to find the various pieces that I needed, I had to dig deep into all of the boxes of electronics that my late father had collected through his life.? When he had died, I had the luxury of just piling his stuff into a spare building for later rather than having to get rid of stuff.? The stuff is quite wonderfully disorganized, and I don't even recognize half of it. But there useful bits such as finding the bag of serial port adapters to connect the tnc.? Among the interesting things that I found were the Timex Sinclair 1000 that my brother got at a yard sale, the nano vna that I lost a couple years ago, my dad's ham radio logbook from the 1960's, and a hand-drawn schematic of the TNC interface cable that I used in the 1990s(can't find the actual cable though).

The scavenger hunt can be fun.? Try posting pictures of things you don't recognize to a local HAM club's email list / Slack channel / etc. and see if they can help you identify stuff.

Here is a dump of axlisten -8ar on 144.390 MHz.

ax0: fm W8JES to APU25N via K8TIH* WIDE1* K8UI-1* WOOSTR* K8GPS-10* WIDE2* ctl UI^ pid=F0(Text) len 59 08:25:19.512045
=4103.48N/08338.65W#PHG82804/Findlay's I-Gate & Wide1 Digi

Ok.. here is how to interpret this:

- "ax0" is the interface name on your Linux machine as configured in /etc/ax25/axports

- You received a packet from "W8JES"

- This packet was sent to "APU25N" which in the APRS standard, is actually an identifier of that station's equipment.? If you look at , you can see that this is coming from a Windows computer running the UIView APRS program - nice program but very obsolete these days

- See the "*" next to "K8TIH*" and the other stations?? That shows what stations heard and digipeated the original packet from W8JES.? Names like "WIDE1-1" is an APRS term to mean "nearby digipeaters only, don't digipeat this packet very far".? Names like "WOOSTR" is an ALIAS for some other TNC on frequency.? That's not illegal but not very common either.? Finally, "WIDE2" is wrong.? It should be "WIDE2-1" but maybe some TNCs view that as legal.? This setting is similar to the WIDE1-1 but this one means, go ahead and digipeat this packet farther away.? This is realistically only needed for more rural areas where there are few digipeaters around you.? The "WIDER" you let you packet go, the more flooding it creates and starts to bog down the network.?

- The payload of the message was "=4103.48N/08338.65W#PHG82804/Findlay's I-Gate & Wide1 Di" which is a non-compressed APRS packet starting out with the station's GPS coordinates, the PHG term is communicating the station's type, antenna type, and rough RF power ( ). The last part is just a helpful comment from the operator who's name seems to be Findlay who says this is a local Interface gateway (I-gate) and and local WIDE1-1 digipeater


Anyway.. so from your listen log, you now have a list remote stations that you can hear. ? I would recommend to look up each of these callsigns+SSID on and see where they are located.? Do you think they are close by and they should hear your station?? If so, try connecting to each of their possible SSIDs:

W8JES
KC8PVB
KD6XH-2
N3DXC-2
N8GD-2
N8GD-1
K8GI-5
N8ZSA-1
K8UI-1
K8QIK-5
NV8P-1
N8JLK-7

--David
KI6ZHD

Folks,

Updated information regarding Direwolf and Hamlib for the IC-F8101.? I have it properly working FINALLY!

Step one.

Download and compile Hamlib for your platform.? The version must be the latest dev from April 16, 2022 or later.? What this provides is the proper PTT commands for the radio so that the USB sound card may be used to modulate the radio.? PLEASE NOTE that if you use the hamlib libraries for other programs, that I have NO IDEA what this will do to your other programs.? This information is provided in order to enable Direwolf to work with this radio properly.

Compile and install Hamlib according to it's instructions:
generally,

./bootstrap
./configure
make
sudo make install

Step two.

Download or clean the Direwolf source.? I am using the current dev snapshot (the "git checkout dev" step).

Edit src/ptt.c
Go to line 1311 or find the line in that vicinity which looks like:

int retcode = rig_set_ptt(rig[chan][ot], RIG_VFO_CURR, ptt ? RIG_PTT_ON : RIG_PTT_OFF);

?

and change "RIG_PTT_ON" to "RIG_PTT_ON_DATA" and save the file.

int retcode = rig_set_ptt(rig[chan][ot], RIG_VFO_CURR, ptt ? RIG_PTT_ON_DATA : RIG_PTT_OFF);

Compile and install according to the instructions for your platform.

The direwolf.conf PTT line for this radio will be:

PTT RIG 3086 /dev/ttyUSBn 38400

where the "n" in ttyUSBn corresponds to the second of the two USB ports created by the radio when it is plugged in (the "B") port.? Generally on a PC with only the radio plugged into it for USB serial devices, this will be /dev/ttyUSB1.? Also, be sure and set the radio to either "Autobaud" for the serial port or explicitly set it to 38400 (preferred) in the programming.

Now, when Direwolf PTT's the radio, it will modulate the radio via the sound card.

Hi Niel,

See if Direwolf decodes anything on 145.01 and 145.07.? You might have to park the radio on each frequency for a while.? The nodes most likely send periodic beacons.? If you copy anything from a particular node callsign, try connecting to it.? Here's a packet node map of your area:

KB8RCO and KI6ZHD,

The callsign here is n8ssw(original).? Pleased to meet you.

I have read your suggestions carefully, and I have some updates, responses, and questions.

I will post the results of axlisten -8ar of 144.390 MHz at the end.

I haven't used packet radio since 1993 when I was 13-14.? My knowledge was limited to what details the local hams mentioned. None of them were electrical engineers, computer scientists, or patient with explaining technical aspects to a teenager who likely already had far more experience using computers.? So my current packet knowledge is dismal especially concerning the jargon.

How is SSID used in the context of packet radio?? I have only heard the term used in the context of wifi.

What does 'callsign+SSID' mean?? In my previous experience, I just knew about callsigns, and the number at the end(e.g. n8ssw-1 usually was the mailbox) which I always assumed was just a different radio(or service) being operated under the same callsign.

What does 'DIGI addressing' mean?

I did not think to try the APRS frequency.? I don't know much about APRS and assumed that it couldn't be manually interfaced.

Also the distinction between connected session requests and packet digipeat requests is foreign to me.? What I always did in the past was connect to a digipeater then connect to something else using the interface of the digipeater.

One of the biggest headaches that I have is not having two of anything making loopback tests difficult.? More on that later.? I don't have two serial ports.? I don't have two available sound cards.? I don't have two sets of cables.? Maybe there is a lesson here.

In the meantime after some begging, I eventually found two TNC's that I could use to test: a Kantronics KAM+ and an AEA PK-900.? I couldn't read anything but gibberish from the KAM despite trying every combination of baud, data, parity, and stop bits(even a factory reset couldn't help).? I could talk to the PK-900 over the serial port, but I lacked proper interface cables for this TNC with any of my radios.

Eventually I discovered that I could put direwolf on VOX, use my single serial port to talk to the PK-900(formerly used for RTS PTT with direwolf), then use a 3.5mm audio jack cable to connect audio out to the input audio of the PK-900.? This only allowed one-way communication, but it worked.? I was able to connect and send text to the PK-900 thus verifying that direwolf can transmit. Eventually the PK-900 bombed complaining about unacknowledged packets, but it was a successful one-way test.

Given that direwolf was already logging packet activity that it heard, I think that this test confirm that direwolf itself is working correctly.

That seems to leave two possibilities:

1. I was trying to connect to stations that just ignored me completely(not even a NAK?)

2. My output audio level is sub-optimal and results in a signal that can't be decoded.

I read the webpage on tuning the AFSK audio.? I am using a Asus Xonar usb sound card.? In linux, the alsamixer program doesn't give me a continuum of values.? For example, some gain controls can be 100, 50, or 0 with nothing in between.? So I will have to play a bit to see if I can tune better.? But I was led to believe that 1200 bps packet was pretty insensitive to volume levels.? But I'm trying to find a local who has a FM deviation meter.? Or if I were confident that audio level was the only problem, I could just diddle with the settings until things mostly worked.

On the topic of open squelch and DCD.? The old TNC's didn't have a sophisticated carrier detect, and I had been bitten by the problem of an open squelch preventing transmit.? I thought that I saw the same behavior in direwolf.? It turns out that it wasn't quite the case.? What seemed to be the problem was a nearby mobile phone charger confusing the carrier detect in direwolf which was avoided by using the squelch.? After removing the charger, direwolf will transmit even with an open squelch.

On the whole, this has been an interesting and soul-searching adventure.? In order to find the various pieces that I needed, I had to dig deep into all of the boxes of electronics that my late father had collected through his life.? When he had died, I had the luxury of just piling his stuff into a spare building for later rather than having to get rid of stuff.? The stuff is quite wonderfully disorganized, and I don't even recognize half of it. But there useful bits such as finding the bag of serial port adapters to connect the tnc.? Among the interesting things that I found were the Timex Sinclair 1000 that my brother got at a yard sale, the nano vna that I lost a couple years ago, my dad's ham radio logbook from the 1960's, and a hand-drawn schematic of the TNC interface cable that I used in the 1990s(can't find the actual cable though).

Alright, back to business.

Here is a dump of axlisten -8ar on 144.390 MHz.

ax0: fm W8JES to APU25N via K8TIH* WIDE1* K8UI-1* WOOSTR* K8GPS-10* WIDE2* ctl UI^ pid=F0(Text) len 59 08:25:19.512045
=4103.48N/08338.65W#PHG82804/Findlay's I-Gate & Wide1 Digi
ax0: fm KC8PVB to APWW11 via N8WCT-1* WIDE1* K8GPS-10* WIDE2* ctl UI^ pid=F0(Text) len 41 08:25:48.623098
@122542h4001.87N/08310.43W-APRS-IS i-Gate
ax0: fm KD6XH-2 to S9UR1V via K8GPS-4* WIDE1* K8GPS-10* WIDE2* ctl UI pid=F0(Text) len 35 08:26:03.783290
`o]Ql"l>/'"6h}MT-RTG|!>%C'C|!wB(!|3
ax0: fm N3DXC-2 to APN001 via K8UI-1* WOOSTR* K8GPS-10* WIDE2* ctl UI pid=F0(Text) len 55 08:26:04.459093
@181226z4047.84NI07858.21W&PHG7360/U=13.8V,T=8.5C/47.3F
ax0: fm N8GD-2 to APOT21 via WIDE2-2 ctl UI pid=F0(Text) len 31 08:26:16.291257
!4022.44N/08042.13W# 13.5V 52F
ax0: fm N8GD-1 to APU25N via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 60 08:26:21.293647
}N8GD-2>APOT21,TCPIP,N8GD-1*:!4022.44N/08042.13W# 13.5V 52F
ax0: fm K8GI-5 to BEACON via WOOSTR* K8GPS-10* WIDE1* ctl UI pid=F0(Text) len 47 08:26:26.554015
@181226z4108.95NI08121.51W&2-way iGate, Kent OH
ax0: fm N8ZSA-1 to APWW11 via MTCLMN* K8GPS-10* WIDE2* ctl UI^ pid=F0(Text) len 56 08:26:33.044594

181226zDX: MTCLMN 28.4mi 118. 12:14 4235.83N 08252.68W

ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 59 08:26:43.097952
;BROOKEEOC*121108z4012.60N/08038.70WoBrooke County EMA/EOC
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 78 08:26:47.871876
;HANCOEOC *181036z4031.88N/08037.32WoHancock County EMA/EOC & 911 Call Center
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 77 08:26:52.006706
;JEFFCOEOC*161104z4021.56N/08042.44WoJefferson Cty EMA/EOC & 911 Call Center
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 77 08:26:56.568489
;443.775OH*272008z4022.45N/08042.13Wr443.775MHz +500 WD8IIJ/SWARC UHF Reptr.
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 78 08:27:04.010735
;146.94NWV*181816z4023.75N/08031.68Wr146.940MHz -060 W8CWO/SWARC Fusion Rptr.
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 76 08:27:08.030492
;SWARC-MTG*161113z4020.17N/08035.59WESWARC Monthly Business Mtg 7PM 1st Wed
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 77 08:27:11.816412
;SWARC-DIN*161111z4022.55N/08042.96WESWARC Dinner Mtg @ Murray's 5PM 3rd Wed
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 78 08:27:15.550772
;N8GD-R?? *291006z4020.57N/08037.17WIN8GD EchoLink Rptr/Node #730484 147.060+
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 78 08:27:19.676746
;TERA-MTG *231044z4022.44N\08041.94W+Tri-Co. ERA Mtg. 2nd Thu 6PM @ Wint. UMC
ax0: fm K8UI-1 to APN383 via WOOSTR* K8GPS-10* WIDE2* ctl UI pid=F0(Text) len 67 08:27:22.711605
!4117.93NS08229.12W#PHG4460/W3, OHn-N Berlin HTs. OH. Ohioaprs Net
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 78 08:27:23.571585
;WNTRMS?? *171725z4023.06N/08043.07W&Winlink RMS Gateway 145.07 MHz, VHF Only
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 76 08:27:27.996620
;WINTOH?? *161053z4023.06N/08043.06WBN8GD/TERA Packet BBS 145.07 MHz EMCOMM
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 78 08:27:31.700487
;WINTVL?? *121028z4023.06N/08043.08WnWintersville OH Pkt Digi/Node 145.07 MHz
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 78 08:27:35.981395
;JEFFOH?? *161059z4022.44N/08041.96WnWintersville OH Main Pkt Node 145.07 MHz
ax0: fm N8GD-1 to WIDE1-1 via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 59 08:27:41.787051

180906ziGate in Wintersville, OH, running UI-View32 V2.03

ax0: fm K8QIK-5 to APNU19 via K8GPS-10* WIDE2-1 ctl UI^ pid=F0(Text) len 65 08:27:52.352324
;147.030x *111111z3944.85N/08235.65Wr 147.030Mhz T71.9 R50M K8QIK
ax0: fm NV8P-1 to APSAR via K8YSE-1* WIDE1* NEWBRY* WOOSTR* K8GPS-10* WIDE2* ctl UI pid=F0(Text) len 91 08:27:53.353954
}K8GPS-4>APMI06,TCPIP,NV8P-1*::K8GPS-4 :PARM.Vin,Temp,Rx1h,Dg1h,A5,O1,O2,O3,O4,I1,I2,I3,I4
ax0: fm N8JLK-7 to APDW17 via NEWBRY* WIDE1* WOOSTR* K8GPS-10* WIDE2* ctl UI pid=F0(Text) len 76 08:27:54.234027
!4121.47NS08141.21W#PHG7240144.390MHz iGate (Yaesu FT-8900R, RPi4, DireWolf)
ax0: fm KC8PVB to APWW11 via K8GPS-10* WIDE1* WIDE2-1 ctl UI^ pid=F0(Text) len 19 08:28:29.145129

181228zAPRSISCE/32

ax0: fm N8GD-1 to APU25N via N8GD-2* WIDE2-1 ctl UI^ pid=F0(Text) len 60 08:28:49.602716
}N8GD-2>APOT21,TCPIP,N8GD-1*:!4022.44N/08042.13W# 13.7V 52F


Neil H. Gray (n8ssw)

开云体育

Hello Neil,

Welcome back to packet!

Everything looks like it should work properly, but I can't connect to any stations.? I also currently don't have any working legacy packet stations at my disposal for testing.? Neither do any of my ham neighbors.

Just to be clear hear, you're saying you have one packet station and you're 99% sure there aren't any other classic packet stations near you?? If so, how do intend to test your setup?? You need something to connect to.? The easiest place to try is your local APRS frequency.? You didn't give a callsign or a location but if you're in the US, that would be on 144.390.? Some of the digipeaters used for APRS also allow for connected sessions to make node connections, etc.

The direwolf text output shows traffic from the stations that it hears on my radio.

Ok.? Make sure the received packet levels are at around 50 or so according to Direwolf.

I do the kissattach, kissparms steps and then run linpac -m.

When I try to connect to a station from linpac, I see a message in the direwolf log that I transmitted.? I can also listen with a second radio with an open squelch and hear my connect packet transmission.? It sounds like normal 1200 baud packet to my ear(though the message does seem brief).

Ok.. that sounds like you have almost everything working.? That's great progress.? I would now recommend to read the bottom part of this page on how to tune your 1200bps AFSK signal:

??

However I never get a response.? I'm not running the best station, but the local digipeater is in a very good location.? I can't imagine that station isn't hearing my transmission.

Digipeaters DON'T have to respond to connected session requests.? What they DO need to do is respond to packet digipeat requests.? In another terminal window, run the command depending on your chosen Linux distribution (you said you were using Debian):

?? sudo axlisten -8ar

You should see all the incoming packet decodes from the Linux AX.25 stack side.? Send us a page or two of this output so we can give you some remote station callsign+SSID ideas to try sending UI packets to using either Linpac's F10 key UI view or using LInux's "beacon" command.

Packet radio breaths nostalgia for a variety of reasons.? One of the many problems that I solved on my own during this recent direwolf adventure was discovering that the reason that my radio was not transmitting was due to my squelch being set too low and never having a clear channel.? I suddenly had a clear memory of spending hours on the same dumb mistake a quarter century ago.

It's recommended to run Direwolf with OPEN SQUELCH.? It uses a software DCD mechanism to detect when there is a signal which a) helps low signal decodes, b) simplifies constantly changing squelch settings, etc.? Open your squelch wide open.

--David
KI6ZHD
(author of Linpac)

The Appalachian Trail Golden Packet event? is an annual tradition started by WB4APR in 2009.? The goal is to set up 15 temporary VHF/UHF APRS stations on mountain tops, along the Appalachian Trail, and send messages end to end between Georgia and Maine.? This year it is on July 16.

?

For more information, see?? ? and join the discussion?

?
73,
John WB2OSZ

Hello everyone.

I am looking for some advice on troubleshooting direwolf+linpac.

The madness(and fun) started a few days ago when I learned that direwolf existed, I immediately jumped at the idea of spinning up my first packet radio station since the early 1990s.? The fx.25 itself seemed to be worth the effort.

I'm experienced at linux and wasn't expecting this to take more than an hour, but I've been stumped for several evenings with the setup.

Everything looks like it should work properly, but I can't connect to any stations.? I also currently don't have any working legacy packet stations at my disposal for testing.? Neither do any of my ham neighbors.

Here's how things stand:

The direwolf text output shows traffic from the stations that it hears on my radio.

I do the kissattach, kissparms steps and then run linpac -m.

When I try to connect to a station from linpac, I see a message in the direwolf log that I transmitted.? I can also listen with a second radio with an open squelch and hear my connect packet transmission.? It sounds like normal 1200 baud packet to my ear(though the message does seem brief).

However I never get a response.? I'm not running the best station, but the local digipeater is in a very good location.? I can't imagine that station isn't hearing my transmission.

Nothing ever appears in the linpac monitor window despite plenty of information in the direwolf monitor log.

I am using the packages in Debian which has direwolf version 1.6.

As far as I know, there isn't a way to make a loopback connection for testing direwolf.

And ideas?? I'm willing to entertain all suggestions.? No idea is too dumb to try.


Thanks in advance,

Neil


P.S.

Packet radio breaths nostalgia for a variety of reasons.? One of the many problems that I solved on my own during this recent direwolf adventure was discovering that the reason that my radio was not transmitting was due to my squelch being set too low and never having a clear channel.? I suddenly had a clear memory of spending hours on the same dumb mistake a quarter century ago.

or perhaps
direwolf -t 9

which will show a range of text colour combinations that it supports.
Then you can take your pick as to which suits best.

Try

I have sight issues and the default white background bothers me. I can go into "Properties" by right clicking title bar and I see 2 choices one for "colors" and the other for "terminal" so I am confused on which is the right tab to be in.? If I try changing colors it doesnt do anything. Please help! I want a BLACK background with GREEN and BLUE text.

This is the working UI "chatting" test build with hamlib PTT on the IC-F8101.? I am just sitting on 30m APRS channel to
gather up some receptions.? Doing this forced me to flesh out my old UIKISSUtils class, so worth the fun diversion.

John, your debugging info switches helped out a LOT.? Thanks for those.

Ah yup.? just had to blow away the build directory and start again .

hamlib latest and direwolf latest confirmed on IC-F8101 via USB CI-V control and USB sound card when set to the proper operating mode for the sound card.

Rick,
Did it actually require *removing* direwolf or just a recompile/reinstall?

Having a similar situation with the IC-F8101 rig (3086).? I helped the hamlib folks get that radio working but direwolf complains.

Hamlib error: Unknown rig model 3086.? Run "rigctl --list" for a list of model numbers.

rigctl is working fine with the radio, so it's not a hamlib issue.

Mitch