Date   

Re: Package Installation Scripts (Was: Re: [RaspberryPi-4-HamRadio] Brand New to Raspberry Pi)

John Nicholas
 

Larry,

Thanks for all the info and the scripts.  I should handle them easily with some practice.  My Unix Command Line Skills have deteriorated over the last 15 years, with minimal usage.  

I may come back with questions as I get into it.  1st Priority is supervise my SIL install a 6 meter and 10 meter dipole, perhaps one to night and one tomorrow night. I was installing them along with a 20 and 40 meter on the roof.  Then I fell down some steps on the 13th and broke some ribs. I got my tech and general tickets on March 14.  The HF stuff is set up and awaiting a tuned antenna.  I’d like to make a few contacts with Field Day, then work on the Pi stuff.

de KE0ZUW  John Nicholas  
Amateur Radio General Class Operator
Member ARRL, Wichita ARC, & Air Capitol ARC 
Grid Square EM17im

On Jun 24, 2020, at 11:32 AM, Larry Dighera <LDighera@...> wrote:

On Mon, 22 Jun 2020 11:12:56 -0500, "John Nicholas"
<stnick@...> wrote:

So when I decide to add an app to my collection.  Do I add it via the etcher to the download, or onto the SD Card, or download after everything is up and running


Re: Tnc-x PI

N5XMT
 

My command was different as I'm using i2c to communicate with the TNC... so still use the /dev/serial0 0


On Wed, Jun 24, 2020 at 9:51 AM N5XMT via groups.io <dacooley=gmail.com@groups.io> wrote:
changes with pitnc_setparams:

pi@HamPi8:~/pitnc $ pitnc_getparams 1 30

   TNC Software Version          11
01 TXDelay - Zero means use ADC  50
02 Persistance                   64
03 Slottime (in 10 mS)           40
04 TXTail                        30
05 Full Duplex - Not used         0
06 Our Channel (Hex)             00
07 I2C Address (0 = async) Hex   00
08 Mode Speed                  1200
09 RX Level (Config)            128
10 TX Level                     255
11 RX Level (Actual)            128
13 Centre Freq                 1700

On Wed, Jun 24, 2020 at 9:36 AM Don Poaps <va7dgp@...> wrote:
I redid the sudo raspi-config > serial Etc.

pi@raspberrypi:~/pitnc $ sudo ./pitnc_getparams /dev/serial0 0

Using Serial port /dev/serial0
retrying...

   TNC Software Version           8
01 TXDelay - Zero means use ADC  50
02 Persistance                  255
03 Slottime (in 10 mS)          255
04 TXTail                       255
05 Full Duplex - Not used       255
06 Our Channel (Hex)             ff
07 I2C Address (0 = async) Hex   ff
08 Mode Speed                  25500
09 RX Level (Config)            255
10 TX Level                     255
11 RX Level (Actual)            255
13 Centre Freq                 2550
8 8 32 ff ff ff ff ff ff ff ff ff ff ff cd c0 sum 0
pi@raspberrypi:~/pitnc $

Not all I need is to get APRS and Figure out Pat Configure, 

73

Don va7dgp/va7qu
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Wed, Jun 24, 2020 at 12:32 AM John Wiseman <john.wiseman@...> wrote:
Unfortunately that instruction is also now out of date.

The correct way is now to use raspi-config Interfacing Options/Serial to disable login on the serial port and enable the port.

73,
John G8BBPQ



On 24/06/2020 05:55, Don Poaps wrote:
Tim I finally see what you meant by Note

  Note added 12/4/2018: Some individuals have reported that there is a problem with the November, 2018 revision of Raspbian that results in the serial port not being accessible. You would notice this, for example, if you run pitnc_getparams and you keep getting “retrying…” instead of the menu. In this case you need to edit the config.txt file in the /boot/ directory. You can do this by running the following from the command line: sudo leafpad /boot/config.txt Add the following line at the bottom of this file: dtoverlay=pi3-miniuart-bt This problem seems to be fixed with more recent versions of the Stretch version of Raspian.   

Thank You.

I thought Buster would have fixed that issue. 

73

Don va7dgp/va7qu
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Tue, Jun 23, 2020 at 1:47 PM Tim via groups.io <the_fro_god=yahoo.com@groups.io> wrote:
Did you try the Note added 12/4/2018 stuff?


Re: Tnc-x PI

N5XMT
 

changes with pitnc_setparams:

pi@HamPi8:~/pitnc $ pitnc_getparams 1 30

   TNC Software Version          11
01 TXDelay - Zero means use ADC  50
02 Persistance                   64
03 Slottime (in 10 mS)           40
04 TXTail                        30
05 Full Duplex - Not used         0
06 Our Channel (Hex)             00
07 I2C Address (0 = async) Hex   00
08 Mode Speed                  1200
09 RX Level (Config)            128
10 TX Level                     255
11 RX Level (Actual)            128
13 Centre Freq                 1700


On Wed, Jun 24, 2020 at 9:36 AM Don Poaps <va7dgp@...> wrote:
I redid the sudo raspi-config > serial Etc.

