Date   

Re: Point to Point (P2P) email transfer #draws

Basil Gunn
 

In your mail apps you address messages using p2p, telnet or ax.25
exactly the same way <some_call_sign>@winlink.org. Do not change this
for p2p.

As I said before once messages are composed and existing in your outbox
directory /usr/local/var/wl2k/outbox, you can send them using p2p
(nearby winlink machine), telnet (CMS) or ax.25 (winlink RMS
Gateway). The messages and how they are addressed are exactly the same
for all the different transports.

To send a message via p2p use wl2kax25 & drop the SSID from the call sign,
that's all there is to it. ie. wl2kax25 -c n7nix

Kevin K. - N7KJK <kkutzera@gmail.com> writes:

OK so the reinstall fixed the PLUWEB.. Thanks..

On the P2P Packet. My friend and I are now reliably handshaking, and
it appears we're transferring messages. I'm sending to his plain call
sign (no @domain) and he's sending to my call sign. He reported the
following information to me.
You are using an unqualified email address. If you did this using mutt
email client it would automatically append the winlink domain.

**
n7kjkpi.localnet says it could not deliver my message, msg "unknown user k7rmz@N7KJKPI.localhost
**
I am of course N7KJK. Not sure where that email address at the end of his report is coming from .

In RainLoop I can't compose a message to him because it requires @domain in the email address.
Claws lets me compose an email to the call sign. (all messages show up in the Sent items folder even before I try to send).
All the email apps require an @domain, specifically <some_callsign>@winlink.org

Somehow while typing this reply, my friend sent me an email directly (no gateway) addressed to N7KJK@winlink.org..
Not sure how that worked...
Did you receive it via internet or radio?

I think something similar to the issue with my email address instead
of pi@localhost. My system doesn't know what to do with a message
addressed to N7KJK (no ssid, no domain, no @)
Correct, the address you use must be a valid email address,
name_or_callsign@<some_actual_domain>

73
Kevin
N7KJK

I can send whatever log segments might help . I'll just not sure which
one's you want to see. I'll certainly update this thread if I find
some interesting information.
Send me the file you are about to send from /usr/local/var/wl2k/outbox.
Looking at that file I can tell you whether it has a chance of being
sent properly.

Exercise for you:
Compose a single message to k7rmz@winlink.org and copy it to a temporary directory.

Send it using: wl2ktelnet

Copy message from temporary directory to /usr/local/var/wl2k/outbox
Send it using: wl2kax25 -c k7rmz-10

Copy message from tmp directory to /usr/local/var/wl2k/outbox
Make sure k7kmz is set to receive via p2p.
Send it using wl2kax25 -c k7kmz

Cut & paste the console output from those 3 transactions in a regular
email to me.

/Basil n7nix


Re: Point to Point (P2P) email transfer #draws

Kevin K. - N7KJK
 


I am getting emails addressed to my winlink.org account. The direwolf logs show that K7RMZ called N7KJK (not N7KJK-10).
Radio is plugged into the right DIN port on the DRAWS

Here's my current Ax25.conf
***********************
#
# When users connect to <incoming callsign>, they will be processed
# by the section that matches.
#
[N7KJK-10 VIA udr1]
NOCALL   * * * * * *  L
default  * * * * * *  - pi /usr/local/bin/rmsgw rmsgw -P %d %U
#
[N7KJK VIA udr1]
NOCALL   * * * * * *  L
default  * * * * * *  - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
#
*****************************
Attaching direwolf.conf


Re: Point to Point (P2P) email transfer #draws

Kevin K. - N7KJK
 

OK so the reinstall fixed the PLUWEB.. Thanks..

On the P2P Packet.  My friend and I are now reliably handshaking, and it appears we're transferring messages.  I'm sending to his plain call sign (no @domain) and he's sending to my call sign. 
He reported the following information to me.
**
 n7kjkpi.localnet says it could not deliver my message, msg "unknown user k7rmz@...
**
I am of course N7KJK.  Not sure where that email address at the end of his report is coming from . 


In RainLoop I can't compose a message to him because it requires @domain  in the email address.
Claws lets me compose an email to the call sign.  (all messages show up in the Sent items folder even before I try to send). 

