Date   
Re: Fldigi receiving but wont key radio

Larry Levesque
 

Add yourself to DIALOUT group and log out and back in.

On Sun, Jan 19, 2020 at 12:06:49PM -0800, Romeo Hotel One Two wrote:
Ok, back around Thanksgiving I got the bright idea that I was going to replace the standard hard drive in my Panasonic CF-19 Toughbook with a 1TB SSD.  At the same time I upgraded Mint 18.something to Mint 19.3 as the OS.  Reloaded Fldigi, Flamp, Flmsg, Flrig, and flwrap among other things.

A few weeks ago I was participating in a net and when I tried to report needed block fills from Flamp, the software said it was transmitting but it wasn't keying the radio.  This is the first I have been back on the radio since the upgrade.  I've tried everything I could think of but I am coming up blank.

Can anyone help?  Luckily I have the old HD and can boot from it if I need to get on the air its just a pain in the tail and requires me to have extra equipment on hand.

Thanks,
Romeo Hotel-12


--
Larry Levesque
KA1VGM

Fldigi receiving but wont key radio

Romeo Hotel One Two
 

Ok, back around Thanksgiving I got the bright idea that I was going to replace the standard hard drive in my Panasonic CF-19 Toughbook with a 1TB SSD.  At the same time I upgraded Mint 18.something to Mint 19.3 as the OS.  Reloaded Fldigi, Flamp, Flmsg, Flrig, and flwrap among other things.

A few weeks ago I was participating in a net and when I tried to report needed block fills from Flamp, the software said it was transmitting but it wasn't keying the radio.  This is the first I have been back on the radio since the upgrade.  I've tried everything I could think of but I am coming up blank. 

Can anyone help?  Luckily I have the old HD and can boot from it if I need to get on the air its just a pain in the tail and requires me to have extra equipment on hand.


Thanks,
Romeo Hotel-12

Re: Fldigi install errors

Keith Kaiser
 

I just tried that entry all I get is "Invalid operation build-deps".

Re: Fldigi install errors

Keith Kaiser
 

I followed the instructions but don't remember seeing a "apt-get build-deps fldigi" anywhere.

Re: Fldigi install errors

Ed W3NR
 

On 1/16/20 11:04 PM, Keith Kaiser wrote:
Below is my latest attempt to install fldigi on a Raspberry Pi running a new copy of Buster. This is not an upgrade this is an initial install. Anyone have an idea what is causing this issue?



Making all in po
make[1]: Entering directory '/home/pi/fldigi-4.1.09/po'
make[1]: Leaving directory '/home/pi/fldigi-4.1.09/po'
Making all in doc
make[1]: Entering directory '/home/pi/fldigi-4.1.09/doc'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/pi/fldigi-4.1.09/doc'
Making all in src
make[1]: Entering directory '/home/pi/fldigi-4.1.09/src'
make  all-recursive
make[2]: Entering directory '/home/pi/fldigi-4.1.09/src'
make[3]: Entering directory '/home/pi/fldigi-4.1.09/src'
  CXX      network/fldigi-xmlrpc.o
In file included from /usr/include/c++/8/map:60,
                 from ./xmlrpcpp/XmlRpcServer.h:25,
                 from ./include/xmlrpc.h:27,
                 from network/xmlrpc.cxx:33:

.... lots of stuff here ….

CXX      dialogs/fldigi-confdialog.o
{standard input}: Assembler messages:
{standard input}:178943: Warning: end of file not at end of a line; newline ins$
{standard input}:180263: Warning: missing operand; zero assumed
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc dire$
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[3]: *** [Makefile:5396: dialogs/fldigi-confdialog.o] Error 1
make[3]: Leaving directory '/home/pi/fldigi-4.1.09/src'
make[2]: *** [Makefile:8106: all-recursive] Error 1
make[2]: Leaving directory '/home/pi/fldigi-4.1.09/src'
make[1]: *** [Makefile:1667: all] Error 2
make[1]: Leaving directory '/home/pi/fldigi-4.1.09/src'
make: *** [Makefile:469: all-recursive] Error 1


Keith, WA0̷TJT


Did you run apt-get build-deps fldigi ?

Ed W3NR

Fldigi install errors

Keith Kaiser
 

Below is my latest attempt to install fldigi on a Raspberry Pi running a new copy of Buster. This is not an upgrade this is an initial install. Anyone have an idea what is causing this issue?