pi@raspberrypi:~/pitnc $ sudo ./pitnc_getparams /dev/serial0 0

Using Serial port /dev/serial0
retrying...

   TNC Software Version           8
01 TXDelay - Zero means use ADC  50
02 Persistance                  255
03 Slottime (in 10 mS)          255
04 TXTail                       255
05 Full Duplex - Not used       255
06 Our Channel (Hex)             ff
07 I2C Address (0 = async) Hex   ff
08 Mode Speed                  25500
09 RX Level (Config)            255
10 TX Level                     255
11 RX Level (Actual)            255
13 Centre Freq                 2550
8 8 32 ff ff ff ff ff ff ff ff ff ff ff cd c0 sum 0
pi@raspberrypi:~/pitnc $

Not all I need is to get APRS and Figure out Pat Configure, 

73

Don va7dgp/va7qu
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Wed, Jun 24, 2020 at 12:32 AM John Wiseman <john.wiseman@...> wrote:
Unfortunately that instruction is also now out of date.

The correct way is now to use raspi-config Interfacing Options/Serial to disable login on the serial port and enable the port.

73,
John G8BBPQ



On 24/06/2020 05:55, Don Poaps wrote:
Tim I finally see what you meant by Note

  Note added 12/4/2018: Some individuals have reported that there is a problem with the November, 2018 revision of Raspbian that results in the serial port not being accessible. You would notice this, for example, if you run pitnc_getparams and you keep getting “retrying…” instead of the menu. In this case you need to edit the config.txt file in the /boot/ directory. You can do this by running the following from the command line: sudo leafpad /boot/config.txt Add the following line at the bottom of this file: dtoverlay=pi3-miniuart-bt This problem seems to be fixed with more recent versions of the Stretch version of Raspian.   

Thank You.

I thought Buster would have fixed that issue. 

73

Don va7dgp/va7qu
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Tue, Jun 23, 2020 at 1:47 PM Tim via groups.io <the_fro_god=yahoo.com@groups.io> wrote:
Did you try the Note added 12/4/2018 stuff?


Re: Tnc-x PI

Don Poaps
 

I redid the sudo raspi-config > serial Etc.

pi@raspberrypi:~/pitnc $ sudo ./pitnc_getparams /dev/serial0 0

Using Serial port /dev/serial0
retrying...

   TNC Software Version           8
01 TXDelay - Zero means use ADC  50
02 Persistance                  255
03 Slottime (in 10 mS)          255
04 TXTail                       255
05 Full Duplex - Not used       255
06 Our Channel (Hex)             ff
07 I2C Address (0 = async) Hex   ff
08 Mode Speed                  25500
09 RX Level (Config)            255
10 TX Level                     255
11 RX Level (Actual)            255
13 Centre Freq                 2550
8 8 32 ff ff ff ff ff ff ff ff ff ff ff cd c0 sum 0
pi@raspberrypi:~/pitnc $

Not all I need is to get APRS and Figure out Pat Configure, 

73

Don va7dgp/va7qu
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Wed, Jun 24, 2020 at 12:32 AM John Wiseman <john.wiseman@...> wrote:
Unfortunately that instruction is also now out of date.

The correct way is now to use raspi-config Interfacing Options/Serial to disable login on the serial port and enable the port.

73,
John G8BBPQ



On 24/06/2020 05:55, Don Poaps wrote:
Tim I finally see what you meant by Note

  Note added 12/4/2018: Some individuals have reported that there is a problem with the November, 2018 revision of Raspbian that results in the serial port not being accessible. You would notice this, for example, if you run pitnc_getparams and you keep getting “retrying…” instead of the menu. In this case you need to edit the config.txt file in the /boot/ directory. You can do this by running the following from the command line: sudo leafpad /boot/config.txt Add the following line at the bottom of this file: dtoverlay=pi3-miniuart-bt This problem seems to be fixed with more recent versions of the Stretch version of Raspian.   

Thank You.

I thought Buster would have fixed that issue. 

73

Don va7dgp/va7qu
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Tue, Jun 23, 2020 at 1:47 PM Tim via groups.io <the_fro_god=yahoo.com@groups.io> wrote:
Did you try the Note added 12/4/2018 stuff?


Package Installation Scripts (Was: Re: [RaspberryPi-4-HamRadio] Brand New to Raspberry Pi)

Larry Dighera
 

On Mon, 22 Jun 2020 11:12:56 -0500, "John Nicholas"
<stnick@...> wrote:

So when I decide to add an app to my collection. Do I add it via the etcher to the download, or onto the SD Card, or download after everything is up and running
Hello John,

Raspbian, a derivative of Debian, uses the 'apt' command, or the
curses-based menu-driven 'aptitude' command-line package manager to
add software packages to your system. You'll also find a GUI software
manager in the applications menu-tree at the upper left corner of your
desktop.

You appear to be comfortable with the command-line interface, as am I,
so below (and attached) are a few scripts I've written for my own use
in adding packages. These are a bit crude, contain inconsistencies,
and surely could be cleaned up and re-written in a more elegant
manner, but I find them very useful none the less.

