开云体育

Date

Re: Direwolf as Traditional Serial TNC

 

>Interesting challenge!? I have an old pre-IBM computer (a 1977-era MAI Jolt) and TV Typewriter

how about a Teletype Model 33? This thing at 100 wpm was a screamer for the days.

Mike K6MFW


Re: Direwolf as Traditional Serial TNC

 

开云体育

Interesting challenge!? I have an old pre-IBM computer (a 1977-era MAI Jolt) and TV Typewriter system that still works.? It would be cool to do some packet radio with it.

I think what you might do is to use the internal serial port on the Raspberry Pi (GPIO 14 Tx, 15 Rx) to get a Linux serial console into the Pi, or a USB serial dongle if that's handy.? The tty consoles are enabled in the Pi's config; they default off.? Connect that to the Apple serial port and its TTY emulator.? Once you can log into the Pi, you can run axcall to connect to the packet nodes, or potentially linpac to do the multi-session stuff if the terminal emulator supports the right TTY model.

Have fun!

Greg? KO6TH


Rob Giuliano via groups.io wrote:

You need to be more specific in what you expect from Direwolf.
the cmd: prompt was used to change settings in the old hardware TNCs.
Most of those settings are now in the Direwolf.ini file (or the ini file you specify on the command line with '-c').

Are you just trying to put Direwolf in the old K (converse) mode to have keyboard-to-keyboard QSOs?
Or are you expecting that your terminal program will be able to change some (or all) of the parameters set in the ini file?
These would be things like: MYCALL, BTEXT, DIGI
? These 'may' or 'may not' make sense for Direwolf.

For QSOs, if your APPLE IIe terminal program allows connection through TCP/IP, you could try connecting that way.?

Robert Giuliano
KB8RCO



On Thursday, December 2, 2021, 09:03:53 AM EST, elgunn.cmma@... <elgunn.cmma@...> wrote:


Hey, I'm running Direwolf 1.6 on a Rasberry Pi 4 and I would like to see if its possible to use this Pi as a traditional Kantronics/Paccomm esque TNC (with the "cmd:" type prompt via a USB-Serial adapter. I have a terminal program running on my Apple //e Enhanced from 1982 and would like to control direwolf as if it were a TNC from the 80s. Is this possible? (Ignore the fact that I'm using an Apple II, I would like this setup to work with any serial terminal)

Thanks!


Re: Direwolf as Traditional Serial TNC

 

You need to be more specific in what you expect from Direwolf.
the cmd: prompt was used to change settings in the old hardware TNCs.
Most of those settings are now in the Direwolf.ini file (or the ini file you specify on the command line with '-c').

Are you just trying to put Direwolf in the old K (converse) mode to have keyboard-to-keyboard QSOs?
Or are you expecting that your terminal program will be able to change some (or all) of the parameters set in the ini file?
These would be things like: MYCALL, BTEXT, DIGI
? These 'may' or 'may not' make sense for Direwolf.

For QSOs, if your APPLE IIe terminal program allows connection through TCP/IP, you could try connecting that way.?

Robert Giuliano
KB8RCO



On Thursday, December 2, 2021, 09:03:53 AM EST, elgunn.cmma@... <elgunn.cmma@...> wrote:


Hey, I'm running Direwolf 1.6 on a Rasberry Pi 4 and I would like to see if its possible to use this Pi as a traditional Kantronics/Paccomm esque TNC (with the "cmd:" type prompt via a USB-Serial adapter. I have a terminal program running on my Apple //e Enhanced from 1982 and would like to control direwolf as if it were a TNC from the 80s. Is this possible? (Ignore the fact that I'm using an Apple II, I would like this setup to work with any serial terminal)

Thanks!


Direwolf as Traditional Serial TNC

 

Hey, I'm running Direwolf 1.6 on a Rasberry Pi 4 and I would like to see if its possible to use this Pi as a traditional Kantronics/Paccomm esque TNC (with the "cmd:" type prompt via a USB-Serial adapter. I have a terminal program running on my Apple //e Enhanced from 1982 and would like to control direwolf as if it were a TNC from the 80s. Is this possible? (Ignore the fact that I'm using an Apple II, I would like this setup to work with any serial terminal)

