Date   

Re: Fldigi on Pi4 after update and upgrade

DavidC KD4E
 

You might try linuxham@groups.io for RPi 4 fldigi support.

If not there - they'll direct you to a more helpful group.

KD4E


Re: Fldigi TX off freq on waterfall on only 20m

Mark Griffith
 

You don't say which mode.  FT8? PSK?

Mark 
KD0QYN 



On Thu, Aug 27, 2020 at 4:29 PM, Walter
<W9KJO@...> wrote:
OK so here is a problem I have had for a long while.

When I use Fldigi on my TS-2000 and the Pi4B setup When I TX the signal is low by about 500 hz.  But this is only the case on 20m.  on 80m and 40m it is off by only a few Hz.  But on receive it is dead on, 

How do I calibrate for 20m without affecting the other bands?  So far in the settings it appears to be a universal adjustment only.  Is there another answer?

Thanks everyone.

--
In Christ, Until He Come, Perhaps Today . . .
73
Walter Huyck
W9KJO


Fldigi TX off freq on waterfall on only 20m

Walter
 

OK so here is a problem I have had for a long while.

When I use Fldigi on my TS-2000 and the Pi4B setup When I TX the signal is low by about 500 hz.  But this is only the case on 20m.  on 80m and 40m it is off by only a few Hz.  But on receive it is dead on, 

How do I calibrate for 20m without affecting the other bands?  So far in the settings it appears to be a universal adjustment only.  Is there another answer?

Thanks everyone.

--
In Christ, Until He Come, Perhaps Today . . .
73
Walter Huyck
W9KJO


Re: Fldigi on Pi4 after update and upgrade

Walter
 

I realized about 30 minutes ago that I did make a backup SD card of my working image a year ago and have the image also saved on my PC hard drive.  Put the old image back in and the problem is now gone, at least so far.

Now I'm hesitant to upgrade to the latest FLDIGI.  This image is 4.1.08.

At least I back to a stable ad reliable transmit.
--
In Christ, Until He Come, Perhaps Today . . .
73
Walter Huyck
W9KJO


Re: Configuring W3DJS V1.0 Direwolf questions.

David Ranch
 


Hello Dennis,


pi@raspberrypi:~ $ rigctl -m 1020 -r /dev/ttyUSB0 -s 4800 -P RIG t
0
and
I played with the rigctl stuff and was able to read the rig's frequency and make changes, so it seems to be communicating over the cable. Of course that was the case with Fldigi, so no surprise there. All I can think of is somehow Direwolf is having a permission problem. Either that, or some sort of group membership problem.

Ok.. I think you highlighted the issue here... "-s 4800"!   In your first post in this thread, you stated your direwolf.conf has:
--
PTT RIG 1020 /dev/ttyUSB0
--


Notice you're not specifying a speed here as well as the fact that you CANNOT tell Direwolf what speed to use.  Looking at the current Hamlib 3.3 stable release (uses RIG 120), the default speed for a Yaesu 817 is:
--
./rigctl -m 120 -L

. . .
serial_speed: "Serial port baud rate"
        Default: 0, Value: 38400
        Range: 300.0..115200.0, step 1.0
--

Hamlib defaults to 0 bps?!  That doesn't see right.  Will your above "rigctl" tests work without specifying the "-s 4800" parameter (which is the Yaesu FT817's default speed)?  If not, that seems like a bug in Hamlib and this also highlights that Direwolf should be able to support any required Hamlib parameters.

--David
KI6ZHD


Re: Fldigi on Pi4 after update and upgrade

Mark Griffith
 

Unfortunately, you have been caught by the process of doing an Linux update/upgrade.  This is a problem with open-sourced software in that you don't know what changes are made to what software packages during an upgrade.  It's also unfortunate that going back to a configuration from before the upgrade is very difficult to do, if possible at all.

This is the reason why you should take a backup image of your SD card before doing an upgrade.  Sorry, I know this doesn't help you now.

You best options would be either download the development source code for FLDIGI, compile that, and see if it fixes your problem, or re-install the previous version of Raspbian and FLDIGI and see if you can get it working there.  If that works, do some updates/upgrades with caution.  Make sure to do regular backups of the entire OS image onto a disk file.

