Date   
Re: Lego Case for DRAWS #case

stprovost@...
 

Hello, love all the content, but HATE the multi megabyte pictures!!!!!!!!!!!!
can you STOP using large format pictures!!
i keep getting full mailbox errors and can't receive any more emails.
thank you for your consideration.
stephen

-------- Original Message --------
Subject: Re: [udrc] Lego Case for DRAWS #case
From: "J P Watters via Groups.Io" <kc9kko@...>
Date: Wed, April 10, 2019 1:28 am
To: udrc@nw-digital-radio.groups.io

For those who inquired, the bottom of the Lego PI Case remains as it was manufactured.
The top was drilled out for the SMA connector for GPS. Where the pair of 6-Pin connectors contact the top of the case, the top case was cut wide enough for both connectors to protrude through the top case. (IMG_4319) The second photo shows the internal side of the top cutout. In the background of the photo is a unaltered top case. 

Re: Basic Direwolf question #draws #direwolf #ax25

Dave N2OA
 

Ok thanks for the help and I’ll give the new one a try too.



On Tue, Apr 9, 2019 at 5:59 PM Basil Gunn <basil@...> wrote:

> Sorry about the delay. I finally got a chance to try it last night and it
> seems to be working as expected. Not that it's likely to be an issue for me
> but is that script limited to North latitude and West longitude? It looks
> hard coded.

(Another) New version of beacmin.sh parses nema sentences instead of
gpsd sentences.  Parsing nema sentences is less work to put into APRS
format & adds parameterized lat/lon direction.
https://github.com/nwdigitalradio/n7nix/commit/772431d2201a5e6f5a3af2771559d13a7efa817c

You are right this fix is not an issue for your location.

/Basil n7nix