Thanks!


Re: APRS-IS data over KISS TCP port

 

I was thinking similar thoughts.?
However, Direwolf puts out a lot of data, including decoding of some packets:

[ig>tx] N8QLT-S>APDG01,TCPIP*,qAC,N8QLT-GS:;N8QLT? A *011508z4228.57ND08352.39WaRNG0001 440 Voice 445.67000MHz +0.0000MHz

Digipeater CHLSEA audio level = 22(5/4)?? [NONE]?? ___||____
[2.3] NU3S-7>APK102,N3FB-2,K8UI-1,CHLSEA*,WIDE3-1:=4022.75N/08004.80W_201/002g009t040r?? p?? P000h93b10219KU2k<0x0d>

???? Weather Report, WEATHER Station (blue), Kenwood D710
???? N 40 22.7500, W 080 04.8000
???? wind 2.3 mph, direction 201, gust 9, temperature 40, rain 0.00 since midnight, humidity 93, barometer 30.18, "KU2k"

It is much easier to get it through a known format.
But it appears only a little more filtering would be required.? The good news is the already decoded packet is less to parse than going through Mic-E, Compressed, Text, all with and without timestamps, etc.

I will take a look at that next.

Robert Giuliano
KB8RCO



On Wednesday, December 1, 2021, 09:58:50 AM EST, charlie gale <charles@...> wrote:


If information you need is being printed (standard out) why not redirect it to your application, rather than trying to get it through the KISS port?


Re: APRS-IS data over KISS TCP port

 

If information you need is being printed (standard out) why not redirect it to your application, rather than trying to get it through the KISS port?


Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

The image is transferred between the machines. You need to maintain library consistency.

On Nov 30, 2021, at 7:03 PM, glen english LIST <glenlist@...> wrote:

?Oh the image was compiled and build and transferred ?

No that wont work, not these days with the arch variations.

always COMPILE ON TARGET

-glen

On 1/12/2021 10:50 am, Don Rolph wrote:
If it is to run on PI Zero W you need to build Dire Wolf on a PI Zero W.


On Nov 30, 2021, at 6:41 PM, Craig, KM6LYW <craig@...> wrote:
? I don't know if it helps in your situation, but after trying to compile on a pi3, then inserting
the sdcard into an older Pi Zero, the compile didn't work. Still had an illegal instruction.
I had to checkout a clean copy of the source. cmake cached something somewhere
I suspect.

best,
-craig


On 11/30/21 3:16 PM, KP3FT via groups.io wrote:
Hi David,

Yep, I tried compiling from source, but I still got the same error. If I can find a Buster image, I'll use that instead and compile Direwolf on it.
--
Glen English
RF Communications and Electronics Engineer

CORTEX RF

Pacific Media Technologies Pty Ltd trading as Cortex RF

ABN 40 075 532 008

PO Box 5231 Lyneham ACT 2602, Australia.
au mobile : +61 (0)418 975077






Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

Oh the image was compiled and build and transferred ?

No that wont work, not these days with the arch variations.

always COMPILE ON TARGET

-glen

On 1/12/2021 10:50 am, Don Rolph wrote:
If it is to run on PI Zero W you need to build Dire Wolf on a PI Zero W.


On Nov 30, 2021, at 6:41 PM, Craig, KM6LYW <craig@...> wrote:

? I don't know if it helps in your situation, but after trying to compile on a pi3, then inserting
the sdcard into an older Pi Zero, the compile didn't work. Still had an illegal instruction.
I had to checkout a clean copy of the source.?? cmake cached something somewhere
I suspect.

best,
-craig


On 11/30/21 3:16 PM, KP3FT via groups.io wrote:
Hi David,

Yep, I tried compiling from source, but I still got the same error.? If I can find a Buster image, I'll use that instead and compile Direwolf on it.
--
Glen English
RF Communications and Electronics Engineer

