Date   

Configuring W3DJS V1.0 Direwolf questions.

Dennis Blanchard
 

I have the W3DJS V1.0 package running on a Raspberry Pi, 3. So far, so good, I have WSJT-x and Fldigi running. I'd like to set up Direwolf so that it works something like my old KPC-2 Kantronics TU. With the Kantronics, I could get on two meter packet and issue a "C calletter" command and connect to local digipeaters.

I haven't been able to successfully make it receive or transmit. I left it running for a while yesterday and it must have been really exercising the CPU because the thermometer popped up on the screen, so I killed Direwolf. It had a message in red, but I didn't capture it. Something about I should use the Linux command "top" to check CPU usage.

The Direwolf login text says something about: "gpsd hamlib cm108-ptt"  I would imagine that it should say something about the FT817, but doesn't.

So, do I have to enable something like Linpac so I can type commands to Direwolf and the radio packet tool?

Here is the config file, the Direwolf login screen text is at the bottom:
#############################################################
#                                                           #
#               Configuration file for Dire Wolf            #
#                                                           #
#                   Linux version                           #
#                                                           #
#############################################################
#
# Consult the User Guide for more details on configuration options.
#
#
# These are the most likely settings you might change:
#
# (1)    MYCALL -  call sign and SSID for your station.
#
# Look for lines starting with MYCALL and
# change NOCALL to your own.
#
# (2) PBEACON -  enable position beaconing.
#
# Look for lines starting with PBEACON and
# modify for your call, location, etc.
#
# (3) DIGIPEATER  -  configure digipeating rules.
#
# Look for lines starting with DIGIPEATER.
# Most people will probably use the given example.
# Just remove the "#" from the start of the line
# to enable it.
#
# (4) IGSERVER, IGLOGIN  - IGate server and login
#
# Configure an IGate client to relay messages between
# radio and internet servers.
#
#
# The default location is "direwolf.conf" in the current working directory.
# On Linux, the user's home directory will also be searched.
# An alternate configuration file location can be specified with the "-c" command line option.
#
# As you probably guessed by now, # indicates a comment line.
#
# Remove the # at the beginning of a line if you want to use a sample
# configuration that is currently commented out.
#
# Commands are a keyword followed by parameters.
#
# Command key words are case insensitive.  i.e. upper and lower case are equivalent.
#
# Command parameters are generally case sensitive.  i.e. upper and lower case are different.
#
#############################################################
#                                                           #
#               FIRST AUDIO DEVICE PROPERTIES               #
#               (Channel 0 + 1 if in stereo)                #
#                                                           #
#############################################################
#
# Many people will simply use the default sound device.
# Some might want to use an alternative device by choosing it here.
#
# Linux ALSA is complicated.  See User Guide for discussion.
# To use something other than the default, generally use plughw
# and a card number reported by "arecord -l" command.  Example:
 
ADEVICE  plughw:1,0
 
# Starting with version 1.0, you can also use "-" or "stdin" to
# pipe stdout from some other application such as a software defined
# radio.  You can also specify "UDP:" and an optional port for input.
# Something different must be specified for output.
 
# ADEVICE - plughw:1,0
# ADEVICE UDP:7355 default
#
# Number of audio channels for this soundcard:  1 or 2.
#
ACHANNELS 1
#ACHANNELS 2
 
#############################################################
#                                                           #
#               SECOND AUDIO DEVICE PROPERTIES              #
#               (Channel 2 + 3 if in stereo)                #
#                                                           #
#############################################################
 
#ADEVICE1  ...
 
#############################################################
#                                                           #
#               THIRD AUDIO DEVICE PROPERTIES               #
#               (Channel 4 + 5 if in stereo)                #
#                                                           #
#############################################################
 
#ADEVICE2  ...
 
#############################################################
#                                                           #
#               CHANNEL 0 PROPERTIES                        #
#                                                           #
#############################################################
 
CHANNEL 0
 
#
# The following MYCALL, MODEM, PTT, etc. configuration items
# apply to the most recent CHANNEL.
#
 