pi@D-KKloud:~/fldigi-4.1.09 $ make
Making all in po
make[1]: Entering directory '/home/pi/fldigi-4.1.09/po'
make[1]: Leaving directory '/home/pi/fldigi-4.1.09/po'
Making all in doc
make[1]: Entering directory '/home/pi/fldigi-4.1.09/doc'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/pi/fldigi-4.1.09/doc'
Making all in src
make[1]: Entering directory '/home/pi/fldigi-4.1.09/src'
make  all-recursive
make[2]: Entering directory '/home/pi/fldigi-4.1.09/src'
make[3]: Entering directory '/home/pi/fldigi-4.1.09/src'
  CXX      network/fldigi-xmlrpc.o
In file included from /usr/include/c++/8/map:60,
                 from ./xmlrpcpp/XmlRpcServer.h:25,
                 from ./include/xmlrpc.h:27,
                 from network/xmlrpc.cxx:33:

.... lots of stuff here ….

CXX      dialogs/fldigi-confdialog.o
{standard input}: Assembler messages:
{standard input}:178943: Warning: end of file not at end of a line; newline ins$
{standard input}:180263: Warning: missing operand; zero assumed
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc dire$
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[3]: *** [Makefile:5396: dialogs/fldigi-confdialog.o] Error 1
make[3]: Leaving directory '/home/pi/fldigi-4.1.09/src'
make[2]: *** [Makefile:8106: all-recursive] Error 1
make[2]: Leaving directory '/home/pi/fldigi-4.1.09/src'
make[1]: *** [Makefile:1667: all] Error 2
make[1]: Leaving directory '/home/pi/fldigi-4.1.09/src'
make: *** [Makefile:469: all-recursive] Error 1
pi@D-KKloud:~/fldigi-4.1.09 $


Keith, WA0̷TJT



Enhancement to fldigi's FSQ heard list

Keith Kaiser
 

Let me start by saying I’m not a big fan of FSQ. But one feature I appreciate a lot is the heard list and its functionality. And for the past several weeks at the end of my various FSQ nets I take a screenshot of it and store it for comparison, week to week. Would it be possible to build in a by-net logger for the heard list, keeping track of each change as the net progress? Stored by date and time or even just run together in a text file would work. I would like to see the call, time stamp and db, and record each change as well. This would give me the ability to study the propagation over time.
Or is all this possible already and I just haven’t found it?

Keith, WA0̷TJT



Re: FSK testers wanted

Andreja YU1NKA/DM1NKA
 

Hi! I have an IC-7300, and an IC-9700, both of which have FSK keying over RTS/DTR, and I have capability to record keyed signals, either as audio or as I/Q.

73 from Andreja YU1NKA/DM1NKA

чет, 16. јан 2020. у 16:46 Dave <w1hkj@...> је написао/ла:

I need users who are willing to test transceiver FSK keying via serial port (DTR or RTS).  You should have some way to copy the generated FSK signal on a separate transceiver, or using a buddy system.  If you are interested please reply in the affirmative and I will add you to the email list of FSK testers.

73, David, W1HKJ


FSK testers wanted

Dave
 

I need users who are willing to test transceiver FSK keying via serial port (DTR or RTS).  You should have some way to copy the generated FSK signal on a separate transceiver, or using a buddy system.  If you are interested please reply in the affirmative and I will add you to the email list of FSK testers.

73, David, W1HKJ


Re: Why Flrig?

KG7D Greg
 
Edited

Thank you all for your input.
It definitely got much simpler to integrate software once everyone started including an option to connect by IP address (Loop back I think its called in this case).

Greg - KG7D

Re: Why Flrig?

Jim
 

Once you have Flrig running you can launch WSJT-x and select Flrig from the radio list. You’ll then need to tell WSJT-x where Flrig is on your network (use the loopback address, on my Linux box that 127.0.0.1:12345) .. test your CAT, test your PTT.. and you’re off to the races.

Why use Flrig in this scenario? Flrig allows you to have share control of the radio (and potentially your rotor) with multiple applications. It streamlines your entire configuration and control environment.

On Jan 14, 2020, at 00:49, Paul W1PJS <@w1pjs> wrote:

How does one interface WSJT-X with Flrig? I cant see a way to do that (at least not an obvious way)

73,

Paul Silverzweig, W1PJS


--
Paul, W1PJS
RI SEC
Red Cross Disaster Tech Manager
AF MARS
FEMA ComL


Re: Why Flrig?

BruceN
 