Somehow while typing this reply,  my friend sent me an email directly (no gateway) addressed to N7KJK@.....
Not sure how that worked...

I think something similar to the issue with my email address instead of pi@localhost.  My system doesn't know what to do with a message addressed to N7KJK  (no ssid, no domain, no @)

73
Kevin
N7KJK





I can send whatever log segments might help .  I'll just not sure which one's you want to see.  I'll certainly update this thread if I find some interesting information.

Kevin


Re: New Draws Case - RPi4 and RPi3

JT Croteau <jt.tobit@...>
 

This looks great, thanks.

N1ESE 

On Fri, Aug 2, 2019, 20:07 Frank Ivan via Groups.Io <k0fei=me.com@groups.io> wrote:
I have uploaded a new 3D printable DRAWS case to Thingiverse https://www.thingiverse.com/thing:3783961.

This is a case for Raspberry Pi 3b or Raspberry Pi 4b + NWDR DRAWS hat with GPS port on side.
It is a modification of RPi3 DRAWS case by N0KZ.

SCAD file provided so you can help tune the design
STL files for both Raspberry Pi 3b or Raspberry Pi 4b - print your choice
Has a powerpole power port
Nice fit for DRAWS card
Rounded corners
Machine screws into card spacers hold case together

Hardware
4 M2.5 x 8mm hex socket head machine screws (8mm does not include head)
4 M2.5 x 11mm female to female spacers
4 M2.5 x 25mm hex socket head machine screws

Assembly
Clean out screw holes - 7/64 or 3mm bit does it nicely
Install Powerpole connector - maybe use a bit of thin double stick tape or super glue to hold in place
Install DRAWS card in lid. It's a close fit but should not be difficult
Push M2.5 x 25mm screws in holes and secure with spacers - finger tight
Plug Pi into DRAWS card - make sure it is aligned correctly and pins go into correct holes
Install base
Secure with the 4 M2.5 x 8mm screws
Tighten every thing up with allen wrench

Note
The Raspberry Pi 4b runs hotter than the Raspberry Pi 3B so the next enhancement
should probably be a fan, perhaps sandwich a POE board with its fan between the
Pi and the DRAWS hat.


Re: Cant compile fldigi on Beta9 #fldigi

Chris Kennedy
 

Consider 512 the minimum swap size to compile fldigi on a pi3.  256 was insufficient.  I monitored it while building and the swap went up to 467MB.

Thanks

Chris KB7NMU


Re: No audio in/out with my FT-817, Pi4, and DRAWS

Chris Metcalf
 

Hmm, I installed and ran DRAWS Manager from source, and set my ALSA settings using its presets. According to alsa-show.sh, the levels are tweaked a bit now but I’m still seeing the same barren field in my waterfall:

 ===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-16.50dB]    R:[-20.00dB]
DAC Playback PT L:[P3]  R:[P3]
LO Playback CM  [Full Chip]
 
 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[-2.00dB]     R:[-2.00dB]
IN1             L:[Off]         R:[Off]
IN2             L:[10 kOhm]     R:[10 kOhm]
CM              L:[10 kOhm]     R:[10 kOhm]

I’m operating remotely at the moment, I’ll double-check everything when I get home. It’s got to be something hardware at this point but I’m out of ideas.

Thanks,
Chris


New Draws Case - RPi4 and RPi3

Frank Ivan
 

I have uploaded a new 3D printable DRAWS case to Thingiverse https://www.thingiverse.com/thing:3783961.

This is a case for Raspberry Pi 3b or Raspberry Pi 4b + NWDR DRAWS hat with GPS port on side.
It is a modification of RPi3 DRAWS case by N0KZ.

SCAD file provided so you can help tune the design
STL files for both Raspberry Pi 3b or Raspberry Pi 4b - print your choice
Has a powerpole power port
Nice fit for DRAWS card
Rounded corners
Machine screws into card spacers hold case together

Hardware
4 M2.5 x 8mm hex socket head machine screws (8mm does not include head)
4 M2.5 x 11mm female to female spacers
4 M2.5 x 25mm hex socket head machine screws