#
# Station identifier for this channel.
# Multiple channels can have the same or different names.
#
# It can be up to 6 letters and digits with an optional ssid.
# The APRS specification requires that it be upper case.
#
# Example (don't use this unless you are me):  MYCALL WB2OSZ-5
#
 
MYCALL K1YPP-5
 
#
# Pick a suitable modem speed based on your situation.
# 1200 Most common for VHF/UHF.  Default if not specified.
# 300 Low speed for HF SSB.
# 9600 High speed - Can't use Microphone and Speaker connections.
#
# In the simplest form, just specify the speed.
#
 
MODEM 1200
#MODEM 300
#MODEM 9600
 
#
# These are the defaults should be fine for most cases.  In special situations,
# you might want to specify different AFSK tones or the baseband mode which does
# not use AFSK.
#
#MODEM 1200 1200:2200
#MODEM 300  1600:1800
#MODEM 9600 0:0
#
#
# On HF SSB, you might want to use multiple demodulators on slightly different
# frequencies to compensate for stations off frequency.  Here we have 7 different
# demodulators at 30 Hz intervals.  This takes a lot of CPU power so you will
# probably need to reduce the audio sampling rate with the /n option.
 
#MODEM 300 1600:1800 7@30 /4
 
#
# Uncomment line below to enable the DTMF decoder for this channel.
#
 
#DTMF
 
#
# If not using a VOX circuit, the transmitter Push to Talk (PTT)
# control is usually wired to a serial port with a suitable interface circuit.
# DON'T connect it directly!
#
# For the PTT command, specify the device and either RTS or DTR.
# RTS or DTR may be preceded by "-" to invert the signal.
# Both can be used for interfaces that want them driven with opposite polarity.
#
# COM1 can be used instead of /dev/ttyS0, COM2 for /dev/ttyS1, and so on.
#
 
#PTT COM1 RTS
#PTT COM1 RTS -DTR
PTT RIG 1020 /dev/ttyUSB0
 
#
# On Linux, you can also use general purpose I/O pins if
# your system is configured for user access to them.
# This would apply mostly to microprocessor boards, not a regular PC.
# See separate Raspberry Pi document for more details.
# The number may be preceded by "-" to invert the signal.
#
 
#PTT GPIO 25
 
# The Data Carrier Detect (DCD) signal can be sent to the same places
# as the PTT signal.  This could be used to light up an LED like a normal TNC.
 
#DCD COM1 -DTR
#DCD GPIO 24
 
#############################################################
#                                                           #
#               CHANNEL 1 PROPERTIES                        #
#                                                           #
#############################################################
 
#CHANNEL 1
 
#
# Specify MYCALL, MODEM, PTT, etc. configuration items for
# CHANNEL 1.   Repeat for any other channels.
 
#############################################################
#                                                           #
#               TEXT TO SPEECH COMMAND FILE                 #
#                                                           #
#############################################################
 
#SPEECH dwespeak.sh
 
#############################################################
#                                                           #
#               VIRTUAL TNC SERVER PROPERTIES               #
#                                                           #
#############################################################
 
#
# Dire Wolf acts as a virtual TNC and can communicate with
# client applications by different protocols:
#
# - the "AGW TCPIP Socket Interface" - default port 8000
# - KISS protocol over TCP socket - default port 8001
# - KISS TNC via pseudo terminal   (-p command line option)
#
 
AGWPORT 8000
KISSPORT 8001
 
#
# It is sometimes possible to recover frames with a bad FCS.
# This applies to all channels.
#
# 0  [NONE] - Don't try to repair.
# 1  [SINGLE] - Attempt to fix single bit error.  (default)
# 2  [DOUBLE] - Also attempt to fix two adjacent bits.
# ... see User Guide for more values and in-depth discussion.
#
 
#FIX_BITS 0
 
#
#############################################################
#                                                           #
#               BEACONING PROPERTIES                        #
#                                                           #
#############################################################
 