Using the packages that can be installed via the apt-get process will not give you the very latest application software, but it has been tested with the existing versions of Raspbian.

And let me express again the absolute necessity of doing backups before you install any software updates or upgrades to prevent painting yourself into a corner.  This is especially important with Linux but still also applies to Windows.

Mark
KD0QYN


On Thursday, August 27, 2020, 7:26:06 AM CDT, Walter <w9kjo@...> wrote:


Thought I had this correct by rolling back but not so.

About have the time when I click on the macro, the text appears in the Send window and as it sends the TXID the send window will clear all on its own and Fldigi will send a plain carrier.  this is in Contestia 4/150.

I dont see a group for Fldigi on the Pi4 just for windows.  is there a better group to post on Fldigi on the Pi4?

--
In Christ, Until He Come, Perhaps Today . . .
73
Walter Huyck
W9KJO


Re: Fldigi on Pi4 after update and upgrade

Walter
 

Thought I had this correct by rolling back but not so.

About have the time when I click on the macro, the text appears in the Send window and as it sends the TXID the send window will clear all on its own and Fldigi will send a plain carrier.  this is in Contestia 4/150.

I dont see a group for Fldigi on the Pi4 just for windows.  is there a better group to post on Fldigi on the Pi4?

--
In Christ, Until He Come, Perhaps Today . . .
73
Walter Huyck
W9KJO


Re: Configuring W3DJS V1.0 Direwolf questions.

Dennis Blanchard
 

Here are some results David. Sorry it takes so long, I've been doing a lot of care taking for family and haven't had much free time.

pi@raspberrypi:~ $ 
pi@raspberrypi:~ $ rigctl -m 1020 -r /dev/ttyUSB0 -s 4800 -P RIG t
0
pi@raspberrypi:~ $ ls -la /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 Aug 26 16:24 /dev/ttyUSB0
pi@raspberrypi:~ $ 

At the moment the system is stand alone. Once I get all this figured out, I'll burn a bigger SD card and do it all over again, so I'm just using the root account.
I played with the rigctl stuff and was able to read the rig's frequency and make changes, so it seems to be communicating over the cable. Of course that was the case with Fldigi, so no surprise there. All I can think of is somehow Direwolf is having a permission problem. Either that, or some sort of group membership problem.

Thanks...

Dennis, K1YPP


Re: Fldigi on Pi4 after update and upgrade

Walter
 

I corrected this problem by rolling back to Fldigi version 4.1.12  It works perfectly.  There is a problem in Fldigi 4.1.14 on the Pi4B.  Once it is corrected I will try running it again.
--
In Christ, Until He Come, Perhaps Today . . .
73
Walter Huyck
W9KJO


Fldigi on Pi4 after update and upgrade

Walter
 

I am running flidigi 4.1.14, flamp 2.2.04, Flrig 1.3.51 on my Pi4B with TS 2000

I has been a while since I did an update and upgrade on my Pi4 so i did that last night.  Now when I hit my Macro it begins to TX and as it starts to send the text inserted in the TX window by the macro disappears and the software just keys the rig and sends the fldigi 4/250 carrier but the text quickly disappeared.

There does not appear to be anything in the macro to cause this behavior.

I tried typing text in the TX window and when I right click and hit transmit the text disappears as soon as Fldigi starts to TX.

What would cause this strange behavior?

--
In Christ, Until He Come, Perhaps Today . . .
73
Walter Huyck
W9KJO


Re: fldigi on raspberry pi 3 B +

David Ranch
 


This user is using a Signalink therefore there is no rig control nor any dedicated PTT signalling required.  Because of this, there is no need to discuss "dialout" group permissions.

--David
KI6ZHD


On 08/26/2020 08:34 AM, jcusick wrote:
The first step is definitely make sure the user running fldigi is in the dialout group. After that, troubleshoot as needed.





Re: fldigi on raspberry pi 3 B +

jcusick
 

The first step is definitely make sure the user running fldigi is in the dialout group. After that, troubleshoot as needed.


Re: fldigi on raspberry pi 3 B +

David Ranch
 


This thread is rather confusing as Charle's original issue was about his Signalink not keying up the radio and other people chimed in with different setups which muddied the waters.   Signalink's don't offer any rig control and don't use serial ports like /dev/ttyS0.