Assembly
Clean out screw holes - 7/64 or 3mm bit does it nicely
Install Powerpole connector - maybe use a bit of thin double stick tape or super glue to hold in place
Install DRAWS card in lid. It's a close fit but should not be difficult
Push M2.5 x 25mm screws in holes and secure with spacers - finger tight
Plug Pi into DRAWS card - make sure it is aligned correctly and pins go into correct holes
Install base
Secure with the 4 M2.5 x 8mm screws
Tighten every thing up with allen wrench

Note
The Raspberry Pi 4b runs hotter than the Raspberry Pi 3B so the next enhancement
should probably be a fan, perhaps sandwich a POE board with its fan between the
Pi and the DRAWS hat.


Re: Point to Point (P2P) email transfer #draws

Basil Gunn
 

Kevin,

For a complete install of the paclink-unix web server do this:

cd
cd n7nix/plu
sudo su
./pluweb_install.sh pi

# Verify with:

systemctl --no-pager status pluweb.service

# run a web browser

On your RPi:
localhost:8082

On a different machine:
<ip_address_of_your_rpi>:8082

/Basil n7nix


Basil Gunn <basil@pacabunga.com> writes:

Kevin K. - N7KJK <kkutzera@gmail.com> writes:

Also is this section with the pluweb failed state normal?
Yes this a problem with the paclink-unix web app install. I will fix
that and in the mean time do this:

npm install -g websocket connect finalhandler serve-static
/Basil n7nix

Aug 1 07:17:06 N7KJKPI systemd[1]: Stopped node.js server for paclink-unix.
Aug 1 07:17:06 N7KJKPI systemd[1]: Started node.js server for paclink-unix.
Aug 1 07:17:09 N7KJKPI pluweb[8753]: module.js:549
Aug 1 07:17:09 N7KJKPI pluweb[8753]: throw err;
Aug 1 07:17:09 N7KJKPI pluweb[8753]: ^
Aug 1 07:17:09 N7KJKPI pluweb[8753]: Error: Cannot find module '/usr/lib/node_modules/websocket'


Re: Point to Point (P2P) email transfer #draws

Basil Gunn
 

Kevin K. - N7KJK <kkutzera@gmail.com> writes:

Also is this section with the pluweb failed state normal?
Yes this a problem with the paclink-unix web app install. I will fix
that and in the mean time do this:

npm install -g websocket connect finalhandler serve-static
/Basil n7nix

Aug 1 07:17:06 N7KJKPI systemd[1]: Stopped node.js server for paclink-unix.
Aug 1 07:17:06 N7KJKPI systemd[1]: Started node.js server for paclink-unix.
Aug 1 07:17:09 N7KJKPI pluweb[8753]: module.js:549
Aug 1 07:17:09 N7KJKPI pluweb[8753]: throw err;
Aug 1 07:17:09 N7KJKPI pluweb[8753]: ^
Aug 1 07:17:09 N7KJKPI pluweb[8753]: Error: Cannot find module '/usr/lib/node_modules/websocket'


Re: Point to Point (P2P) email transfer #draws

Kevin K. - N7KJK
 

Also is this section with the pluweb failed state normal?

 1 07:17:06 N7KJKPI systemd[1]: pluweb.service: Service hold-off time over, scheduling restart.