#
# Beaconing is configured with these two commands:
#
# PBEACON - for a position report (usually yourself)
# OBEACON - for an object report (usually some other entity)
#
# Each has a series of keywords and values for options.
# See User Guide for details.
#
# Example:
#
# This results in a broadcast once every 10 minutes.
# Every half hour, it can travel via two digipeater hops.
# The others are kept local.
#
 
#PBEACON delay=1  every=30 overlay=S symbol="digi" lat=42^37.14N long=071^20.83W power=50 height=20 gain=4 comment="Chelmsford MA" via=WIDE1-1,WIDE2-1
#PBEACON delay=11 every=30 overlay=S symbol="digi" lat=42^37.14N long=071^20.83W power=50 height=20 gain=4 comment="Chelmsford MA"
#PBEACON delay=21 every=30 overlay=S symbol="digi" lat=42^37.14N long=071^20.83W power=50 height=20 gain=4 comment="Chelmsford MA"
 
# With UTM coordinates instead of latitude and longitude.
 
#PBEACON delay=1 every=10 overlay=S symbol="digi" zone=19T easting=307477 northing=4720178
 
#
# When the destination field is set to "SPEECH" the information part is
# converted to speech rather than transmitted as a data frame.
#
 
#CBEACON dest="SPEECH" info="Club meeting tonight at 7 pm."
 
# Similar for Morse code.  If SSID is specified, it is multiplied
# by 2 to get speed in words per minute (WPM).
 
#CBEACON dest="MORSE-6" info="de MYCALL"
 
#
# Modify for your particular situation before removing
# the # comment character from the beginning of appropriate lines above.
#
 
#############################################################
#                                                           #
#               DIGIPEATER PROPERTIES                       #
#                                                           #
#############################################################
 
#
# For most common situations, use something like this by removing
# the "#" from the beginning of the line below.
#
 
#DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
 
# See User Guide for more explanation of what this means and how
# it can be customized for your particular needs.
 
# Filtering can be used to limit was is digipeated.
# For example, only weather weather reports, received on channel 0,
# will be retransmitted on channel 1.
#
 
#FILTER 0 1 t/wn
 
#############################################################
#                                                           #
#               INTERNET GATEWAY                            #
#                                                           #
#############################################################
 
# First you need to specify the name of a Tier 2 server.
# The current preferred way is to use one of these regional rotate addresses:
 
# noam.aprs2.net - for North America
# soam.aprs2.net - for South America
# euro.aprs2.net - for Europe and Africa
# asia.aprs2.net - for Asia
# aunz.aprs2.net - for Oceania
 
#IGSERVER noam.aprs2.net
 
# You also need to specify your login name and passcode.
# Contact the author if you can't figure out how to generate the passcode.
 
#IGLOGIN WB2OSZ-5 123456
 
# That's all you need for a receive only IGate which relays
# messages from the local radio channel to the global servers.
 
# Some might want to send an IGate client position directly to a server
# without sending it over the air and relying on someone else to
# forward it to an IGate server.  This is done by using sendto=IG rather
# than a radio channel number. Overlay R for receive only, T for two way.
 
#PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=42^37.14N long=071^20.83W
#PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=T lat=42^37.14N long=071^20.83W
 
 
# To relay messages from the Internet to radio, you need to add
# one more option with the transmit channel number and a VIA path.
 
#IGTXVIA 0 WIDE1-1
 
# You might want to apply a filter for what packets will be obtained from the server.
# Read about filters here:  http://www.aprs-is.net/javaprsfilter.aspx
# Example, positions and objects within 50 km of my location:
 
#IGFILTER m/50
 
# That is known as a server-side filter.  It is processed by the IGate server.
# You can also apply local filtering to limit what will be transmitted on the
# RF side.  For example, transmit only "messages" on channel 0 and weather
# reports on channel 1.
 
#FILTER IG 0 t/m
#FILTER IG 1 t/wn
 
# Finally, we don't want to flood the radio channel.
# The IGate function will limit the number of packets transmitted
# during 1 minute and 5 minute intervals.   If a limit would
# be exceeded, the packet is dropped and message is displayed in red.
 
IGTXLIMIT 6 10
 
