|
I have been trying to duplicate the results in the excellent youtube video "Pat Winlink 2M Packet 1200 baud Setup" Everything seems to be working, however, I am unable to establish a connection with my local Remote Message Server. I am getting this error code in Pat Winlink:
2021/03/22 20:05:04 Connecting to K2DLL-10 (ax25)...
2021/03/22 20:05:49 Unable to establish connection to remote: Dial timeout
I am also getting these messages in the Direwolf terminal window (my local RMS is called K2DLL-10):
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
K2DLL-10 audio level = 96(13/8)? ?[NONE]? ?____|||__
[0.5] K2DLL-10>KC2EHR:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)[WL2K-5.0-B2FWIHJM$]<0x0d>
?
K2DLL-10 audio level = 59(11/7)? ?[NONE]? ?___|||||_
[0.5] K2DLL-10>KC2EHR:(I cmd, n(s)=1, n(r)=0, p=0, pid=0xf0);PQ: 12009205<0x0d>
?
K2DLL-10 audio level = 102(23/13)? ?[NONE]? ?____|||__
[0.5] K2DLL-10>KC2EHR:(I cmd, n(s)=2, n(r)=0, p=0, pid=0xf0)CMS via K2DLL ><0x0d>
?
K2DLL-10 audio level = 127(13/9)? ?[NONE]? ?____|||__
Audio input level is too high.? Reduce so most stations are around 50.
[0.5] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
1) Am I correct in that the Direwolf lines that start with "K2DLL-10>KC2EHR" is the RMS server responding to my radio's request to establish a connection?
2) Is there some reference someone can point me to that describes the command structure of these interactions so I can try to figure out what is going wrong?
3) Has anyone seen this before and can recommend some things to try?
I am using a very humble hardware setup: Baofeng uv-5r + Raspberry Pi 4 + home made PTT relay circuit + USB sound card dongle.? Since I just built the Pi from scratch over the past 5 days, I am pretty sure I am using the latest versions of everything.
Thanks in advance for any ideas on next steps.
Mike
KC2EHR
|
It's hard to tell exactly what is going on without understanding the larger context.
However, I can provide a few clues for troubleshooting.
"SABM" is a connect request.? Your station would send this to establish a connection with a bulletin board system, RMS server, etc.
The expected response is either:
- "UA" connection accepted or
- "DM" connection refused.
Instead we see "I" (information) frames so it looks like the other end thinks it already has an established connection.
"DISC" is a disconnect request.
Chapter 10 of the Dire Wolf User Guide has a quick overview of the connection sequence.
For the advanced user, Why-is-9600-only-twice-as-fast-as-1200.pdf goes into more details about acknowledgements, timeouts, retries, and efficiency.
|
Hello Michael,
Everything seems to be working, however, I am unable
to establish a connection with my local Remote Message Server.
Ok.
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
This is your KC2EHR system making an outgoing connection request to
K2DLL-10.? That's good.
?K2DLL-10 audio level =
96(13/8)? ?[NONE]? ?____|||__
[0.5] K2DLL-10>KC2EHR:(I
cmd, n(s)=0, n(r)=0, p=0,
pid=0xf0)[WL2K-5.0-B2FWIHJM$]<0x0d>
This is K2DLL-10 responding to your connection request to data but
you're missing some previous packets acknowledging the initial
connection.? Also notice the "96" in the signal level here.? That's
too high.? You need to lower your RX audio to show levels around
50.? This is critically important.? Equally as important, you will
also need to ensure your transmitted level is right as well.? I
recommend to read
which can give
you a few ways to help tune your transmit levels.
K2DLL-10 audio level =
59(11/7)? ?[NONE]? ?___|||||_
[0.5] K2DLL-10>KC2EHR:(I
cmd, n(s)=1, n(r)=0, p=0, pid=0xf0);PQ: 12009205<0x0d>
?
K2DLL-10 audio level =
102(23/13)? ?[NONE]? ?____|||__
[0.5] K2DLL-10>KC2EHR:(I
cmd, n(s)=2, n(r)=0, p=0, pid=0xf0)CMS via K2DLL
><0x0d>
These are other packets coming from the remote station.
?
K2DLL-10 audio level =
127(13/9)? ?[NONE]? ?____|||__
Audio input level is too
high.? Reduce so most stations are around 50.
[0.5] K2DLL-10>KC2EHR:(DM
res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC
cmd, p=1)
It's strange that we don't see your system sending retries for the
initial connection.? In another Linux terminal window, you can run
"sudo listen -a" and see similar AX.25 packet frames to confirm what
the Linux stack is seeing.
1) Am I correct in that the
Direwolf lines that start with "K2DLL-10>KC2EHR" is the RMS
server responding to my radio's request to establish a
connection?
Yes..
2) Is there some reference
someone can point me to that describes the command structure
of these interactions so I can try to figure out what is going
wrong?
There is a lot of technical docs out there but here are two:
?? - Simple summary:
?? - The standard itself:
I am using a very humble
hardware setup: Baofeng uv-5r + Raspberry Pi 4 + home made PTT
relay circuit + USB sound card dongle.? Since I just built the
Pi from scratch over the past 5 days, I am pretty sure I am
using the latest versions of everything.
Some Baofeng radios are notoriously unreliable on packet though they
can be ok for voice communications.? Some people chalk these up to
poor radio quality control from Baofeng but whatever the reason, you
might forever have issues with your specific radio.? Some people
have reported that they had to go though several Baofeng radios
until they found one that would wort reliably.? It's *highly*
recommended to use better quality radios as you'll save yourself
tearing your hair out.?
The other things to consider:
?? - Depending on how close the remote station is, 5w from an HT
might not be enough
?? - When trying to make a connection, the antenna is critically
important.? If at all possible, get the antenna out side and ideally
as high as possible
?? - The stock Baofeng antennas are usually pretty terrible.? If
you're operating from home, you should ideally be use a high gain
base station antenna using low loss coax.? If your intention is to
always operate "portable", buy a better 3rd party antenna for your
HT and locate your HT as high up as possible (be away from
structures and buildings)
--David
|
I agree about the audio levels - I have figured out how to stabilize the audio level response from the Remote Message Server, but I am still unable to connect.? The RMS seems to be immediately issuing a DM, which I believe is a connection refused message.? Also, I noticed a message from Direwolf about needing to issue a "kissparms -c 1 -p radio" command, so I did that.? This got rid of the Direwolf message on the next restart, but I am still getting the DM messages from the RMS.? I am working through the 3 documents referenced to better understand how it is supposed to work.? I continue to try different antennas, located in different locations.? Progress, but no success yet...
?
Pat Winlink Log 3/24/2021
-------------------------
pi@RaspPi4:~ $ sudo kissattach /dev/pts/8 wl2k
AX.25 port wl2k bound to device ax0
pi@RaspPi4:~ $ kissparms -c 1 -p wl2k
kissparms: socket: Operation not permitted
pi@RaspPi4:~ $ sudo kissparms -c 1 -p wl2k
pi@RaspPi4:~ $ pat http
2021/03/24 16:28:41 Starting HTTP service (0.0.0.0:5000)...
2021/03/24 16:29:14 Connecting to K2DLL-10 (ax25)...
2021/03/24 16:29:59 Unable to establish connection to remote: Dial timeout
?
Direwolf Log 3/24/2021
----------------------
pi@RaspPi4:~ $ sudo direwolf -p
Dire Wolf version 1.6
Includes optional support for:? hamlib cm108-ptt
?
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Virtual KISS TNC is available on /dev/pts/7
Created symlink /tmp/kisstnc -> /dev/pts/7
Invalid transmit channel 8 from KISS client app.
?
Are you using AX.25 for Linux?? It might be trying to use a modified
version of KISS which uses the port (channel) field differently than the
original KISS protocol specification.? The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1
?
?
<<< Data frame from KISS client application, port 8, total length = 18
? 010:? c9 d9? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ..
Invalid transmit channel 2 from KISS client app.
?
Are you using AX.25 for Linux?? It might be trying to use a modified
version of KISS which uses the port (channel) field differently than the
original KISS protocol specification.? The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1
?
?
<<< Data frame from KISS client application, port 2, total length = 18
? 010:? 24 20? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? $?
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?|||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
?
KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(DISC cmd, p=1)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?||||||___
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
KC2EHR audio level = 10(10/10)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
K2DLL-10 audio level = 50(21/21)? ?[NONE]? ?|||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
KC2EHR audio level = 0(0/0)? ?[NONE]? ?|||||____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
K2DLL-10 audio level = 49(20/21)? ?[NONE]? ?|||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
?
KC2EHR audio level = 0(3/3)? ?[NONE]? ?|||||____
[0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)
|
I have made some progress and now have good audio levels and am getting stable call/response between my home radio setup and the RMS.
However, it seems like my station calls for SAMB, then the RMS returns with the expected RR (ready to receive), but my station ignores this
and sends another SAMB anyway.? Then the RMS sends a DM (Disconnect) command.
Any ideas why my station is not continuing on with the connection steps after the RR command from the RMS?
Thanks in advance for your help.
Mike KC2EHR
Direwolf Log 3/25/2021 ---------------------------------
pi@RaspPi4:~ $ sudo direwolf -p
Dire Wolf version 1.6
Includes optional support for: ?hamlib cm108-ptt
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,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 ...
Virtual KISS TNC is available on /dev/pts/2
Created symlink /tmp/kisstnc -> /dev/pts/2
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 0(0/0) ? [NONE] ? _|||_____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 55(22/23) ? [NONE] ? |||||____
[0.2] K2DLL-10>KC2EHR:(RR cmd, n(r)=0, p=1)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 2(6/7) ? [NONE] ? |||||____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 55(22/23) ? [NONE] ? |||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 0(0/0) ? [NONE] ? |||||____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 54(21/23) ? [NONE] ? ||||||___
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
KC2EHR audio level = 0(1/1) ? [NONE] ? |||||____
[0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)
On Wed, Mar 24, 2021 at 5:06 PM Michael LaBlanc via <mlablan1= [email protected]> wrote: I agree about the audio levels - I have figured out how to stabilize the audio level response from the Remote Message Server, but I am still unable to connect.? The RMS seems to be immediately issuing a DM, which I believe is a connection refused message.? Also, I noticed a message from Direwolf about needing to issue a "kissparms -c 1 -p radio" command, so I did that.? This got rid of the Direwolf message on the next restart, but I am still getting the DM messages from the RMS.? I am working through the 3 documents referenced to better understand how it is supposed to work.? I continue to try different antennas, located in different locations.? Progress, but no success yet...
?
Pat Winlink Log 3/24/2021
-------------------------
pi@RaspPi4:~ $ sudo kissattach /dev/pts/8 wl2k
AX.25 port wl2k bound to device ax0
pi@RaspPi4:~ $ kissparms -c 1 -p wl2k
kissparms: socket: Operation not permitted
pi@RaspPi4:~ $ sudo kissparms -c 1 -p wl2k
pi@RaspPi4:~ $ pat http
2021/03/24 16:28:41 Starting HTTP service (0.0.0.0:5000)...
2021/03/24 16:29:14 Connecting to K2DLL-10 (ax25)...
2021/03/24 16:29:59 Unable to establish connection to remote: Dial timeout
?
Direwolf Log 3/24/2021
----------------------
pi@RaspPi4:~ $ sudo direwolf -p
Dire Wolf version 1.6
Includes optional support for:? hamlib cm108-ptt
?
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Virtual KISS TNC is available on /dev/pts/7
Created symlink /tmp/kisstnc -> /dev/pts/7
Invalid transmit channel 8 from KISS client app.
?
Are you using AX.25 for Linux?? It might be trying to use a modified
version of KISS which uses the port (channel) field differently than the
original KISS protocol specification.? The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1
?
?
<<< Data frame from KISS client application, port 8, total length = 18
? 010:? c9 d9? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ..
Invalid transmit channel 2 from KISS client app.
?
Are you using AX.25 for Linux?? It might be trying to use a modified
version of KISS which uses the port (channel) field differently than the
original KISS protocol specification.? The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1
?
?
<<< Data frame from KISS client application, port 2, total length = 18
? 010:? 24 20? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? $?
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?|||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
?
KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(DISC cmd, p=1)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?||||||___
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
KC2EHR audio level = 10(10/10)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
K2DLL-10 audio level = 50(21/21)? ?[NONE]? ?|||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
KC2EHR audio level = 0(0/0)? ?[NONE]? ?|||||____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
?
K2DLL-10 audio level = 49(20/21)? ?[NONE]? ?|||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
?
KC2EHR audio level = 0(3/3)? ?[NONE]? ?|||||____
[0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)
|
On Thu, Mar 25, 2021 at 08:53 AM, Michael LaBlanc wrote:
However, it seems like my station calls for SAMB, then the RMS returns with the expected RR (ready to receive), but my station ignores this
and sends another SAMB anyway.? Then the RMS sends a DM (Disconnect) command.
RR is not expected at this point. The station requesting a connection sends SABM until one of the following happens: - Receive UA frame which means the connection has been accepted. - Receive DM frame which means the connection has been refused. - Retry count has been exceeded. The relevant state diagrams can be found on pages? 86 - 88? here:?? The other station is refusing the connection: [0.2] K2DLL-10>KC2EHR:(DM res, f=0)
|
I have seem some TNCs that have a larger packet window configured,
they sometimes will both accept the initial connection AND send
subsequent payload packets before the connection is confirmed up.? I
imagine this is a AX.25 protocol violation but none-the-less, I've
seen it.? Since your system missed the "UA" connection request
acknowledge frame, your system will retry the connection attempt by
sending another SABM packet.? If you have a clean packet channel,
retries will eventually figure things out and get things working.
Btw, if the initial connection is always being
answered with a DM, either the remote station has another packet
connection on or there is an issue with the remote station.? To do
more testing, that remote Winlink station might have other other
SSIDs listening so try connecting to other SSID values like -5 or
-7 as those are commonly open if they are using a hardware TNC.?
The winlink session won't work but you should be able to see if
you can at least create a successful AX.25 connection.?? If not,
try another Winlink station or any other reachable packet station
on other packet frequencies used in your geo.
--David
KI6ZHD
On 03/25/2021 07:13 AM, WB2OSZ wrote:
toggle quoted message
Show quoted text
On Thu, Mar 25, 2021 at 08:53 AM, Michael LaBlanc
wrote:
However, it seems like my station calls for SAMB, then the
RMS returns with the expected RR (ready to receive), but my
station ignores this
and sends another SAMB anyway.? Then the RMS sends a DM
(Disconnect) command.
RR is not expected at this point.
The station requesting a connection sends SABM until one of the
following happens:
- Receive UA frame which means the connection has been accepted.
- Receive DM frame which means the connection has been refused.
- Retry count has been exceeded.
The relevant state diagrams can be found on pages? 86 - 88?
here:??
The other station is refusing the connection:
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
|
I know you won't want to hear this .....
The problem may be as simple as using the Baofeng radio, those radios having a very solid reputation for poor performance for packet radio. Rx recovery time after dropping PTT is unacceptably long and somewhat unpredictable in this regard regardless of running squelched or unsquelched. The rx recovery time is a long way from good enough for data. That problem can only be solved by getting other stations to increase their TXD to unacceptable times, to the detriment of the entire network.
If you search the archives you'll find poor Baofeng performance mentioned over and over again. I have the skills and test equipment but gave up on trying to use the Baofeng for packet radio, and I'm not the only one.
The frequently recommended fix is to source a used "brand name" radio and use that instead.
Ray vk2tv
toggle quoted message
Show quoted text
On 25/3/21 11:52 pm, Michael LaBlanc wrote: I have made some progress and now have good audio levels and am getting stable call/response between my home radio setup and the RMS.
However, it seems like my station calls for SAMB, then the RMS returns with the expected RR (ready to receive), but my station ignores this
and sends another SAMB anyway.? Then the RMS sends a DM (Disconnect) command.
Any ideas why my station is not continuing on with the connection steps after the RR command from the RMS?
Thanks in advance for your help.
Mike
KC2EHR
Direwolf Log 3/25/2021
---------------------------------
pi@RaspPi4:~ $ sudo direwolf -p
Dire Wolf version 1.6
Includes optional support for: ?hamlib cm108-ptt
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,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 ...
Virtual KISS TNC is available on /dev/pts/2
Created symlink /tmp/kisstnc -> /dev/pts/2
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 0(0/0) ? [NONE] ? _|||_____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 55(22/23) ? [NONE] ? |||||____
[0.2] K2DLL-10>KC2EHR:(RR cmd, n(r)=0, p=1)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 2(6/7) ? [NONE] ? |||||____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 55(22/23) ? [NONE] ? |||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 0(0/0) ? [NONE] ? |||||____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 54(21/23) ? [NONE] ? ||||||___
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
KC2EHR audio level = 0(1/1) ? [NONE] ? |||||____
[0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)
On Wed, Mar 24, 2021 at 5:06 PM Michael LaBlanc via groups.io <> <mlablan1@... <mailto:[email protected]>> wrote:
I agree about the audio levels - I have figured out how to
stabilize the audio level response from the Remote Message Server,
but I am still unable to connect.? The RMS seems to be immediately
issuing a DM, which I believe is a connection refused message.?
Also, I noticed a message from Direwolf about needing to issue a
"kissparms -c 1 -p radio" command, so I did that.? This got rid of
the Direwolf message on the next restart, but I am still getting
the DM messages from the RMS.? I am working through the 3
documents referenced to better understand how it is supposed to
work.? I continue to try different antennas, located in different
locations.? Progress, but no success yet...
Pat Winlink Log 3/24/2021
-------------------------
pi@RaspPi4:~ $ sudo kissattach /dev/pts/8 wl2k
AX.25 port wl2k bound to device ax0
pi@RaspPi4:~ $ kissparms -c 1 -p wl2k
kissparms: socket: Operation not permitted
pi@RaspPi4:~ $ sudo kissparms -c 1 -p wl2k
pi@RaspPi4:~ $ pat http
2021/03/24 16:28:41 Starting HTTP service (0.0.0.0:5000)...
2021/03/24 16:29:14 Connecting to K2DLL-10 (ax25)...
2021/03/24 16:29:59 Unable to establish connection to remote: Dial
timeout
Direwolf Log 3/24/2021
----------------------
pi@RaspPi4:~ $ sudo direwolf -p
Dire Wolf version 1.6
Includes optional support for:? hamlib cm108-ptt
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Virtual KISS TNC is available on /dev/pts/7
Created symlink /tmp/kisstnc -> /dev/pts/7
Invalid transmit channel 8 from KISS client app.
Are you using AX.25 for Linux?? It might be trying to use a modified
version of KISS which uses the port (channel) field differently
than the
original KISS protocol specification.? The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module
with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1
<<< Data frame from KISS client application, port 8, total length = 18
? 000:? 80 96 64 88 98 98 40 f4 96 86 64 8a 90 a4 61 3f?
[email protected]?
? 010:? c9 d9 ? ? ..
Invalid transmit channel 2 from KISS client app.
Are you using AX.25 for Linux?? It might be trying to use a modified
version of KISS which uses the port (channel) field differently
than the
original KISS protocol specification.? The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module
with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1
<<< Data frame from KISS client application, port 2, total length = 18
? 000:? 20 96 64 88 98 98 40 f4 96 86 64 8a 90 a4 61 3f?
[email protected]?
? 010:? 24 20 ? ? $
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?|||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(DISC cmd, p=1)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?||||||___
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 10(10/10)? ?[NONE]? ?||||_____
[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 50(21/21)? ?[NONE]? ?|||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
KC2EHR audio level = 0(0/0)? ?[NONE]? ?|||||____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
K2DLL-10 audio level = 49(20/21)? ?[NONE]? ?|||||____
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
KC2EHR audio level = 0(3/3)? ?[NONE]? ?|||||____
[0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)
|
Today I successfully connected to my local 1200 baud, packet Remote
Message Server about 10 times and was able to both send and receive
email messages.
What allowed me to do this was
to swap out the Baofeng UV-5R for a 21 year old Kenwood TNC.? I used the
exact same antenna, in the exact same spot and left the software
configuration for the Pi, Pat Winlink, and Direwolf the same.
I
know some folks have been successful with the UV-5R's on packet, but
the 2 Baofeng's that I own (purchased from Amazon about 2 years ago) did
not seem to be up to the task.
I want to send
out a HUGE THANKS to everyone that responded with all your helpful
suggestions.? As I am just returning to the Ham Radio hobby after a long
absence, it is totally inspiring to find a vibrant community willing to
help out a newbie.
Thanks again,
Mike KC3EHR
On Thu, Mar 25, 2021 at 5:05 PM Ray Wells < aprs@...> wrote: I know you won't want to hear this .....
The problem may be as simple as using the Baofeng radio, those radios
having a very solid reputation for poor performance for packet radio. Rx
recovery time after dropping PTT is unacceptably long and somewhat
unpredictable in this regard regardless of running squelched or
unsquelched. The rx recovery time is a long way from good enough for
data. That problem can only be solved by getting other stations to
increase their TXD to unacceptable times, to the detriment of the entire
network.
If you search the archives you'll find poor Baofeng performance
mentioned over and over again. I have the skills and test equipment but
gave up on trying to use the Baofeng for packet radio, and I'm not the
only one.
The frequently recommended fix is to source a used "brand name" radio
and use that instead.
Ray vk2tv
On 25/3/21 11:52 pm, Michael LaBlanc wrote:
> I have made some progress and now have good audio levels and am
> getting stable call/response between my home radio setup and the RMS.
>
> However, it seems like my station calls for SAMB, then the RMS returns
> with the expected RR (ready to receive), but my station ignores this
> and sends another SAMB anyway.? Then the RMS sends a DM (Disconnect)
> command.
>
> Any ideas why my station is not continuing on with the connection
> steps after the RR command from the RMS?
>
> Thanks in advance for your help.
>
> Mike
> KC2EHR
>
> Direwolf Log 3/25/2021
> ---------------------------------
>
> pi@RaspPi4:~ $ sudo direwolf -p
> Dire Wolf version 1.6
> Includes optional support for: ?hamlib cm108-ptt
>
> Reading config file direwolf.conf
> Audio device for both receive and transmit: plughw:2,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 ...
> Virtual KISS TNC is available on /dev/pts/2
> Created symlink /tmp/kisstnc -> /dev/pts/2
> [0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> KC2EHR audio level = 0(0/0) ? [NONE] ? _|||_____
> [0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> K2DLL-10 audio level = 55(22/23) ? [NONE] ? |||||____
> [0.2] K2DLL-10>KC2EHR:(RR cmd, n(r)=0, p=1)
> [0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> KC2EHR audio level = 2(6/7) ? [NONE] ? |||||____
> [0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> K2DLL-10 audio level = 55(22/23) ? [NONE] ? |||||____
> [0.2] K2DLL-10>KC2EHR:(DM res, f=0)
> [0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> KC2EHR audio level = 0(0/0) ? [NONE] ? |||||____
> [0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> K2DLL-10 audio level = 54(21/23) ? [NONE] ? ||||||___
> [0.2] K2DLL-10>KC2EHR:(DM res, f=0)
> [0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>
> KC2EHR audio level = 0(1/1) ? [NONE] ? |||||____
> [0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>
> On Wed, Mar 24, 2021 at 5:06 PM Michael LaBlanc via
> <> <mlablan1=[email protected]
> <mailto:[email protected]>> wrote:
>
>? ? ?I agree about the audio levels - I have figured out how to
>? ? ?stabilize the audio level response from the Remote Message Server,
>? ? ?but I am still unable to connect.? The RMS seems to be immediately
>? ? ?issuing a DM, which I believe is a connection refused message.?
>? ? ?Also, I noticed a message from Direwolf about needing to issue a
>? ? ?"kissparms -c 1 -p radio" command, so I did that.? This got rid of
>? ? ?the Direwolf message on the next restart, but I am still getting
>? ? ?the DM messages from the RMS.? I am working through the 3
>? ? ?documents referenced to better understand how it is supposed to
>? ? ?work.? I continue to try different antennas, located in different
>? ? ?locations.? Progress, but no success yet...
>? ? ?Pat Winlink Log 3/24/2021
>? ? ?-------------------------
>? ? ?pi@RaspPi4:~ $ sudo kissattach /dev/pts/8 wl2k
>? ? ?AX.25 port wl2k bound to device ax0
>? ? ?pi@RaspPi4:~ $ kissparms -c 1 -p wl2k
>? ? ?kissparms: socket: Operation not permitted
>? ? ?pi@RaspPi4:~ $ sudo kissparms -c 1 -p wl2k
>? ? ?pi@RaspPi4:~ $ pat http
>? ? ?2021/03/24 16:28:41 Starting HTTP service (0.0.0.0:5000)...
>? ? ?2021/03/24 16:29:14 Connecting to K2DLL-10 (ax25)...
>? ? ?2021/03/24 16:29:59 Unable to establish connection to remote: Dial
>? ? ?timeout
>? ? ?Direwolf Log 3/24/2021
>? ? ?----------------------
>? ? ?pi@RaspPi4:~ $ sudo direwolf -p
>? ? ?Dire Wolf version 1.6
>? ? ?Includes optional support for:? hamlib cm108-ptt
>? ? ?Reading config file direwolf.conf
>? ? ?Audio device for both receive and transmit: plughw:2,0? (channel 0)
>? ? ?Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
>? ? ?Ready to accept AGW client application 0 on port 8000 ...
>? ? ?Ready to accept KISS TCP client application 0 on port 8001 ...
>? ? ?Virtual KISS TNC is available on /dev/pts/7
>? ? ?Created symlink /tmp/kisstnc -> /dev/pts/7
>? ? ?Invalid transmit channel 8 from KISS client app.
>? ? ?Are you using AX.25 for Linux?? It might be trying to use a modified
>? ? ?version of KISS which uses the port (channel) field differently
>? ? ?than the
>? ? ?original KISS protocol specification.? The solution might be to use
>? ? ?a command like "kissparms -c 1 -p radio" to set CRC none mode.
>? ? ?Another way of doing this is pre-loading the "kiss" kernel module
>? ? ?with CRC disabled:
>? ? ?sudo /sbin/modprobe -q mkiss crc_force=1
>? ? ?<<< Data frame from KISS client application, port 8, total length = 18
>? ? ?? 000:? 80 96 64 88 98 98 40 f4 96 86 64 8a 90 a4 61 3f?
>? ? [email protected]?
>? ? ?? 010:? c9 d9 ? ? ..
>? ? ?Invalid transmit channel 2 from KISS client app.
>? ? ?Are you using AX.25 for Linux?? It might be trying to use a modified
>? ? ?version of KISS which uses the port (channel) field differently
>? ? ?than the
>? ? ?original KISS protocol specification.? The solution might be to use
>? ? ?a command like "kissparms -c 1 -p radio" to set CRC none mode.
>? ? ?Another way of doing this is pre-loading the "kiss" kernel module
>? ? ?with CRC disabled:
>? ? ?sudo /sbin/modprobe -q mkiss crc_force=1
>? ? ?<<< Data frame from KISS client application, port 2, total length = 18
>? ? ?? 000:? 20 96 64 88 98 98 40 f4 96 86 64 8a 90 a4 61 3f?
>? ? [email protected]?
>? ? ?? 010:? 24 20 ? ? $
>? ? ?[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
>? ? ?[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?|||||____
>? ? ?[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
>? ? ?[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>? ? ?KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
>? ? ?[0.1] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>? ? ?[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
>? ? ?[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?||||||___
>? ? ?[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
>? ? ?[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?KC2EHR audio level = 10(10/10)? ?[NONE]? ?||||_____
>? ? ?[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?K2DLL-10 audio level = 50(21/21)? ?[NONE]? ?|||||____
>? ? ?[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
>? ? ?[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?KC2EHR audio level = 0(0/0)? ?[NONE]? ?|||||____
>? ? ?[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?K2DLL-10 audio level = 49(20/21)? ?[NONE]? ?|||||____
>? ? ?[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
>? ? ?[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>? ? ?KC2EHR audio level = 0(3/3)? ?[NONE]? ?|||||____
>? ? ?[0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>
>
|
CORRECTION -
??
I swaped out the Baofeng UV-5R for a 21 year old Kenwood HT ?? NOT a TNC
On Thu, Mar 25, 2021 at 10:13 AM WB2OSZ < wb2osz@...> wrote: On Thu, Mar 25, 2021 at 08:53 AM, Michael LaBlanc wrote:
However, it seems like my station calls for SAMB, then the RMS returns with the expected RR (ready to receive), but my station ignores this
and sends another SAMB anyway.? Then the RMS sends a DM (Disconnect) command.
RR is not expected at this point.
The station requesting a connection sends SABM until one of the following happens:
- Receive UA frame which means the connection has been accepted.
- Receive DM frame which means the connection has been refused.
- Retry count has been exceeded.
The relevant state diagrams can be found on pages? 86 - 88? here:??
The other station is refusing the connection:
[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
|
Thanks for the update here Michael and we really
need to pin your post on Groups.IO.? Why?? There are many users
trying to setup packet stations with Baofeng and other too-cheap
radios due to new / popular Youtube videos, the solution cost is
so low not to try it, etc. yet few will have real *complete*
success.
--David
KI6ZHD
On 03/26/2021 12:26 PM, Michael LaBlanc
wrote:
toggle quoted message
Show quoted text
Today I successfully connected to my local 1200 baud,
packet Remote Message Server about 10 times and was able to
both send and receive email messages.
What allowed me to do this was to swap out the Baofeng
UV-5R for a 21 year old Kenwood TNC.? I used the exact same
antenna, in the exact same spot and left the software
configuration for the Pi, Pat Winlink, and Direwolf the same.
I know some folks have been successful with the UV-5R's on
packet, but the 2 Baofeng's that I own (purchased from Amazon
about 2 years ago) did not seem to be up to the task.
I want to send out a HUGE THANKS to everyone that responded
with all your helpful suggestions.? As I am just returning to
the Ham Radio hobby after a long absence, it is totally
inspiring to find a vibrant community willing to help out a
newbie.
Thanks again,
Mike
KC3EHR
On Thu, Mar 25, 2021 at 5:05
PM Ray Wells < aprs@...>
wrote:
I
know you won't want to hear this .....
The problem may be as simple as using the Baofeng radio, those
radios
having a very solid reputation for poor performance for packet
radio. Rx
recovery time after dropping PTT is unacceptably long and
somewhat
unpredictable in this regard regardless of running squelched
or
unsquelched. The rx recovery time is a long way from good
enough for
data. That problem can only be solved by getting other
stations to
increase their TXD to unacceptable times, to the detriment of
the entire
network.
If you search the archives you'll find poor Baofeng
performance
mentioned over and over again. I have the skills and test
equipment but
gave up on trying to use the Baofeng for packet radio, and I'm
not the
only one.
The frequently recommended fix is to source a used "brand
name" radio
and use that instead.
Ray vk2tv
On 25/3/21 11:52 pm, Michael LaBlanc wrote:
> I have made some progress and now have good audio levels
and am
> getting stable call/response between my home radio setup
and the RMS.
>
> However, it seems like my station calls for SAMB, then
the RMS returns
> with the expected RR (ready to receive), but my station
ignores this
> and sends another SAMB anyway.? Then the RMS sends a DM
(Disconnect)
> command.
>
> Any ideas why my station is not continuing on with the
connection
> steps after the RR command from the RMS?
>
> Thanks in advance for your help.
>
> Mike
> KC2EHR
>
> Direwolf Log 3/25/2021
> ---------------------------------
>
> pi@RaspPi4:~ $ sudo direwolf -p
> Dire Wolf version 1.6
> Includes optional support for: ?hamlib cm108-ptt
>
> Reading config file direwolf.conf
> Audio device for both receive and transmit: plughw:2,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 ...
> Virtual KISS TNC is available on /dev/pts/2
> Created symlink /tmp/kisstnc -> /dev/pts/2
> [0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> KC2EHR audio level = 0(0/0) ? [NONE] ? _|||_____
> [0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> K2DLL-10 audio level = 55(22/23) ? [NONE] ? |||||____
> [0.2] K2DLL-10>KC2EHR:(RR cmd, n(r)=0, p=1)
> [0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> KC2EHR audio level = 2(6/7) ? [NONE] ? |||||____
> [0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> K2DLL-10 audio level = 55(22/23) ? [NONE] ? |||||____
> [0.2] K2DLL-10>KC2EHR:(DM res, f=0)
> [0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> KC2EHR audio level = 0(0/0) ? [NONE] ? |||||____
> [0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>
> K2DLL-10 audio level = 54(21/23) ? [NONE] ? ||||||___
> [0.2] K2DLL-10>KC2EHR:(DM res, f=0)
> [0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>
> KC2EHR audio level = 0(1/1) ? [NONE] ? |||||____
> [0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>
> On Wed, Mar 24, 2021 at 5:06 PM Michael LaBlanc via
> <>
<mlablan1=[email protected]
> <mailto:[email protected]>>
wrote:
>
>? ? ?I agree about the audio levels - I have figured out
how to
>? ? ?stabilize the audio level response from the Remote
Message Server,
>? ? ?but I am still unable to connect.? The RMS seems to
be immediately
>? ? ?issuing a DM, which I believe is a connection refused
message.?
>? ? ?Also, I noticed a message from Direwolf about needing
to issue a
>? ? ?"kissparms -c 1 -p radio" command, so I did that.?
This got rid of
>? ? ?the Direwolf message on the next restart, but I am
still getting
>? ? ?the DM messages from the RMS.? I am working through
the 3
>? ? ?documents referenced to better understand how it is
supposed to
>? ? ?work.? I continue to try different antennas, located
in different
>? ? ?locations.? Progress, but no success yet...
>? ? ?Pat Winlink Log 3/24/2021
>? ? ?-------------------------
>? ? ?pi@RaspPi4:~ $ sudo kissattach /dev/pts/8 wl2k
>? ? ?AX.25 port wl2k bound to device ax0
>? ? ?pi@RaspPi4:~ $ kissparms -c 1 -p wl2k
>? ? ?kissparms: socket: Operation not permitted
>? ? ?pi@RaspPi4:~ $ sudo kissparms -c 1 -p wl2k
>? ? ?pi@RaspPi4:~ $ pat http
>? ? ?2021/03/24 16:28:41 Starting HTTP service
(0.0.0.0:5000)...
>? ? ?2021/03/24 16:29:14 Connecting to K2DLL-10 (ax25)...
>? ? ?2021/03/24 16:29:59 Unable to establish connection to
remote: Dial
>? ? ?timeout
>? ? ?Direwolf Log 3/24/2021
>? ? ?----------------------
>? ? ?pi@RaspPi4:~ $ sudo direwolf -p
>? ? ?Dire Wolf version 1.6
>? ? ?Includes optional support for:? hamlib cm108-ptt
>? ? ?Reading config file direwolf.conf
>? ? ?Audio device for both receive and transmit:
plughw:2,0? (channel 0)
>? ? ?Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+,
44100 sample rate / 3.
>? ? ?Ready to accept AGW client application 0 on port 8000
...
>? ? ?Ready to accept KISS TCP client application 0 on port
8001 ...
>? ? ?Virtual KISS TNC is available on /dev/pts/7
>? ? ?Created symlink /tmp/kisstnc -> /dev/pts/7
>? ? ?Invalid transmit channel 8 from KISS client app.
>? ? ?Are you using AX.25 for Linux?? It might be trying to
use a modified
>? ? ?version of KISS which uses the port (channel) field
differently
>? ? ?than the
>? ? ?original KISS protocol specification.? The solution
might be to use
>? ? ?a command like "kissparms -c 1 -p radio" to set CRC
none mode.
>? ? ?Another way of doing this is pre-loading the "kiss"
kernel module
>? ? ?with CRC disabled:
>? ? ?sudo /sbin/modprobe -q mkiss crc_force=1
>? ? ?<<< Data frame from KISS client application,
port 8, total length = 18
>? ? ?? 000:? 80 96 64 88 98 98 40 f4 96 86 64 8a 90 a4 61
3f?
>? ? [email protected]?
>? ? ?? 010:? c9 d9 ? ? ..
>? ? ?Invalid transmit channel 2 from KISS client app.
>? ? ?Are you using AX.25 for Linux?? It might be trying to
use a modified
>? ? ?version of KISS which uses the port (channel) field
differently
>? ? ?than the
>? ? ?original KISS protocol specification.? The solution
might be to use
>? ? ?a command like "kissparms -c 1 -p radio" to set CRC
none mode.
>? ? ?Another way of doing this is pre-loading the "kiss"
kernel module
>? ? ?with CRC disabled:
>? ? ?sudo /sbin/modprobe -q mkiss crc_force=1
>? ? ?<<< Data frame from KISS client application,
port 2, total length = 18
>? ? ?? 000:? 20 96 64 88 98 98 40 f4 96 86 64 8a 90 a4 61
3f?
>? ? [email protected]?
>? ? ?? 010:? 24 20 ? ? $
>? ? ?[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
>? ? ?[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?|||||____
>? ? ?[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
>? ? ?[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>? ? ?KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
>? ? ?[0.1] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>? ? ?[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?KC2EHR audio level = 0(0/0)? ?[NONE]? ?||||_____
>? ? ?[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?K2DLL-10 audio level = 50(20/21)? ?[NONE]? ?||||||___
>? ? ?[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
>? ? ?[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?KC2EHR audio level = 10(10/10)? ?[NONE]? ?||||_____
>? ? ?[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?K2DLL-10 audio level = 50(21/21)? ?[NONE]? ?|||||____
>? ? ?[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
>? ? ?[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?KC2EHR audio level = 0(0/0)? ?[NONE]? ?|||||____
>? ? ?[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)
>? ? ?K2DLL-10 audio level = 49(20/21)? ?[NONE]? ?|||||____
>? ? ?[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
>? ? ?[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>? ? ?KC2EHR audio level = 0(3/3)? ?[NONE]? ?|||||____
>? ? ?[0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)
>
>
|