Aug  1 07:17:06 N7KJKPI systemd[1]: Stopped node.js server for paclink-unix.
Aug  1 07:17:06 N7KJKPI systemd[1]: Started node.js server for paclink-unix.
Aug  1 07:17:09 N7KJKPI pluweb[8753]: module.js:549
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     throw err;
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     ^
Aug  1 07:17:09 N7KJKPI pluweb[8753]: Error: Cannot find module '/usr/lib/node_modules/websocket'
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at Function.Module._resolveFilename (module.js:547:15)
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at Function.Module._load (module.js:474:25)
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at Module.require (module.js:596:17)
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at require (internal/module.js:11:18)
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at Object.<anonymous> (/usr/local/src/paclink-unix/webapp/plu-server.js:48:23)
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at Module._compile (module.js:652:30)
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at Object.Module._extensions..js (module.js:663:10)
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at Module.load (module.js:565:32)
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at tryModuleLoad (module.js:505:12)
Aug  1 07:17:09 N7KJKPI pluweb[8753]:     at Function.Module._load (module.js:497:3)
Aug  1 07:17:09 N7KJKPI systemd[1]: pluweb.service: Main process exited, code=exited, status=1/FAILURE
Aug  1 07:17:09 N7KJKPI systemd[1]: pluweb.service: Unit entered failed state.
Aug  1 07:17:09 N7KJKPI systemd[1]: pluweb.service: Failed with result 'exit-code'.
Aug  1 07:17:19 N7KJKPI systemd[1]: pluweb.service: Service hold-off time over, scheduling restart.
Aug  1 07:17:19 N7KJKPI systemd[1]: Stopped node.js server for paclink-unix.
Aug  1 07:17:19 N7KJKPI systemd[1]: Started node.js server for paclink-unix.
Aug  1 07:17:21 N7KJKPI pluweb[8802]: module.js:549
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     throw err;
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     ^
Aug  1 07:17:21 N7KJKPI pluweb[8802]: Error: Cannot find module '/usr/lib/node_modules/websocket'
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at Function.Module._resolveFilename (module.js:547:15)
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at Function.Module._load (module.js:474:25)
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at Module.require (module.js:596:17)
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at require (internal/module.js:11:18)
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at Object.<anonymous> (/usr/local/src/paclink-unix/webapp/plu-server.js:48:23)
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at Module._compile (module.js:652:30)
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at Object.Module._extensions..js (module.js:663:10)
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at Module.load (module.js:565:32)
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at tryModuleLoad (module.js:505:12)
Aug  1 07:17:21 N7KJKPI pluweb[8802]:     at Function.Module._load (module.js:497:3)
Aug  1 07:17:21 N7KJKPI systemd[1]: pluweb.service: Main process exited, code=exited, status=1/FAILURE
Aug  1 07:17:21 N7KJKPI systemd[1]: pluweb.service: Unit entered failed state.
Aug  1 07:17:21 N7KJKPI systemd[1]: pluweb.service: Failed with result 'exit-code'.
Aug  1 07:17:29 N7KJKPI dovecot: auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth
Aug  1 07:17:29 N7KJKPI dovecot: auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat
Aug  1 07:17:29 N7KJKPI dovecot: auth: Debug: auth client connected (pid=8844)




On Fri, Aug 2, 2019 at 5:26 AM Kevin K. - N7KJK via Groups.Io <kkutzera=gmail.com@groups.io> wrote:
Ok,
Understood.  Not sure why I didn't catch that in the man page.
Thanks

On Thu, Aug 1, 2019 at 9:00 PM Basil Gunn <basil@...> wrote:

Kevin,

You need to change 'gunn' which is my user name to your user name
probably pi. ie.

#
[N7KJK VIA udr1]
  NOCALL * * * * * * L
  default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

Also make sure there are NO blank lines in your ax25d.conf file.
Look in /var/log/syslog for any wl2kax25d entries.

/Basil

Kevin K. - N7KJK <kkutzera@...> writes:

