Greetings David!

After banging into the "Error writing" issue, I used your document to build direwolf DEV/1.8 on the most recent DRAWS hat image Raspbian GNU/Linux 11 (bullseye)
starting the direwolf service still fails but no longer hangs the service start

Jun 05 07:44:07? direwolf[15736]: Error writing "12" to /sys/class/gpio/export, errno=22
Jun 05 07:44:07? direwolf[15736]: Invalid argument
Jun 05 07:44:07? direwolf[15736]: It looks like gpio with sysfs is not supported on this operating system.
Jun 05 07:44:07? direwolf[15736]: Rather than the following form, in the configuration file,
Jun 05 07:44:07 direwolf[15736]: ? ? PTT GPIO ?12
Jun 05 07:44:07 direwolf[15736]: try using gpiod form instead. ?e.g.
Jun 05 07:44:07? direwolf[15736]: ? ? PTT GPIOD ?gpiochip0 ?12
Jun 05 07:44:07 direwolf[15736]: You can get a list of gpio chip names and corresponding I/O lines with "gpioinfo" comma>
Jun 05 07:44:07 systemd[1]: direwolf.service: Main process exited, code=exited, status=1/FAILURE
Jun 05 07:44:07? systemd[1]: direwolf.service: Failed with result 'exit-code'.

You MAY want to add that installing gpiod and manually modifying the direwolf config is needed

73 KM6KEF

开云体育

All the details of what broke is covered earlier in this very thread:

?? /g/direwolf/topic/105914156


Regardless, downgrading the Raspberry Pi firmware, Linux kernels, etc. is a poor option.? You loose getting any security fixes, bug fixes, and ultimately various technology is (disruptively) moving forward and you will be ultimately fighting the inevitable.? Direwolf 1.8 (the DEV branch has the fix) for this long planned change.? I totally get the pain aspect of all this and we all feel it elsewhere be it disruptive changes from other projects like Python, etc.

--David
KI6ZHD

On Tue, Jun 4, 2024 at 12:45 AM, David Ranch wrote:

Hello Ian,

I have (and want to use) an old pac-comm 220 TNC [no comments please].? I am not interested in TCP/[AF]X25 Internet packet radio for now..

Ok.. and just to confirm, you 're running this hardware TNC at 1200bps AFSK right?? No a slower or faster mode.

port 1 300 baud HF, port? and 1200 comes later!

The direwolf+pi can hear and decode the initial "con MM7XXX" tones? from the pac-comm TNC-220.
BUT I cant make the pac-comm hear anything from direwolf+pi.
. . .
Sticking the headphones into the TX of the direwolf+PI - I hear what could be the right tones, I have checked the wiring of the plugs/sockets? into the TNC-220 etc and am happy.

This isn't an uncommon problem for new users to have the sound levels wrong.? Did you follow say this URL to tune your "playback" volume:

??

I checked out the instructions in the original pac-comm manual.? I will go and read the above soon.

How can I make the direwolf software generate a "connect CALLSIGN" from the command prompt?
I can telnet to port 8001 of direwolf and get a "cmd:" prompt - the message that appears on the TNC-220 - but I dont seem able to generate any tones when I issue a "call MM7XXX" command.

You cannot with just TELNET.? You need a higher level program using either AGW port, the TCP-KISS port, or the serial KISS port.? As WB9TEN mentioned, Windows based ipserial program included with Outpost PM will work.? You can also use one of these listed "terminal programs":

??

Is it possible to use a keyboard on direwolf as a "wee tester" to TX/RX data to-from a real TNC??

No.? You have to use an application to interface with Direwolf.

I have picked up paracon, put it on the PI and it works great with direwolf - it allows the old TNC commands "call XXX" to work between a pair of PIs.

[Yes, I know that the TNC-220 runs 2025-2225Hz as the mark/space tones and I have set up dirwolf to work "around" that set of frequencies rather than the 1600-1800 that direwolf starts with..... the dirwolf receives OK].

I am suspicious that the TNC-220 may be deaf.? The best alternative I can think of doing is captuing the outgoing packet on the pi and trying to replay it back into the TNC-220.

Thomas has already chimed in on this topic and that's why I wanted to confirm what SPEED you're trying to get the hardware TNC and software TNC to communicate at.

--David
KI6ZHD

Dave: I never thought of doing a digipeater - much easier than 2 x PI and all the leads!?

But the fact that the Pac-comm wont bi-direction communicate with a known working PI+dirwolf+paracon (that talks to another of the same) suggests that my pac-comm unit is deaf - the PI can see my outgoing messages OK, but I cant see the generated replies being accepted.....

