Re: Configuring W3DJS V1.0 Direwolf questions.
I have the W3DJS V1.0 package running on a Raspberry Pi, 3. So far, so good, I have WSJT-x and Fldigi running. I'd like to set up Direwolf so that it works something like my old KPC-2 Kantronics TU. With the Kantronics, I could get on two meter packet and issue a "C calletter" command and connect to local digipeaters.
This discussion would probably better to have on firstname.lastname@example.org . Anyway..
I haven't been able to successfully make it receive or transmit. I left it running for a while yesterday and it must have been really exercising the CPU because the thermometer popped up on the screen, so I killed Direwolf.
That's not normal as Direwolf is very light weight.
It had a message in red, but I didn't capture it. Something about I should use the Linux command "top" to check CPU usage.
We need to see the specific errors to give you any specific help.
The Direwolf login text says something about: "gpsd hamlib cm108-ptt" I would imagine that it should say something about the FT817, but doesn't.
That text is only reporting what features Direwolf was build with. In this case:
GPS for obtaining your location
hamlib for PTT control
cm108-ptt for asserting PTT on specific sound devices
So, do I have to enable something like Linpac so I can type commands to Direwolf and the radio packet tool?
Direwolf doesn't directly offer any command line interface to create packet connections. You can use the "call" program from the "ax25apps", you can use Linpac, etc. to create connected packet connections, or use one of the many other Linux or AGW-enabled terminal programs: SV2AGW's ag2term, UZ7HO's easyterm, Outpost's ipserial. etc)
#This seems fine assuming this is the right sound device per "aplay -l" and "arecord -l"
#These are fine
#This is using Hamlib to assert PTT though I don't know what rig "1020" is. It's assumed you *already* have CAT
#control already working with your radio using a serial port
PTT RIG 1020 /dev/ttyUSB0
Here is the Direwolf login text:
I assume this bottom "c" is you trying to give a TNC2-like command line response. Direwolf doesn't work that way. See above. If you really really want a classic TNC-like interface, you can consider configuring Direwolf to wort with LinBPQ32 and then configure it's TNC2 interface emulator.