> Thanks Basil,
> So I've read the MAN pages for both wl2kax25d and ax25d. Somewhat illuminating..
>
> A friend of mine tried to connect using both N7KJK, and N7KJK-10 (my Winlink Gateway address).
> He tried these both as Packet P2P, and Packet WinLink. He only had one connection using the callsign with SSID. It didn't accept of send email and he had to force the disconnect.
>
> I think I am beginning to understand how to control this. So Here's my new configuration of ax25d.conf.
> My radio is connected to the DIN port farthest away from the GPS sma antenna port. I see traffic (beacons) all day long (mostly with invalid or Unknown APRS Type Indicator.. (no big deal).
>
> My assumption is that if a station is trying to call me with my SSID they are treating my PI as an RMS-Gateway. I send their traffic through to the gateway software.
> If the station is trying to call me without the SSID they are attempting Packet P2P and local email will be forwarded as indicated in the man page.
>
> [N7KJK-10 VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
> #
> [N7KJK VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - gunn /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
>
> The version I was running during the test had N7KJK-10 listening on udr0. I don't have a second radio listening on that port but the hand off to rmsgw was given the wrong port so my station didn't reply properly.
>
> So my friend will test again tomorrow. I'll update this thread success of failure so we have info to share with others.
>
> Next on my punch list is to get this to beacon periodically like other stations do...
> 73
> Kevin / N7KJK



--
Kevin J. Kutzera CISSP, CISM, CEH
Cell: 206-850-7762



--
Kevin J. Kutzera CISSP, CISM, CEH
Cell: 206-850-7762


Re: Point to Point (P2P) email transfer #draws

Kevin K. - N7KJK
 

Ok,
Understood.  Not sure why I didn't catch that in the man page.
Thanks

On Thu, Aug 1, 2019 at 9:00 PM Basil Gunn <basil@...> wrote:

Kevin,

You need to change 'gunn' which is my user name to your user name
probably pi. ie.

#
[N7KJK VIA udr1]
  NOCALL * * * * * * L
  default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

Also make sure there are NO blank lines in your ax25d.conf file.
Look in /var/log/syslog for any wl2kax25d entries.

/Basil

Kevin K. - N7KJK <kkutzera@...> writes:

> Thanks Basil,
> So I've read the MAN pages for both wl2kax25d and ax25d. Somewhat illuminating..
>
> A friend of mine tried to connect using both N7KJK, and N7KJK-10 (my Winlink Gateway address).
> He tried these both as Packet P2P, and Packet WinLink. He only had one connection using the callsign with SSID. It didn't accept of send email and he had to force the disconnect.
>
> I think I am beginning to understand how to control this. So Here's my new configuration of ax25d.conf.
> My radio is connected to the DIN port farthest away from the GPS sma antenna port. I see traffic (beacons) all day long (mostly with invalid or Unknown APRS Type Indicator.. (no big deal).
>
> My assumption is that if a station is trying to call me with my SSID they are treating my PI as an RMS-Gateway. I send their traffic through to the gateway software.
> If the station is trying to call me without the SSID they are attempting Packet P2P and local email will be forwarded as indicated in the man page.
>
> [N7KJK-10 VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
> #
> [N7KJK VIA udr1]
> NOCALL * * * * * * L
> default * * * * * * - gunn /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
>
> The version I was running during the test had N7KJK-10 listening on udr0. I don't have a second radio listening on that port but the hand off to rmsgw was given the wrong port so my station didn't reply properly.
>
> So my friend will test again tomorrow. I'll update this thread success of failure so we have info to share with others.
>
> Next on my punch list is to get this to beacon periodically like other stations do...
> 73
> Kevin / N7KJK



--
Kevin J. Kutzera CISSP, CISM, CEH
Cell: 206-850-7762


Re: Point to Point (P2P) email transfer #draws

Basil Gunn
 

Kevin,

You need to change 'gunn' which is my user name to your user name
probably pi. ie.

#
[N7KJK VIA udr1]
NOCALL * * * * * * L
default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

Also make sure there are NO blank lines in your ax25d.conf file.
Look in /var/log/syslog for any wl2kax25d entries.

/Basil

Kevin K. - N7KJK <kkutzera@gmail.com> writes:

Thanks Basil,
So I've read the MAN pages for both wl2kax25d and ax25d. Somewhat illuminating..

A friend of mine tried to connect using both N7KJK, and N7KJK-10 (my Winlink Gateway address).
He tried these both as Packet P2P, and Packet WinLink. He only had one connection using the callsign with SSID. It didn't accept of send email and he had to force the disconnect.

I think I am beginning to understand how to control this. So Here's my new configuration of ax25d.conf.
My radio is connected to the DIN port farthest away from the GPS sma antenna port. I see traffic (beacons) all day long (mostly with invalid or Unknown APRS Type Indicator.. (no big deal).

My assumption is that if a station is trying to call me with my SSID they are treating my PI as an RMS-Gateway. I send their traffic through to the gateway software.
If the station is trying to call me without the SSID they are attempting Packet P2P and local email will be forwarded as indicated in the man page.

[N7KJK-10 VIA udr1]
NOCALL * * * * * * L
default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[N7KJK VIA udr1]
NOCALL * * * * * * L
default * * * * * * - gunn /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

The version I was running during the test had N7KJK-10 listening on udr0. I don't have a second radio listening on that port but the hand off to rmsgw was given the wrong port so my station didn't reply properly.

So my friend will test again tomorrow. I'll update this thread success of failure so we have info to share with others.

Next on my punch list is to get this to beacon periodically like other stations do...
73
Kevin / N7KJK


Re: Point to Point (P2P) email transfer #draws

Kevin K. - N7KJK
 

Thanks Basil, 
So I've read the MAN pages for both wl2kax25d and ax25d.  Somewhat illuminating..

A friend of mine tried to connect using both N7KJK,  and N7KJK-10 (my Winlink Gateway address).
He tried these both as Packet P2P, and Packet WinLink.  He only had one connection using the callsign with SSID.  It didn't accept of send email and he had to force the disconnect.

I think I am beginning to understand how to control this.  So Here's my new configuration of ax25d.conf.
My radio is connected to the DIN port farthest away from the GPS sma antenna port.  I see traffic (beacons) all day long (mostly with invalid or Unknown APRS Type Indicator.. (no big deal).

My assumption is that if a station is trying to call me with my SSID they are treating my PI as an RMS-Gateway.  I send their traffic through to the gateway software.
If the station is trying to call me without the SSID they are attempting Packet P2P and local email will be forwarded as indicated in the man page.

[N7KJK-10 VIA udr1]
NOCALL   * * * * * *  L
default  * * * * * *  - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[N7KJK VIA udr1]
NOCALL   * * * * * *  L
default  * * * * * *  - gunn /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

The version I was running during the test had N7KJK-10 listening on udr0.  I don't have a second radio listening on that port but the hand off to rmsgw was given the wrong port so my station didn't reply properly.

So my friend will test again tomorrow.   I'll update this thread success of failure so we have info to share with others.

Next on my punch list is to get this to beacon periodically like other stations do...
 73 
Kevin / N7KJK


Headphone/Microphone break-out?

Stuart Longland VK4MSL
 

Hi all,

Silly thought just occurred to me… one sore point with the Raspberry Pi
is that the device provides no audio I/O apart from the PWM audio output.

Now, the UDRC/DRAWS is a big improvement on that, with a decent audio
CODEC chip capable of 192kHz audio. There's 3 line-in channels, a
MICBIAS output, a line-out and a headphone output, all available on the
audio CODEC chip. The mixer is able to do all kinds of routing voodoo.

With such a set-up, whilst of course you won't drive a headset and two
radios off the two ADC and two DAC channels, you could conceivably drive
one radio and one headset with the right routing settings, or use the
headphone output as a monitor.

In applications where you just want something to connect a headset to
your radio for SSB/FM voice, that can be facilitated through the mixer
alone (no latency as it's purely analogue): e.g. if the microphone
hooked to IN3[L+R], you could route IN3L→LOL and IN1L→HPL; or IN3R→LOR
and IN1R→HPR.

You'd then just need a switch to connect your headset either to HPL or
HPR (or both if you want to use the UDRC/DRAWS as a sound card for
music, etc).

Anyway, it was a thought that occurred to me. Maybe in a future design,
a small pin header could expose those pins for those who choose to use them.

Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.


Re: No audio in/out with my FT-817, Pi4, and DRAWS

 


On Wed, Jul 31, 2019, 21:22 John D Hays - K7VE via Groups.Io <john=hays.org@groups.io> wrote:
Try DRAWS ™ Manager 


It should set levels properly. 




Re: No audio in/out with my FT-817, Pi4, and DRAWS

 

Try DRAWS ™ Manager 


It should set levels properly. 


On Wed, Jul 31, 2019, 20:42 Chris Metcalf <chris@...> wrote:
I've been trying to get my Raspberry Pi 4 working with my DRAWS hat but I think either my connection is messed up or my audio setup / levels wrong. 
 
 
Maybe I'm doing something wrong and I've been staring at it too long to notice? Can somebody please look over my setup below and let me know if spot something amiss? I had things working with my Pi3, so I suspect I’m missing something that’s in the stock Compass image but missing in a hand-configured Buster setup.
 
## Symptoms
 
- S7 noise floor, and I can hear signals but nothing in the WSJT-X waterfall
- Panadapter shows plenty of signals I'm not getting in the WSJT-X waterfall
- Nothing on ALC meter when I tune with WSJT-X
- No signal displayed in the waterfall when I switch to VHF and send a test transmission from my HT
- Nothing received on my HT when I transmit a tuning signal on VHF
 
## Hardware
 
- Yaesu FT-817
- LDG Z-817 antenna tuner
- 4GB Raspberry Pi 4
- DRAWS hat
- PAT-V panadapter installed
 
## Settings 
 
- 03 9600 Mic: 50
- 24 Dig Disp: 0Hz
- 25 Dig Mic: 61
- 26 Dig Mode: User-U
- 27 Dig Shift: 0Hz
- 38 Op Filter: Off
- 39 Pkt Mic: 50
- 40 Pkt Rate: 1200
- AGC: Fast
- Noise Blanker: Off
 
## Connections
 
- Pin 6 removed from the Data cable
- Data cable in Left (facing the connectors) jack
- USB Serial CAT cable
- Offset fed dipole on a 6:1 balun connected via an antenna tuner
 
## WSJT-X Setup
 
- CAT control set up and working
- Input: plughw:CARD=udrc,DEV=0 in Mono mode (
- Output: plughw:CARD=udrc,DEV=0 in Mono mode
 
I've tried Left, Right, and other udrc input devices to no success)
 
## ALSA Setup
 
I ran the setup-ft817.sh script to set my levels:
 
===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-20.00dB]    R:[-20.00dB]
DAC Playback PT L:[P3]  R:[P3]
LO Playback CM  [Full Chip]
 
 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[-2.00dB]     R:[-2.00dB]
IN1             L:[Off]         R:[Off]
IN2             L:[10 kOhm]     R:[10 kOhm]
CM              L:[10 kOhm]     R:[10 kOhm]
 
Thanks,
Chris Metcalf
K1NOT


No audio in/out with my FT-817, Pi4, and DRAWS

Chris Metcalf
 

I've been trying to get my Raspberry Pi 4 working with my DRAWS hat but I think either my connection is messed up or my audio setup / levels wrong. 
 
I've followed the Google Doc on how to set up your Pi4 (https://docs.google.com/document/u/2/d/1Wq-jNLXYuREIOcr0OVu1FxPNhDFGuCOu6dX5OQ2BVxA/mobilebasic) and the setup guide for the FT-817 (https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-App-Notes-for-Radios)
 
Maybe I'm doing something wrong and I've been staring at it too long to notice? Can somebody please look over my setup below and let me know if spot something amiss? I had things working with my Pi3, so I suspect I’m missing something that’s in the stock Compass image but missing in a hand-configured Buster setup.
 
## Symptoms
 
- S7 noise floor, and I can hear signals but nothing in the WSJT-X waterfall
- Panadapter shows plenty of signals I'm not getting in the WSJT-X waterfall
- Nothing on ALC meter when I tune with WSJT-X
- No signal displayed in the waterfall when I switch to VHF and send a test transmission from my HT
- Nothing received on my HT when I transmit a tuning signal on VHF
 
## Hardware
 
- Yaesu FT-817
- LDG Z-817 antenna tuner
- 4GB Raspberry Pi 4
- DRAWS hat
- PAT-V panadapter installed
 
## Settings 
 
- 03 9600 Mic: 50
- 24 Dig Disp: 0Hz
- 25 Dig Mic: 61
- 26 Dig Mode: User-U
- 27 Dig Shift: 0Hz
- 38 Op Filter: Off
- 39 Pkt Mic: 50
- 40 Pkt Rate: 1200
- AGC: Fast
- Noise Blanker: Off
 
## Connections
 
- Pin 6 removed from the Data cable
- Data cable in Left (facing the connectors) jack
- USB Serial CAT cable
- Offset fed dipole on a 6:1 balun connected via an antenna tuner
 
## WSJT-X Setup
 
- CAT control set up and working
- Input: plughw:CARD=udrc,DEV=0 in Mono mode (
- Output: plughw:CARD=udrc,DEV=0 in Mono mode
 
I've tried Left, Right, and other udrc input devices to no success)
 
## ALSA Setup
 
I ran the setup-ft817.sh script to set my levels:
 
===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-20.00dB]    R:[-20.00dB]
DAC Playback PT L:[P3]  R:[P3]
LO Playback CM  [Full Chip]
 
 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[-2.00dB]     R:[-2.00dB]
IN1             L:[Off]         R:[Off]
IN2             L:[10 kOhm]     R:[10 kOhm]
CM              L:[10 kOhm]     R:[10 kOhm]
 
Thanks,
Chris Metcalf
K1NOT


Re: Fans, Pi4, and the DRAWS case

Chris Metcalf
 

FWIW, the “Pi-Fan” brand fan that came with my case is _extremely_ quiet and can barely be heard even from a foot or two away.

A big passive heat sink could possibly help, but the “hat” standard makes that difficult since the hat sits right on top of the Pi and doesn’t leave much room for a heat sink. Perhaps a later generation case could include a riser or some sort of heat pipe system to dissipate heat outside the case.

Key learning though is that it looks like the Pi4 is impractical without some sort of cooling for the CPU. I’ve still got my 3B+ and may reconsider it if the power and cooling requirements are too high, but right now I’m _loving_ the extra memory and CPU. 

-- 
Chris Metcalf

On July 31, 2019 at 2:47:43 PM, Jeff NE1U (jwalden@...) wrote:

I like the idea of not having to have a fan ... maybe. lol

Orienting heat sink fins vertical and given that warm air flows up, makes the best use of passive cooling. Can you tell that I am an engineer? Apologies. Probably good that there be a little air space around below and above the heatsink. 

On the other hand, the specs for fans include the dB noise level and a very quiet low speed fan can greatly improve heat exchange in any orientation. Just read the specs and investigate.


Re: Fans, Pi4, and the DRAWS case

Jeff AE8W
 

I like the idea of not having to have a fan ... maybe. lol

Orienting heat sink fins vertical and given that warm air flows up, makes the best use of passive cooling. Can you tell that I am an engineer? Apologies. Probably good that there be a little air space around below and above the heatsink. 

On the other hand, the specs for fans include the dB noise level and a very quiet low speed fan can greatly improve heat exchange in any orientation. Just read the specs and investigate.


Re: Fans, Pi4, and the DRAWS case

JT Croteau <jt.tobit@...>
 

I am hoping the Pi 4 draws less than 20W.  I run completely on solar power and looking for a desktop replacement with DRAWS.  Fan noise can be mitigated.   I have a 2n1 laptop/tablet that draws about 25W but I'd much rather have the DRAWS and some other apps in one device.


On Wed, Jul 31, 2019, 16:23 Steve Stroh <steve.stroh@...> wrote:
It's a personal perspective, but I don't want a fan on an appliance
like a DRAWS. Fans are noisy. They suck dust in and spray it all over
the board. They're non-static hardware that will inevitably fail.

I hope to build up my DRAWS units as (silent) appliances, and tack
them up and out of the way on a shelf, or wall, or ??? and access them
remotely.

The extra power (and the 2 GB or 4 GB of RAM) of the RPi4 is nice, and
I plan to have at least a couple, probably as standalone workstations,
but on the DRAWS, I haven't seen / heard / read anything that
indicates that the additional power of the RPi4 would be of any
benefit to a DRAWS unit above and beyond what the RPi3 does. Thus, the
RPi3 which doesn't need a fan, is preferable to the RPi4, which does
seem to need a fan, for use on DRAWS.

Thanks,

Steve

On Wed, Jul 31, 2019 at 7:06 AM Bryan Hoyer <bhhoyer@...> wrote:
>
> Chris,

<snip>

> And yes fans are under consideration

--
Steve Stroh (personal / general): stevestroh@...



1581 - 1600 of 5337