I need some free hours and the 'scope.? I will let you know how things go.

Thomas thanks for the comments.
I had to change the regulator on the old beast and a bit of switch cleaner to the on-off.? Then it seems to talk to itself on loopback OK.
the [no commnts please] comment is that lots of groups start with "You dont want to do that!? Why not use X or Y or Z".? So I appreciate your input.

I am of an vintage where RS232 for computer comms was common - so I have all the tools and can check out RX/TX, baud parity and stopbits along with DTR and CTS and and and in my sleep.

I set up 2 x paracon software systems on 2 x PIs? talking to each other (PIs - set the tones to 2025-2225 in the config files, set up MYCALL to be MM7IRM in one and MX7IRM (no radio involved yet))? They talked to each other and I could open a session (con MM7IRM etc) and chat between the two systems.? So I am using different call signs in the lab.

Great. Loopback on the TNC-220 works, the PIs talk, But when I connect up the TNC to the PI, the PI can 'hear' the TNC, but not such luck the other way around.?

I cant seem to find a way to debug incoming data on the pac-comm.? as in trace on, monitor on, mcon on, and mcom dont seem to produce output.? Is there a way to get some "debug on" messages?

When I get a few minutes free I need to get a heatsink for the LM regulator AND get the scope out to see what I can find.? I have not yet looked at the schematic/circuit diagram, so I dont know where the loopback mode tests to - how far out to the port.

I have tried many different audio-out levels from the PI and none seem to trigger a response.....

Any debug clues welcome - I am sure the 'scope will reveal a lot.? If it does not the the logic analyser needs to appear on the kitchen table!

Iain

开云体育

Hello Ian,

I have (and want to use) an old pac-comm 220 TNC [no comments please].? I am not interested in TCP/[AF]X25 Internet packet radio for now..

Ok.. and just to confirm, you 're running this hardware TNC at 1200bps AFSK right?? No a slower or faster mode.

The direwolf+pi can hear and decode the initial "con MM7XXX" tones? from the pac-comm TNC-220.
BUT I cant make the pac-comm hear anything from direwolf+pi.
. . .
Sticking the headphones into the TX of the direwolf+PI - I hear what could be the right tones, I have checked the wiring of the plugs/sockets? into the TNC-220 etc and am happy.

This isn't an uncommon problem for new users to have the sound levels wrong.? Did you follow say this URL to tune your "playback" volume:

??

How can I make the direwolf software generate a "connect CALLSIGN" from the command prompt?
I can telnet to port 8001 of direwolf and get a "cmd:" prompt - the message that appears on the TNC-220 - but I dont seem able to generate any tones when I issue a "call MM7XXX" command.

You cannot with just TELNET.? You need a higher level program using either AGW port, the TCP-KISS port, or the serial KISS port.? As WB9TEN mentioned, Windows based ipserial program included with Outpost PM will work.? You can also use one of these listed "terminal programs":

??

Is it possible to use a keyboard on direwolf as a "wee tester" to TX/RX data to-from a real TNC??

No.? You have to use an application to interface with Direwolf.

[Yes, I know that the TNC-220 runs 2025-2225Hz as the mark/space tones and I have set up dirwolf to work "around" that set of frequencies rather than the 1600-1800 that direwolf starts with..... the dirwolf receives OK].

I am suspicious that the TNC-220 may be deaf.? The best alternative I can think of doing is captuing the outgoing packet on the pi and trying to replay it back into the TNC-220.

Thomas has already chimed in on this topic and that's why I wanted to confirm what SPEED you're trying to get the hardware TNC and software TNC to communicate at.

--David
KI6ZHD

Hi Iain,

It seems that I have overlooked something important when I first read and replied to your post.

[Yes, I know that the TNC-220 runs 2025-2225Hz as the mark/space tones and I have set up dirwolf to work "around" that set of frequencies rather than the 1600-1800 that direwolf starts with..... the dirwolf receives OK].

I foolishly assumed that you were looking at 1200 baud AFSK packet (as is common on VHF or higher frequencies). However your comment about 2025-2225Hz sounds like you are trying 300 baud packet on HF bands. Both Direwolf and your hardware TNC can do both. For Direwolf you control both the baudrate and the actual tone frequencies with the Modem command in the direwolf.conf file.