> Thank you!
>
> On Sat, Apr 6, 2019 at 6:53 PM Basil Gunn <basil@...> wrote:
>
>>
>> Dave N20A,
>>
>> I checked-in a fix to the problem that you reported with beacmin.sh.
>> Fix GPS to APRS position format: Degrees Minutes.m
>>
>> https://github.com/nwdigitalradio/n7nix/commit/5821f4ff36b3ca976439c9325f484664476e839a
>>
>> To get the new script:
>> I you modified the beacmin.sh script in n7nix/debug then you need to
>> remove it.
>>
>> cd
>> cd n7nix/debug
>> rm beacmin.sh
>>
>> # To get new script
>> git pull
>>
>> When you first run beacmin.sh in may take some time to install the bc
>> program, an
>> arbitrary precision command line calculator. It will run much more
>> quickly the next times.
>>
>> When you get a chance please run beacmin.sh and let me know if it meets
>> your
>> expectations. You should edit the script to set the SSID to what ever
>> you want. You should also set the beacon_msg string to use a different icon
>>
>> Thanks,
>> /Basil
>>
>> Dave N2OA <kdcarlso@...> writes:
>>
>> > Thank you. I did a search on SSID so I missed the SID and thought it
>> pulled
>> > it with the call.
>> >
>> > Here is the results of beacmin.sh with debug turned on.
>> >
>> > pi@n2oa-draws-1:~/n7nix/debug $ ./beacmin.sh
>> > Read 1 lines of gps data
>> > gpsdata: 43.01159
>> > -78.189806667
>> > lat: 43.01159
>> > lon: -78.189806667
>> > ./beacmin.sh: line 52: 01159: value too great for base (error token is
>> > "01159")
>> > axports: found line: udr0 N2OA-1 9600 255 2 Direwolf port
>> > udr1 N2OA-10 9600 255 2 Winlink port
>> > Found callsign: N2OA
>> > Set callsign N2OA
>> >  Sent: /usr/local/sbin/beacon -c N2OA-1 -d 'APUDR1 via WIDE1-1' -l -s
>> udr0
>> > !43.01159N/78.189806667Wp06 15:46:43 EDT, Seq: 21
>> >
>> >
>> > Dave
>> > N2OA
>> >
>> > On Fri, Apr 5, 2019 at 5:36 PM Basil Gunn <basil@...> wrote:
>> >
>> >>
>> >> Dave,
>> >> Thanks for trying out my script.
>> >> I will fix the errors you are seeing but I need some more info.
>> >> Could you please do the following:
>> >>
>> >> # Go to the directory where beacmin.sh lives.
>> >>
>> >> cd
>> >> cd n7nix/debug
>> >>
>> >> # Using your favorite text editor change the following two lines near
>> >> #  the top of the file.
>> >>
>> >> # 1. Get rid the hash symbol in front of DEBUG=1
>> >> #DEBUG=1
>> >>
>> >> # 2. Change the SID number to what ever you want to use.
>> >> SID=15
>> >>
>> >> Now run the the beacmin.sh script and copy & paste the console output to
>> >> me in
>> >> an email.
>> >>
>> >> Thanks, Dave.
>> >> /Basil
>> >>
>> >>
>> >> Dave N2OA <kdcarlso@...> writes:
>> >>
>> >> > On Fri, Apr 5, 2019 at 12:09 PM, Basil Gunn wrote:
>> >> >
>> >> > Thanks for the answers and Basil for the scrips. I tried thebeacmin.sh
>> >> script and it does beacon but I am not getting a location on my TH-D74
>> or
>> >> FTM-400. I also notice that the SSID is always is always 15 even though
>> my
>> >> SSID in axports is set to -1.
>> >> >
>> >> > The message sent is Sent: /usr/local/sbin/beacon -d N2OA-15 -d 'APUDR1
>> >> via WIDE1-1' -l -s udr0 !43.01165833N/78.1899Wp05 16:19:08 EDT, Seq: 15
>> >> >
>> >> > I do get an error in line 52: 01165833: value too great for base
>> (error
>> >> token is "011658333")
>> >> >
>> >> > I also noticed int your example you show beacon -c and mine is showing
>> >> -d and the decimal is 2 digits in for lat and long which I would expect
>> but
>> >> your example show 4 digits and then a decimal. Am I missing something?
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Dave
>> >> > N2OA



Re: PiGate

Gary KC3PO
 

Thanks for the pointers, I'll take a look.

It doesn't HAVE to be "PiGate" (at least in my opinion)... but similar functionality would be nice - and of course there are numerous ways to get same/similar functionality.

- Gary  KC3PO

Re: PiGate

Gary KC3PO
 

Julie,

All valid points - I'm not saying it HAS to be PiGate... but a DRAWS adaptation with the same or similar functionality would be nice, and a great use of DRAWS.

I'm hoping someone with more spare time than I have is interested in doing something along those lines. I'd be happy to help where I could, but honestly have too much on my plate at the moment.

- Gary  KC3PO

Re: Lego Case for DRAWS #case

J P Watters
 

For those who inquired, the bottom of the Lego PI Case remains as it was manufactured.
The top was drilled out for the SMA connector for GPS. Where the pair of 6-Pin connectors contact the top of the case, the top case was cut wide enough for both connectors to protrude through the top case. (IMG_4319) The second photo shows the internal side of the top cutout. In the background of the photo is a unaltered top case. 

Re: PiGate

Basil Gunn
 

You can look at a list of programs that are installed on the DRAWS image
here:
https://github.com/nwdigitalradio/n7nix/blob/master/docs/IMAGE_README.md

SquirrelMail is not there. I chose rainloop for the web based email
client. https://www.rainloop.net/

When you run ./app_config.sh plu

paclink-unix postfix, dovecot, lighttpd, mutt, claws-mail & rainloop all get
installed. That gives you a choice of 3 email clients & a web based
interface to paclink-unix. If you want an RMS Gateway that can be
installed via scripts as well.

