Date   

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


flrig-1.3.49 posted

Dave
 

At http://www.w1hkj.com/files/flrig/

and at Source Forge.

73, David
W1HKJ


                           Version 1.3.49
                                                    Jan 12 15:29:23 2020
Config
  * Change configuration from tab to tree pick metaphor
  * Change serial port discovery on OS-X to just use tty and not cu.

MilliSleep
  * Change MINGW implementation to use nanosleep vice Sleep

FT991A
  * add separate class to support the FT-991A

drag-release
  * Add FL_RELEASE event processing to Fl_Value_Slider widget

TT566 update
  * mods to TT566 class methods by W5PNY
    - detect PTT changes made at xcvr
    - correct S meter scale conversion

rig.cat_string
  * change xmlrpc implementation to return the transceiver response string

IC756PROII
  * Start up seg fault if xcvr is in AM or FM mode

scripts
  * modify build scripts for current OS install

Increase User commands
  * increase from 8 to 16 user definable commands

Unguarded statement
  * fix unguarded statement in src/TS990.cxx

IC9100
  * Correct bandwidth tables

IC9700
  * Add Icom 9700 transceiver

FT857/897
  * add delay after changing mode
  * add extras drop down entries
  * add Commands tab
  * add Band select tab
    - band/mode select buttons
  * Add CTCSS and repeater controls tab
  * Store band data in prefs file:
    - freq, mode,
    - CTCSS tx/rx tones
    - FM simplex/minus/plus; offset frequency



fldigi 4.1.09 posted

Dave
 

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

and at Source Forge.

This is the first update release in 6 months and contains many bug fixes, performance enhancements, non-English text translations, and new capabilities.  Please review the fldigi.txt, reprinted below.


                           Version 4.1.09
                                                 Thu Jan 10 18:00:00 2020

config-dialog-mod
  * Modify config dialog creation to insure that locale translations apply
    to table entries

MilliSleep
  * Change MINGW MilliSleep implementation to use nanosleep

PO updates
  * Update po submissions from translation authors
  * Change Italian translator to Emanuale Repetto, IZ1UKX

Alert/Rx-monitor playback
  * fix playback distortion on Pi3 internal sound card
    - sound OK on Cmedia thumb audio device
    - sound chopped/distorted on internal sound card
    - improved efficiency of portaudio callback function
    - increased sound data blocks to 1024 frames each frame 2 float values;
      right/left channel
  * Add alert stream volume control
  * Remove filter transients from rx audio stream
  * Update Alert configuration tab
  * Detect if use does not connect to audio alert device

New Install
  * restore Data Source dialog tab to new install wizard
  * fix missing cell element that caused table to not redraw correctly after
    table resize or column resize

Audio alerts disable
  * add enable/disable button to Audio Alerts playback device selection
    - opening a portaudio stream on unavailable device
    - caused segmentation fault
    - open stream now properly handled
    - default is disabled
  * fix seg fault bug on "new" install Wizard if audio alerts activated

cw mods
  * change timing parameter ranges
  * change CW sample rate to 16000
  * change waterfall drop rate computation
    - drop rate independent of mode samplerate
  * simplified CW AFCW generation code
  * add CW keyline on DTR/RTS
  * correct Farnsworth timing
  * insure that initial state of DTR is disabled
  * CW TUNE using DTR / RTS pins

Winkeyer
  * correct WK_online status detection

Analysis mode
  * change displayed tracking frequency to .001 precision

hamcall
  * fix to broken hamcall lookups

RSID code assignments
  * Assigned secondary Rsid Codes:
    - DominoEX Micro: 691
    - ThorEX : 693

ARRL CW bulletins
  * changes to CW modem and macro language to support bulleting transmissions by W1AW
  * add new transmit interval macro
      <!SKED:HHMMSS:YYYYMMDD> to provide segmented scheduling
    of transmission at exact date/time.
  * change right channel QSK/PTT signal to square wav
    - user configurable base frequency
  * correct Farnsworth timing
  * add timing compensation for more accurate WPM timing
  * modified to work with 1.2.0 nanoIO sketch