For Signalink sound devices, the device's ability to key up the radio is based on the application using the correct sound device and the audio levels being strong enough to have the Signalink auto-assert the PTT LED on the little box.

--David
KI6ZHD


On 08/25/2020 07:22 AM, Charles Albert wrote:
The radio is an ICOM IC737, Signalink sound card, running fldigi on the pi 3B+, shows /dev/ttyS0, perhaps /dev/ttyS0 neds to change?


Re: fldigi on raspberry pi 3 B +

Charles Albert
 

The radio is an ICOM IC737, Signalink sound card, running fldigi on the pi 3B+, shows /dev/ttyS0, perhaps /dev/ttyS0 neds to change?


Re: Configuring W3DJS V1.0 Direwolf questions.

David Ranch
 


Hello Dennis,

Dire Wolf DEVELOPMENT version 1.6 G (Jun 18 2020)
Includes optional support for:  gpsd hamlib cm108-ptt

Ok.. perfect.. looks good.


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 ...

Ok.. also looks good


Attached to AGW client application 0...
Ready to accept AGW client application 1 on port 8000 ...
Hamlib Error: rig_set_ptt command for channel 0 PTT
Communication timed out

Ok, I recommend to try some specific testing outside of Direwolf first.  For example, try reading the state of your radio's PTT.  Here is the command I use for my FT950 with an older version of Hamlib:

  rigctl -m 128 -r /dev/USI_CAT -s 38400 -P RIG t

I get a result of "0" meaning PTT is not asserted.  If you substitute in your proper rig number, serial port device, and serial port speed, does that command work for you?  It *must*.


Next up, what is the permissions of your serial port?  Run the following command:

   ls -la /dev/ttyUSB0


In Fldigi I use the Rigcat or Hamlib configs, either works. They use /dev/ttyUSB0 device, which is the Yaesu CAT-62 cable.

Ok.. you previously also mentioned Flrig works which is also it's own type of rig control. 


I was aware that Direwolf uses it's own hamlib. If I do a list of rigs (rigctl --list):
 
  1020  Yaesu    FT-817            20200616.0      Stable      RIG_MODEL_FT817
  1021  Yaesu    FT-100            20200323.0      Beta        RIG_MODEL_FT100
  1022  Yaesu    FT-857            20200323.0      Stable      RIG_MODEL_FT857
  1023  Yaesu    FT-897            20200607.0      Stable      RIG_MODEL_FT897

It's not that Direwolf uses it's own Hamlib, it just uses libraries to communicate to whatever hamlib you have installed.  WSJT-X is different as it brings in it's own special copy of Hamlib which is localized for WSJTX only.

--David
KI6ZHD


Re: fldigi on raspberry pi 3 B +

VK2AHB
 

I was having problems with Pat Menu, getting error trying to connect to 127.0.0.1, so I did that.
sudo usermod -G dialout pi

The next time I tried to connect with VNC, I got 'Access is denied'.

Paul VK2AHB


Re: Dragon w/IC-7100 Icom Packet/ARDOP/Packet

John G8BPQ
 

Jim,

It would be better to ask questions about BPQ on the BPQ32 groups.io forum.

Normally with the Dragon 7800 VHF packet would be on a separate radio and
would not normally involve scanning as VHF packet is generally allows
multiple connects.

You can run packet and pactor on the same port, but normally this would be
on hf and the Dragon only supports Robust Packet, not normal 300 baud
packet. In this (Robust Packet) mode scanning is stopped when a user
connects. It may be possible to configure so that BPQ thinks you are using
Robust Packet even with the TNC set to 1200 baud. If you send me the SCS
port section of your bpq32.cfg I'll see if I can find a way to do this. If
not it will probably need a code change. I do have a 7100 and a Dragon but
am currently away from home so can't test it myself.

73,
John G8BPQ

