Date   

Re: YAAC Port Settings #yaac #xastir

Andrew P.
 

Tim:

Speaking from experience, I wouldn't run YAAC on a Pi for bicycle operations, unless you're using an alternate disk drive device for the YAAC tiledir (where the imported OpenStreetMap data is stored). SD cards are far too slow for map re-rendering if you need to pan the map around to look for where a bicyclist is broken down. I've measured it, and it's not the Pi CPU that is the limiting factor, but reading the SD card. And not all of the streets in OpenStreetMap actually have names on them (although most do); sometimes you may not be able to find a named cross-street where the bicyclist broke down with YAAC's Locate->Landmark option, especially if you don't spell it matching how the map data submitter spelled it.

For a bike event, I typically run YAAC on a laptop with a decently fast disk, hooked up to a large 4HD flatscreen TV, so I can see the whole course. The Pi is fine to run DireWolf and provide other functionality, but it's terrible for map rendering.

Andrew, KA2DDO
author of YAAC and
APRS manager, Chester County ARES/RACES team for the French Creek Iron Tour (a 100-mile bike course https://irontour.org/ )

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Tim Huffaker <thuffaker@mindspring.com>
Sent: Friday, August 6, 2021 4:12 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] YAAC Port Settings #yaac #xastir

Basil,

Thank you for sharing the ports. Maybe this with a drawing should be published I think it would help. If you are interested this is for a bike event base station to see the SAG vehicles as they pick up stranded bike riders.

Thank you again for your excellent help.
Tim
KM4ESU


Re: YAAC Port Settings #yaac #xastir

Tim Huffaker
 

Basil,

Thank you for sharing the ports.  Maybe this with a drawing should be published I think it would help.  If you are interested this is for a bike event base station to see the SAG vehicles as they pick up stranded bike riders.  

Thank you again for your excellent help. 
Tim
KM4ESU


Re: YAAC Port Settings #yaac #xastir

Basil Gunn
 

Thanks for posting your console output. Everything looks good.

I am using he AGWPE port as Andrew mentioned yesterday. That is how I
always connect direwolf to YAAC. When you select the AGWPE port it
has a drop down that says Port 1 first Soundcard left and Port 2 first
Soundcard Right. I would like to know how to decide which one without
guessing since both are available.
With regards to YAAC:
Port 1 is left mDin6 connector
Port 2 is right mDin6 connector

With regards to Direwolf
Port 0 is left mDin6 connector
Port 1 is right mDin6 connector

The default install using my scripts has the left connector active. I
believe that Direwolf supports a single AGWPE port and that will using
the left connector for the default configuration.