#############################################################
#                                                           #
#               APRStt GATEWAY                              #
#                                                           #
#############################################################
 
#
# Dire Wolf can receive DTMF (commonly known as Touch Tone)
# messages and convert them to packet objects.
#
# See separate "APRStt-Implementation-Notes" document for details.
#
 
#
# Sample gateway configuration based on:
#
# http://www.aprs.org/aprstt/aprstt-coding24.txt
# http://www.aprs.org/aprs-jamboree-2013.html
#
 
# Define specific points.
 
TTPOINT  B01  37^55.37N  81^7.86W
TTPOINT  B7495088  42.605237  -71.34456
TTPOINT  B934  42.605237  -71.34456
 
TTPOINT B901  42.661279  -71.364452
TTPOINT B902  42.660411  -71.364419
TTPOINT B903  42.659046  -71.364452
TTPOINT B904  42.657578  -71.364602
 
 
# For location at given bearing and distance from starting point.
 
TTVECTOR  B5bbbddd  37^55.37N  81^7.86W  0.01  mi
 
# For location specified by x, y coordinates.
 
TTGRID   Byyyxxx    37^50.00N  81^00.00W  37^59.99N  81^09.99W
 
# UTM location for Lowell-Dracut-Tyngsborough State Forest.
 
TTUTM  B6xxxyyy  19T  10  300000  4720000
 
# Location for the corral.
 
TTCORRAL   37^55.50N  81^7.00W  0^0.02N
 
# Compact messages - Fixed locations xx and object yyy where
#    Object numbers 100 - 199 = bicycle
# Object numbers 200 - 299 = fire truck
# Others = dog
 
TTMACRO  xx1yy  B9xx*AB166*AA2B4C5B3B0A1yy
TTMACRO  xx2yy  B9xx*AB170*AA3C4C7C3B0A2yy
TTMACRO  xxyyy  B9xx*AB180*AA3A6C4A0Ayyy
 
TTMACRO  z  Cz
 
# Receive on channel 0, Transmit object reports on channel 1 with optional via path.
# You probably want to put in a transmit delay on the APRStt channel so it
# it doesn't start sending a response before the user releases PTT.
# This is in 10 ms units so 100 means 1000 ms = 1 second.
 
#TTOBJ 0 1 WIDE1-1
#CHANNEL 0
#DWAIT 100
 
# Advertise gateway position with beacon.
 
# OBEACON DELAY=0:15 EVERY=10:00 VIA=WIDE1-1 OBJNAME=WB2OSZ-tt SYMBOL=APRStt LAT=42^37.14N LONG=71^20.83W COMMENT="APRStt Gateway"
 
# Sample speech responses.
# Default is Morse code "R" for received OK and "?" for all errors.
 
#TTERR  OK               SPEECH  Message Received.
#TTERR  D_MSG            SPEECH  D not implemented.
#TTERR  INTERNAL         SPEECH  Internal error.
#TTERR  MACRO_NOMATCH    SPEECH  No definition for digit sequence.
#TTERR  BAD_CHECKSUM     SPEECH  Bad checksum on call.
#TTERR  INVALID_CALL     SPEECH  Invalid callsign.
#TTERR  INVALID_OBJNAME  SPEECH  Invalid object name.
#TTERR  INVALID_SYMBOL   SPEECH  Invalid symbol.
#TTERR  INVALID_LOC      SPEECH  Invalid location.
#TTERR  NO_CALL          SPEECH  No call or object name.
#TTERR  SATSQ            SPEECH  Satellite square must be 4 digits.
#TTERR  SUFFIX_NO_CALL   SPEECH  Send full call before using suffix.

Here is the Direwolf login text:

Dire Wolf DEVELOPMENT version 1.6 G (Jun 18 2020)
Includes optional support for:  gpsd hamlib cm108-ptt
 
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:1,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
 
c
  

de K1YPP
 


Re: PiGate possible with TNC-Pi9k6 and BF HT?

Jeffry Isaacson <Jsisaacson@...>
 