-----Original Message-----
From: RaspberryPi-4-HamRadio@groups.io
[mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of Jim Hudson via
groups.io
Sent: 24 August 2020 05:14
To: RaspberryPi-4-HamRadio@groups.io
Subject: [RaspberryPi-4-HamRadio] Dragon w/IC-7100 Icom Packet/ARDOP/Packet

I'm working on a SCS-7800 Dragon. The OS is Raspi-OS on a PI 3B+, latest
BPQ(20.1) connected to a IC-7100 Icom.

PacTor, ARDOP, and packet; all connect and send receive traffic to
CMS(gateway).

Scan starts and stops on PacTor and ARDOP ports. The packet port on the
Dragon does not stop the scan.

I've been thru the doc's and don't see any reference to packet on the Dragon
except for Channels and TXD.

I set RIGCONTROL to a long delay(15 sec) on the packet channel(VHF) and
short scan time on the HF ports(3 sec).

When a connect comes in on packet, how do I tell BPQ to stop on freq till
the packet connection is done.

Should I use the same port on the Dragon for Packet and PacTor? The 13 pin
on the Dragon is wired to the ACC port on the radio and the main audio on
the Dragon goes to the mini din on the radio. Everything works except scan
stop on packet.

Thanks in advanced for any help.

Jim WB9QPM


Re: Configuring W3DJS V1.0 Direwolf questions.

Dennis Blanchard
 

Thanks for jumping in to help David. Here are some data dumps from the RPI:
Direwolf startup dialog:
 
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 ...
 
Attached to AGW client application 0...
 
Ready to accept AGW client application 1 on port 8000 ...
Hamlib Error: rig_set_ptt command for channel 0 PTT
Communication timed out
[0L] K1YPP>APJYC1,WIDE1-1,WIDE2-1:=2726.00N/08251.06W# K1YPP testing  station<0x0d>
Hamlib Error: rig_set_ptt command for channel 0 PTT
Communication timed out
 
 
Yes, I had already set up: sudo usermod -G dialout k1ypp
 
The only error message I see is the one I originally posted.
 
In Fldigi I use the Rigcat or Hamlib configs, either works. They use /dev/ttyUSB0 device, which is the Yaesu CAT-62 cable.
 
I was aware that Direwolf uses it's own hamlib. If I do a list of rigs (rigctl --list):
 
  1020  Yaesu    FT-817            20200616.0      Stable      RIG_MODEL_FT817
  1021  Yaesu    FT-100            20200323.0      Beta        RIG_MODEL_FT100
  1022  Yaesu    FT-857            20200323.0      Stable      RIG_MODEL_FT857
  1023  Yaesu    FT-897            20200607.0      Stable      RIG_MODEL_FT897
 
 
W3DJL builds the whole ham package into one .iso build and I burned an SD card with it. It is built with hamlib, WSJT-X, Fligi, etc. I haven't been able to figure out exactly where it keeps the hamlib data. Somehow, it must not be using the hamlib data correctly, but I don't understand how.

Anyway, I'll keep trying. I can't believe that I am the only one that has run into this.

Dennis, K1YPP


Re: TNC-96K with HT

Mark Griffith
 

Martin,

There are a number of people that use the PiGate with an HT.  The problem with yours is the very low input level of 5mv.  The TNC-Pi9k6 can only be set to 24mv at it's lowest setting.

The manual for your HT shows you how to make a cable including a 2K ohm load and capacitor. You should try that and set the TX level to as low as you can and see what happens.

HT's are not the best radios for packet.  Unless you are very close to the station you are trying to link to, the poor antennas, noise sensitivity, and a host of other factors will make it more difficult than using a good mobile radio with a dedicated packet port on the back.  But you can experiment with this stuff and find out for yourself.

Mark
KD0QYN


On Monday, August 24, 2020, 12:54:43 PM CDT, <martissinio@...> wrote:


Has anyone tried/succeeded using a TNC-96K with an HT? Or thoughts/ideas how to do so?
I'm hoping to be able to deploy the PiGate with HT as an ultra-portable, low-power-use ARES/EmComm solution.
I can use Winlink via my Yaesu FT60R with a SignaLink, but the TNC-96K defies me. According to the manual, the FT60R wants 5mV at 2k Ohm from the TNC as input.

73,
Martin


Re: Welcome to RaspberryPi-4-HamRadio@groups.io

Chris Maness
 

Hello all. Thanks for starting this group. I have been tinkering
with the Pi using WSJT-X, ARDOP and soundcard AX.25 packet with JNOS.
It has been a lot of fun.

Regards,
Chirs KQ6UP

1181 - 1200 of 13257