For your hardware TNC it is a bit more complex. The TNC has two radio ports where the factory default is that port 1 is used for 300 baud packet on HF and port 2 is used for 1200 baud packet on VHF. This default configuration can be altered with jumpers and it is possible to have both ports configured for 300 baud packet or both ports configured for 1200 baud packet. Since you say that Direwolf received a connection attempt from the hardware TNC, it appears that you are using the correct port and baud rate but those things can be deceiving! Direwolf can be incredibly sensitive (depending on the audio hardware) and I have seen it successfully pick up audio signals from a nearby packet station where the only connection between the two was a common ground.
Since your hardware TNC won't be decoding any packets if the baud rate or tone frequencies are wrong, this is something you should definitely double check.
Also be sure the issue "port 1" or "port 2" commands on your hardware TNC to ensure that you are monitoring on the correct radio port.

I can telnet to port 8001 of direwolf and get a "cmd:" prompt

Yes, you can but telnet to port 8001 but by default port 8001 is using the KISS protocol and you are not going to be able to generate a valid KISS frame by typing on your keyboard. You do need either a KISS or AGWPE protocol client applications to use Direwolf to transmit packet data other then beacons. For your test purposes, I would suggest configuring a beacon in direwolf.conf. If you are testing over the air, check the rules that apply to your country regarding how frequent you may be able to send those beacons.
If you are doing bench testing with Direwolf directly connected to the hardware TNC, you can make those beacons very frequent (like every 30 seconds in this example):
CBEACON dest=BEACON info="MM7xxxx testing packet station" every=0:30

73,
Thomas
KK6FPP

First, I'm not familiar with the TNC you are using but I do have a bit of experience with Direwolf.

I find that the easiest way to add keyboard functionality to Direwolf is with a client such as Outpost Igapwpe (PC only) or QtTerm. Either of those clients connect to Direwolf via an IP address (localhost if on the same computer as Direwolf) and either an AGW or KISS connection. With those clients, you don’t really have a function like “cmd:”. You put your callsign and the destination callsign in a setup menu, click connect and then you just start keyboarding. You start Direwolf first and then the client.

The other thing you can do is add a connected packet digipeater to Direwolf. The next two lines are what I use in a BBS system here in Goshen IN. You just need to add your callsign for “WB9TEN” with an SSID ID “-1” for your own callsigns. I’m not sure about the SSID in your country but the important thing is that you have to have two unique callsigns. If on a dummy or low power just make one up (P1RAT).

CDIGIPEAT 0 0
CBEACON every=30 info="+++ WB9TEN-7 Digipeater in Goshen In ?+++"

Then you can do a connect to yourself. For example, on my old MFJ-1270 TNC it would look like this:

Cmd:connect WB9TEN via WB9TEN-1

That bounces everything off of the digipeater in Direwolf and back to the original keyboard and you only need one keyboard. The instructions are in the Direwolf manual but you have to look for connected packet. The other digipeater is for APRS. Page 142 in my manual.

Hope this helps.

Dave
WB9TEN

Hi Iain,

I have (and want to use) an old pac-comm 220 TNC [no comments please].

Why not ? Don't think you are the only one that still owns and uses hardware from that era.

It sounds like you have the documentation for that hardware TNC and it also sounds that you have proper RS-232 serial communication between your computer and that TNC. That is a good start.

Since you conducted a loopback test of the TNC, be sure that you returned the loopback jumper back to its original position and that you turned "fulldup off" again (normal over the air operation is half-duplex).
Unfortunately the Pac-Comm TNC-220 doesn't have a Receive LED as visual indicator of incoming data.
This means you need to rely on the "monitor on" command to show incoming data on your serial connection.