CORTEX RF

Pacific Media Technologies Pty Ltd trading as Cortex RF

ABN 40 075 532 008

PO Box 5231 Lyneham ACT 2602, Australia.
au mobile : +61 (0)418 975077


Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

开云体育

Note that an image built on a PI Zero W will run on PI Zero W, PI Zero 2 W, PI 3 or PI 4.

I have one image that runs on all processors.


On Nov 30, 2021, at 6:50 PM, Andrew P. <andrewemt@...> wrote:

?
Problem is, when compiling on a Pi3, that gcc thinks you're always going to have the full instruction set of that Pi3 CPU available. You need to do the compilation (painful as that may be) on the exact processor you plan on running it, i.e., the Pi 1 or Pi Zero, so the compiler knows how limited your instruction set is.

Either that, or figure out which ARM compiler options are being applied on the Pi 3 and not on the Pi 1/Zero by default, and then deliberately disable those extra options.

Andrew, KA2DDO


From: [email protected] <[email protected]> on behalf of Craig, KM6LYW <craig@...>
Sent: Tuesday, November 30, 2021 6:41 PM
To: [email protected] <[email protected]>
Subject: Re: [direwolf] "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1
?
I don't know if it helps in your situation, but after trying to compile on a pi3, then inserting
the sdcard into an older Pi Zero, the compile didn't work.? Still had an illegal instruction.
I had to checkout a clean copy of the source.?? cmake cached something somewhere
I suspect.

best,
-craig


On 11/30/21 3:16 PM, KP3FT via groups.io wrote:
Hi David,

Yep, I tried compiling from source, but I still got the same error.? If I can find a Buster image, I'll use that instead and compile Direwolf on it.


Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

开云体育

If it is to run on PI Zero W you need to build Dire Wolf on a PI Zero W.


On Nov 30, 2021, at 6:41 PM, Craig, KM6LYW <craig@...> wrote:

? I don't know if it helps in your situation, but after trying to compile on a pi3, then inserting
the sdcard into an older Pi Zero, the compile didn't work.? Still had an illegal instruction.
I had to checkout a clean copy of the source.?? cmake cached something somewhere
I suspect.

best,
-craig


On 11/30/21 3:16 PM, KP3FT via groups.io wrote:
Hi David,

Yep, I tried compiling from source, but I still got the same error.? If I can find a Buster image, I'll use that instead and compile Direwolf on it.


Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

开云体育

Problem is, when compiling on a Pi3, that gcc thinks you're always going to have the full instruction set of that Pi3 CPU available. You need to do the compilation (painful as that may be) on the exact processor you plan on running it, i.e., the Pi 1 or Pi Zero, so the compiler knows how limited your instruction set is.

Either that, or figure out which ARM compiler options are being applied on the Pi 3 and not on the Pi 1/Zero by default, and then deliberately disable those extra options.

Andrew, KA2DDO


From: [email protected] <[email protected]> on behalf of Craig, KM6LYW <craig@...>
Sent: Tuesday, November 30, 2021 6:41 PM
To: [email protected] <[email protected]>
Subject: Re: [direwolf] "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1
?
I don't know if it helps in your situation, but after trying to compile on a pi3, then inserting
the sdcard into an older Pi Zero, the compile didn't work.? Still had an illegal instruction.
I had to checkout a clean copy of the source.?? cmake cached something somewhere
I suspect.

best,
-craig


On 11/30/21 3:16 PM, KP3FT via groups.io wrote:
Hi David,

Yep, I tried compiling from source, but I still got the same error.? If I can find a Buster image, I'll use that instead and compile Direwolf on it.


Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

Try compiling without using vector instruction (flags)

On 1/12/2021 10:41 am, Craig, KM6LYW wrote:
I don't know if it helps in your situation, but after trying to compile on a pi3, then inserting
the sdcard into an older Pi Zero, the compile didn't work.? Still had an illegal instruction.
I had to checkout a clean copy of the source.?? cmake cached something somewhere
I suspect.

