Topics

minicom->pilinbpq->direwold->udrc-II, getting decodes but no transmit.


udrc@...
 

I am shifting gears from FLDIGI, can't get that package to work yet at all.

Thought I would try VHF BBS's in the area, my local ARES BBS in this case.

Using the default device for UDRC (not virtual sound card), I started up direwolf to create the KISS TNC port on TCP/8001. I then used pilinbpq to attach to that device at 127.0.0.1 port 8001. Then using Minicom to attach to the /tmp/com1 port as a full TNC2 port, I got my familiar CMD: promt, and started a call to the local BBS (144.990 MHz in PKT mode on the radio, 1200 Baud) K7CLL-8 is it's call.


I am delighted to see decodes, yay! Audio in is working in this mode at least. But I swear, FLDIGI was able to use teh GPIO PTT, but direwolf seems to not be able to. I get no PTT action at all.


[0.2] KC7ILK>CQ:Martin, East Mnnehaha, Vancouver, WA, USA<0x0d>
Unknown message type M

KC7ILK audio level = 87(48/39)   [NONE]   _|||||||_
[1.4] KC7ILK>CQ:Martin, East Mnnehaha, Vancouver, WA, USA<0x0d>
Unknown message type M
[0L] N7CKY-4>K7CLL-8:
[0L] N7CKY-4>K7CLL-8:
[0L] N7CKY-4>K7CLL-8:
[0L] N7CKY-4>K7CLL-8:

KB7FND-3 audio level = 0(0/0)   [NONE]   ||||||___
[0.2] KB7FND-3>BEACON:T#798,234,120,075,045,138,01110011<0x0d>
Telemetry, FIRE TRUCK
Seq=798, A1=234, A2=120, A3=75, A4=45, A5=138, D1=0, D2=1, D3=1, D4=1, D5=0, D6=0, D7=1, D8=1

KB7FND-3 audio level = 63(29/23)   [NONE]   |||||||__
[1.3] KB7FND-3>BEACON:T#798,234,120,075,045,138,01110011<0x0d>
Telemetry, FIRE TRUCK
Seq=798, A1=234, A2=120, A3=75, A4=45, A5=138, D1=0, D2=1, D3=1, D4=1, D5=0, D6=0, D7=1, D8=1

Nick





udrc@...
 


OK, so I am wondering in the dfault config, how does direwolf know which port (15 Pin or 6din) to use for that KISS port 8001 it sets up, and what if it's trying to use the 15 Pin? So I restored my Virtual Soundcard setup according to the docs (minus the typo in ADEVICE, there is an extra character there) and rebooted. Started direwolf with:

ADEVICE din6
ACHANNELS 1
CHANNEL 0
MODEM 1200
MYCALL UN1X-3
PTT GPIO 23
KISSPORT 8001

and then started pilinbpq with:

SIMPLE
LOCATOR=NONE
NODECALL=N7CKY-4
TNCPORT
    COMPORT=/tmp/com1
    TYPE=TNC2
    APPNUM=32
    APPFLAGS=6
ENDPORT
PORT
    ID=NICKS TNC
    TYPE=ASYNC
    PROTOCOL=KISS
    IPADDR=127.0.0.1
    TCPPORT=8001
    CHANNEL=A
    MAXFRAME=2
    FRACK=7000
    RESPTIME=1000
    RETRIES=10
    PACLEN=128
    TXDELAY=500
    SLOTTIME=100
    PERSIST=64
ENDPORT

And then attached minicom to the TNC2 port /tmp/com1 with:

minicom -D /tmp/com1 -b 1200

And got my CMD: prompt again, but this time it connects just fine to my local BBS, PTT works! :-D That's two way traffic!! That makes me happy, and gives me confidence that the card is working, and that my other issues might be resolvable by finding the magic settings.


So for this issue, when I am in standard UDRC mode and not Virtual Soundcard mode, what might have been the issue with PTT? It was set for the same pin. <shrug>

Nick







 

Make sure you have the right GPIO selected in the config.

Also try running direwolf with sudo in case you have a permissions problem.

This looks like your sound chip is good.


On Nov 26, 2016 23:37, <udrc@...> wrote:

I am shifting gears from FLDIGI, can't get that package to work yet at all.

Thought I would try VHF BBS's in the area, my local ARES BBS in this case.