The first is 'apt.sh' which I run to see if there are any updates
available, before actually downloading a package:

-----------------------------------------------------------------------
# apt.sh Initialize package handler
# LGD: Mon Jun 5 11:58:39 PDT 2017

#set -xv # DEBUG
LOGFIL="$HOME/logs/$0.log"
[[ -d ${HOME}/logs ]] || echo -e "\n$0\: Log directory $LOGFIL does
not exist$(exit 2)" >&2

# Check for internet connection
STAT(){
ping -c1 -q 8.8.8.8 2>/dev/null 1>/dev/null ;STATUS=`echo $?`
return $?
}

# Check for stale lock file
LOCKED(){
LOCFIL=/var/lib/dpkg/lock
if [[ -f $LOCFIL ]] ;then # Does stale lock file
exist?
ls -l $LOCFIL # Display lock file
parameters
read -n 1 CHOICE?"`echo -e \"\nRemove Lock File
[Y/n/q]?\c\"`";echo # Prompt for user action
case $CHOICE in
q|Q*) exit ;; # Quit this script
*) echo; rm $LOCFIL;return "$?" ;; # Remove lock file and
return to caller with command status
esac
fi
return 0
}

LOCKED # Check for stale lock
file
until [[ $STATUS -eq 0 ]] ;do # Wait for network
connection
echo -e "Waiting for network connection."
sleep 3
STAT
done
setterm -foreground green # Set text color to
green
echo -e "\n\tNetwork connection successful\n";
#setterm -foreground white # Set text color to
white
setterm --default # Set terminal to
default values
aplay -q /usr/lib/libreoffice/share/gallery/sounds/apert.wav #
Announce successful network connection

echo;date +%A", "%B" "%d", "%Y" "%R
read -n 1 CHOICE?"`echo -e \"\nUpdate apt package system before
continuing [Y/n]? \"`";echo
case $CHOICE in
[nN]) exit ;; # Don't update
*) echo -e "\n##### `date` ####" >> ${LOGFIL};apt-get update 2>&1 |
tee -a ${LOGFIL} && apt-get --show-progress upgrade 2>&1 | tee -a
${LOGFIL} ;; # Update
esac

read -n 1 CHOICE?"`echo -e \"\nUpgrade Debian system before continuing
[Y/n]? \"`";echo
case $CHOICE in
[nN]) exit ;; # Don't upgrade
*) date >> ${LOGFIL};apt-get --show-progress dist-upgrade 2>&1 | tee
-a ${LOGFIL} ;; # Ugrade
esac
-----------------------------------------------------------------------

Between the effects of word-wrap and Windows Carriage-return,
Line-feed convention to end lines, the above will require some editing
to use. The attachments won't have those issues.

The next script, 'show.sh' is used to query the package database to
find if it contains a package supplied as an argument after the
command itself. I often find it useful to append a '\*' after the
package name to display package name variants.

-----------------------------------------------------------------------
#! /bin/ksh
# show.sh Display package information
#
# LGD: Sat 25 Jun 07:56:55 PDT 2016
# LGD: Mon 13 Feb 16:23:15 PST 2017 Added smart-pager support
#

if [[ $(tty |grep pts) ]] ;then
export LESS="-P\ ?f%f .?n?m(file %i of %m) ..?ltlines %lt-%lb?L/%L.
: byte %bB?s/%s. .?e(END) ?x- Next\: %x.:?pB%pB\%..%t (pts`tty|cut -d/
-f4`) "
else
export LESS="-P\ ?f%f .?n?m(file %i of %m) ..?ltlines %lt-%lb?L/%L.
: byte %bB?s/%s. .?e(END) ?x- Next\: %x.:?pB%pB\%..%t (`tty|cut -d/
-f3`) "
fi