I believe (not sure as I haven't tried it) there is a way to use two
AGWPE ports with Direwolf in the latest DEV version of the software.

See Direwolf User-Guide.pdf Section 9.4.1 AGWPE network protocol


Re: YAAC Port Settings #yaac #xastir

Tim Huffaker
 

On Fri, Aug 6, 2021 at 08:32 AM, Basil Gunn wrote:

Hi Basil,

I am using he AGWPE port as Andrew mentioned yesterday.  That is how I always connect  direwolf to YAAC.  When you select the AGWPE port it has a drop down that says Port 1 first Soundcard left and   Port 2 first Soundcard Right.  I would like to know how to decide which one without guessing since both are available.  


pi@KM4ESU:~ $ ax25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: RUNNING and ENABLED
Status for ax25d.service: RUNNING and ENABLED
AX.25 device: ax0 successfully configured with ip: 192.168.255.2
AX.25 device: ax1 successfully configured with ip: 192.168.255.3
Direwolf is running with pid of 3618
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
Device: ax0 exists, Device: ax1 exists
pi@KM4ESU:~ $ buginfo.sh
=== Versions ===
== Kernel:
Linux KM4ESU 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux
 
== Firmware:
Nov 30 2020 22:12:08 
Copyright (c) 2012 Broadcom
version ab1181cc0cb6df52bfae3b1d3fef0ce7c325166c (clean) (release) (start)
 
== Pi hardware:
 Pi 4 Model B, Rev 1.1, 4GB mem, Mfg by Sony UK with WiFi
temp=66.2'C
 
== DRAWS hardware:
Product id: 0x0004, ver: 0x0108, Assembly rev: 1, fab rev: 8
 
=== Checks ===
== Codec driver check:
[    3.646897] asoc-simple-card soc:sound: tlv320aic32x4-hifi <-> fe203000.i2s mapping ok
 
== DRAWS driver check:
udrc card number line: card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #2
 
== Boot 'fail' check:
[    0.485908] bcmgenet fd580000.ethernet: failed to get enet clock
[    0.485926] bcmgenet fd580000.ethernet: failed to get enet-wol clock
[    0.485935] bcmgenet fd580000.ethernet: failed to get enet-eee clock
[    3.307034] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
 
== GPS check:
Serial devices OK
gpsd OK
 
== /boot/config file
[pi4]
dtoverlay=vc4-fkms-v3d
[all]
dtoverlay=
dtoverlay=draws,alsaname=udrc
force_turbo=1
dtparam=audio=on
 
pi@KM4ESU:~ $ systemctl status direwolf.service
● direwolf.service - Direwolf Daemon
   Loaded: loaded (/etc/systemd/system/direwolf.service; enabled; vendor preset:
   Active: active (running) since Fri 2021-08-06 08:35:26 CDT; 2h 45min ago
 Main PID: 3618 (direwolf)
    Tasks: 15 (limit: 4915)
   CGroup: /system.slice/direwolf.service
           └─3618 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p
 
Aug 06 11:19:12 KM4ESU direwolf[3618]: Weather Report, WEATHER Station (blue), O
Aug 06 11:19:12 KM4ESU direwolf[3618]: N 34 39.2800, W 086 40.4400
Aug 06 11:19:12 KM4ESU direwolf[3618]: , temperature 68, rain 0.00 in last 24 ho
Aug 06 11:19:12 KM4ESU direwolf[3618]: DW0076 audio level = 185(55/30)   [NONE] 
Aug 06 11:19:12 KM4ESU direwolf[3618]: Audio input level is too high.  Reduce so
Aug 06 11:19:12 KM4ESU direwolf[3618]: [1.5] DW0076>APOT21,AL2-2:!3439.28N/08640
Aug 06 11:19:12 KM4ESU direwolf[3618]: Weather Report, WEATHER Station (blue), O
Aug 06 11:19:12 KM4ESU direwolf[3618]: N 34 39.2800, W 086 40.4400
Aug 06 11:19:12 KM4ESU direwolf[3618]: , temperature 68, rain 0.00 in last 24 ho
Aug 06 11:21:12 KM4ESU systemd[1]: /etc/systemd/system/direwolf.service:10: Defa
lines 1-18/18 (END)
 
 


Re: YAAC Port Settings #yaac #xastir

Basil Gunn
 

1. From your previous post I still would like to confirm that
your AX.25/Direwolf/DRAWS is working properly.

Please post the console output of:

ax25-status
buginfo.sh
systemctl status direwolf.service

2. 'Port' is an overloaded term. I believe you want to connect YAAC to the
Direwolf AGWPE port, as Andrew KA2DDO mentioned yesterday in a post
(https://nw-digital-radio.groups.io/g/udrc/message/5806)

Please read the following links and let me know if
they help.

https://www.ka2ddo.org/ka2ddo/YAACdocs/config_agwpe.html

I did not see the port in your file you show above. I don not see a
way to determine the port of the Draws to connect. How can you tell
the active port connect to a radio to make sure you can get YAAC
connected. I have port 1 on sound card left on my setup.


Re: YAAC Port Settings #yaac #xastir

Andrew P.
 

YAAC does not connect directly to a port on the DRAWS hat. Instead, it connects to the Direwolf process, and DireWolf connects to the appropriate port (or ports) on the DRAWS hat as configured in the direwolf.conf file. When you open a port of type AGWPE in YAAC, it will connect to DireWolf using the AGWPE protocol, which allows YAAC to query DireWolf for what ports it has available to use; this is for cases when DireWolf is configured with multiple ADEVICE entries in its configuration file, although it works just as well for a single ADEVICE (you will only get one choice appearing in the YAAC AGWPE configuration panel).

Andrew, KA2DDO
author of YAAC

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Tim Huffaker <thuffaker@mindspring.com>
Sent: Friday, August 6, 2021 10:10 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] YAAC Port Settings #yaac #xastir

I did not see the port in your file you show above. I don not see a way to determine the port of the Draws to connect. How can you tell the active port connect to a radio to make sure you can get YAAC connected. I have port 1 on sound card left on my setup.

[X]


Re: YAAC Port Settings #yaac #xastir

Tim Huffaker
 

I did not see the port in your file you show above. I don not see a way to determine the port of the Draws to connect.  How can you tell the active port connect to a radio to make sure you can get YAAC connected. I have port 1 on sound card left on my setup.  


Re: broken Img #1pps #release

Tim Huffaker
 

Basil,

If you are telling me nwdr19.img.xz is a good image then I think I have a Balena Etcher issue on a M1 Mac.  I will use another computer to burn the image and see if that works. 

Also can you tell what version of an image you have while running the raspberry pi.  It would be useful to know and if you need to upgrade or burn anothe


Re: broken Img #1pps #release

Basil Gunn
 

today I wanted to flash a new image and I tried current_image.zx and
nwdr19.x and both will not boot on my raspberry pi 4.
You most likely have a problem flashing the image to the SD Card. Which
utility did you use?

Did you verify that you do not have a download problem?
Confirm with either the md5 or sha256 hashes from the checksum.txt file.

They also have the same Boot loader of C3o5221A Sept 3 2020 and confer
04ad5ae6.
I do not know what that means. How do you get those numbers?

Also I get error 4.
With respect to what? I need more context.


What is a current good image to download?
nwdr19.img.xz


broken Img #1pps #release

Tim Huffaker
 

today I wanted to flash a new image and I tried current_image.zx and nwdr19.x and both will not boot on my raspberry pi 4.  They also have the same Boot loader of C3o5221A Sept 3 2020 and confer 04ad5ae6.  Also I get error 4.  

What is a current good image to download?


Re: ax25ipd- is something broken, or is the WIKI not up to date?

Basil Gunn
 

Run the following 3 scripts and post the console output.

ax25-restart
ax25-status

cd
cd n7nix/bin

./buginfo.sh


Tim Huffaker <thuffaker@mindspring.com> writes:

I saw this and I am having a similar issue AX25 looks like its not connected but YAAC is showing data. I do not see the ax25 devices ax0 and ax1 not configured. Did I miss a step setting up my image. How is YAAC seeing data?

Tim
KM4ESU

~ $ ax25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: NOT RUNNING and ENABLED
Status for ax25d.service: NOT RUNNING and NOT ENABLED
AX.25 device: ax0 not configured
AX.25 device: ax1 not configured
Direwolf is running with pid of 24698
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: , t2 timeout:
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: , t2 timeout:
Device: ax0 does NOT exist, Device: ax1 does NOT exist


Re: ax25ipd- is something broken, or is the WIKI not up to date?

Andrew P.
 

YAAC doesn't connect to the kernel AX.25 stack via AX25 sockets; it connects via a TCP/IP local socket directly to the Direwolf process (typically, TCP port 8000).

Andrew, KA2DDO
author of YAAC

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Tim Huffaker <thuffaker@mindspring.com>
Sent: Thursday, August 5, 2021 11:51 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] ax25ipd- is something broken, or is the WIKI not up to date?

I saw this and I am having a similar issue AX25 looks like its not connected but YAAC is showing data. I do not see the ax25 devices ax0 and ax1 not configured. Did I miss a step setting up my image. How is YAAC seeing data?

Tim
KM4ESU

~ $ ax25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: NOT RUNNING and ENABLED
Status for ax25d.service: NOT RUNNING and NOT ENABLED
AX.25 device: ax0 not configured
AX.25 device: ax1 not configured
Direwolf is running with pid of 24698
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: , t2 timeout:
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: , t2 timeout:
Device: ax0 does NOT exist, Device: ax1 does NOT exist


Re: ax25ipd- is something broken, or is the WIKI not up to date?

Tim Huffaker
 

I saw this and I am having a similar issue AX25 looks like its not connected but YAAC is showing data. I do not see the ax25 devices ax0 and ax1 not configured.  Did I miss a step setting up my image.  How is YAAC seeing data?

Tim 
KM4ESU

~ $ ax25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: NOT RUNNING and ENABLED
Status for ax25d.service: NOT RUNNING and NOT ENABLED
AX.25 device: ax0 not configured
AX.25 device: ax1 not configured
Direwolf is running with pid of 24698
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: , t2 timeout: 
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: , t2 timeout: 
Device: ax0 does NOT exist, Device: ax1 does NOT exist
 


Re: GPS setup inconsistent #ft-817 #gpsd

John S Gruber
 

Thanks Basil. I just tested it and it works great here, too.

On Sun, Aug 1, 2021 at 12:31 PM Basil Gunn <basil@pacabunga.com> wrote:


John,

Yesterday morning unattended upgrades updated the pi to version
1:1.20210727-1. From both the debian changelog and the name of the
directory it appears to contain linux 5.10.52.

kernver.sh:
Released kernel version: 5.10.17
Running kernel version: 5.10.11
Thanks for that information.

I turned off my kernel hold and did an apt-get update/apt-get upgrade
and successfully installed kernel 5.10.52 which DOES HAVE Anna's kernel
patches. That kernel works fine with the DRAWS hat.

The kernel in the released version of Raspberry Pi OS image is still down rev (5.10.17)
and will NOT work. The kernel in http://archive.raspberrypi.org/debian/ buster main
repo is now 5.10.52 and will work just fine with DRAWS. Any kernel
version newer than 5.10.31 should be fine.

My previous point was that it is OK to use apt-get upgrade or apt upgrade
but I would stay away from rpi-update which I only use to down grade a
kernel version.

Thanks for pointing out the new kernel in the raspberry pi debian repo.
I will spin up a new NWDR image with this kernel in the next few weeks.

To test your tlv320aic driver after updating to a new kernel run:

aplay -l

and verify that udrc "bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0" is
enumerated in the displayed list.

/Basil





Re: GPS setup inconsistent #ft-817 #gpsd

John S Gruber
 

Excellent! That's great news.

Thanks so much and good work, Anna.

I'll try to test it on our club pi this week.

Thanks, Basil.

John N8MSU

On Sun, Aug 1, 2021 at 12:31 PM Basil Gunn <basil@pacabunga.com> wrote:


John,

Yesterday morning unattended upgrades updated the pi to version
1:1.20210727-1. From both the debian changelog and the name of the
directory it appears to contain linux 5.10.52.

kernver.sh:
Released kernel version: 5.10.17
Running kernel version: 5.10.11
Thanks for that information.

I turned off my kernel hold and did an apt-get update/apt-get upgrade
and successfully installed kernel 5.10.52 which DOES HAVE Anna's kernel
patches. That kernel works fine with the DRAWS hat.

The kernel in the released version of Raspberry Pi OS image is still down rev (5.10.17)
and will NOT work. The kernel in http://archive.raspberrypi.org/debian/ buster main
repo is now 5.10.52 and will work just fine with DRAWS. Any kernel
version newer than 5.10.31 should be fine.

My previous point was that it is OK to use apt-get upgrade or apt upgrade
but I would stay away from rpi-update which I only use to down grade a
kernel version.

Thanks for pointing out the new kernel in the raspberry pi debian repo.
I will spin up a new NWDR image with this kernel in the next few weeks.

To test your tlv320aic driver after updating to a new kernel run:

aplay -l

and verify that udrc "bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0" is
enumerated in the displayed list.

/Basil





Re: GPS setup inconsistent #ft-817 #gpsd

Basil Gunn
 

John,

Yesterday morning unattended upgrades updated the pi to version
1:1.20210727-1. From both the debian changelog and the name of the
directory it appears to contain linux 5.10.52.

kernver.sh:
Released kernel version: 5.10.17
Running kernel version: 5.10.11
Thanks for that information.

I turned off my kernel hold and did an apt-get update/apt-get upgrade
and successfully installed kernel 5.10.52 which DOES HAVE Anna's kernel
patches. That kernel works fine with the DRAWS hat.

The kernel in the released version of Raspberry Pi OS image is still down rev (5.10.17)
and will NOT work. The kernel in http://archive.raspberrypi.org/debian/ buster main
repo is now 5.10.52 and will work just fine with DRAWS. Any kernel
version newer than 5.10.31 should be fine.

My previous point was that it is OK to use apt-get upgrade or apt upgrade
but I would stay away from rpi-update which I only use to down grade a
kernel version.

Thanks for pointing out the new kernel in the raspberry pi debian repo.
I will spin up a new NWDR image with this kernel in the next few weeks.

To test your tlv320aic driver after updating to a new kernel run:

aplay -l

and verify that udrc "bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0" is
enumerated in the displayed list.

/Basil


Re: GPS setup inconsistent #ft-817 #gpsd

Basil Gunn
 

My system doesn't have the kernel pinned since it was already running
a broken kernel version.
Read the following link. It will tell you how to down rev your kernel
AND place a hold on updating the kernel. The current kernel that
Raspberry Pi OS has in their repo (5.10.17) will NOT work with a DRAWS
hat.

https://github.com/nwdigitalradio/n7nix/blob/master/docs/DRAWS_CONFIG.md#placing-a-hold-on-kernel-upgrade


Because of the breakage and the fact that's it doing what we need it
to do we have just kept it running without reboot for 173 days. It's
high, has Internet, and is hard for me to access.

Yesterday morning unattended upgrades updated the pi
Huh? You are using automated upgrades? If you do that you really need to
put a hold on upgrading your kernel. Also NEVER use rpi-update unless
you know what you are doing as that will install a bleeding edge kernel.

to version 1:1.20210727-1. From both the debian changelog and the name
of the directory it appears to contain linux 5.10.52.

kernver.sh:
Released kernel version: 5.10.17
Running kernel version: 5.10.11

The release notes used by kernver.sh don't include the 5/27 or 7/27
raspberrypi-kernel packages. (sadly 5/27 was 5.10.17).
Correct, the release notes used are what is in the raspberrypi.org download
directory ie. what the Raspberry Pi Foundation actually supports.

Has the 7/27/21 kernel release been tested to be sure Anna's fixes are
on and that everything is working properly?
I do NOT test every bleeding edge kernel that is installed with
rpi-update. The last one I tested was 5.10.31 a few months ago and that
kernel had Anna's fixes and everything worked fine. I will test the
latest Raspberry Pi OS released kernel BUT that is 5.10.17 and that is
known NOT to work properly.

The following link is a directory of bleeding edge kernels, NOT released
kernels. I assume that is where you got the 7/27/2021 kernel from.

http://archive.raspberrypi.org/debian/pool/main/r/raspberrypi-firmware/



/etc/apt/sources.list.d/raspi.list:
deb http://archive.raspberrypi.org/debian/ buster main

Package location:
http://archive.raspberrypi.org/debian/pool/main/r/raspberrypi-firmware/raspberrypi-kernel_1.20210727-1_arm64.deb

On Sat, Jul 31, 2021 at 11:59 AM Basil Gunn <basil@pacabunga.com> wrote:


I try to make my own image. I added the following to my
/boot/config.txt
1. I do not support making your own image. A LOT of time went into
making an image that works with the NWDR hats and there is NO compelling
reason for you to make your own image other than it might be fun. By all
means ask questions on the forum because others might be willing to
support you.

2. gpsd configuration is in file: /etc/default/gspd NOT /boot/config.txt

# Configure gpsd
START_DAEMON="true"
DEVICES="/dev/ttySC0 /dev/pps0"
GPSD_OPTIONS="-n"
3. Look at the kernel version on the image you started with.

The last RELEASED Linux kernel that worked with the audio codec that
NWDR DRAWS uses (TI tlv320aic 32x4) is 5.4.83. Kernel version 5.4.79
also works well with that codec. The currently released Raspberry Pi
Foundation kernel, 5.10.17, WILL NOT WORK with this codec. Hence the
hold on kernel updates on the currently released NWDR image.

Anna fixed the kernel problem in Feb 2021 and those patches were
accepted to the main line kernel in March 2021. The currently released
kernel by the Raspberry Pi Foundation, 5.10.17, does NOT have the
following fixes:

* [[https://www.spinics.net/lists/stable/msg455357.html | [PATCH v2 2/2] ASoC: tlv320aic32x4: Register clocks before registering component]]
* [[https://www.spinics.net/lists/stable/msg455356.html | [PATCH v2 1/2] ASoC: tlv320aic32x4: Increase maximum register in regmap]]
* [[https://www.spinics.net/lists/stable/msg455066.html | [PATCH v2] sc16is7xx: Defer probe if device read fails]]

To Summarize:
Kernel versions that work:
5.4.79, 5.4.83, 5.10.31 and above

Kernel versions that DO NOT work:
Any kernel after 5.4.83 and before 5.10.31

Note that Kernel 5.10.31 is not a kernel released by Raspberry Pi
Foundation. If the n7nix repository is installed you can run the
kernver.sh script which will display the currently released Raspberry
Pi foundation kernel and the kernel version you are currently running.

$ kernver.sh
Released kernel version: 5.10.17
Running kernel version: 5.4.79

Also run the following command to display your current kernel version:

uname -a
or
uname -r


Then I rebooted and I got my GPS working. Then I moved my setup to different room and since then the GPS is not working.
pi@w4mhi-shack:~ $ systemctl status gpsd.service
Jul 30 20:12:24 w4mhi-shack gpsd[1576]: gpsd:ERROR: SER: device open of /dev/ttySC0 failed: No such file or directory - retrying
Jul 30 20:12:24 w4mhi-shack gpsd[1576]: gpsd:ERROR: SER: read-only device open of /dev/ttySC0 failed: No such file or directory
Jul 30 20:12:24 w4mhi-shack gpsd[1576]: gpsd:ERROR: initial GPS device /dev/ttySC0 open failed





Re: GPS setup inconsistent #ft-817 #gpsd

Mihai M.
 

I totally agrre with you. I am developer and I want to use your HAT in a particular configuration. 
After Basil's reply, everything works like a charm, thank you again! 
I apologize for creating trouble on the forum. 
You guys rock, so much appreciation. 

73,
Mihai (W4MHI) 


-------- Original message --------
From: Annaliese McDermond <nh6z@...>
Date: 7/31/21 13:58 (GMT-08:00)
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] GPS setup inconsistent #ft-817 #gpsd

Let me be very clear about this for others that may read this.  We do not recommend the following for anyone at all, and Basil, myself or anyone else associated with NWDR won't be here to help you if you wander off the trail.  This information is given for educational purposes to someone that's already decided to forgo any formal support from us, and what they do with the information is their own thing.  This is likely my last post on the subject, and probably Basil's as well.

The necessary patches were pushed both upstream and to the Pi Foundation's repository in hopes they'd get into the distro sooner.  They didn't upgrade the kernel in the May release, so it didn't make it in there.  One could use rpi-update to upgrade to the latest testing kernel, which should have the patches.  Again, DANGER WILL ROBINSON, THERE BE DRAGONS HERE.  Note all of the RPi Foundation's warnings on the linked page as well.

You have been warned.


Re: GPS setup inconsistent #ft-817 #gpsd

Annaliese McDermond
 

Let me be very clear about this for others that may read this.  We do not recommend the following for anyone at all, and Basil, myself or anyone else associated with NWDR won't be here to help you if you wander off the trail.  This information is given for educational purposes to someone that's already decided to forgo any formal support from us, and what they do with the information is their own thing.  This is likely my last post on the subject, and probably Basil's as well.

The necessary patches were pushed both upstream and to the Pi Foundation's repository in hopes they'd get into the distro sooner.  They didn't upgrade the kernel in the May release, so it didn't make it in there.  One could use rpi-update to upgrade to the latest testing kernel, which should have the patches.  Again, DANGER WILL ROBINSON, THERE BE DRAGONS HERE.  Note all of the RPi Foundation's warnings on the linked page as well.

You have been warned.


Re: GPS setup inconsistent #ft-817 #gpsd

Mihai M.
 

Thank you Basil!
Couple of thoughts:
- the boot/config.txt doesn't have the snippet, true - copy&paste fault. I followed the documentation to include the drivers but I didn't copy that snippet
- in the gpsd I have the snippet
- will do a full kernel update to get the 5.10.31 (current is 5.10.17)

I understand you do not support custom images, but how would we learn to use something if we do not try to hack that thing? RaspberryPi is intended to be a platform where anyone can do fun things.
I have a big thanks to Anna for the fixes!

Much appreciate your help!
73,
Mihai (W4MHI)

201 - 220 of 5987