best,
-craig


On 11/30/21 3:16 PM, KP3FT via groups.io wrote:
Hi David,

Yep, I tried compiling from source, but I still got the same error.? If I can find a Buster image, I'll use that instead and compile Direwolf on it.
--
Glen English
RF Communications and Electronics Engineer

CORTEX RF

Pacific Media Technologies Pty Ltd trading as Cortex RF

ABN 40 075 532 008

PO Box 5231 Lyneham ACT 2602, Australia.
au mobile : +61 (0)418 975077


Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

开云体育

I don't know if it helps in your situation, but after trying to compile on a pi3, then inserting
the sdcard into an older Pi Zero, the compile didn't work.? Still had an illegal instruction.
I had to checkout a clean copy of the source.?? cmake cached something somewhere
I suspect.

best,
-craig


On 11/30/21 3:16 PM, KP3FT via groups.io wrote:

Hi David,

Yep, I tried compiling from source, but I still got the same error.? If I can find a Buster image, I'll use that instead and compile Direwolf on it.


Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

开云体育

You know, it might not be DireWolf that's the problem. Since the Raspbian distro seems built only for the more powerful ARM processors, it's entirely possible one of the libraries that DireWolf is linking to also has the problem of using instructions not in the Pi 1 processor's limited instruction set.

You might try enabling core dumps, running DireWolf again until it crashes, and then using gdb to display the stack dump where the program crashed. If it's in a library called by DireWolf (such as libalsa), you might have to compile that library from source on your Pi 1, install it in /usr/local/lib, and see if that fixes the problem.

Andrew, KA2DDO


From: [email protected] <[email protected]> on behalf of glen english LIST <glenlist@...>
Sent: Tuesday, November 30, 2021 6:21 PM
To: [email protected] <[email protected]>
Subject: Re: [direwolf] "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1
?
32/64 bit problem ?

and/ or

vector instructions not present or wrong ARCH ?


On 1/12/2021 10:20 am, KP3FT via groups.io wrote:
> Well, I guess I won't try Buster.? The image is already Buster. No
> idea why the error on a Raspberry Pi 1 and freshly compiled DW 1.6.







Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

32/64 bit problem ?

and/ or

vector instructions not present or wrong ARCH ?

On 1/12/2021 10:20 am, KP3FT via groups.io wrote:
Well, I guess I won't try Buster.? The image is already Buster. No idea why the error on a Raspberry Pi 1 and freshly compiled DW 1.6.


Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

Well, I guess I won't try Buster.? The image is already Buster.? No idea why the error on a Raspberry Pi 1 and freshly compiled DW 1.6.


Re: "Illegal instruction" when trying to run Direwolf 1.6 on Raspberry Pi 1

 

Hi David,

Yep, I tried compiling from source, but I still got the same error.? If I can find a Buster image, I'll use that instead and compile Direwolf on it.


Re: APDW17

 

Merci André ( Andrew.... )
je? ne comprenais pas pourquoi j'étais le seul digi avec APDW17 en début de trames .? ?HI.
Je ne cherche donc plus à modifier ?a, j'ai compris.
Les relais APRS sont devenus très rares en France et commencent, en général,? par?APFD suivi du numéro du département.
73


Re: APDW17

 

thanks Ian ZL1VFO.

I did not understand everything but not knowing how to compile anyway, so I will leave with APDW17, I understood that well.

Is that why, by chance, sometimes my frames are no longer visible in the info. from aprs.fi?


Re: APDW17

 

Further to Andrew's reply, if you like to see a list of tocalls to see how the various versions of hardware/software TNC are represented, it is available on the aprs.org website
And if really feel like tinkering with the tocall in Direwolf, then I suppose search the source code for APDW17 and replacing it with something of your choice & recompiling would probably do it, although generally it would have to start with AP at least, otherwise a lot of other TNCs will likely just ignore any packets, as they won't consider it to be an APRS packet. In general, its probably best just to leave it at APDW17
-Ian ZL1VFO