Date   

Re: Nixtracker

Basil Gunn
 

I have 13 satellites.
Excellent! /Basil


Re: Problems with Winlink handshaking on VHF and no power to transmitter on HF

Dave Christensen
 

I did read and apply the settings for the IC-7000.
******************************

 

I have an Icom IC-7000 radio that I am feeding by the DIN-6 data connector in the back.  I can get the VHF stuff working with default ALSA settings or even the setalsa-ic7000settings for the IC-7000 and it works great.  Clean audio and no retries.

 

For FLDigi I have to change the ALSA settings from Analog = -3, Digital gain = -16 to 20 to Analog=-2.00 db and Digital = -8.00 db just to get clean audio.  Lower gain settings produces noise - no clean tone with FLDigi Tune turned on.  The signal is so hot that I can not get the ALC below full scale on the meter.   I lower the gain and the noise comes back  One interesting thing is that the sound card available for FLDigi selection is “udrc: bcm2835-i2s-tlv320aic32x4-hifi tlv320aicx4-hifi-0 (hw 1,0)”   

 

With WSJTX and JS8Call the soundcard is listed as plughw: CARD=udrc, DEV=0  The power setting slider in the apps do nothing.  These apps are opposite from FLDigi in that I can’t get enough drive to the radio using the same ALSA settings to generate any transmit power or even increasing the transmit gain.

