Re: KISS TNC emulation issue

#5917

A followup to this:

You can't set the KISS channel number in YAAC until you have connected to the Direwolf instance. This is because the port behavior is different if you make a KISS connection to W1HKJ's fldigi program, where only channel 0 is supported, but it is possible to change fldigi software modems on-the-fly from the YAAC UI. If the remote KISS server is identified as _not_ fldigi (such as for DireWolf), then you can configure the KISS channel number for the YAAC port.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Andrew P. <andrewemt@...>
Sent: Monday, December 6, 2021 1:35 PM
To: [email protected]
Subject: Re: [direwolf] KISS TNC emulation issue

WB2OSZ asked me to answer this.

YAAC actually looks at the KISS channel number in the received frame, and only consumes if it matches the configured channel number. Transmission also uses the configured channel number in the KISS header byte. The channel number defaults to zero and can be configured to any of the legal values (0 to 15).

If one YAAC wants to listen to more than one channel from the same Direwolf, it will have to open more than one KISS-over-TCP connection to the same Direwolf instance. I probably should optimize that, since Direwolf's default maximum number of KISS connections is smaller than the total range of port numbers.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Douglas Pervine <douglas.pervine@...>
Sent: Sunday, December 5, 2021 1:15 PM
To: [email protected]
Subject: [direwolf] KISS TNC emulation issue

I have two RPi 4's both have Audio Injector Zero sound cards. Both are running DW 1.7B. Both are configured with Channel 0 at 1200 baud and Channel 1 at 9600 baud.
The two RPi 4's communicate perfectly.

I have one RPi 4 configured with "SERIALKISS /dev/ttyUSB0 115200" as described in the User Guide, para 9.4.3 on page 85.  I then attached a
null-modem cable to a WIN-10 machine running YAAC as described in the User Guide, para 4.4.3 on page 16.

My problem is this:  DW will only listen to/communicate with Channel 0.  Any activity on Channel 1 is ignored.

I have verified this by using a Kenwood TH-D74A.  When I beacon at 1200 baud, the both RPi's receive it and the one that has a SERIALKISS null-modem cable to
YAAC also receives the beacon.  However, when I beacon at 9600 baud, only the RPi's receive the beacon.  The beacon isn't passed to YAAC over the null-modem cable.

Any assistance would be greatly appreciated.

Re: KISS TNC emulation issue

#5916

WB2OSZ asked me to answer this.

YAAC actually looks at the KISS channel number in the received frame, and only consumes if it matches the configured channel number. Transmission also uses the configured channel number in the KISS header byte. The channel number defaults to zero and can be configured to any of the legal values (0 to 15).

If one YAAC wants to listen to more than one channel from the same Direwolf, it will have to open more than one KISS-over-TCP connection to the same Direwolf instance. I probably should optimize that, since Direwolf's default maximum number of KISS connections is smaller than the total range of port numbers.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Douglas Pervine <douglas.pervine@...>
Sent: Sunday, December 5, 2021 1:15 PM
To: [email protected]
Subject: [direwolf] KISS TNC emulation issue

I have two RPi 4's both have Audio Injector Zero sound cards. Both are running DW 1.7B. Both are configured with Channel 0 at 1200 baud and Channel 1 at 9600 baud.
The two RPi 4's communicate perfectly.

I have one RPi 4 configured with "SERIALKISS /dev/ttyUSB0 115200" as described in the User Guide, para 9.4.3 on page 85.  I then attached a
null-modem cable to a WIN-10 machine running YAAC as described in the User Guide, para 4.4.3 on page 16.

My problem is this:  DW will only listen to/communicate with Channel 0.  Any activity on Channel 1 is ignored.

I have verified this by using a Kenwood TH-D74A.  When I beacon at 1200 baud, the both RPi's receive it and the one that has a SERIALKISS null-modem cable to
YAAC also receives the beacon.  However, when I beacon at 9600 baud, only the RPi's receive the beacon.  The beacon isn't passed to YAAC over the null-modem cable.

Any assistance would be greatly appreciated.