Thanks Carlos and Mark for the good advice! I figured getting these HTs to work would be a near impossible challenge, but I had them laying around and thought it was worth trying (I’m a new Ham  and find packet radio, APRS, TNC kits, RPi-based radio incredibly fun). Out of curiosity, are there particular  2M radios you prefer for packet?

      Jeff KN6JSI


Re: PiGate possible with TNC-Pi9k6 and BF HT?

Mark Griffith
 

If you like being frustrated, keep trying.  :)  I don't know how many people have come to me to get these radios to work, and nearly all have given up and bought a better radio.

It *is* possible, but these radios just are not designed for digital and many times just won't work.  I have two that I have experimented with.  One works OK, the other just sometimes refuses to work for no reason.

As has been mentioned, turnoff everything in the menu system that can be turned off, and set everything that has a value to zero.  Then perhaps it will work.  Eventually you will buy a decent radio and the world of packet communications will open up to you.

Good luck!

Mark
KD0QYN


On Monday, July 13, 2020, 12:28:25 AM CDT, Jeffry Isaacson <jsisaacson@...> wrote:


I've built a PiGate following Mark Griffith's excellent instructions and thought I'd take a shot to see if a BF-F8HP was capable of connecting with local RMS stations. So far I am unable to connect (time out errors in the log file) though I hear packets being sent... Does it require particular TNC settings (ie transmit voltage) or radio settings? Or am I just being silly in trying with a cheap 8 W radio and a modest antenna?
     Thanks in advance,
       Jeff KN6JSI


Re: PiGate possible with TNC-Pi9k6 and BF HT?

N3RDR
 
Edited

Forgot to mention, make sure the beeps are off. Menu 8 and 39 on my radio. For the longest time mine did not work because one beep remained on (39). 

The other thing I ended up doing for all radios, keep the antenna away from the computer. I use a two band mag mount for my gobag. My HP laptop freezes when any 2m radio transmits close to it (BF or otherwise). Some users have reported similar issues with their Pis.


Carlos
N3RDR 


Re: PiGate possible with TNC-Pi9k6 and BF HT?

N3RDR
 

OMG. What a heated discussion your question can bring. There’s a group that feels those radios do not belong in the US, others feel that it can work with lots of effort, others have no issues with them. 


I use a Pigate with an UV-5RE+. Adjust de levels as recommended by the documentation, stick to 1200 baud. Keep the radio volume very low. I keep the volume at the first hint of being able to hear it. 

Carlos
N3RDR


PiGate possible with TNC-Pi9k6 and BF HT?

Jeffry Isaacson <Jsisaacson@...>
 

I've built a PiGate following Mark Griffith's excellent instructions and thought I'd take a shot to see if a BF-F8HP was capable of connecting with local RMS stations. So far I am unable to connect (time out errors in the log file) though I hear packets being sent... Does it require particular TNC settings (ie transmit voltage) or radio settings? Or am I just being silly in trying with a cheap 8 W radio and a modest antenna?
     Thanks in advance,
       Jeff KN6JSI


Re: Transmit message <...>0/zzzzzzzz in WSJT-x using W3DJS image window is too large for 7 inch screen

Dennis Blanchard
 

I've reinstalled the W3DJS HamPi V1.0 and the WSJT-x does now fit on the seven inch screen. I did adjust the framesize in the config.txt file by removing the "#" comment.

The problem I've run into in WSJT-x on V1.0 is the Hamlib database for the FT-817 does not recognize the CAT controller and won't key the transmitter. The work around is to use the Hamlib database for the FT-857, it does seem to work  okay. Is there a way to have WSJT-x use a FT817.xml file instead? That would be a work around. 

I've also installed Filezilla to transfer files between systems. That might be a handy addition to the W3DJS package in the future.

Oh, perhaps Dave should have considered calling the latest version, V3.0, instead of V1.0. This would have brought folks to the latest version without confusion, since it was actually a name change that might go unnoticed. Just a thought.

73, de K1YPP


Re: Conky missing from build-a-pi v3

dkc2030@...
 