lotw mangled report files
  * tqsl trace file occassionally mangled when read by fldigi function 
    check_lotw_log.  delay reading file until no change in trace file size 
    occurs with a 100 msec window
  * improved lotw message box contents based on lotw trace file contents
  * increase time-out delays waiting for tqsl trace file completion

tree metaphor
  * change configuration dialog to use tree vice tab metaphor
  * update user documentation

OS X Bus 10 error
  * Bug fix on OS X.

Log ADIF export
  * Add fields to "all" export

xmlrpc_rig
  * increase timeout to 5 seconds

Display Logbook Datum
  * re-enable control of displaying logbook datum when starting program

Rx monitor
  * add monitor audio stream to allow user to listen to unprocessed Rx audio stream
  * add Rx audio stream filter
  * create separate Rx Audio dialog
    - open on View menu pull down

Combo Box behavior
  * add scrollwheel action to combo/list box behavior
  * add widget Fl_Group::do_callback() to event handler
  * correct FreqControl handler for scrollwheel

cw prosigns
  * allow user to select cw prosign display
    - long view, <SK> <BT> ...
    - short view, as prosign short cut key defined on the CW prosign config' tab

RTTY bell
  * enable BELL, visual and audible for TTY decoder
  * pass BELL, \a, and CR, \r to xml rx data stream
  * add RTTY bell waveform file
  * add user configuration controls to disable BELL annunciation
      * fixed Windows alert failure
      * added ctrl-shift-g to special character group to insert
        the <BEL>, 0x07 character into the transmit text
        - hold control and shift down and press g multiple times
          for a string of <BEL> insertions
      * clean up trailing edge of phone ring
      * implement separate thread for handling mp3 and wav
        file playback.
        - removes dr_mp processing from main thread
        - prevents main thread locking during mp3/wav file
          processing

MinGW mods
  * changes imposed by changes to gcc and mxe components
  * modifications to accommodate changes in mingw libraries and headers

CW International Chars

mp3
  * Add mp3 decoder for mp3 files
    - uses public domain decoder drmp3
    - Audio playback, and
    - Alerts

macros
  * Allow CWID execution at specified position in macro text
  * Modify macro tag <TIMER:nnn> to always start when state changes from Tx to Rx.
  * Add <# comments> tag.  Works same as <COMMENT:comments> tag
  * Correct coding for proper operation of <SKED:..., <TIMER:...
    and <REPEAT...> tags.
  * Implement <UNTIL:hhmm[ss]:[YYYYMMDD]> macro tag
    - halts macro at specified date/time when either <REPEAT>,
      or <TIMER:nn> are specified in the macro text.

Xmt Audio file
  * Add ability to transmit an audio file using new macro tag: <AUDIO:path-filename>
    - macro editor opens an OS select file dialog
      when the tag is selected from the pick list suggested use:
        <MODEM:NULL><TX>
        <AUDIO:path-filename-1>
        <AUDIO:path-filename-2>
        <RX><@MODEM:BPSK31>
      or modem type of choice
  * Audio file must be wav format, either mono or stereo any sample rate
  * Returning to Rx stops current and any pending audio playback.  Post Tx
    macro tags are then executed.  T/R button or Escape key will abort the playback.
  * Please use responsibly - know and understand your license limitations for
    transmitting audio files, especially music and/or copyrighted material.

Alerts
  * Correct test for no output device
    - do not use pa error handler
  * Add ability to select the pa device for alerts output
    - was using default device
    - detect device default sample rate
    - convert all sound files to def sr using fastest sinc converter
  * Change output to use pa callbacks

Data file update
  * Update/correction to file NAVTEX_stations.csv
    - contributed by N2RY

flrig freq/mode
  * Change order of sending frequency and mode to mode then frequency

Fltk 1.4.x
  * Change to startup resize on MacOS built against fltk-1.4.x

Wefax autosave
  * Change max lines to counter min=1000, max = 1000

Update check
  * correct logic for update checking

WEFAX AFC
  * Fix wefax AFC computation / application
    - incorrect computation of center frequency
  * Disallow audio stream playback on WEFAX
    - not compatible with HAMFAX class decoder
  * Remove status display messages
    - state changes still logged to event log
  * Force ".png" file extension on saved images
  * wefax code cleanup