So summary:  VHF/Direwolf work OK with default alsa settings.  FLDigi requires a hotter signal to get clean audio (as listened to by another HF rig.  JS8Call and WSJTX have such low drive into the transmitter that you can barely hear the transmitted signal.  I would love to find someone with an IC-7000 and get their settings to try.

Thanks for your continued interest.
Dave


Re: Nixtracker

 

I have 13 satellites.


Re: Nixtracker

 

Bingo! 

sudo npm -g install uid-number

Just telnetted an email to myself through the tracker.

Thank you again. I am doing so much with this board that I could not otherwise do without you, Anna, Bryan and John.

david, Ke7rgp 


Re: Nixtracker

 

Wonderful Basil. I’ll try this. screen -x Ctrl a 1 in the verify step walked me through all the missing dependencies except that last one, so this will be a new thing to try. Very excited and I’ll let you know either way.

david


Re: Nixtracker

Basil Gunn
 

David,

I'm still testing but this is what I had to do get things working.

The tracker_install.sh script disables pluweb.service and starts
tracker.service so that is why your previous web connection stopped
working. That is by design.

You should be able to connect to the tracker server in a
browser with: <ip_address>:8081 where ip_address can be localhost if you
are running on the RPi.

To make this work:
# I believe only uid-number module is not installed but checking the
# other required modules doesn't hurt.

sudo npm -g install ctype iniparser websocket connect serve-static finalhandler uid-number

As root edit /etc/tracker/aprs_tracker.ini
In the [station] section mycall = <your_call_sign>
In the [gps] section comment out with a '#' type=serial
In the [gps] section UNcomment (remove '#') type=gpsd

I've made these changes to the install script so you won't have to do
this manually next time & added a tracker-status script to verify a
couple of things.

To get the new scripts:
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

Also when you get the web page to render if the satellite count is zero
then you may have to pull the latest track source to get a small fix I
put in a while back & forgot to check-in. Check the 3rd panel for
'Locked: 0 sats'. I'll walk you through that later if that turns out to
be the case.

/Basil

Basil Gunn <@basil860> writes:

David Lowry <huskyrunnr@...> writes:

Ahh! I see now how the lvd renders the Ctrl tab obsolete. I didn’t
make the connection yesterday. I’ve been shadowing that development
since it appeared in the NWDR change log. My son bought me the its-12
for Christmas.
The its-12 is nice gift!

The history of my mobile APRS device is like this. I was going to an
APRS event & installed nixtracker on the UDR cpu card (not an Rpi) about
7 or 8 years ago and powered it from the cigarette lighter in the
truck. This was supposed to be a temporary setup that I eventually ran
for about 8 years. Note that the cpu card didn't have any power
protection & was powered off/on with the ignition key. That setup worked
flawlessly for about 8 years ie. same mSD card for that time was never
corrupted.

I did not want to run the same experiment with the RPi and now have the
its-12 powered from the truck battery set for 2 minutes. This allows me
to easily detect a voltage change using a DRAWS hat & beacon one last
time when I leave my truck then do a polite shutdown. I've been running
this setup for about 3 months.

Thanks for all your help. As always, no rush. I really wanted to try
plu and nixtracker with a fresh image a third time but that won’t
happen until tomorrow. Claws mail and the wl2k commands work.
I will do some testing over the next couple of days.
/Basil


Re: DRAWS hat + PiJuice

Michael WA7SKG <wa7skg@...>
 

Not the PiJuice specifically, but I am using the MoPi 2 (https://pi.gate.ac.uk/pages/mopi.html). This does not include a built-in battery like the PiJuice, but has two inputs that accept 6.5-24VDC, a charger input and a management system. It gives you a push button to start/stop the RPi, monitors voltage and will initiate automatic shutdown for low voltage, on-board LEDs as well as on-screen notifications. Each input can configure for different battery chemistries. It also has a relay connection if you need to switch higher current sources.

In my configuration, I am not using a DRAWS hat, but a TNC-X. I think the DRAWS configuration would be similar. The whole package is mounted on the back of a SmartiPi Touch case. It seems to work quite well. I am mounting it in my vehicle connected to the vehicle 12V supply.

Michael WA7SKG



Chris Metcalf wrote on 1/27/20 1:09 PM:

Has anybody successfully incorporated a RPi UPS board like the PiJuice (https://uk.pi-supply.com/products/pijuice-standard) to prevent corruption based on power loss, especially while operating mobile? I've got automatic backups to a USB thumb drive set up with RSnapshot now, but it'd be nice to have the PiJuice there to automatically shut down gracefully the RPi when power is disconnected.
It looks like it interfaces using spring pins on the 40 pin connector, and everything is pass-through except power and I2C: https://github.com/PiSupply/PiJuice
Does that conflict with anything that the DRAWS hat needs? My only other concern would be being able to power/charge the PiJuice from the 12v connection on the DRAWS.
Thanks,
Chris


Re: DRAWS hat + PiJuice

Basil Gunn
 

For mobile apps using 12V battery.
I don't use PiJuice, instead I use Powerwerx its-12.
https://powerwerx.com/automotive-dc-timer-lvd-battery-guard

It's a low voltage detect & a timer.
Using 'sensors' command I can read the 12V supply from the DRAWS hat &
detect when it goes from altenator/generator to battery only and do an
APRS beacon & graceful RPi shut down. Been using it for about 3 months.
/Basil n7nix

Chris Metcalf <chris@...> writes:

Has anybody successfully incorporated a RPi UPS board like the PiJuice (
https://uk.pi-supply.com/products/pijuice-standard) to prevent corruption
based on power loss, especially while operating mobile? I've got automatic
backups to a USB thumb drive set up with RSnapshot now, but it'd be nice to
have the PiJuice there to automatically shut down gracefully the RPi when
power is disconnected.

It looks like it interfaces using spring pins on the 40 pin connector, and
everything is pass-through except power and I2C:
https://github.com/PiSupply/PiJuice

Does that conflict with anything that the DRAWS hat needs? My only other
concern would be being able to power/charge the PiJuice from the 12v
connection on the DRAWS.

Thanks,
Chris


DRAWS hat + PiJuice

Chris Metcalf
 

Has anybody successfully incorporated a RPi UPS board like the PiJuice (https://uk.pi-supply.com/products/pijuice-standard) to prevent corruption based on power loss, especially while operating mobile? I've got automatic backups to a USB thumb drive set up with RSnapshot now, but it'd be nice to have the PiJuice there to automatically shut down gracefully the RPi when power is disconnected.

It looks like it interfaces using spring pins on the 40 pin connector, and everything is pass-through except power and I2C: https://github.com/PiSupply/PiJuice

Does that conflict with anything that the DRAWS hat needs? My only other concern would be being able to power/charge the PiJuice from the 12v connection on the DRAWS.

Thanks,
Chris


Re: Nixtracker

Basil Gunn
 

David Lowry <huskyrunnr@...> writes:

Ahh! I see now how the lvd renders the Ctrl tab obsolete. I didn’t
make the connection yesterday. I’ve been shadowing that development
since it appeared in the NWDR change log. My son bought me the its-12
for Christmas.
The its-12 is nice gift!

The history of my mobile APRS device is like this. I was going to an
APRS event & installed nixtracker on the UDR cpu card (not an Rpi) about
7 or 8 years ago and powered it from the cigarette lighter in the
truck. This was supposed to be a temporary setup that I eventually ran
for about 8 years. Note that the cpu card didn't have any power
protection & was powered off/on with the ignition key. That setup worked
flawlessly for about 8 years ie. same mSD card for that time was never
corrupted.

I did not want to run the same experiment with the RPi and now have the
its-12 powered from the truck battery set for 2 minutes. This allows me
to easily detect a voltage change using a DRAWS hat & beacon one last
time when I leave my truck then do a polite shutdown. I've been running
this setup for about 3 months.

Thanks for all your help. As always, no rush. I really wanted to try
plu and nixtracker with a fresh image a third time but that won’t
happen until tomorrow. Claws mail and the wl2k commands work.
I will do some testing over the next couple of days.
/Basil


Re: Nixtracker

 

Correction: I first saw the reference to lvd in the individual commit around November 11, not the nwdr14 announcement or change log.


Re: Nixtracker

 

Ahh! I see now how the lvd renders the Ctrl tab obsolete. I didn’t make the connection yesterday. I’ve been shadowing that development since it appeared in the NWDR change log. My son bought me the its-12 for Christmas.

Thanks for all your help. As always, no rush. I really wanted to try plu and nixtracker with a fresh image a third time but that won’t happen until tomorrow. Claws mail and the wl2k commands work.


Re: #direwolf #direwolf

Paul Noa
 

Will do guys,

Thanks for the input I will start fresh with the NWDR15.  That is the advantage of having issues it gives you more experience.

Best regards,

Paul KO4BCZ

On Mon, 27 Jan 2020 at 02:43, Basil Gunn <basil@...> wrote:

J P is correct there is no AI in these scripts to go back & undo. The
configuration scripts were meant to be run exactly once. Some scripts
are more forgiving than others because I had to run them a bunch of
times to get them to work properly. If you know you need to fix
something then just manually edit that config file.

For your call sign KO4BCV Look for the following line in file:
/etc/direwolf.conf

IGLOGIN KO4BCV 11409

You can look at the status of the tier 2 servers here:
http://status.aprs2.net/

Having said that I do not do any aprs client stuff in direwolf. I only
use it as a sound modem.
What I use for APRS is this:
aprx for digipeating
yaac & Xastir when I want maps
nixtracker in my vehicle for smart beaconing

I also use mobilinkd with a handy talky & droid phone for hiking.
You have some choices depending on what you want to do.


J P Watters via Groups.Io <kc9kko=mac.com@groups.io> writes:

> Paul,
>
> This is still a beta work in progress. Basil has done and outstanding job at making this work.
>
> There really isn't an UNDO script for running the getting started scripts after entering bad or erroneous information.
> Entering a Bogus call sign and an associated invalid password would not be good.
>
> It would appear that running the scripts the first time with a BOGUS call sign has some pretty real effects.
> Like never being able to connect to APRSIS with a Bogus Call Sign and an invalid password that was not generated by the CALLPASS algorithm.
> When I saw that the script reported that it was not the first time it had been run, that pointed out that a fresh image would be
> likely the best plan.
>
> Start with a fresh NW15 image and most importantly ' Follow the 'Getting Started Guide'
> https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started
>
> Members of our radio club and myself have had regular success following the getting started guide.
> When we have changed our minds in the initial configuration we have found it best to start with a fresh image.
>
> ..jpw J P Watters
> KC9KKO
>
>




Re: NWDR15 Image observations

Bernard f6bvp / ai7bg
 

Hi Basil,
Your fix works great !
Now ax25-start is ok.

Thanks for repairing the bug so fast.

73’s de Bernard

 


Re: #direwolf #direwolf

Basil Gunn
 

J P is correct there is no AI in these scripts to go back & undo. The
configuration scripts were meant to be run exactly once. Some scripts
are more forgiving than others because I had to run them a bunch of
times to get them to work properly. If you know you need to fix
something then just manually edit that config file.

For your call sign KO4BCV Look for the following line in file:
/etc/direwolf.conf

IGLOGIN KO4BCV 11409

You can look at the status of the tier 2 servers here:
http://status.aprs2.net/

Having said that I do not do any aprs client stuff in direwolf. I only
use it as a sound modem.
What I use for APRS is this:
aprx for digipeating
yaac & Xastir when I want maps
nixtracker in my vehicle for smart beaconing

I also use mobilinkd with a handy talky & droid phone for hiking.
You have some choices depending on what you want to do.


J P Watters via Groups.Io <kc9kko=mac.com@groups.io> writes:

Paul,

This is still a beta work in progress. Basil has done and outstanding job at making this work.

There really isn't an UNDO script for running the getting started scripts after entering bad or erroneous information.
Entering a Bogus call sign and an associated invalid password would not be good.

It would appear that running the scripts the first time with a BOGUS call sign has some pretty real effects.
Like never being able to connect to APRSIS with a Bogus Call Sign and an invalid password that was not generated by the CALLPASS algorithm.
When I saw that the script reported that it was not the first time it had been run, that pointed out that a fresh image would be
likely the best plan.

Start with a fresh NW15 image and most importantly ' Follow the 'Getting Started Guide'
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

Members of our radio club and myself have had regular success following the getting started guide.
When we have changed our minds in the initial configuration we have found it best to start with a fresh image.

..jpw J P Watters
KC9KKO


Re: Nixtracker

Basil Gunn
 

David,

Give me a day or 2 on this one ( mail tab gives an error “Unable to
communicate with the PLU Websocket server).

I think that the web server enabled with the standard paclink-unix
install might be interfering with the nixtracker web server.

David Lowry <huskyrunnr@...> writes:

Basil, I will really enjoy this interface in the truck. A quick
question, on the CTRL tab, what do I type in the Confirm box?
So I have been using nixtracker since before the Raspberry Pi when NWDR
made their own CPU cards. At that time it was handy to be able to
'shutdown' & 'reset' the CPU card from the Web interface. I believe the
confirm for each was 'down' and 'reset'. See
nixtracker/webapp/tracker-frontend.js.

Using the DRAWS card on an RPi I can detect when I shut my truck off by
reading the voltage ie. running off 12 V you can just run the 'sensors'
command. See n7nix/tracker/updown_log.sh script. When the voltage is
less than 13V I know my truck is off and the RPi is running on
battery. I have the power for the RPi coming off the Powerwerx ITS-12
https://powerwerx.com/automotive-dc-timer-lvd-battery-guard

so I can do a polite shut down within a couple of minutes after I shut
my truck off.

That was a long winded explanation for why I don't use the CTRL tab any
more.

A more complex question... if it is not a simple answer and you don’t
want to answer, I understand.

In my hands, the mail tab gives an error “Unable to communicate with
the PLU Websocket server.” I realize this feature may not be supported
at this time or I have set up plu and nixtracker in the wrong order
for this to work. At this point I have no localhost:8082. Earlier, I
had both 8081 and 8082, but still the same error on the mail tab.
Let me check on this.


Re: #direwolf #direwolf

J P Watters <kc9kko@...>
 

Paul,

This is still a beta work in progress. Basil has done and outstanding job at making this work. 

There really isn't an UNDO script for running the getting started scripts after entering bad or erroneous information.
Entering a Bogus call sign and an associated invalid password would not be good. 

It would appear that running the scripts the first time with a BOGUS call sign has some pretty real effects. 
Like never being able to connect to APRSIS with a Bogus Call Sign and an invalid password that was not generated by the CALLPASS algorithm. 
When I saw that the script reported that it was not the first time it had been run, that pointed out that a fresh image would be 
likely the best plan.

Start with a fresh NW15 image and most importantly  'Follow the 'Getting Started Guide'
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

Members of our radio club and myself have had regular success following the getting started guide.
When we have changed our minds in the initial configuration we have found it best to start with a fresh image. 

..jpw J P Watters
KC9KKO



Re: #direwolf #direwolf

Paul Noa
 

Thanks Jim will check it out!

Paul KO4BCZ


Re: #direwolf #direwolf

Jim Erickson
 

Paul, you’ll find the Direwolf config file at /etc/direwolf.conf   In there you’ll find the auto generated passcode for aprs. 

73 Jim

On Jan 26, 2020, at 18:29, Paul Noa <pauljnoa@...> wrote:


Basil,

I forgot to include the console output for the showudrc.sh.

here it is.

On Sun, 26 Jan 2020 at 20:44, Paul Noa <pauljnoa@...> wrote:
Basil,

I went back to my NWDR14 build to see if i could remember what the issue was, attached is an output file: NWDR14 Rebuild.txt

But perhaps this is all you will need to know:

#Configure core functionality

pi@asawizard:~/n7nix $ cd config
pi@asawizard:~/n7nix/config $ sudo su
root@asawizard:/home/pi/n7nix/config# ./app_config.sh core
app_config.sh: script start
Enter call sign, followed by [enter]: KO4BCV
app_config.sh: Config core
  Already run 1 time(s):  core config script
current dir: /home/pi/n7nix/config
Test pwd: /home/pi/n7nix/config, path: /home/pi/n7nix

Verify IF dtoverlay= is set properly
  dtoverlay currently set to: dtoverlay=draws,alsaname=udrc
  dtoverlay for DRAWS OK

Verify IF dtparam=audio is set properly
  Last line in /boot/config.txt OK

Verify IF dtoverlay= is set properly
  dtoverlay currently set to: dtoverlay=draws,alsaname=udrc
  dtoverlay for DRAWS OK

Verify IF dtparam=audio is set properly
  Last line in /boot/config.txt OK
app_config.sh core has already been run, exiting
-- cfg_script_name  hostname: 0, passwd: 0, logfile: 0
root@asawizard:/home/pi/n7nix/config#

So despite git pull and updating and running  ./app_config.sh core again, and entering my new License instead of the made up one,
i.e KO4BCZ instead of the made up one NOAPJ

I still get this:
pi@asawizard:~ $ 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
pi@asawizard:~ $ tail -f /var/log/direwolf/direwolf.log
Jan 26 20:10:51 asawizard direwolf[455]: KISS protocol set TXtail = 10 (*10mS units = 100 mS), port 1
Jan 26 20:10:51 asawizard direwolf[455]: KISS protocol set Persistence = 32, port 1
Jan 26 20:10:51 asawizard direwolf[455]: KISS protocol set SlotTime = 20 (*10mS units = 200 mS), port 1
Jan 26 20:10:51 asawizard direwolf[455]: KISS protocol set FullDuplex = 0, port 1
Jan 26 20:10:56 asawizard direwolf[455]: Can't get address for IGate server noam.aprs2.net, Temporary failure in name resolution
Jan 26 20:11:01 asawizard direwolf[455]: Can't get address for IGate server noam.aprs2.net, Temporary failure in name resolution
Jan 26 20:11:06 asawizard direwolf[455]: Now connected to IGate server noam.aprs2.net (167.114.2.176)
Jan 26 20:11:06 asawizard direwolf[455]: Check server status here http://167.114.2.176:14501
Jan 26 20:11:11 asawizard direwolf[455]: [ig] # aprsc 2.1.5-g8af3cdc
Jan 26 20:11:11 asawizard direwolf[455]: [ig] # logresp N0APJ verified, server T2CAWEST

So as you see having alread run the core config once it did not prompt me for my passcode and did not change the original entry.
I am unable to find the direwolf.conf file to edit it for the correct info. perhaps that will suffice.  The APRS.SI site is receiving

Is feasible to try to correct NOAPJ with KO4BCZ or should I just bite the bullet and start fresh with the NWDR15 image.

A complete output txt file is attached anticipating other questions.  

Paul KO4BCZ

On Sun, 26 Jan 2020 at 18:34, Basil Gunn <basil@...> wrote:

> I have three RPi 3's, one with my own build and one with the NWDR14
> build, one spare. I have been more successful with my build but not so
> much with yours,

And exactly (with console output) what problem are you having with the
image? Also, when you get a chance, switch to the NWDR15 image.

> with all due respect Basil I find it tedious to jump
> back and forth from one URL to another trying to follow three
> different paths for

> installing,

If you use the NWDR image there is nothing to install.
If you do your own custom install you are on your own.

>configuring

Follow the 'Getting Started Guide'
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

> and testing,

https://github.com/nwdigitalradio/n7nix/blob/master/docs/DEBUG_BASICS.md
https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md

> So I hope find my argument compelling enough to continue to support
> the three units which I purchased.

Like I said before if you use the image you will get my support. If you
make your own custom install, post your questions on the forum and maybe
someone will answer.
/Basil



<showudrc_output.txt>


Re: #direwolf #direwolf

Paul Noa
 

Basil,

I forgot to include the console output for the showudrc.sh.

here it is.

On Sun, 26 Jan 2020 at 20:44, Paul Noa <pauljnoa@...> wrote:
Basil,

I went back to my NWDR14 build to see if i could remember what the issue was, attached is an output file: NWDR14 Rebuild.txt

But perhaps this is all you will need to know:

#Configure core functionality

pi@asawizard:~/n7nix $ cd config
pi@asawizard:~/n7nix/config $ sudo su
root@asawizard:/home/pi/n7nix/config# ./app_config.sh core
app_config.sh: script start
Enter call sign, followed by [enter]: KO4BCV
app_config.sh: Config core
  Already run 1 time(s):  core config script
current dir: /home/pi/n7nix/config
Test pwd: /home/pi/n7nix/config, path: /home/pi/n7nix

Verify IF dtoverlay= is set properly
  dtoverlay currently set to: dtoverlay=draws,alsaname=udrc
  dtoverlay for DRAWS OK

Verify IF dtparam=audio is set properly
  Last line in /boot/config.txt OK

Verify IF dtoverlay= is set properly
  dtoverlay currently set to: dtoverlay=draws,alsaname=udrc
  dtoverlay for DRAWS OK

Verify IF dtparam=audio is set properly
  Last line in /boot/config.txt OK
app_config.sh core has already been run, exiting
-- cfg_script_name  hostname: 0, passwd: 0, logfile: 0
root@asawizard:/home/pi/n7nix/config#

So despite git pull and updating and running  ./app_config.sh core again, and entering my new License instead of the made up one,
i.e KO4BCZ instead of the made up one NOAPJ

I still get this:
pi@asawizard:~ $ 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
pi@asawizard:~ $ tail -f /var/log/direwolf/direwolf.log
Jan 26 20:10:51 asawizard direwolf[455]: KISS protocol set TXtail = 10 (*10mS units = 100 mS), port 1
Jan 26 20:10:51 asawizard direwolf[455]: KISS protocol set Persistence = 32, port 1
Jan 26 20:10:51 asawizard direwolf[455]: KISS protocol set SlotTime = 20 (*10mS units = 200 mS), port 1
Jan 26 20:10:51 asawizard direwolf[455]: KISS protocol set FullDuplex = 0, port 1
Jan 26 20:10:56 asawizard direwolf[455]: Can't get address for IGate server noam.aprs2.net, Temporary failure in name resolution
Jan 26 20:11:01 asawizard direwolf[455]: Can't get address for IGate server noam.aprs2.net, Temporary failure in name resolution
Jan 26 20:11:06 asawizard direwolf[455]: Now connected to IGate server noam.aprs2.net (167.114.2.176)
Jan 26 20:11:06 asawizard direwolf[455]: Check server status here http://167.114.2.176:14501
Jan 26 20:11:11 asawizard direwolf[455]: [ig] # aprsc 2.1.5-g8af3cdc
Jan 26 20:11:11 asawizard direwolf[455]: [ig] # logresp N0APJ verified, server T2CAWEST

So as you see having alread run the core config once it did not prompt me for my passcode and did not change the original entry.
I am unable to find the direwolf.conf file to edit it for the correct info. perhaps that will suffice.  The APRS.SI site is receiving

Is feasible to try to correct NOAPJ with KO4BCZ or should I just bite the bullet and start fresh with the NWDR15 image.

A complete output txt file is attached anticipating other questions.  

Paul KO4BCZ

On Sun, 26 Jan 2020 at 18:34, Basil Gunn <basil@...> wrote:

> I have three RPi 3's, one with my own build and one with the NWDR14
> build, one spare. I have been more successful with my build but not so
> much with yours,

And exactly (with console output) what problem are you having with the
image? Also, when you get a chance, switch to the NWDR15 image.

> with all due respect Basil I find it tedious to jump
> back and forth from one URL to another trying to follow three
> different paths for

> installing,

If you use the NWDR image there is nothing to install.
If you do your own custom install you are on your own.

>configuring

Follow the 'Getting Started Guide'
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

> and testing,

https://github.com/nwdigitalradio/n7nix/blob/master/docs/DEBUG_BASICS.md
https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md

> So I hope find my argument compelling enough to continue to support
> the three units which I purchased.

Like I said before if you use the image you will get my support. If you
make your own custom install, post your questions on the forum and maybe
someone will answer.
/Basil