Re: Receive via USB Connection on IC7100 with direwolf

#5915

开云体育

On 12/5/21 08:49, Doug via groups.io wrote:

...? I only have a USB connection to my radio.? I can hear the APRS packets coming through on my Radio, but they aren't registering with direwolf.? Do I need to connect my radio to a sound card input to be able to hear from the radio?? I guess I was thinking the USB could handle both transmit and receive connections.

alsamixer (then F5) should display something similar to the following; make note of your original settings. Controls with "MM" are muted, so you'll want to use the left/right arrow keys to select a particular control, then the M key to toggle muting. Up/down arrow keys adjust levels. Experiment in real-time until things work as desired; <esc> exits. To save settings across reboots type "alsactl store" as root.

???

Re: Receive via USB Connection on IC7100 with direwolf

#5914

This gave me some clues.? Essentially I did not have my ADEVICE set up properly.? Using "arecord -l" command showed me the USB Codec was on Card 2 instead of 1.? After setting my ADEVICE properly, the audio was passing for transmit and receive.? I also found that previously when I thought I was transmitting, I was just transmitting blank air.? It was keyying my transmitter, but not sending any APRS codes.? Hopefully this helps someone else in the future.?

Thanks for the support! 73?

Below are my options that worked.

#ADEVICE plughw:1,0
ADEVICE plughw:2,0
ACHANNELS 1
CHANNEL 0
MYCALL KI5SBM
MODEM 1200
PTT RIG 370 /dev/ttyUSB1
AGWPORT 8000
KISSPORT 8001

Re: KISS TNC emulation issue

#5913

On Sun, Dec 5, 2021 at 11:43 AM, David Ranch wrote:

When you configure the SERIALKISS parameter in each of the "channel" areas, are you specifying unique serial ports or are you assuming the data from both Direwolf channel 0 and channel 1 will be mux'ed into the same serial port?? As an experiment, gave you tried just configuring the SERIALKISS parameter for channel 1 only and see if you now receive the 9600bps traffic on the configured serial port?

--David
KI6ZHD

On 12/05/2021 10:15 AM, Douglas Pervine wrote:

I have two RPi 4's both have Audio Injector Zero sound cards. Both are running DW 1.7B. Both are configured with Channel 0 at 1200 baud and Channel 1 at 9600 baud.
The two RPi 4's communicate perfectly.

I have one RPi 4 configured with "SERIALKISS /dev/ttyUSB0 115200" as described in the User Guide, para 9.4.3 on page 85.? I then attached a
null-modem cable to a WIN-10 machine running YAAC as described in the User Guide, para 4.4.3 on page 16.

My problem is this:? DW will only listen to/communicate with Channel 0.? Any activity on Channel 1 is ignored.

I have verified this by using a Kenwood TH-D74A.? When I beacon at 1200 baud, the both RPi's receive it and the one that has a SERIALKISS null-modem cable to?
YAAC also receives the beacon.? However, when I beacon at 9600 baud, only the RPi's receive the beacon.? The beacon isn't passed to YAAC over the null-modem cable.

Any assistance would be greatly appreciated.
?

?The SERIALKISS configuration option seems
to be a Global option instead of a Channel specific option.

Just incase, I've put the SERIALKISS configuration down under CHANNEL 1 near the AGWPORT and KISSPORT area. (In the 'Virtual TNC' area - Not that it matters)

Re: ham hat

#5912

I don't want to use it for D-DTAR either! :p

I think the group has given some very good feedback though. Please keep us informed.
I am VERY new to R-Pi but need something like this going forward.
--
Paul AC1DW

Re: KISS TNC emulation issue

#5911

开云体育

When you configure the SERIALKISS parameter in each of the "channel" areas, are you specifying unique serial ports or are you assuming the data from both Direwolf channel 0 and channel 1 will be mux'ed into the same serial port?? As an experiment, gave you tried just configuring the SERIALKISS parameter for channel 1 only and see if you now receive the 9600bps traffic on the configured serial port?

--David
KI6ZHD

On 12/05/2021 10:15 AM, Douglas Pervine wrote:

