¿ªÔÆÌåÓý

Kissutil 1.6 looping in TXed packets - bug?


 

Hi,
I just noticed that when I feed a packet into Kissutil is correctly TXed but immediately looped back in and received.

Processing test_message.txt for transmit...

ES3BEC-10>APZSKU,WIDE2-1::ES3BEC-11:Skudo test balloon at 48315 seconds{9999

Sending to KISS TNC:

? 000:? c0 00 82 a0 b4 a6 96 aa e0 8a a6 66 84 8a 86 f4? ...........f....

? 010:? ae 92 88 8a 64 40 63 03 f0 3a 45 53 33 42 45 43? ....d@c..:ES3BEC

? 020:? 2d 31 31 3a 53 6b 75 64 6f 20 74 65 73 74 20 62? -11:Skudo test b

? 030:? 61 6c 6c 6f 6f 6e 20 61 74 20 34 38 33 31 35 20? alloon at 48315?

? 040:? 73 65 63 6f 6e 64 73 7b 39 39 39 39 c0 ? ? ? ? ? seconds{9999.

From KISS TNC:

? 000:? c0 00 82 a0 b4 a6 96 aa e0 8a a6 66 84 8a 86 f4? ...........f....

? 010:? ae 92 88 8a 64 40 63 03 f0 3a 45 53 33 42 45 43? ....d@c..:ES3BEC

? 020:? 2d 31 31 3a 53 6b 75 64 6f 20 74 65 73 74 20 62? -11:Skudo test b

? 030:? 61 6c 6c 6f 6f 6e 20 61 74 20 34 38 33 31 35 20? alloon at 48315?

? 040:? 73 65 63 6f 6e 64 73 7b 39 39 39 39 c0 ? ? ? ? ? seconds{9999.

[0] ES3BEC-10>APZSKU,WIDE2-1::ES3BEC-11:Skudo test balloon at 48315 seconds{9999

Save received frame to /tmp/rx/20201201-134931-433

it does not happen on DW1.5.

Is this a bug or an intended behaviour?

Thanks folks


 

¿ªÔÆÌåÓý


With a standard Direwolf installation, if your station is hearing itself, it's been noticed it could be:

?? 1. RFI issues: try lowering your radio's power level or even turn the radio off to see if you still receive your own packets

?? 2. Audio levels: It's common that Direwolf uses the RIGHT channel of your sound device for both playback (TX) and record (RX).? Try muting or lowering the levels to ZERO for the non-used audio channel (aka the LEFT) channel for both playback and record

--David
KI6ZHD



On 12/01/2020 03:55 AM, Simone wrote:

Hi,
I just noticed that when I feed a packet into Kissutil is correctly TXed but immediately looped back in and received.

Processing test_message.txt for transmit...

ES3BEC-10>APZSKU,WIDE2-1::ES3BEC-11:Skudo test balloon at 48315 seconds{9999

Sending to KISS TNC:

? 000:? c0 00 82 a0 b4 a6 96 aa e0 8a a6 66 84 8a 86 f4? ...........f....

? 010:? ae 92 88 8a 64 40 63 03 f0 3a 45 53 33 42 45 43? ....d@c..:ES3BEC

? 020:? 2d 31 31 3a 53 6b 75 64 6f 20 74 65 73 74 20 62? -11:Skudo test b

? 030:? 61 6c 6c 6f 6f 6e 20 61 74 20 34 38 33 31 35 20? alloon at 48315?

? 040:? 73 65 63 6f 6e 64 73 7b 39 39 39 39 c0 ? ? ? ? ? seconds{9999.

From KISS TNC:

? 000:? c0 00 82 a0 b4 a6 96 aa e0 8a a6 66 84 8a 86 f4? ...........f....

? 010:? ae 92 88 8a 64 40 63 03 f0 3a 45 53 33 42 45 43? ....d@c..:ES3BEC

? 020:? 2d 31 31 3a 53 6b 75 64 6f 20 74 65 73 74 20 62? -11:Skudo test b

? 030:? 61 6c 6c 6f 6f 6e 20 61 74 20 34 38 33 31 35 20? alloon at 48315?

? 040:? 73 65 63 6f 6e 64 73 7b 39 39 39 39 c0 ? ? ? ? ? seconds{9999.

[0] ES3BEC-10>APZSKU,WIDE2-1::ES3BEC-11:Skudo test balloon at 48315 seconds{9999

Save received frame to /tmp/rx/20201201-134931-433

it does not happen on DW1.5.

Is this a bug or an intended behaviour?

Thanks folks



 

¿ªÔÆÌåÓý

Hi,
1: I tested with radio off and still it repeats the message to itself. Probably like someone else said it happens only for the first packet

Thanks
HB9HCM

On 3 Dec 2020, at 17:10, David Ranch <direwolf-groupsio@...> wrote:


With a standard Direwolf installation, if your station is hearing itself, it's been noticed it could be:

?? 1. RFI issues: try lowering your radio's power level or even turn the radio off to see if you still receive your own packets

?? 2. Audio levels: It's common that Direwolf uses the RIGHT channel of your sound device for both playback (TX) and record (RX).? Try muting or lowering the levels to ZERO for the non-used audio channel (aka the LEFT) channel for both playback and record

--David
KI6ZHD



On 12/01/2020 03:55 AM, Simone wrote:
Hi,
I just noticed that when I feed a packet into Kissutil is correctly TXed but immediately looped back in and received.

Processing test_message.txt for transmit...

ES3BEC-10>APZSKU,WIDE2-1::ES3BEC-11:Skudo test balloon at 48315 seconds{9999

Sending to KISS TNC:

? 000:? c0 00 82 a0 b4 a6 96 aa e0 8a a6 66 84 8a 86 f4? ...........f....

? 010:? ae 92 88 8a 64 40 63 03 f0 3a 45 53 33 42 45 43? ....d@c..:ES3BEC

? 020:? 2d 31 31 3a 53 6b 75 64 6f 20 74 65 73 74 20 62? -11:Skudo test b

? 030:? 61 6c 6c 6f 6f 6e 20 61 74 20 34 38 33 31 35 20? alloon at 48315?

? 040:? 73 65 63 6f 6e 64 73 7b 39 39 39 39 c0 ? ? ? ? ? seconds{9999.

From KISS TNC:

? 000:? c0 00 82 a0 b4 a6 96 aa e0 8a a6 66 84 8a 86 f4? ...........f....

? 010:? ae 92 88 8a 64 40 63 03 f0 3a 45 53 33 42 45 43? ....d@c..:ES3BEC

? 020:? 2d 31 31 3a 53 6b 75 64 6f 20 74 65 73 74 20 62? -11:Skudo test b

? 030:? 61 6c 6c 6f 6f 6e 20 61 74 20 34 38 33 31 35 20? alloon at 48315?

? 040:? 73 65 63 6f 6e 64 73 7b 39 39 39 39 c0 ? ? ? ? ? seconds{9999.

[0] ES3BEC-10>APZSKU,WIDE2-1::ES3BEC-11:Skudo test balloon at 48315 seconds{9999

Save received frame to /tmp/rx/20201201-134931-433

it does not happen on DW1.5.

Is this a bug or an intended behaviour?

Thanks folks




 

Had this 'crosstalk' problem also. This command helped to adjust the audio-channels: "amixer sset Master 0%,100%". LEFT channel is set to 0%, RIGHT to 100%. A better solution would be to connect the mono audio-output of the TRX only to the RIGHT mic-input channel of the soundcard.

Regards
Tom


 

I've had 'crosstalk' problems as well.
My setup:
?? Pi3 running Nexus OS
?? Fe-Pi sound card
?? Nexus DR-X radio interface board with separated left & right audio channels
?? KISS over TCP/IP from Direwolf to attached client(s)
?? One channel connected to the radio, the other had no connections.

Almost always, the perceived crosstalk would report with zero audio level.
It has been awhile, but as I recall, whenever one audio channel would TX, the other would list it as received as well.?
Some very strong received stations would also report on the 'open' side.

Rob KB8RCO


 

I learned from my own stupidity!

The crosstalk problems appear to be due to my settings.? I had the jumpers set to 9600 baud input, but the cable was coming in on the 1200 baud input.? It appears some audio was sneaking around (best guess) through the ground side.?

I am now set for 9600 baud input, and the cables are wired as such.? Now it decodes on the proper channel only (except on TX where RF gets in), and the decode values are much more consistent!? Everything is working properly now.

Rob KB8RCO