You need an Internet connection when you do this install and it helps if
you already have your Winlink password. Use this link to get a Winlink
account: https://winlink.org/user

I understand this needs a lot more documentation.
It was difficult to configure the gui email clients with a script so use
these notes for each gui email app:

claws-mail:
https://github.com/nwdigitalradio/n7nix/blob/master/email/claws/README.md

rainloop:
https://github.com/nwdigitalradio/n7nix/tree/master/email/rainloop

THIS is not PiGate. You should talk to Mark Griffith if that is what you
want.

/Basil


Gary KC3PO <kc3po@...> writes:

All or most of the pieces seem to be there (haven't checked to see if
SquirrelMail is there, but it can be added obviously)...

I'm mainly talking about the integration that was done... ideally, I'd
like to run a setup script and fire up the hot spot, web server, mail
server, etc and have it ready to roll. It's not rocket science for
someone familiar with the pieces, but there would be some legwork and
trial and error for someone to recreate the wheel.

- Gary KC3PO

Re: PiGate

Julie McGrew
 

Actually there are a number of issues that would make this a heavy lift.

First off, squirrelmail uses php 5 and is not Stretch friendly.  Also, that email client is now poorly supported.  PiGate 1.5 currently does not run on the new RPI 3 B+.  There are some recent issues with changes made by the WDT that Mark Griffith has been working on, but you would have to contact him for current status.

Not to be negative as I very much like PiGate and respect the hard work Mark has put into that project.  If fact, I’ve built several over the past couple years.  Just noting that it may be a more complex undertaking than seen at first “blush”.  :)

73,
julie mcgrew
ac0wn


On Apr 9, 2019, at 4:02 PM, Gary KC3PO <kc3po@...> wrote:

All or most of the pieces seem to be there (haven't checked to see if SquirrelMail is there, but it can be added obviously)...

I'm mainly talking about the integration that was done... ideally, I'd like to run a setup script and fire up the hot spot, web server, mail server, etc and have it ready to roll. It's not rocket science for someone familiar with the pieces, but there would be some legwork and trial and error for someone to recreate the wheel.

- Gary  KC3PO

Re: Icom 706MKIIG Setup #icom #ptt

 

I use my 706 for packet with PTT over the mini din 6 along with rig control using a USB CI-V cable

Re: Icom 706MKIIG Setup #icom #ptt

 

You should be able to use GPIO keying with the mini DIN-6 cable.

On Tue, Apr 9, 2019 at 3:52 PM Todd via Groups.Io <ic7461=yahoo.com@groups.io> wrote:
So, what I guess your saying is I can't use the 6 pin DIN connectors directly to my 6 pin DIN on the back of my Icom 706MKIIG radio. I did try and configure Fldigi with the GPIO setting but wasn't successful. Cannot key the radio with fldigi either. Same condition with JS8Call. 



--


John D. Hays
Edmonds, WA
K7VE

   

Re: PiGate

Gary KC3PO
 

All or most of the pieces seem to be there (haven't checked to see if SquirrelMail is there, but it can be added obviously)...

I'm mainly talking about the integration that was done... ideally, I'd like to run a setup script and fire up the hot spot, web server, mail server, etc and have it ready to roll. It's not rocket science for someone familiar with the pieces, but there would be some legwork and trial and error for someone to recreate the wheel.

- Gary  KC3PO

Re: Icom 706MKIIG Setup #icom #ptt

Todd
 

So, what I guess your saying is I can't use the 6 pin DIN connectors directly to my 6 pin DIN on the back of my Icom 706MKIIG radio. I did try and configure Fldigi with the GPIO setting but wasn't successful. Cannot key the radio with fldigi either. Same condition with JS8Call. 

Re: PiGate

 

Hi Gary,

What feature does PiGate have that isn’t already on the image?

Bryan K7UDR

PiGate

Gary KC3PO
 

Has anyone integrated the PiGate (KDØQYN) into the Draws image and/or are there plans to do it with the main NW Digital Draws image? Seems like a slam dunk.

I don't want to reinvent the wheel if someone has already done it or working on it.

- Gary KC3PO

Re: Basic Direwolf question #draws #direwolf #ax25

Basil Gunn
 

Sorry about the delay. I finally got a chance to try it last night and it
seems to be working as expected. Not that it's likely to be an issue for me
but is that script limited to North latitude and West longitude? It looks
hard coded.
(Another) New version of beacmin.sh parses nema sentences instead of
gpsd sentences. Parsing nema sentences is less work to put into APRS
format & adds parameterized lat/lon direction.
https://github.com/nwdigitalradio/n7nix/commit/772431d2201a5e6f5a3af2771559d13a7efa817c

You are right this fix is not an issue for your location.

/Basil n7nix

Thank you!

On Sat, Apr 6, 2019 at 6:53 PM Basil Gunn <@basil860> wrote:


Dave N20A,

I checked-in a fix to the problem that you reported with beacmin.sh.
Fix GPS to APRS position format: Degrees Minutes.m

https://github.com/nwdigitalradio/n7nix/commit/5821f4ff36b3ca976439c9325f484664476e839a

To get the new script:
I you modified the beacmin.sh script in n7nix/debug then you need to
remove it.

cd
cd n7nix/debug
rm beacmin.sh

# To get new script
git pull

When you first run beacmin.sh in may take some time to install the bc
program, an
arbitrary precision command line calculator. It will run much more
quickly the next times.

When you get a chance please run beacmin.sh and let me know if it meets
your
expectations. You should edit the script to set the SSID to what ever
you want. You should also set the beacon_msg string to use a different icon

Thanks,
/Basil

Dave N2OA <kdcarlso@...> writes:

Thank you. I did a search on SSID so I missed the SID and thought it
pulled
it with the call.

Here is the results of beacmin.sh with debug turned on.

pi@n2oa-draws-1:~/n7nix/debug $ ./beacmin.sh
Read 1 lines of gps data
gpsdata: 43.01159
-78.189806667
lat: 43.01159
lon: -78.189806667
./beacmin.sh: line 52: 01159: value too great for base (error token is
"01159")
axports: found line: udr0 N2OA-1 9600 255 2 Direwolf port
udr1 N2OA-10 9600 255 2 Winlink port
Found callsign: N2OA
Set callsign N2OA
Sent: /usr/local/sbin/beacon -c N2OA-1 -d 'APUDR1 via WIDE1-1' -l -s
udr0
!43.01159N/78.189806667Wp06 15:46:43 EDT, Seq: 21


Dave
N2OA

On Fri, Apr 5, 2019 at 5:36 PM Basil Gunn <@basil860> wrote:


Dave,
Thanks for trying out my script.
I will fix the errors you are seeing but I need some more info.
Could you please do the following:

# Go to the directory where beacmin.sh lives.

cd
cd n7nix/debug

# Using your favorite text editor change the following two lines near
# the top of the file.

# 1. Get rid the hash symbol in front of DEBUG=1
#DEBUG=1

# 2. Change the SID number to what ever you want to use.
SID=15

Now run the the beacmin.sh script and copy & paste the console output to
me in
an email.

Thanks, Dave.
/Basil


Dave N2OA <kdcarlso@...> writes:

On Fri, Apr 5, 2019 at 12:09 PM, Basil Gunn wrote:

Thanks for the answers and Basil for the scrips. I tried thebeacmin.sh
script and it does beacon but I am not getting a location on my TH-D74
or
FTM-400. I also notice that the SSID is always is always 15 even though
my
SSID in axports is set to -1.

The message sent is Sent: /usr/local/sbin/beacon -d N2OA-15 -d 'APUDR1
via WIDE1-1' -l -s udr0 !43.01165833N/78.1899Wp05 16:19:08 EDT, Seq: 15

I do get an error in line 52: 01165833: value too great for base
(error
token is "011658333")

I also noticed int your example you show beacon -c and mine is showing
-d and the decimal is 2 digits in for lat and long which I would expect
but
your example show 4 digits and then a decimal. Am I missing something?

Thanks,

Dave
N2OA

Re: DRAWS™ and YAESU FTM-100 for analog and digital modes

John Spoonhower
 

Bernard,
thanks for the update!
73,
John, NX2I

On Tue, Apr 9, 2019 at 3:48 PM f6bvp <f6bvp@...> wrote:
John,

I forgot to mention that transmitted signal used for level adjustment
was performed by either n7nix deviation measure deviation script or
using direwolf -t 0 -x

Bernard

Le 09/04/2019 à 21:42, f6bvp a écrit :
> Hi John,
>
> I performed audio level adjustment for I found that FTM-100DE VHF
> transmitted signal from DRAWS modem was spreading around the TX frequency.
>
> After adjusment this is the result of alsa-show.sh :
>
>  ===== ALSA Controls for Radio Tansmit =====
> LO Driver Gain  L:[15.00dB]   R:[15.00dB]
> PCM           L:[-31.00dB]    R:[-31.00dB]
> DAC Playback PT       L:[PTM_P3]      R:[PTM_P3]
> LO Playback CM        [Full Chip CM]
>
>  ===== ALSA Controls for Radio Receive =====
> ADC Level     L:[0.00dB]      R:[-5.00dB]
> IN1           L:[Off]         R:[Off]
> IN2           L:[10 kOhm]     R:[10 kOhm]
> CM            L:[10 kOhm]     R:[10 kOhm]
>
> Here is how I proceeded for level adjustement using alsamixer.
> I have set a second yaesu device with a Raspberry Pi, UDRC II modem and
> audacity to listen to my packets.
> While recording the audio signal, I first changed LO driver gain in
> alsamixer.
> I then stepped down the PCM and then increased it again until the
> received signal did not increase any more.
>
> With above levels, the transmitted 1200 bauds FSK signal was clean and
> it was copied correctly by adjacent APRS repeater stations.
>
> On average received APRS frames are reported to have an audio level
> around 20. AFSK frames are perfectly decoded.
>
> 73 de Bernard, f6bvp
>
> p.s. there is a typo in first line of alsa-show.sh dump:
>      "Radio Tansmit =====" should be Radio Transmit =====
>
>
> Le 06/04/2019 à 18:22, John Spoonhower a écrit :
>> Bernard,
>> I am curious about what are the audio level settings for this radio. Can
>> you please post the results of "alsa-show.sh"?
>> 73,
>> John,
>> NX2I
>>



Re: DRAWS™ and YAESU FTM-100 for analog and digital modes

Basil Gunn
 

p.s. there is a typo in first line of alsa-show.sh dump:
"Radio Tansmit =====" should be Radio Transmit =====
Thanks Bernard!
/Basil

Re: DRAWS™ and YAESU FTM-100 for analog and digital modes

f6bvp
 

John,

I forgot to mention that transmitted signal used for level adjustment
was performed by either n7nix deviation measure deviation script or
using direwolf -t 0 -x

Bernard

Le 09/04/2019 à 21:42, f6bvp a écrit :
Hi John,

I performed audio level adjustment for I found that FTM-100DE VHF
transmitted signal from DRAWS modem was spreading around the TX frequency.

After adjusment this is the result of alsa-show.sh :

===== ALSA Controls for Radio Tansmit =====
LO Driver Gain L:[15.00dB] R:[15.00dB]
PCM L:[-31.00dB] R:[-31.00dB]
DAC Playback PT L:[PTM_P3] R:[PTM_P3]
LO Playback CM [Full Chip CM]

===== ALSA Controls for Radio Receive =====
ADC Level L:[0.00dB] R:[-5.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[10 kOhm]
CM L:[10 kOhm] R:[10 kOhm]

Here is how I proceeded for level adjustement using alsamixer.
I have set a second yaesu device with a Raspberry Pi, UDRC II modem and
audacity to listen to my packets.
While recording the audio signal, I first changed LO driver gain in
alsamixer.
I then stepped down the PCM and then increased it again until the
received signal did not increase any more.

With above levels, the transmitted 1200 bauds FSK signal was clean and
it was copied correctly by adjacent APRS repeater stations.

On average received APRS frames are reported to have an audio level
around 20. AFSK frames are perfectly decoded.

73 de Bernard, f6bvp

p.s. there is a typo in first line of alsa-show.sh dump:
"Radio Tansmit =====" should be Radio Transmit =====


Le 06/04/2019 à 18:22, John Spoonhower a écrit :
Bernard,
I am curious about what are the audio level settings for this radio. Can
you please post the results of "alsa-show.sh"?
73,
John,
NX2I

Re: DRAWS™ and YAESU FTM-100 for analog and digital modes

f6bvp
 

Hi John,

I performed audio level adjustment for I found that FTM-100DE VHF
transmitted signal from DRAWS modem was spreading around the TX frequency.

After adjusment this is the result of alsa-show.sh :

===== ALSA Controls for Radio Tansmit =====
LO Driver Gain L:[15.00dB] R:[15.00dB]
PCM L:[-31.00dB] R:[-31.00dB]
DAC Playback PT L:[PTM_P3] R:[PTM_P3]
LO Playback CM [Full Chip CM]

===== ALSA Controls for Radio Receive =====
ADC Level L:[0.00dB] R:[-5.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[10 kOhm]
CM L:[10 kOhm] R:[10 kOhm]

Here is how I proceeded for level adjustement using alsamixer.
I have set a second yaesu device with a Raspberry Pi, UDRC II modem and
audacity to listen to my packets.
While recording the audio signal, I first changed LO driver gain in
alsamixer.
I then stepped down the PCM and then increased it again until the
received signal did not increase any more.

With above levels, the transmitted 1200 bauds FSK signal was clean and
it was copied correctly by adjacent APRS repeater stations.

On average received APRS frames are reported to have an audio level
around 20. AFSK frames are perfectly decoded.

73 de Bernard, f6bvp

p.s. there is a typo in first line of alsa-show.sh dump:
"Radio Tansmit =====" should be Radio Transmit =====

Le 06/04/2019 à 18:22, John Spoonhower a écrit :
Bernard,
I am curious about what are the audio level settings for this radio. Can
you please post the results of "alsa-show.sh"?
73,
John,
NX2I

On Sat, Apr 6, 2019 at 12:15 PM f6bvp <f6bvp@...
<mailto:f6bvp@...>> wrote:

Hi,

I just want to report the successful use of
Data Cable, 10-pin mini-DIN to 6-pin mini-DIN, for FTM-400DR/FTM-100DR,
from https://www.dxengineering.com/parts/ysu-ct-164
This lets you use DRAWS hat modem and Direwolf for AX.25 packet
applications.

FTM-100DE is an interesting mobile VHF/UHF FM rig that I am using at
home for 1200/9600 bauds AX.25 APRS application.
As a transition device it has both "analog" and new digital C4FM modes.
Data plug is a 10 pin mini DIN while UDRC II and DRAWS have mini DIN 6
plugs. This is the reason I had to use a compatible data cable.

Bernard, f6bvp
https://radiotelescopelavillette.wordpress.com/photos/stars-song-le-chant-des-etoiles/



_._,_._,_

Re: Basic Direwolf question #draws #direwolf #ax25

Dave N2OA
 

Sorry about the delay. I finally got a chance to try it last night and it seems to be working as expected. Not that it's likely to be an issue for me but is that script limited to North latitude and West longitude? It looks hard coded.

Thank you!

On Sat, Apr 6, 2019 at 6:53 PM Basil Gunn <basil@...> wrote:

Dave N20A,

I checked-in a fix to the problem that you reported with beacmin.sh.
Fix GPS to APRS position format: Degrees Minutes.m
https://github.com/nwdigitalradio/n7nix/commit/5821f4ff36b3ca976439c9325f484664476e839a

To get the new script:
I you modified the beacmin.sh script in n7nix/debug then you need to remove it.

cd
cd n7nix/debug
rm beacmin.sh

# To get new script
git pull

When you first run beacmin.sh in may take some time to install the bc program, an
arbitrary precision command line calculator. It will run much more
quickly the next times.

When you get a chance please run beacmin.sh and let me know if it meets your
expectations. You should edit the script to set the SSID to what ever
you want. You should also set the beacon_msg string to use a different icon

Thanks,
/Basil

Dave N2OA <kdcarlso@...> writes:

> Thank you. I did a search on SSID so I missed the SID and thought it pulled
> it with the call.
>
> Here is the results of beacmin.sh with debug turned on.
>
> pi@n2oa-draws-1:~/n7nix/debug $ ./beacmin.sh
> Read 1 lines of gps data
> gpsdata: 43.01159
> -78.189806667
> lat: 43.01159
> lon: -78.189806667
> ./beacmin.sh: line 52: 01159: value too great for base (error token is
> "01159")
> axports: found line: udr0 N2OA-1 9600 255 2 Direwolf port
> udr1 N2OA-10 9600 255 2 Winlink port
> Found callsign: N2OA
> Set callsign N2OA
>  Sent: /usr/local/sbin/beacon -c N2OA-1 -d 'APUDR1 via WIDE1-1' -l -s udr0
> !43.01159N/78.189806667Wp06 15:46:43 EDT, Seq: 21
>
>
> Dave
> N2OA
>
> On Fri, Apr 5, 2019 at 5:36 PM Basil Gunn <basil@...> wrote:
>
>>
>> Dave,
>> Thanks for trying out my script.
>> I will fix the errors you are seeing but I need some more info.
>> Could you please do the following:
>>
>> # Go to the directory where beacmin.sh lives.
>>
>> cd
>> cd n7nix/debug
>>
>> # Using your favorite text editor change the following two lines near
>> #  the top of the file.
>>
>> # 1. Get rid the hash symbol in front of DEBUG=1
>> #DEBUG=1
>>
>> # 2. Change the SID number to what ever you want to use.
>> SID=15
>>
>> Now run the the beacmin.sh script and copy & paste the console output to
>> me in
>> an email.
>>
>> Thanks, Dave.
>> /Basil
>>
>>
>> Dave N2OA <kdcarlso@...> writes:
>>
>> > On Fri, Apr 5, 2019 at 12:09 PM, Basil Gunn wrote:
>> >
>> > Thanks for the answers and Basil for the scrips. I tried thebeacmin.sh
>> script and it does beacon but I am not getting a location on my TH-D74 or
>> FTM-400. I also notice that the SSID is always is always 15 even though my
>> SSID in axports is set to -1.
>> >
>> > The message sent is Sent: /usr/local/sbin/beacon -d N2OA-15 -d 'APUDR1
>> via WIDE1-1' -l -s udr0 !43.01165833N/78.1899Wp05 16:19:08 EDT, Seq: 15
>> >
>> > I do get an error in line 52: 01165833: value too great for base (error
>> token is "011658333")
>> >
>> > I also noticed int your example you show beacon -c and mine is showing
>> -d and the decimal is 2 digits in for lat and long which I would expect but
>> your example show 4 digits and then a decimal. Am I missing something?
>> >
>> > Thanks,
>> >
>> > Dave
>> > N2OA



#2 in the draws video series

Steve McGrane <temporarilyoffline@...>
 


More to come, We might even get on the air!