Show quoted text

I have two RPi 4's both have Audio Injector Zero sound cards. Both are running DW 1.7B. Both are configured with Channel 0 at 1200 baud and Channel 1 at 9600 baud.
The two RPi 4's communicate perfectly.

I have one RPi 4 configured with "SERIALKISS /dev/ttyUSB0 115200" as described in the User Guide, para 9.4.3 on page 85.? I then attached a
null-modem cable to a WIN-10 machine running YAAC as described in the User Guide, para 4.4.3 on page 16.

My problem is this:? DW will only listen to/communicate with Channel 0.? Any activity on Channel 1 is ignored.

I have verified this by using a Kenwood TH-D74A.? When I beacon at 1200 baud, the both RPi's receive it and the one that has a SERIALKISS null-modem cable to?
YAAC also receives the beacon.? However, when I beacon at 9600 baud, only the RPi's receive the beacon.? The beacon isn't passed to YAAC over the null-modem cable.

Any assistance would be greatly appreciated.

?

Re: ham hat

#5910

Nice little project.? I've somewhat constructed the same thing using COTS devices.? The sound card is an Audio Injector Zero (Left and Right Input/Outputs) capable so far up to 9600 baud packet.? The RTC is just a plain DS1307.
I've soldered the PTT devices.? The project is from??

Good luck

20211125_104156.jpg

20211125_174433.jpg

KISS TNC emulation issue

#5909

I have two RPi 4's both have Audio Injector Zero sound cards. Both are running DW 1.7B. Both are configured with Channel 0 at 1200 baud and Channel 1 at 9600 baud.
The two RPi 4's communicate perfectly.

I have one RPi 4 configured with "SERIALKISS /dev/ttyUSB0 115200" as described in the User Guide, para 9.4.3 on page 85.? I then attached a
null-modem cable to a WIN-10 machine running YAAC as described in the User Guide, para 4.4.3 on page 16.

My problem is this:? DW will only listen to/communicate with Channel 0.? Any activity on Channel 1 is ignored.

I have verified this by using a Kenwood TH-D74A.? When I beacon at 1200 baud, the both RPi's receive it and the one that has a SERIALKISS null-modem cable to?
YAAC also receives the beacon.? However, when I beacon at 9600 baud, only the RPi's receive the beacon.? The beacon isn't passed to YAAC over the null-modem cable.

Any assistance would be greatly appreciated.

Re: ham hat

#5908

I've updated my hat project.

* Standard pinout on the DB9 connector
* Added RTC
* Some other fixes
* Created assembly




-- 
Levente Kovacs
Senior Electronic Engineer

W: 

Re: Receive via USB Connection on IC7100 with direwolf

#5907

开云体育

Direwolf can use your IC7100's built-in soundcard just fine assuming you configured your radio to use USB for it's audio I/O (not the default).?? Have you Google'ed around for some hints?

? Search: icom ic7100 direwolf setup

???? - Windows centric but gives you a bunch of settings to check:

???? - /g/direwolf/topic/icom_7100_pi/34952806?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,20,34952806

???? -

Etc.

--David
KI6ZHD

On 12/04/2021 11:11 PM, Doug via groups.io wrote:

Show quoted text

I'm trying to use direwolf with my IC-7100.? I can get the transmit to work, but I can't receive any packets.? I hear them coming from my radio, but I don't see them getting logged by direwolf.? I'm using linux.

My Major modification in the direwolf.conf file is
PTT RIG 370 /dev/ttyUSB1

Is there something special I need to do to get it to receive?

Below is what it looks like when I start direwolf.? I am using Linux.

Reading config file direwolf.conf
Audio device for both receive and transmit: default? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate, DTMF decoder enabled.
Hamlib determined CAT control serial port rate of 19200.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...

Thanks,
Doug
KI5SBM

Re: Receive via USB Connection on IC7100 with direwolf

#5906

I assume USB sound card?

Even if the USB sound card is 'half duplex', the device will be only in 1 state at a time.? None of the applications decode while transmitting, unless (maybe) if you have left andf right audio channels enabled.