# USAGE: Multi-package search not yet implemented
[[ $# -lt 1 ]] && echo -e "\n\tUsage: $0 [package name] \<package
name\> \<...\>\n" >&2 && exit 1

LOGFIL="$HOME/logs/$0.log"
[[ -d ${HOME}/logs ]] || echo -e "\n$0\: Log directory $LOGFIL does
not exist$(exit 2)" >&2

#set -x
SRCH=$(echo "$@"|sed 's/*/\\\\*/') # Escape * so shell doesn't show
filenames

FOUND=$(/usr/bin/apt-cache show $SRCH 2>&1) # BUG: Fails to assign
value to $FOUND
#FOUND=$(/usr/bin/apt-cache show "$SRCH")

if [[ `echo "$FOUND"|grep "purely virtual"` ]] ;then # BUG: This
fails to display output
echo "$FOUND" >&2; exit 1
elif [[ `echo "$FOUND"|grep "No packages found"` ]] ;then
echo "$FOUND" >&2; exit 1
else # Only pipe output through less when necessary
[[ `echo "$FOUND"|wc -l` -gt 30 ]] && echo "$FOUND"| less -p
'Package:'
[[ `echo "$FOUND"|wc -l` -le 30 ]] && echo "$FOUND"; exit
fi
-----------------------------------------------------------------------

You'll notice that I'm using the Korn Shell (ksh) command-line
interpreter. If you want to use it, you'll have to install it with:
'apt-get install ksh' first. Otherwise, I'll leave the editing to
support bash or sh as an exercise. :-) I like 'ksh' because, it
supports 'vi' command-line editing and floating-point math, and it was
what I learned back in the '80s.

And finally, here is 'get.sh' to actually install the package:

-----------------------------------------------------------------------
#! /usr/bin/ksh
#
# get.sh Install packages
#
# A front-end for 'apt-get' that provides package installation
information before installing packages and logs actions
#
# LGD: Sat 25 Jun 07:56:55 PDT 2016
# LGD: Tue 05 May 2020 10:43:28 AM PDT: Bug fixes and enhancements
#


# Check for positional parameters
[[ $# -lt 1 ]] && echo -e "\n\tUsage: $0 [package names]\n" && exit 1

# Set variable values and verify log file structure
PROG=$(basename $0)
ARGS="$@"
LOGDIR="$HOME/logs/"
LOGFIL="$HOME/logs/$(basename $0).log"
# Check for existence of log directory and writable log file
if [[ -d ${LOGDIR} ]] ;then
:
else echo -e "\n${0}: Log directory $LOGDIR does not exist." >&2
exit 2
fi

if [[ -w ${LOGFIL} ]] ;then
:
else echo -e "\n${0}: Log file ${LOGFIL} does not exist or is not
writeable." >&2
exit 3
fi

echo -e "\n${PROG}: Working. Please standby ..." >&2 # Display
assurance message

# Enter date into logfile
DATSTAMP() {
echo -e "\nOOOO- $ARGS -OOOO \c" >>$LOGFIL # Blank line
separator in log file
$(/bin/date '+%_A, %B %-d, %Y %H%M %Z'\)>>$LOGFIL)
return 0
}


# Test package installation before continuing
apt-get -s install $@ 2>&1 >/dev/null; EXSTAT=$? # Test for
success: 100=Unable to locate package; 0=Already newest version

# Get the package
case $EXSTAT in # 1=fail; 100=Unable to locate package(S)
0) echo -e "\nInstall $@ [y/N]? \c"
read REPLY
[[ ${REPLY} == [yY] ]] && DATSTAMP
# apt-get -s install $@ 2>&1 |tee -a $LOGFIL ;; #
DEBUG Install package(s)
apt-get install $@ 2>&1 |tee -a $LOGFIL ;; # DEBUG
Install package(s)
"100") DATSTAMP;echo -e "\nUnable to locate package(s) $@"|tee -a
$LOGFIL ; exit 100 ;; # Log event
*) echo "EXTSTAT = $EXTSTAT";echo -e "\n${0}: Package install
failure (${?}).";exit 5 ;; # Report failure with exit
code
esac

exit
-----------------------------------------------------------------------

You'll notice that these scripts write log files of the output of
their 'apt' commands in a 'logs' subdirectory under your $HOME
directory, so you'll need to 'mkdir $HOME/logs' before using the
scripts, if you want to keep logs. This can be useful when the output
scrolls too fast to read, and as a record of what you've done.

Finally, I put the name of this file '.fun' in my '$ENV' file so that
it adds a few useful functions to my environment. The 'd' function
can be useful for navigating convoluted directory structures.

-----------------------------------------------------------------------
cls(){
tput clear
cd
tty
}

u(){
cd ..
}