Note that using two TNCs with the same callsign on the same frequency can (and often does) cause problems. If you are doing these experiments by yourself and only have your own callsign to work with, be sure to configure a different SSID on Direwolf and the hardware TNC (e.g. MM7xxx-4 and MM7xxx-8) to eliminate the possibility that the hardware TNC suppresses incoming data with its own id (I don't know whether or not it does, just trying to eliminate that possibility).

Depending on how your TNC to Radio interface cable is connected to the radio, it may be sensitive to volume controls on the radio (that is normally the case if you are using the speaker output of the radio to connect to the receive audio input on the TNC). This means it is possible that your volume is off or too low to be decoded but even more likely can mean that the volume is too high and the incoming data cannot be decoded because of the distortion created from the overpowering audio signal.

To eliminate issues with the radios or RF (two stations too close together can have a surprising amount of difficulty communicating!), you can test your hardware TNC by connecting the transmit audio output of Direwolf to the receive audio input of the TNC. When that works properly, you can continue to troubleshoot your RF packet reception issue.


73,
Thomas
KK6FPP

I have a problem.? I was trying to use direwolf to help me debug it, but I seem to be caught in a spiders web....

BACKGROUND
I am in the north of Scotland.? We dont have any "on air" TNC running here - but a group in Aberdeen are keen to get an "old school" system together.

I have (and want to use) an old pac-comm 220 TNC [no comments please].? I am not interested in TCP/[AF]X25 Internet packet radio for now..

Having been "on air" with the unit for a while I am not hearing any data..... One reason is we dont have many "old style" packet radio folk around here - but there is one guy a few miles away that I think I should be able to hear......

So I decided to test out my pac-comm? on the bench.? [It works when I use the internal loop-back jumpers as documented in the manual. ? The "cmd: connect MM7XXX.." command does what the manual says.

Ah ha I thought, I will stick direwolf on a PI and use that to rx/tx data to check all is OK.
Then the troubles started.

I set up direwolf to beacon out.

The direwolf+pi can hear and decode the initial "con MM7XXX" tones? from the pac-comm TNC-220.
BUT I cant make the pac-comm hear anything from direwolf+pi.
I dont know if the pac-comm is broken or if it wont respond to/hear a beacon signal.?
Will a TNC-220 decode a beacon- does anyone know?? I have no idea and cant figure it out from the manual.

Sticking the headphones into the TX of the direwolf+PI - I hear what could be the right tones, I have checked the wiring of the plugs/sockets? into the TNC-220 etc and am happy.

So here is the problem.
How can I make the direwolf software generate a "connect CALLSIGN" from the command prompt?
I can telnet to port 8001 of direwolf and get a "cmd:" prompt - the message that appears on the TNC-220 - but I dont seem able to generate any tones when I issue a "call MM7XXX" command.

Is it possible to use a keyboard on direwolf as a "wee tester" to TX/RX data to-from a real TNC??
[Yes, I know that the TNC-220 runs 2025-2225Hz as the mark/space tones and I have set up dirwolf to work "around" that set of frequencies rather than the 1600-1800 that direwolf starts with..... the dirwolf receives OK].

I am suspicious that the TNC-220 may be deaf.? The best alternative I can think of doing is captuing the outgoing packet on the pi and trying to replay it back into the TNC-220.

I would welcome clues and advice.

Iain

I am also having trouble getting PTT to toggle on GPIO25. This is on Bookworm on a Pi 3b with direwolf 1.6 which I installed using apt .Direwolf quits with this message: when I uncomment the PTT line in direwolf.conf ("PTT GPIO 25")

?Error writing "25" to /sys/class/gpio/export, errno=22


I looked at the Radio Interface Guide and tried gpiod as suggested but I'm still not seeing GPIO25 go high to transmit. Here is the message I get after changing to "PTT GPIOD gpiochip0 25":

Reading config file direwolf.conf
Config file line 196: Expected RTS or DTR after PTT device name.

Here are the non-commented parts of my direwolf.conf file:

ADEVICE ?plughw:1,0
CHANNEL 0
MYCALL KI7JS-10
MODEM 1200

# PTT GPIO 25 ?## this shuts down direwolf with errno=22
PTT GPIOD gpiochip0 25

AGWPORT 8000
KISSPORT 8001
DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
IGSERVER noam.aprs2.net
IGLOGIN KI7JS-10 XXXXX
PBEACON sendto=IG delay=0:30 every=30:00 symbol="igate" overlay=R lat=45.740418 long=-121.520083 COMMENT="KI7JS-10 igate | Direwolf 1.6, Pi3B+, Icom V800"
IGTXLIMIT 6 10

Except for PTT, direwolf is working: receives packets, decodes, forwards to internet, tries to retransmit packets.

Any suggestions to get it going??

In case it helps, here is some output from direwolf:

jayst@piwolf:~ $ direwolf
Dire Wolf version 1.6
Includes optional support for: ?gpsd hamlib cm108-ptt

Reading config file direwolf.conf
Config file line 196: Expected RTS or DTR after PTT device name.
Audio device for both receive and transmit: plughw:1,0 ?(channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Note: PTT not configured for channel 0. (Ignore this if using VOX.)
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 (205.209.228.99)
Check server status here http://205.209.228.99:14501

[ig] # aprsc 2.1.15-gc67551b
[ig] # logresp KI7JS-10 verified, server T2TEXAS
[ig] KI7JS-10>APDW16:!4544.43NR12131.20W&KI7JS-10 igate | Direwolf 1.6, Pi3B+, Icom V800

K1OSH-15 audio level = 15(5/3) ? [NONE] ? _||||||__
[0.3] K1OSH-15>APTT4,WIDE1-1,WIDE2-1:Battery: 13.6V Volts
Unknown APRS Data Type Indicator "B", VAN, Tiny Track
[0H] K1OSH-15>APTT4,KI7JS-10*,WIDE2-1:Battery: 13.6V Volts

KJ7PAG audio level = 11(6/3) ? [NONE] ? ___|||||_
[0.5] KJ7PAG>TUTUXZ,WIDE1-1,WIDE2-1:`18Nl <0x1c>-/`"8M}440.325MHz monitoring 146.520_%<0x0d>
MIC-E, House, Yaesu FTM-400DR, Off Duty
N 45 45.8000, W 121 28.5000, 0 MPH, alt 1371 ft, 440.325 MHz
?monitoring 146.520
[0H] KJ7PAG>TUTUXZ,KI7JS-10*,WIDE2-1:`18Nl <0x1c>-/`"8M}440.325MHz monitoring 146.520_%<0x0d>

APRSd github.com/craigerl/aprsd implements a web interface that connects to direwolf giving you easy access to APRS texting.?
APRSDroid and aprs.fi(ios) work well also.? ?

if that's what you're after,
-craig
KM6LYW

On Wed, Dec 14, 2016 at 07:46 AM, WB2OSZ wrote:

AGWterm is known to work.

I had some trouble with AGWterm. It does connect to BBSes via Direwolf and exchange data successfully. But when I tried to copy-n-paste a lot of data to send, it (a) sent each line in a separate packet and (b) didn't send all of the data.

On Tue, Dec 13, 2016 at 03:45 PM, Stan Ham wrote:

I would like to learn how ... to do very simple "texting" in this manner, keyboard to keyboard via a digipeater without any other software involved.

I made some fairly simple software that does this. You can get it . It runs on Windows or Linux (at least). It is "other software", so it doesn't quite meet your requirement, but it's pretty close.

I made some software that does that. It works with Direwolf on Windows and Linux (at least). You can get it . The chatter program won't work with an ancient ink-on-paper teletype, since it relies on overwriting output using backspaces.

Hello

There is an incresing number of Packet nodes and stations in the UK running IL2P+CRC, with the NinoTNC now offering 7 different baud and modulation variants. John G8BPQ has built support in QtSoundModem.

It would be awesome to get IL2P+CRC support in Direwolf too, so that Direwolf continues to be an available option. Details and words of support here -->

Many thanks
Kevin M0AHN

Alamogordo Amateur Radio Club 开云体育 Hams In The Tularosa Basin And Around The World And Beyond

AARCs' 38th Annual Hamfest 31 Aug Labor Day Weekend 2024 from 7am to 3pm-ish (depends upon presentations)

Free admissions, donations from local and Ham related vendors for door prize drawings throughout the day

Morning brew and eats by club for donations, for lunch support your local vendors.

Plenty of parking at the Otero County Fairgrounds, RV's welcome but no RV hookups, dump station on site

Hamfest is ARRL approved and small listed nonprofit (needing all the help we can get)

AARC is also looking for items to be donated as door prizes throughout the day

"Give a big thank you to those who donated to our past Hamfests." You keep us afloat

We would like to list your logo on our website to show donor support and advertise your business during the event

Main prizes and Ht drawings are normally purchased by the club, (donations accepted) must be present for all except 1st prize

? ? 1st FT-710 AESS
? ? 2nd FTM-6000R
? ? 3rd Mini 1.3 OLED ZUMspot Kit
? ? 4th DM-30TR
? ?$1.00 Drawing for FT65 HT

Main Prize drawing tickets $8.00 mail in post dated before 24 Aug (eligible for Pre-Registration Prize drawing of $50.00) $10.00 at the door, Swap Tables $15.00 with one chair

Any profits made from our event goes back into paying our bills, insurance, repeater systems maintenance, classes and our other public activities

We are also looking for folks/groups who would like to do short presentations

Testing will be conducted on site around 9am-ish (depends upon the VE and VEC's)

Apologize up front for any doubling up on email requests

Check us out at http://www.qsl.net/k5lrw/ and on FB at Alamogordo Amateur Radio Club NM

Our mails;

KI5RUS Rusty rjaskolo@... ? (2024 AARC Pres and Hamfest Chair)

KB7SQF Rick rick@...

Street mailing address for packages please use;

Russell Jaskolowski
1107 Hendrix Ave
Alamogordo, NM 88310

AARC mail box is;

AARC
Hamfest 2024
12 Main St #383
LaLuz, NM 88337

Rusty's cell 575-491-3631

Thank you all for supporting our small club serving the community

Rick KB7SQF
2024 AARC Director
Hamfest Committee Member
73

The -L log format is not the same as the -l format? Is there a way to make the -L format the same as -l? With -L I'm getting a copy of the console output.