To me, the key is that you are able to TX.? That is usually the more difficult part (at least to me).

More things can prevent TX (Carrier detect, busy frequency, etc.).

Robert Giuliano
KB8RCO

On Sunday, December 5, 2021, 11:44:05 AM EST, Doug via groups.io <dscott7000@...> wrote:

A little more information on this...I'm connecting my radio via a USB data connection.? The USB drivers have been working for Gpredict, WSJT-x and FLrig, so I feel like the radio is setup properly.? Can Direwolf handle both transmit and receive via a USB connection??

Re: Receive via USB Connection on IC7100 with direwolf

#5905

You are correct, Rob.? I am trying to decode APRS on 144.390 MHz.? I only have a USB connection to my radio.? I can hear the APRS packets coming through on my Radio, but they aren't registering with direwolf.? Do I need to connect my radio to a sound card input to be able to hear from the radio?? I guess I was thinking the USB could handle both transmit and receive connections.

Re: Receive via USB Connection on IC7100 with direwolf

#5904

The IC-7100 is capable of many bands.

I assume you are referring to decoding whne the radio in FM mode on VHF (144.390 MHz).

If you are running the radio on HF bands, the the baud and frequencies will be different.

?? Interesting writeup here:

The next comment would be that if you are hearing packets that 'sound decodable', but are not being decoded, it is most likey that the sound card settings are not matching.? Since you are using the default sound device, you should check which devices are default on your system.? I mostly use the KDE desktop (KUbuntu) which has different icon tray icons and settings, I will leave the settings part up to you to check.

Robert Giuliano
KB8RCO

On Sunday, December 5, 2021, 08:52:37 AM EST, Doug via groups.io <dscott7000@...> wrote:

I'm trying to use direwolf with my IC-7100.? I can get the transmit to work, but I can't receive any packets.? I hear them coming from my radio, but I don't see them getting logged by direwolf.? I'm using linux.

My Major modification in the direwolf.conf file is
PTT RIG 370 /dev/ttyUSB1

Is there something special I need to do to get it to receive?

Below is what it looks like when I start direwolf.? I am using Linux.

Reading config file direwolf.conf
Audio device for both receive and transmit: default? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate, DTMF decoder enabled.
Hamlib determined CAT control serial port rate of 19200.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...

Thanks,
Doug
KI5SBM

Re: Receive via USB Connection on IC7100 with direwolf

#5903

A little more information on this...I'm connecting my radio via a USB data connection.? The USB drivers have been working for Gpredict, WSJT-x and FLrig, so I feel like the radio is setup properly.? Can Direwolf handle both transmit and receive via a USB connection??

Re: Receive via USB Connection on IC7100 with direwolf

#5902

I do don't use hf and Linux with direwolf, I run it on a raspberry pi through a easy digital board.

Show quoted text

On Sun, Dec 5, 2021, 8:52 AM Doug via <dscott7000=[email protected]> wrote:

I'm trying to use direwolf with my IC-7100.? I can get the transmit to work, but I can't receive any packets.? I hear them coming from my radio, but I don't see them getting logged by direwolf.? I'm using linux.

My Major modification in the direwolf.conf file is
PTT RIG 370 /dev/ttyUSB1

Is there something special I need to do to get it to receive?

Below is what it looks like when I start direwolf.? I am using Linux.

Reading config file direwolf.conf
Audio device for both receive and transmit: default? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate, DTMF decoder enabled.
Hamlib determined CAT control serial port rate of 19200.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...

Thanks,
Doug
KI5SBM

Receive via USB Connection on IC7100 with direwolf

#5901

I'm trying to use direwolf with my IC-7100.? I can get the transmit to work, but I can't receive any packets.? I hear them coming from my radio, but I don't see them getting logged by direwolf.? I'm using linux.

My Major modification in the direwolf.conf file is
PTT RIG 370 /dev/ttyUSB1

Is there something special I need to do to get it to receive?

Below is what it looks like when I start direwolf.? I am using Linux.