Using the default device for UDRC (not virtual sound card), I started up direwolf to create the KISS TNC port on TCP/8001. I then used pilinbpq to attach to that device at 127.0.0.1 port 8001. Then using Minicom to attach to the /tmp/com1 port as a full TNC2 port, I got my familiar CMD: promt, and started a call to the local BBS (144.990 MHz in PKT mode on the radio, 1200 Baud) K7CLL-8 is it's call.


I am delighted to see decodes, yay! Audio in is working in this mode at least. But I swear, FLDIGI was able to use teh GPIO PTT, but direwolf seems to not be able to. I get no PTT action at all.


[0.2] KC7ILK>CQ:Martin, East Mnnehaha, Vancouver, WA, USA<0x0d>
Unknown message type M

KC7ILK audio level = 87(48/39)   [NONE]   _|||||||_
[1.4] KC7ILK>CQ:Martin, East Mnnehaha, Vancouver, WA, USA<0x0d>
Unknown message type M
[0L] N7CKY-4>K7CLL-8:
[0L] N7CKY-4>K7CLL-8:
[0L] N7CKY-4>K7CLL-8:
[0L] N7CKY-4>K7CLL-8:

KB7FND-3 audio level = 0(0/0)   [NONE]   ||||||___
[0.2] KB7FND-3>BEACON:T#798,234,120,075,045,138,01110011<0x0d>
Telemetry, FIRE TRUCK
Seq=798, A1=234, A2=120, A3=75, A4=45, A5=138, D1=0, D2=1, D3=1, D4=1, D5=0, D6=0, D7=1, D8=1

KB7FND-3 audio level = 63(29/23)   [NONE]   |||||||__
[1.3] KB7FND-3>BEACON:T#798,234,120,075,045,138,01110011<0x0d>
Telemetry, FIRE TRUCK
Seq=798, A1=234, A2=120, A3=75, A4=45, A5=138, D1=0, D2=1, D3=1, D4=1, D5=0, D6=0, D7=1, D8=1

Nick






Bernard f6bvp / ai7bg
 

Hi,

When PTT is acting you should see red LED lighting on the side of activated connector either din-6 or hd15 of UDRC board. To check transmit you can use pbeacon on either channels like in sample direwolf.conf file.

Your config for PTT is gpio 23 is for din/6  (default channel or port 1).
If your wiring is on din-6 this is channel 1 ! As your config is setting channel 0 you are expecting audio input and output on hd-15 connector. 

73 de Bernard f6bvp

Envoyé de mon iPhone
Sent from my iPhone
. Started direwolf with:

ADEVICE din6
ACHANNELS 1
CHANNEL 0
MODEM 1200
MYCALL UN1X-3
PTT GPIO 23
KISSPORT 8001

......

So for this issue, when I am in standard UDRC mode and not Virtual Soundcard mode, what might have been the issue with PTT? It was set for the same pin. 


udrc@...
 


In this case, each port is a separate sound card, so they are each their own Channel 0, as this is a working config. I was using the original direwolf.conf from the WIKI Setup for the UDRC-II whne I had it acting as a dual channel sound device.


I admit freely that I tackled several new packages to me all at once to try and turn my RPi into what I get from my Kenwood onboard the radio. Sometimes I am unable to even frame the question properly because I am still learning what I do not know.

I believe Direwolf is my soundcard aware middleware, that presents the KISS and AGWPE ports, it is the software decoding the radio sounds into AX25 like packets for consumption as well as packaging up messages for transmit (and watching the medium for a clear spot to send (COS detect) and using the PTT to send.

Trying to translate that into my world (Ethernet Networking) I would see this as my NIC Driver in a fashion. But I admit to still being a bit baffled as to the addressing part. By setting my NODE ID to say: N7CKY-4, I thought that would be the only source address that I would send. But when I then connect pilinbpq with say N7CKY-3 configured, I saw THAT call go out in the Direwolf console.. (as in my example in this thread, I really did forget to change the UN1X-3 call to my own, but Direwolf never used it) Now I did see the becon lines in the example, that I did not include in my config, perhaps that is where that call is used as a source, when direwolf itself makes a transmission?

But I was able to get pilinbpq to use teh KISS port successfully, AND I went to my desktop Windows PC and got RMS Express to attach to the KISS TCP Port as well. I wasn't able to get my mail though, it would disconnect right away and the winlink gateway I use would keep sending back messages to just "N7CKY" without any SSID added.. not sure what the deal is there yet, but I was able to use the Packet P2P terminal to also hit the ARES BBS, so neat! A little KISS Hot Spot :-D

Now that the sound is shown to work, I am having much more fun at the whole trial and error process.

And thank you all for helping me through this. :-)