d() {
if [ "$BASH" ] && [ "$BASH" != "/bin/sh" ]; then
echo "$FUNCNAME: ksh only";return 1
fi

FIGNORE= # ksh93 equivalent to bash shopt -s dotglob

if [ ${#} -gt 0 ] ;then # Only one
command line argument accepted
cd -- "$1" && return 0
fi

if [ `ls -AF1|grep /|wc -l` -eq 1 ] ;then # cd if only
one subdirectory
cd -- `ls -AF1|grep /` && return 0
fi

destdir=$(
while :; do
subdirs=( ~(N)*/ ) # ksh93 equivalent to subdirs=( */ ) with
shopt -s nullglob
(( ${#subdirs[@]} > 2 )) || break # . and .. are two entries

echo -e "\n\t\tSubdirectories below ${PWD}: \n" >&2

for idx in "${!subdirs[@]}"; do
printf '%d) %q\n' "$idx" "${subdirs[$idx]%/}" >&2
done

printf '\nSelect a subdirectory: ' >&2
read -r
if [[ $REPLY ]]; then
cd -- "${subdirs[$REPLY]}" || break # Continue to
loop through subdirectories after cding
else
break
fi
done
printf '%s\n' "$PWD"
)
[[ $destdir ]] && cd -- "$destdir" && return 0
}

f(){
echo -e "You have these functions in your environment:\n"
typeset +f
echo
}

alias rm="rm -i"
alias cp="cp -i"
alias mv="mv -i"

alias ls="ls --color"
alias date="/bin/date '+%_A, %B %-d, %Y %H%M %Z'"
-----------------------------------------------------------------------

Of course, you'll have to enable execute permissions on these script
files before you will be able to run them:

chmod 755 apt.sh show.sh get.sh

Have fun, and if you improve my scripts, please e-mail a copy to me:
@LDighera

Best regards,
Larry
WB6BBB


PS: I was chatting with a fellow on 40-meters the other day, and
happened to mention that this pandemic means "Bye Bye Boomer," and
cleaver fellow, he said that made a good mnemonic for my call. :-)


Re: CAT Control Options

W6TUX Dave
 

John, I realize I'm coming into this late, but absolutely have never had a problem with FTDI USB cables - Prolific was always hit or miss.  For many years now have purchased FTDI cables from Mark KJ6ZWL (BlueMax49ers on eBay), have enjoyed excellent response time and not a single failure yet.  https://www.ebay.com/usr/bluemax49ers?_trksid=p2047675.l2559

Replaced our old IC-718 with a 7300 a couple years ago, but here is the FTDI USB CAT cable for the 718:

https://www.ebay.com/itm/FTDI-USB-CI-V-CAT-Programming-Cable-CAT-CI-V-IC-718-IC-725-IC-726-IC-728-CT-17/151268063957?hash=item2338477ad5:g:mskAAOSwG~ZaEIoB

73, dave/W6TUX


Re: Tnc-x PI

John Wiseman
 

Unfortunately that instruction is also now out of date.

The correct way is now to use raspi-config Interfacing Options/Serial to disable login on the serial port and enable the port.

73,
John G8BBPQ



On 24/06/2020 05:55, Don Poaps wrote:
Tim I finally see what you meant by Note

  Note added 12/4/2018: Some individuals have reported that there is a problem with the November, 2018 revision of Raspbian that results in the serial port not being accessible. You would notice this, for example, if you run pitnc_getparams and you keep getting “retrying…” instead of the menu. In this case you need to edit the config.txt file in the /boot/ directory. You can do this by running the following from the command line: sudo leafpad /boot/config.txt Add the following line at the bottom of this file: dtoverlay=pi3-miniuart-bt This problem seems to be fixed with more recent versions of the Stretch version of Raspian.   

Thank You.

I thought Buster would have fixed that issue. 

73

Don va7dgp/va7qu
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Tue, Jun 23, 2020 at 1:47 PM Tim via groups.io <the_fro_god=yahoo.com@groups.io> wrote:
Did you try the Note added 12/4/2018 stuff?


Re: Tnc-x PI

Don Poaps
 

Tim I finally see what you meant by Note

  Note added 12/4/2018: Some individuals have reported that there is a problem with the November, 2018 revision of Raspbian that results in the serial port not being accessible. You would notice this, for example, if you run pitnc_getparams and you keep getting “retrying…” instead of the menu. In this case you need to edit the config.txt file in the /boot/ directory. You can do this by running the following from the command line: sudo leafpad /boot/config.txt Add the following line at the bottom of this file: dtoverlay=pi3-miniuart-bt This problem seems to be fixed with more recent versions of the Stretch version of Raspian.   

Thank You.

I thought Buster would have fixed that issue. 

73

Don va7dgp/va7qu
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Tue, Jun 23, 2020 at 1:47 PM Tim via groups.io <the_fro_god=yahoo.com@groups.io> wrote:
Did you try the Note added 12/4/2018 stuff?


Re: HamPi 1.0 Released!

chuck gelm <rpi4ham@...>
 

On 6/20/20 12:23 PM, Dave Slotter, W3DJS wrote:
A couple of thoughts. First, what BitTorrent client are you running? Can you try using the main BitTorrent client?
Hi, Dave:

I am baffled. It worked. Just tried again and it worked.
I did a 'diff' on your recent attachment and the original. They are identical.

Thanks for this.

FirstL I am using Linux, program is 'transmission-gtk 2.92'.
I have no clue what a 'main BitTorrent client' is.

73, Chuck


Re: Tnc-x PI

Don Poaps
 

The Red light is not steady. It's Off

Thank You


Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Tue, Jun 23, 2020 at 4:06 PM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

If your RED LED power light is flashing, your power supply is very weak.  It needs to be steady on all the time.  If adding an external USB device like a TNC-X causes it to start flashing, then again, the power supply is too weak.

Mark
KD0QYN


On Tuesday, June 23, 2020, 5:21:32 PM CDT, Don Poaps <va7dgp@...> wrote:


Tad 

that's one of the first syntaxes I used. The yellow light is flashing on the Pi Hat. All of the lights blink when power is applied.

Putting it to bed for a while. If I plugged my USB tnc-x I get it to start in not type.

later

Don va7dgp/va7qu

On Tue., Jun. 23, 2020, 1:00 p.m. Tadd KA2DEW in NC via groups.io <tadd=mac.com@groups.io> wrote:
Try doing sudo before the command.   


On Jun 23, 2020, at 3:58 PM, Don Poaps <va7dgp@...> wrote:

I've been reading the setup from tncpi pdf from off the tnc-x website.

I've downloaded the zipped files,  there are now in the folder pitnc.
Both files permission are for Owner 

I keep getting retrying.

If I do ls /dev/serial*
It shows /dev/serial0 and /dev/serial1



So sort of lost as to where to go next

73 

Don




Re: GPS install

jrreid_24@...
 

I'll add I didn't realize this issue was on HamPi. That makes remote digi extremely difficult if your GPS can't provide a clock. Very disappointing. Hope more users than Tim are trying to figure this out or have figured it out. It's a no go for me if I can't use the GPS dongle. Just gave to stick with the old 2.0 as I'm not savvy enough to figure it out.
Thanks for all your hard work Dave. I'm running your 2.0 so since it ain't broke I'll hang on to it for now.


2400 baud with Yeasu/Vertex FTL-1011

 

The Yeasu/Vertex FTL-1011 vhf-lo (6m) (and probably the 2011, 7011 radios for 2m, 70cm) seem to work with 2400 baud.  They aren’t quite as noise immune on 2400 as on 1200 but the 6m version is really cheap!   https://www.ebay.com/itm/Vertex-FTL-1011-VHF-FM-Transceiver-FREE-SHIPPING/282346444832.  They do 35watts @51mhz and easily tune to the 1.5mhz of the 6m band.  Some of them work higher in 6m band.  


   Tadd — KA2DEW





On Jun 23, 2020, at 7:26 PM, Mark Griffith via groups.io <mdgriffith2003@...> wrote:

The TNC-Pi9k6 has a voltage range that is software select able from 24mv to 3000mv (3 volts).  This range works with most radios, but I've personally only tried a small set.

There is also a 2400 baud mode, but I have yet to find a radio that will work with it.  It's nice to have all those speeds, but then finding a radio that it can work with is another matter entirely.

I have a couple NinoTNC boards (ver2) that I need to start more earnest testing.  Too many other spring time things are in the way, planting the garden, keeping up on the grass cutting, smoking meat, eating it, etc etc etc.  Oh, and naps.  Naps are important.  *Sign*, retirement is such a tough life.

Mark
KD0QYN


On Tuesday, June 23, 2020, 6:07:13 PM CDT, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:


Another issue which may be important is some radios require more audio voltage/level going into the data port.  The NinoTNC has two selectable output ranges, high, for data radios, and low, for microphone audio, for this very reason.  NinoTNC has 1200, 2400, 4800, 9600 baud DSP modems built in so it needs to support a wide range of radios.  
   Tadd - KA2DEW

On Jun 23, 2020, at 6:29 PM, Ray Wells <vk2tv@...> wrote:

That's not quite correct. For receive, the difference between the 1200 and 9600 ports on the rear socket is that the former has de-emphasised audio while the latter has "flat" audio from the discriminator. There are reasons why using the discriminator output for 1200 packet is often superior for many hardware TNC/modems that aren't smart enough to compensate for relative tone levels (1200/2200Hz) when they are wrong. Soundcard style modems like Direwolf are far more capable and less particular in this regard. If you want to know why the correct audio is important, take a look at this site with pictures and a very simple explanation.   https://www.febo.com/packet/layer-one/transmit.html

I know I flog that site and will continue to do so because if everybody using packet read that article and implemented correct audio practices there would be a lot more stations having much greater reliability with packet radio/APRS communications. If I sound like a grumpy old man, I am. I've been involved with packet since about 1985 and the biggest single factor for people's
woes and failures with the mode remains wrong audio setup.

For transmit when using the rear socket, the radio will probably select the right option depending on whether you choose 1200 or 9600 for the speed in the radio setup, like my Kenwood TM-V71A does.

Ray vk2tv

On 24/6/20 3:17 am, Jim Lange wrote:
You need to use the 1200 port on the radio. The other is for high speed packet and won’t work with a TNC that isn’t made for it. Otherwise all is good. 

Sent by me


On Jun 23, 2020, at 13:13, Al Massaro <almassaro1@...> wrote:

OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.




Re: TV HDMI #pi

Chuck M
 

If my senioritis isn't acting up, remember making the changes in the config file re HDMI setup.  Will check again and also check the other item mentioned re TV setup.  Tried several different cables, TVs, and monitors before buying the booster.

having no problems with my Pi 4B or an older Pi 2 that controls my 3D printer.  Just the Pi 3B.

Chuck
KD9DVB


On Tuesday, June 23, 2020, 6:33:24 PM EDT, N5XMT <dacooley@...> wrote:


Shouldn't need it.  You can boost the HDMI signal out with a single command in the /boot/config.txt file

On Tue, Jun 23, 2020 at 1:34 PM Chuck M via groups.io <cam51mail=yahoo.com@groups.io> wrote:
Had a similar problem with a Pi 3B.  Ended up buying one of these to boost its signal.  Works okay with this.


Bit of a pain for portable use as it's another device to tote, plus extra HDMI cable, etc.  Does fine at home.

GL
Chuck
KD9DVB


On Tuesday, June 23, 2020, 2:33:57 PM EDT, w9ran <w9ran@...> wrote:


Hopefully this isn't your issue, but I recently found one of my Pi 3Bs
would no longer display hdmi output even though it has for months.   A
different Pi worked fine on the same monitor and cable.   Since ssh was
enabled I was able to communicate with it and tried all the stuff you
find in the FAQs, knowing it wasn't just a config.txt setting because
there was no video at startup which comes from the bootloader not from
Linux.   Google searching confirmed that random hdmi hardware failure on
the Pi is not unheard of.   Since the composite video works and the
published documentation doesn't show anything beyond the hdmi connector
I'm not optimistic about being able to fix it, but am open to suggestions.

73, Bob W9RAN





Re: TNCPi WITH YAESU FT 7900R

Mark Griffith
 

The TNC-Pi9k6 has a voltage range that is software select able from 24mv to 3000mv (3 volts).  This range works with most radios, but I've personally only tried a small set.

There is also a 2400 baud mode, but I have yet to find a radio that will work with it.  It's nice to have all those speeds, but then finding a radio that it can work with is another matter entirely.

I have a couple NinoTNC boards (ver2) that I need to start more earnest testing.  Too many other spring time things are in the way, planting the garden, keeping up on the grass cutting, smoking meat, eating it, etc etc etc.  Oh, and naps.  Naps are important.  *Sign*, retirement is such a tough life.

Mark
KD0QYN


On Tuesday, June 23, 2020, 6:07:13 PM CDT, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:


Another issue which may be important is some radios require more audio voltage/level going into the data port.  The NinoTNC has two selectable output ranges, high, for data radios, and low, for microphone audio, for this very reason.  NinoTNC has 1200, 2400, 4800, 9600 baud DSP modems built in so it needs to support a wide range of radios.  
   Tadd - KA2DEW

On Jun 23, 2020, at 6:29 PM, Ray Wells <vk2tv@...> wrote:

That's not quite correct. For receive, the difference between the 1200 and 9600 ports on the rear socket is that the former has de-emphasised audio while the latter has "flat" audio from the discriminator. There are reasons why using the discriminator output for 1200 packet is often superior for many hardware TNC/modems that aren't smart enough to compensate for relative tone levels (1200/2200Hz) when they are wrong. Soundcard style modems like Direwolf are far more capable and less particular in this regard. If you want to know why the correct audio is important, take a look at this site with pictures and a very simple explanation.   https://www.febo.com/packet/layer-one/transmit.html

I know I flog that site and will continue to do so because if everybody using packet read that article and implemented correct audio practices there would be a lot more stations having much greater reliability with packet radio/APRS communications. If I sound like a grumpy old man, I am. I've been involved with packet since about 1985 and the biggest single factor for people's
woes and failures with the mode remains wrong audio setup.

For transmit when using the rear socket, the radio will probably select the right option depending on whether you choose 1200 or 9600 for the speed in the radio setup, like my Kenwood TM-V71A does.

Ray vk2tv

On 24/6/20 3:17 am, Jim Lange wrote:
You need to use the 1200 port on the radio. The other is for high speed packet and won’t work with a TNC that isn’t made for it. Otherwise all is good. 

Sent by me


On Jun 23, 2020, at 13:13, Al Massaro <almassaro1@...> wrote:

OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.



Re: TNCPi WITH YAESU FT 7900R

Mark Griffith
 

Al,

I use a FT-7900 with my TNC-Pi9k6.  You need to use the 6 pin mini-DIN connector and not the DB-9.  That way, you don't need to change anything when switching between 1200 and 9600 baud except the settings on the TNC and on the radio.  No switching jumpers or cables.

The pin-out you mention on the PiGate site is just for radios that don't have the built-in packet port.  You *could* set it up through the mic and headset ports, but then you are limited to 1200 baud only.

Please let me know if you have any more questions.

Mark
KD0QYN


On Tuesday, June 23, 2020, 12:13:35 PM CDT, Al Massaro <almassaro1@...> wrote:


OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.


Re: TNCPi WITH YAESU FT 7900R

 

Another issue which may be important is some radios require more audio voltage/level going into the data port.  The NinoTNC has two selectable output ranges, high, for data radios, and low, for microphone audio, for this very reason.  NinoTNC has 1200, 2400, 4800, 9600 baud DSP modems built in so it needs to support a wide range of radios.  
   Tadd - KA2DEW

On Jun 23, 2020, at 6:29 PM, Ray Wells <vk2tv@...> wrote:

That's not quite correct. For receive, the difference between the 1200 and 9600 ports on the rear socket is that the former has de-emphasised audio while the latter has "flat" audio from the discriminator. There are reasons why using the discriminator output for 1200 packet is often superior for many hardware TNC/modems that aren't smart enough to compensate for relative tone levels (1200/2200Hz) when they are wrong. Soundcard style modems like Direwolf are far more capable and less particular in this regard. If you want to know why the correct audio is important, take a look at this site with pictures and a very simple explanation.   https://www.febo.com/packet/layer-one/transmit.html

I know I flog that site and will continue to do so because if everybody using packet read that article and implemented correct audio practices there would be a lot more stations having much greater reliability with packet radio/APRS communications. If I sound like a grumpy old man, I am. I've been involved with packet since about 1985 and the biggest single factor for people's
woes and failures with the mode remains wrong audio setup.

For transmit when using the rear socket, the radio will probably select the right option depending on whether you choose 1200 or 9600 for the speed in the radio setup, like my Kenwood TM-V71A does.

Ray vk2tv

On 24/6/20 3:17 am, Jim Lange wrote:
You need to use the 1200 port on the radio. The other is for high speed packet and won’t work with a TNC that isn’t made for it. Otherwise all is good. 

Sent by me


On Jun 23, 2020, at 13:13, Al Massaro <almassaro1@...> wrote:

OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.



Re: Tnc-x PI

Mark Griffith
 

Don,

If your RED LED power light is flashing, your power supply is very weak.  It needs to be steady on all the time.  If adding an external USB device like a TNC-X causes it to start flashing, then again, the power supply is too weak.

Mark
KD0QYN


On Tuesday, June 23, 2020, 5:21:32 PM CDT, Don Poaps <va7dgp@...> wrote:


Tad 

that's one of the first syntaxes I used. The yellow light is flashing on the Pi Hat. All of the lights blink when power is applied.

Putting it to bed for a while. If I plugged my USB tnc-x I get it to start in not type.

later

Don va7dgp/va7qu

On Tue., Jun. 23, 2020, 1:00 p.m. Tadd KA2DEW in NC via groups.io <tadd=mac.com@groups.io> wrote:
Try doing sudo before the command.   


On Jun 23, 2020, at 3:58 PM, Don Poaps <va7dgp@...> wrote:

I've been reading the setup from tncpi pdf from off the tnc-x website.

I've downloaded the zipped files,  there are now in the folder pitnc.
Both files permission are for Owner 

I keep getting retrying.

If I do ls /dev/serial*
It shows /dev/serial0 and /dev/serial1



So sort of lost as to where to go next

73 

Don




Re: TV HDMI #pi

N5XMT
 

Shouldn't need it.  You can boost the HDMI signal out with a single command in the /boot/config.txt file


On Tue, Jun 23, 2020 at 1:34 PM Chuck M via groups.io <cam51mail=yahoo.com@groups.io> wrote:
Had a similar problem with a Pi 3B.  Ended up buying one of these to boost its signal.  Works okay with this.


Bit of a pain for portable use as it's another device to tote, plus extra HDMI cable, etc.  Does fine at home.

GL
Chuck
KD9DVB


On Tuesday, June 23, 2020, 2:33:57 PM EDT, w9ran <w9ran@...> wrote:


Hopefully this isn't your issue, but I recently found one of my Pi 3Bs
would no longer display hdmi output even though it has for months.   A
different Pi worked fine on the same monitor and cable.   Since ssh was
enabled I was able to communicate with it and tried all the stuff you
find in the FAQs, knowing it wasn't just a config.txt setting because
there was no video at startup which comes from the bootloader not from
Linux.   Google searching confirmed that random hdmi hardware failure on
the Pi is not unheard of.   Since the composite video works and the
published documentation doesn't show anything beyond the hdmi connector
I'm not optimistic about being able to fix it, but am open to suggestions.

73, Bob W9RAN





Re: TNCPi WITH YAESU FT 7900R

Ray Wells
 

That's not quite correct. For receive, the difference between the 1200 and 9600 ports on the rear socket is that the former has de-emphasised audio while the latter has "flat" audio from the discriminator. There are reasons why using the discriminator output for 1200 packet is often superior for many hardware TNC/modems that aren't smart enough to compensate for relative tone levels (1200/2200Hz) when they are wrong. Soundcard style modems like Direwolf are far more capable and less particular in this regard. If you want to know why the correct audio is important, take a look at this site with pictures and a very simple explanation.   https://www.febo.com/packet/layer-one/transmit.html

I know I flog that site and will continue to do so because if everybody using packet read that article and implemented correct audio practices there would be a lot more stations having much greater reliability with packet radio/APRS communications. If I sound like a grumpy old man, I am. I've been involved with packet since about 1985 and the biggest single factor for people's
woes and failures with the mode remains wrong audio setup.

For transmit when using the rear socket, the radio will probably select the right option depending on whether you choose 1200 or 9600 for the speed in the radio setup, like my Kenwood TM-V71A does.

Ray vk2tv

On 24/6/20 3:17 am, Jim Lange wrote:
You need to use the 1200 port on the radio. The other is for high speed packet and won’t work with a TNC that isn’t made for it. Otherwise all is good. 

Sent by me


On Jun 23, 2020, at 13:13, Al Massaro <almassaro1@...> wrote:

OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.


Re: TV HDMI #pi

N5XMT
 

Try uncommenting the the following.  Try the first one and see if that works, if not uncomment the 2nd one as well.



# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

On Tue, Jun 23, 2020 at 9:54 AM Rob <n3ljs@...> wrote:
Running the pi with a 20 inch vizio tv out in the shop all is good. Decided to use a 32 inch vizio tv. No signal on the 32 in. When the 20 inch is on I unplug the hdmi cable Then plug into the 32 inch it works.....I did a reboot... then no display on the 32 inch......TNX

Newbie

ROB N3LJS