I have built 4 systems from the BAP V3 and updated two of the BAP scripts to 3.0.2 and it all works.  Here is what I am doing:  I run all my PIs as headless using VNC to connect to them.  Out of the box the screen resolution needs to be changed in the following manner:
1.  run sudo raspi-config and select Advanced and screen resolution.  Set it to the highest (1920x1080).  You are not done yet.
2.  If you have a rpi4b you have to bring up the desktop and select Preferences and then Screen Resolution .. Configure >> Screens >> HDMI-1 >> Resolution and then set it to 1920x1080
3.  Still not done.  Do a Configure .. Apply to make it stick.
4.  Conky is very sensitive to failing if it doesn't see what it expects to happen.

Conky won't show up on a 7" monitor, it is off the screen to the right.


Re: Help with TNC-Pi9k6 serial0 in YAAC

John G8BPQ
 

The drive level from TNC to radio is set by setting the TX Level value using pitnc_setparams.

Assuming you are using the 6 pin DIN connector on the 7100 the manual suggests 100mV for 1200 or 0.2 to 0.5 V p-p for 9600. I assume 100mV is the rms value. The peak to peak output from the TNC is approximately 3000/256 times the TX Level setting so a value of around 25 should be about right. There are also level settings in the 7100.

If you are running at 1200 you will probably be best off with the TNC jumper set to 1200 and 9600 mode in the 7100 turned off.

73,
John G8BPQ

On 12/07/2020 07:59, richard.overman@... wrote:
It's at 19200.  I'm using the HamPi image now, and after disabling SSH serial, I can talk to the TNC-pi9k6 and I believe I'm transmitting something based on looking at the signal with an RTL-SDR.  One thing that is odd, is that there is no change in either the pulse of the ammeter on the radio power supply or how the waterfall looks no matter what I set the transmit power to on the IC-7100.  I set it at both extremes of low and high power and it looks like the same power level.  I switched the jumper from 1200 to 9600 and I get a much flatter line, so it looks like I'm transmitting something, just maybe not enough power?  Does the TNC control transmit power through the radio?  Also, I am not using GPS (arrives tomorrow), so I have manually entered in my coordinates.  Thanks for all the help!  HamPi is awesome!

73'
KJ7DDV


Re: Help with TNC-Pi9k6 serial0 in YAAC

richard.overman@...
 

It's at 19200.  I'm using the HamPi image now, and after disabling SSH serial, I can talk to the TNC-pi9k6 and I believe I'm transmitting something based on looking at the signal with an RTL-SDR.  One thing that is odd, is that there is no change in either the pulse of the ammeter on the radio power supply or how the waterfall looks no matter what I set the transmit power to on the IC-7100.  I set it at both extremes of low and high power and it looks like the same power level.  I switched the jumper from 1200 to 9600 and I get a much flatter line, so it looks like I'm transmitting something, just maybe not enough power?  Does the TNC control transmit power through the radio?  Also, I am not using GPS (arrives tomorrow), so I have manually entered in my coordinates.  Thanks for all the help!  HamPi is awesome!

73'
KJ7DDV


Re: Transmit message <...>0/zzzzzzzz in WSJT-x using W3DJS image window is too large for 7 inch screen

John Nicholas
 

The Video was Friday June 12  Episode 294 of Ask Dave

I caught it Friday the 19th.  That encouraged me to buy my first Raspberry Pi.

73

de  KE0ZUW

On Jul 11, 2020, at 6:17 PM, Dennis Blanchard via groups.io <k1ypp@...> wrote:

I came to the HamPi game late. I saw a video a week or two ago that talked about it, don't recall the fellow's call, something with 'OG' in it.


Re: Help with TNC-Pi9k6 serial0 in YAAC

Mat Murdock
 

What baud rate have you set YAAC to, to communicate with the tnc?   Should be 19200.

Mat

On Sat, Jul 11, 2020, 3:08 PM N5XMT <dacooley@...> wrote:
Looking in your getparams output, your txlevel was only 4.  I'd set it to 255

On Sat, Jul 11, 2020 at 12:41 PM <richard.overman@...> wrote:
Hi there, thanks for the reply.  That gives me:

lrwxrwxrwx   1 root root          5 Jul 11 11:33 serial0 -> ttyS0
lrwxrwxrwx   1 root root          5 Jul 11 11:33 serial0 -> ttyS0

So it looks like ttyS0 is serial0.  Cool.  I can even use getparams on ttyS0 and it gives me the same list of parameters.

I tried using ttyS0 in YAAC and still I get a blank screen when I press "test"  and still can't see my beacon on the APRS map.

Cheers,
Richard


Re: Help with TNC-Pi9k6 serial0 in YAAC

Bill WA4OPQ
 

I used YAAC with the Pi9k6 some time ago. I never had any luck with the test window.


Re: Conky missing from build-a-pi v3

Gary
 

Ron,
Make sure you have the latest version of Build-a-Pi, which is 3.0.2.   Also you can get direct support by joining the group [KM4ACK-Pi]
--
=Gary AK2QJ


On Mon, Jun 29, 2020 at 7:56 AM Ron Liekens <r.e.liekens@...> wrote:
Seems Conky is missing in the build-a-Pi v3 edition. Also the new WSJT-X v2.2.2 does no longer perform CAT connection with the Yaesu FT-817. For the moment I'm using Flrig as the interface to get things done.

best regards,
Ron - on2ron


Re: SDRpi

Bryan Corkran, VK3KEZ
 

Tried it on pi4 .
HamPi has most of the same software including Gpredict.
I’ll stick with that 


Re: Transmit message <...>0/zzzzzzzz in WSJT-x using W3DJS image window is too large for 7 inch screen

Dennis Blanchard
 

I don't recall, but I think I forgot to include the link to the V1.0: https://forums.qrz.com/index.php?threads/hampi-1-0-released.711515/

Dennis, K1YPP


Re: Transmit message <...>0/zzzzzzzz in WSJT-x using W3DJS image window is too large for 7 inch screen

Dennis Blanchard
 

I came to the HamPi game late. I saw a video a week or two ago that talked about it, don't recall the fellow's call, something with 'OG' in it.I didn't realize that I came in at the middle of something that W3DJS was doing and didn't catch the name change. I still have the V1.0 image that I had initially used, I can put it back on. I should have paid more attention, instead of running off half-cocked and not paying attention to detail. My bad.

I think this announcement page covers things and gives links to the latest. Sorry for all the bother for everyone. Incidentally, the V1.0 did actually size properly on the 7 inch screen. I had to fiddle with a few things, but did get it to work properly.

See you all down the waterfall on on CW somewhere...

Dennis, K1YPP


Re: Help with TNC-Pi9k6 serial0 in YAAC

richard.overman@...
 

So far I've tried TX levels of 4, 255, and 128.  Still nothing.  Am I supposed to get something other than a blank window when I push "test" on the port tab?


Re: Help with TNC-Pi9k6 serial0 in YAAC

Mark Griffith
 

A TX level of 255 will put 3 volts peak to peak on that line.  That is pretty high and that will probably overdrive his radio. 

Mark
KD0QYN


On Saturday, July 11, 2020, 4:08:41 PM CDT, N5XMT <dacooley@...> wrote:


Looking in your getparams output, your txlevel was only 4.  I'd set it to 255

On Sat, Jul 11, 2020 at 12:41 PM <richard.overman@...> wrote:
Hi there, thanks for the reply.  That gives me:

lrwxrwxrwx   1 root root          5 Jul 11 11:33 serial0 -> ttyS0
lrwxrwxrwx   1 root root          5 Jul 11 11:33 serial0 -> ttyS0

So it looks like ttyS0 is serial0.  Cool.  I can even use getparams on ttyS0 and it gives me the same list of parameters.

I tried using ttyS0 in YAAC and still I get a blank screen when I press "test"  and still can't see my beacon on the APRS map.

Cheers,
Richard


Re: Help with TNC-Pi9k6 serial0 in YAAC

richard.overman@...
 

OK tried setting the TX to 255, still getting a blank window when I test the port.

1861 - 1880 of 13781