I don't necessarily use Flrig for two reasons: 1.  It does NOT contain all the commands needed for all radios.  If the radio isn't "built in", you have to use a substitute rig and hope it doesn't have a command that messes up your radio.  True, too, for home built rigs where you may run custom rig controls.  2.  I quit using Flrig when it kept erasing my saved memory locations.  NOT in the radio itself.  But if I built a list of memories in the program then exited FLrig, that list disappeared and I'd have to create it again.  A PITA.  Other than that, it can be a handy program.

BruceN, K4TQL

Re: Why Flrig?

Paul W1PJS
 

How does one interface WSJT-X with Flrig? I cant see a way to do that (at least not an obvious way)

73,

Paul Silverzweig, W1PJS


--
Paul, W1PJS
RI SEC
Red Cross Disaster Tech Manager
AF MARS
FEMA ComL

Re: Why Flrig?

NU3Q
 

On Jan 13, 2020, at 5:56 PM, Ralph Alden Brigham <ralph.alden.brigham@...> wrote:

    Greetings,

   I also have an IC-7100 - but flrig will not, repeat will not work with my rig
at all.  But rigCAT works just fine.

-- ***** ---
Ralph Brigham KG4CSQ -- EM64RQ2OOQ
W5YI VE  33080;  ARRL VE
ARRL #1000033463
ARES/RACES SKYWARN
(931) 906-9277
-- ****





Re: Why Flrig?

Ralph Alden Brigham
 

Greetings,

I also have an IC-7100 - but flrig will not, repeat will not work with my rig
at all. But rigCAT works just fine.

-- ***** ---
Ralph Brigham KG4CSQ -- EM64RQ2OOQ
W5YI VE 33080; ARRL VE
ARRL #1000033463
ARES/RACES SKYWARN
(931) 906-9277
-- ****

Re: Why Flrig?

Pat
 

i also use flrig.. and have more controls for the radio.
rf gain, af gain, NB, etc
I can run two digi programs at the sam time.
WSJT and FLDIGI with flrig.
Murf
n7uvh

fldigi 4.1.09.02 posted

Dave
 

At http://www.w1hkj.com/alpha/fldigi/

Date:   Mon Jan 13 10:39:42 2020 -0600

    TUNE macro
    
     * Restore execution code for <TUNE
     * Retain delayed execution code for <!TUNE

    contestia cr
    
      * correct suppression of <CR> display

    serial port
    
      * insure that DTR and RTS are always disabled when closing port

    Check Version
    
      * correct version check logic

73, David, W1HKJ

Re: Why Flrig?

Harry Bloomberg
 

Three reasons I use Flrig:
  1. Easier to interface to a radio than Fldigi.  With Flrig you don't need to download and install XML files, everything's built right in.
  2. Simplifies interfacing to Fldigi and WSJT-X.  Both of those programs will use Flrig as your "radio", so if you change rigs, you only need to change in Flrig and nowhere else.
  3. Ease of remote operating.  This is the most important for me.  Most of my operating is done remotely by logging onto my Raspberry Pi.   Flrig allows me to easily control my radio's major controls.

73,
Harry Bloomberg W3YJ

On Mon, Jan 13, 2020 at 12:38 PM KG7D Greg via Groups.Io <big_blue_scout=yahoo.com@groups.io> wrote:
My question is why do you use Flrig? What features does it have that you use that RigCat doesn't? I'm using an Icom IC-7100 and for the last few years I've had no problems using RigCat, and found no features that were missing with Fldigi, FLamp, Flmsg. I'm not trying to start a debate rather its needed or not. Just wanting to know what I might be missing.

Going back to the Fast Light part of the name, I'm a believer that less is usually more.

Greg - KG7D

Why Flrig?

KG7D Greg
 

My question is why do you use Flrig? What features does it have that you use that RigCat doesn't? I'm using an Icom IC-7100 and for the last few years I've had no problems using RigCat, and found no features that were missing with Fldigi, FLamp, Flmsg. I'm not trying to start a debate rather its needed or not. Just wanting to know what I might be missing.

Going back to the Fast Light part of the name, I'm a believer that less is usually more.

Greg - KG7D

fldigi 4.1.9.01 posted

Dave
 

At http://www.w1hkj.com/alpha/fldigi

A few fixes for 4.1.09 inspite of hundreds of hours of testing.

Date:   Mon Jan 13 08:15:53 2020 -0600

    contestia cr
    
      * correct suppression of <CR> display

Date:   Sun Jan 12 20:46:49 2020 -0600

    serial port
    
      * insure that DTR and RTS are always disabled when closing port

Date:   Sun Jan 12 07:29:58 2020 -0600

    Version check
    
      * correct version check logic

73, David
W1HKJ