Reading config file direwolf.conf
Audio device for both receive and transmit: default? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate, DTMF decoder enabled.
Hamlib determined CAT control serial port rate of 19200.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...

Thanks,
Doug
KI5SBM

Re: LoRa APRS & DW

#5900

开云体育

I see:

    433 MHz
    868 MHz
    915 MHz
    923 MHz

My understanding is that 868 is for Europe only.  433 and 915, and maybe
923, are allowable under Part 15

Correct.. these are unlicensed ISM frequencies and there are many others as well:

?

but I am not sure the Lora modulation/power is ok at 433 under Part 15 (which is low duty cycle
only?), and my impression is that the Lora norm in the US is to use 915
under Part 15.

Anything is generally allowed on ISM frequencies within specific power parameters, etc.

But, one can operate a 915 radio under 97 or 15, if the emission type
meets both rules.  This seems similar to people using wifi hardware at
2.4, 3 and 5 GHz in spectrum that is authorized for both Part 97 and
Part 15 use, but choosing to operate under Part 97 rules, sometimes with
amps and higher gain antennas.

Correct.. up to certain power levels but also without being allowed to run encryption, etc.

I would think that an APRS network would  have to treat a Part 15 radio
as "internet" rather than "amatuer radio" in terms of gatewaying, and
that's what I was trying to ask about/understand.

APRS is just a protocol that you run on top of some other transport be it LORA, 1200bps AFSK, etc.? Your choice of power levels and other features will determine which frequencies are appropriate.? For those of us in the US, then comes the rules be it Part 97, Part 15, etc.? Gatewaying into the Internet is essentially moot as the FCC has no jurisdiction / rules / etc there.

--David
KI6ZHD

Re: LoRa APRS & DW

#5899

开云体育

Yes, part 97 can use Part 15 Radio Frequency devices. Witness Bluetooth on transceivers. ?LoRA is documented. APRS over LoRA is completely fine.

Show quoted text

On Dec 4, 2021, at 17:34, David Ranch <direwolf-groupsio@...> wrote:

?
The LILYGO TTGO T-beam devices don't use Part 97 frequencies.. they use Part 15 that don't have the same requirements:

??

--David
KI6ZHD

On 12/04/2021 05:17 PM, Greg Troxel wrote:

And, there's another point: Lora, last I heard, is a proprietary format
and needs a patent license.  So at least in the US, there is no
possibility of a Free Software SDR implementation, even if one had an
adequately wide-band SDR.  In this respect it is similar to AMBE (or
maybe that's expired and it's similar to AMBE2).




Separately from that, I'm also curious if the Lora protocols fall under
the Part 97 Spread Spectrum rules and how that works.  I have lost track
of the rules and never tried to operate spread spectrum.  (I am guessing
people are talking about operating Lora hardware under amateur rules,
rather than talking about gatewaying Part 15 data to and from Part 97
systems, which seems also unclear to me.)

73 de n1dam

Re: LoRa APRS & DW

#5898

"David Ranch" <direwolf-groupsio@...> writes:

The LILYGO TTGO T-beam devices don't use Part 97 frequencies.. they
use Part 15 that don't have the same requirements:

   

--David
KI6ZHDI see:

    433 MHz
    868 MHz
    915 MHz
    923 MHz

My understanding is that 868 is for Europe only.  433 and 915, and maybe
923, are allowable under Part 15, but I am not sure the Lora
modulation/power is ok at 433 under Part 15 (which is low duty cycle
only?), and my impression is that the Lora norm in the US is to use 915
under Part 15.

But, one can operate a 915 radio under 97 or 15, if the emission type
meets both rules.  This seems similar to people using wifi hardware at
2.4, 3 and 5 GHz in spectrum that is authorized for both Part 97 and
Part 15 use, but choosing to operate under Part 97 rules, sometimes with
amps and higher gain antennas.

I would think that an APRS network would  have to treat a Part 15 radio
as "internet" rather than "amatuer radio" in terms of gatewaying, and
that's what I was trying to ask about/understand.

73 de n1dam

signature.asc