Date   

RETRIVING EQSL AND LOTW IN LOGBOOK.

 

How do u retrive the eqsl and lotw in FLDIGI logbook.
In the logbook it shows I sent eqsl and Lotw. Now how to I retrive them ??
73 Dave

--
nu4n


Re: FLDigi transmit text file contents application question

Dave
 

Try removing the white space between the "<FILE:" and "~/.fldigi/10fname>"

Dave

On 10/24/20 1:56 AM, Andy_VE4PER wrote:

Dave,

From what I have read the code below should work unless something in the debian based

tar ball for fldigi vers ...15  isn't handling  the <FILE: > tag as advertised possibly ???

attached actual dos2unix processed text file for someone else with linux box to try possibly.


I have simplified my code practice macro to a single dos2unix processed cipher group file transmission. I use fldigi UI screen to control CW mode and code speeds

to keep the macro as simple as possible

macro code:     even tried <TX><FILE: 10fname><RX>  

<TX>

<FILE: ~/.fldigi/10fname>

<RX>
---------------------------

<TX>

<FILE: /home/userID/.fldigi/10fname>

<RX>

-------------------------------

<TX>

<FILE: "/home/userID/.fldigi/10fname">

<RX>

-------------------------------------

<TX>

<FILE: "~/.fldigi/10fname">

<RX>

-------------------------------------------------


Normally in linux "~/" is shorthand symbol for "/home/userID/"  (equivalent to C:/users/userid in windows) . so I tried each of the above examples and none worked.

all activated the PTT ready to send then simply displayed a " r^"  and then dropped the PTT without sending any of the text groups from the file.


after dos2unix conversion the 10fname file partial contents is as below (with idle tag eliminated from between each cipher group as was in original):

lJu0V        bylB7        Ed7Uy        yMz1j        eAF4e        ES7CG        82o6I        V7ZhU        V9v9A        QaLO2        xEw4Q        KQd08        m2oSt        KQd08        m2oSt
Rl3nU        o1OV6        USId7        RkMY4        SUJh8        uB3PX        Ka0XW        ADg2q        p2hwH        ibQ7w        x0Q6d        su6Nw        vlu7D        su6Nw        vlu7D








On 2020-10-23 8:03 p.m., Dave wrote:


On 10/23/20 6:56 PM, Andy_VE4PER wrote:

I was aware of that text difference Dave where the difference is  is specifying ref's to specific files to link to from withing the macro itself; ie  windows is C:/users/userID/.fldigi.files/filename

The file reference has to coincide with the operating system.


while Linux is /home/userID/.fldigi/filename.txt  or ~/.fldigi/filename.txt not sure what fldigi macro is expecting to recognize.


I guess the second question is does fldigi macro code system recognize macro tags as tags when embedded within the text files that it selects to transmit. 

The parser does not interpret includes text files.  The file contents should be ASCII or UTF-8 text.

David



Re: Callsign colour

Panos
 

Yes thanks this is what I am looking for 73


Re: FLDigi transmit text file contents application question

Andy_VE4PER
 

Dave,

From what I have read the code below should work unless something in the debian based

tar ball for fldigi vers ...15  isn't handling  the <FILE: > tag as advertised possibly ???

attached actual dos2unix processed text file for someone else with linux box to try possibly.


I have simplified my code practice macro to a single dos2unix processed cipher group file transmission. I use fldigi UI screen to control CW mode and code speeds

to keep the macro as simple as possible

macro code:     even tried <TX><FILE: 10fname><RX>  

<TX>

<FILE: ~/.fldigi/10fname>

<RX>
---------------------------

<TX>

<FILE: /home/userID/.fldigi/10fname>

<RX>

-------------------------------

<TX>

<FILE: "/home/userID/.fldigi/10fname">

<RX>

-------------------------------------

<TX>

<FILE: "~/.fldigi/10fname">

<RX>

-------------------------------------------------


Normally in linux "~/" is shorthand symbol for "/home/userID/"  (equivalent to C:/users/userid in windows) . so I tried each of the above examples and none worked.

all activated the PTT ready to send then simply displayed a " r^"  and then dropped the PTT without sending any of the text groups from the file.


after dos2unix conversion the 10fname file partial contents is as below (with idle tag eliminated from between each cipher group as was in original):

lJu0V        bylB7        Ed7Uy        yMz1j        eAF4e        ES7CG        82o6I        V7ZhU        V9v9A        QaLO2        xEw4Q        KQd08        m2oSt        KQd08        m2oSt
Rl3nU        o1OV6        USId7        RkMY4        SUJh8        uB3PX        Ka0XW        ADg2q        p2hwH        ibQ7w        x0Q6d        su6Nw        vlu7D        su6Nw        vlu7D








On 2020-10-23 8:03 p.m., Dave wrote:


On 10/23/20 6:56 PM, Andy_VE4PER wrote:

I was aware of that text difference Dave where the difference is  is specifying ref's to specific files to link to from withing the macro itself; ie  windows is C:/users/userID/.fldigi.files/filename

The file reference has to coincide with the operating system.


while Linux is /home/userID/.fldigi/filename.txt  or ~/.fldigi/filename.txt not sure what fldigi macro is expecting to recognize.


I guess the second question is does fldigi macro code system recognize macro tags as tags when embedded within the text files that it selects to transmit. 

The parser does not interpret includes text files.  The file contents should be ASCII or UTF-8 text.

David


Re: Callsign colour

Cliff
 

Hi Panos,

If you hover the mouse over the call sign fldigi will popup an info box that includes the last contact date and mode. Will that help?

73,
Cliff, AE5ZA

On Oct 18, 2020, at 04:13, Panos <sv1grn@...> wrote:

Hi dear friends I wonder if its possible when I copy a callsign or when its decoded on rx to show it with red if it is already in the log 73


Re: Flrig

Cliff
 

Dave,

Forgot to respond regarding ALC. When transmitting click the SWR scale to change it to ALC, assuming that has been implemented for the TX-2000. At this point that setting is only remembered during one flrig session so you have to set it each time you start flrig.

73,
Cliff, AE5ZA

On Oct 23, 2020, at 20:40, Cliff <ae5zaham@...> wrote:

Dave,

Go to the flrig config Restore tab and uncheck the “Use Xcvr Data” box. With that checked flrig will start with things just as the transceiver is set.

I have all the Restore checkboxes checked except “Use Xcvr Data”. That way on exit from flrig the rig is restored to the way it was before flrig started, but while flrig is running I can have totally different settings that are for digital mode. These settings are remembered by flrig and will be then restored for your use when flrig starts again regardless of the current rig settings at startup time.

73,
Cliff, AE5ZA

On Oct 23, 2020, at 15:30, Dave Tucker Nu4N <dwtucker19@...> wrote:

I am using FLrig as computer control. Is there a way to keep FLrig on my Kenwood TS 2000 from starting with my noise blanker blanker on  and swr. I use ALC more than he SWR. and I dont   use t noise blanker
73 Dave
--
nu4n



Re: Flrig

Cliff
 

Dave,

Go to the flrig config Restore tab and uncheck the “Use Xcvr Data” box. With that checked flrig will start with things just as the transceiver is set.

I have all the Restore checkboxes checked except “Use Xcvr Data”. That way on exit from flrig the rig is restored to the way it was before flrig started, but while flrig is running I can have totally different settings that are for digital mode. These settings are remembered by flrig and will be then restored for your use when flrig starts again regardless of the current rig settings at startup time.

73,
Cliff, AE5ZA

On Oct 23, 2020, at 15:30, Dave Tucker Nu4N <dwtucker19@...> wrote:

I am using FLrig as computer control. Is there a way to keep FLrig on my Kenwood TS 2000 from starting with my noise blanker blanker on  and swr. I use ALC more than he SWR. and I dont   use t noise blanker
73 Dave
--
nu4n


Re: FLDigi transmit text file contents application question

Dave
 



On 10/23/20 6:56 PM, Andy_VE4PER wrote:

I was aware of that text difference Dave where the difference is  is specifying ref's to specific files to link to from withing the macro itself; ie  windows is C:/users/userID/.fldigi.files/filename

The file reference has to coincide with the operating system.


while Linux is /home/userID/.fldigi/filename.txt  or ~/.fldigi/filename.txt not sure what fldigi macro is expecting to recognize.


I guess the second question is does fldigi macro code system recognize macro tags as tags when embedded within the text files that it selects to transmit. 

The parser does not interpret includes text files.  The file contents should be ASCII or UTF-8 text.

David


Request RSID for Contestia 16/250 mode #fldigi #rsid

Jim AJ8S
 

My request is to add an RSID code for the Contestia mode 16/250 mode. This mode provides a reasonable speed with robust S/N and is very useful for ragchewing DX on HF. I make regular skeds on 40 meters with Europe and Australia using this mode and have found it to be the best choice. Adding RSID would help promote its use.


Re: FLDigi transmit text file contents application question

Andy_VE4PER
 

I was aware of that text difference Dave where the difference is  is specifying ref's to specific files to link to from withing the macro itself; ie  windows is C:/users/userID/.fldigi.files/filename

while Linux is /home/userID/.fldigi/filename.txt  or ~/.fldigi/filename.txt not sure what fldigi macro is expecting to recognize.


I guess the second question is does fldigi macro code system recognize macro tags as tags when embedded within the text files that it selects to transmit



On 2020-10-23 6:07 p.m., Dave wrote:

Andy,

When moving a text file from Windows to Linux or reverse you have to change the end-of-line sequence.  In linux it is <LF>. In Windows it is <CR><LF>.

The utility programs dos2unix, unix2dos, mac2unix, unix2mac provide an easy solution to modifying the file.  On a Debian based system you can install the utility programs:

$ sudo apt install dos2unix

The man page for dos2unix:

dos2unix(1)                                 2017-10-10                                dos2unix(1)

NAME
       dos2unix - DOS/Mac to Unix and vice versa text file format converter

SYNOPSIS
           dos2unix [options] [FILE ...] [-n INFILE OUTFILE ...]
           unix2dos [options] [FILE ...] [-n INFILE OUTFILE ...]

DESCRIPTION
       The Dos2unix package includes utilities "dos2unix" and "unix2dos" to convert plain text
       files in DOS or Mac format to Unix format and vice versa.

       In DOS/Windows text files a line break, also known as newline, is a combination of two
       characters: a Carriage Return (CR) followed by a Line Feed (LF). In Unix text files a line
       break is a single character: the Line Feed (LF). In Mac text files, prior to Mac OS X, a
       line break was single Carriage Return (CR) character. Nowadays Mac OS uses Unix style (LF)
       line breaks.

       Besides line breaks Dos2unix can also convert the encoding of files. A few DOS code pages
       can be converted to Unix Latin-1. And Windows Unicode (UTF-16) files can be converted to
       Unix Unicode (UTF-8) files.

73, David, W1HKJ

Hi Dave,

I managed to get one working using fldigi macro on a windows box, but when I tried to move it to the fldigi on my Linux box It would do the tone set up, key the transmitter, but then not send any file contents. It appeared to send some EOF control character after each file name , although it did not sequence through all the listed files as there wasn't the same number of EOF characters showing as there were files listed to send.

I was wondering if it was related to actual file contents as explained below, or how I specified the filenames in the macro listing as it differs between windows and linux. I looked through the docs for fldigi and noticed that the repertoire of commands for doing macros seems to be limited, since some of the macro tags in the ARRL macro code that you had att for ref had some not listed in the docs or the embedded list in the macro editor window; I searched about for what one could consider a more complete programmers code ref manual for fldigi macro coding and didn't have much luck finding one.

I had hoped if I found one it might have an explanation of how to modify the filespec syntax to use in linux boxes; but no luck. I included what I came up with below in hopes you or someone else in the group might be able to point me in right direction. Maybe need a Nifty Minimanual for fldigi macro code ref manual hihi


cheers & thanks for your time and tips 73

Andy

*****************************************************************

<# CW STEPPED CODE PRACTICE>
<MODEM:CW>                                                                           <# CODE PRACTICE TRANSMISSION set MODEM to CW Mode>

<TX>                                                                                 <# Start OF CODE PRACTICE TRANSMISSION set PGM to XMT Mode>

<!GOFREQ:650> <!WPM:11> <FILE: "/home/UserID/.fldigi/Infofname.txt">                    <# 11 WPM CODE PRACTICE Info TRANSMISSION >
<!WAIT:2>

<!GOFREQ:650> <!WPM:11> <FILE: "/home/UserID/.fldigi/Introfname.txt">                   <# 11 WPM CODE PRACTICE Intro TRANSMISSION >
<!WAIT:2>

<!GOFREQ:650> <!WPM:40> <FILE: "/home/UserID/.fldigi/40fname.txt">                       <# 40 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (16 mins) >
<!WAIT:2>

<!GOFREQ:650> <!WPM:35> <FILE: "/home/UserID/.fldigi/35fname.txt">                       <# 35 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (19 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:30> <FILE: "/home/UserID/.fldigi/30fname.txt">                       <# 30 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (22 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:25> <FILE: "/home/UserID/.fldigi/25fname.txt">                       <# 25 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (26 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:20> <FILE: "/home/UserID/.fldigi/20fname.txt">                       <# 20 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (32 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:15> <FILE: "/home/UserID/.fldigi/15fname.txt">                        <# 15 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (44 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:10> <FILE: "/home/UserID/.fldigi/10fname.txt">                        <# 10 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (64 mins) >
<!WAIT:2>

<!GOFREQ:650> <!WPM:10> <FILE: "/home/UserID/.fldigi/Qsignalsfname.txt">                  <# 10 WPM Q-codes & Punctuation CODE PRACTICE TRANSMISSION (14 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:11> <FILE: "/home/UserID/.fldigi/BDCST_EOF_practicestringfname.txt">  <# END OF STEPPED CODE PRACTICE Message String TRANSMISSION ( Total ET 3.5 HRs) >

<RX>                                                                                   <# END OF CODE PRACTICE TRANSMISSION return PGM to RCV Mode>

___________________________________________________________________________________________________________________________________________________________________________

The ??fname.txt  files are all the same 640 random 5 ascii char groups  The Qsignals text file is made up of commonly used amateur radio Q-code rather than the full
ICAO international and Marine Service Q-code mast set. Punctuation collection includes period, comma, question mark, hyphen, slash, parenthesis and Q-codes have assertive sent as well as interrogative format.

I use a linux command line random ascii text generator used for passwords; but specify groupings of 5 chars and save it to a csv file then use that to narrow it down to 640 separate groups. Below is actual file contents

I was wondering if the idle tag maybe is what is hanging things up and maybe I should use just an ascii "/" in those cells to delineate separation of word equiv groups


lJu0V <!IDLE:0.5> bylB7 <!IDLE:0.5> Ed7Uy <!IDLE:0.5> yMz1j <!IDLE:0.5>
Rl3nU <!IDLE:0.5> o1OV6 <!IDLE:0.5> USId7 <!IDLE:0.5> RkMY4 <!IDLE:0.5>
ClzI6 <!IDLE:0.5> wDO4x <!IDLE:0.5> lOA7X <!IDLE:0.5> sJB31 <!IDLE:0.5>
3LQPw <!IDLE:0.5> Oy3rQ <!IDLE:0.5> f8Yek <!IDLE:0.5> wDw0u <!IDLE:0.5>
do1cI <!IDLE:0.5> 4Kwka <!IDLE:0.5> c7dGS <!IDLE:0.5> qmUT1 <!IDLE:0.5>



*****************************************************************







On 2020-06-12 12:20 p.m., Dave wrote:

ARRL uses fldigi for it's broadcasts

http://www.w1hkj.com/FldigiHelp/inline_macro_page.html#arrl_style_broadcast

Attached find ARRL macros that I assisted in writing for W1AW.

73, David, W1HKJ

On 6/12/20 10:39 AM, Andy_VE4PER wrote:
 Does anyone know if there is a command in the FLDigi repertoire that
I can use in a macro to command the CW Mode to change sending speed
automatically so that the CW test macro can be used as a code practice
macro that emulates what W1AW uses for code practice sessions.

See extra info in the twitter posts below as well. I have it running on
40 M 7.005.70 MHz QRP 5 watts at the moment while I work on it.

https://twitter.com/CdnARS_VE4PER/status/1271463176802992128?s=20

https://twitter.com/CdnARS_VE4PER/status/1271463675296022528?s=20

https://twitter.com/CdnARS_VE4PER/status/1271464078867787779?s=20

appreciate any feedback.





Re: Auto-Cq

Dave
 

Now that I have worn out my welcome with the notifier answer to your auto-CQ question, let me add a bit of icing to the cake.

fldigi has "audio alerts" that can play back beeps, whistles, dog barks, train horns, or any other wav / mp3 file on the computer.  The "notifier" can include an audio alert action

see: http://www.w1hkj.com/FldigiHelp/audio_alerts_page.html#notifier_events

Have fun Rein.

73, David, W1HKJ


Re: Auto-Cq

Dave
 

Create a triggered notification event:

When the parser detects <MYCALL> de CALL (any call) in the Rx buffer, it will immediately trigger these events:

  • popup notifier dialog opens to announce the event,
  • Rx text is appended with a marker
  • TX text will be acted upon immediately, the transmit enable will turn off the macro timer

fldigi's notifier is much more robust than the MixW reaction that you are accustomed to.

see: http://www.w1hkj.com/FldigiHelp/notifier_page.html

73, David, W1HKJ

On 10/23/20 10:50 AM, Rien Aarden wrote:
Good afternoon,

I've been working with FLdigi for a while now and before that with Mixw3
What I liked about Mixw3 is that if I do Auto-Cq and a station comes back with my call that the Auto-CQ stops.
Now my question is is this also possible in FLdigi?
and how can I do this?
thanks in advance and above all stay healthy
73, Rien, PA7RA


Re: FLDigi transmit text file contents application question

Dave
 

Andy,

When moving a text file from Windows to Linux or reverse you have to change the end-of-line sequence.  In linux it is <LF>. In Windows it is <CR><LF>.

The utility programs dos2unix, unix2dos, mac2unix, unix2mac provide an easy solution to modifying the file.  On a Debian based system you can install the utility programs:

$ sudo apt install dos2unix

The man page for dos2unix:

dos2unix(1)                                 2017-10-10                                dos2unix(1)

NAME
       dos2unix - DOS/Mac to Unix and vice versa text file format converter

SYNOPSIS
           dos2unix [options] [FILE ...] [-n INFILE OUTFILE ...]
           unix2dos [options] [FILE ...] [-n INFILE OUTFILE ...]

DESCRIPTION
       The Dos2unix package includes utilities "dos2unix" and "unix2dos" to convert plain text
       files in DOS or Mac format to Unix format and vice versa.

       In DOS/Windows text files a line break, also known as newline, is a combination of two
       characters: a Carriage Return (CR) followed by a Line Feed (LF). In Unix text files a line
       break is a single character: the Line Feed (LF). In Mac text files, prior to Mac OS X, a
       line break was single Carriage Return (CR) character. Nowadays Mac OS uses Unix style (LF)
       line breaks.

       Besides line breaks Dos2unix can also convert the encoding of files. A few DOS code pages
       can be converted to Unix Latin-1. And Windows Unicode (UTF-16) files can be converted to
       Unix Unicode (UTF-8) files.

73, David, W1HKJ

Hi Dave,

I managed to get one working using fldigi macro on a windows box, but when I tried to move it to the fldigi on my Linux box It would do the tone set up, key the transmitter, but then not send any file contents. It appeared to send some EOF control character after each file name , although it did not sequence through all the listed files as there wasn't the same number of EOF characters showing as there were files listed to send.

I was wondering if it was related to actual file contents as explained below, or how I specified the filenames in the macro listing as it differs between windows and linux. I looked through the docs for fldigi and noticed that the repertoire of commands for doing macros seems to be limited, since some of the macro tags in the ARRL macro code that you had att for ref had some not listed in the docs or the embedded list in the macro editor window; I searched about for what one could consider a more complete programmers code ref manual for fldigi macro coding and didn't have much luck finding one.

I had hoped if I found one it might have an explanation of how to modify the filespec syntax to use in linux boxes; but no luck. I included what I came up with below in hopes you or someone else in the group might be able to point me in right direction. Maybe need a Nifty Minimanual for fldigi macro code ref manual hihi


cheers & thanks for your time and tips 73

Andy

*****************************************************************

<# CW STEPPED CODE PRACTICE>
<MODEM:CW>                                                                           <# CODE PRACTICE TRANSMISSION set MODEM to CW Mode>

<TX>                                                                                 <# Start OF CODE PRACTICE TRANSMISSION set PGM to XMT Mode>

<!GOFREQ:650> <!WPM:11> <FILE: "/home/UserID/.fldigi/Infofname.txt">                    <# 11 WPM CODE PRACTICE Info TRANSMISSION >
<!WAIT:2>

<!GOFREQ:650> <!WPM:11> <FILE: "/home/UserID/.fldigi/Introfname.txt">                   <# 11 WPM CODE PRACTICE Intro TRANSMISSION >
<!WAIT:2>

<!GOFREQ:650> <!WPM:40> <FILE: "/home/UserID/.fldigi/40fname.txt">                       <# 40 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (16 mins) >
<!WAIT:2>

<!GOFREQ:650> <!WPM:35> <FILE: "/home/UserID/.fldigi/35fname.txt">                       <# 35 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (19 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:30> <FILE: "/home/UserID/.fldigi/30fname.txt">                       <# 30 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (22 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:25> <FILE: "/home/UserID/.fldigi/25fname.txt">                       <# 25 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (26 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:20> <FILE: "/home/UserID/.fldigi/20fname.txt">                       <# 20 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (32 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:15> <FILE: "/home/UserID/.fldigi/15fname.txt">                        <# 15 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (44 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:10> <FILE: "/home/UserID/.fldigi/10fname.txt">                        <# 10 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (64 mins) >
<!WAIT:2>

<!GOFREQ:650> <!WPM:10> <FILE: "/home/UserID/.fldigi/Qsignalsfname.txt">                  <# 10 WPM Q-codes & Punctuation CODE PRACTICE TRANSMISSION (14 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:11> <FILE: "/home/UserID/.fldigi/BDCST_EOF_practicestringfname.txt">  <# END OF STEPPED CODE PRACTICE Message String TRANSMISSION ( Total ET 3.5 HRs) >

<RX>                                                                                   <# END OF CODE PRACTICE TRANSMISSION return PGM to RCV Mode>

___________________________________________________________________________________________________________________________________________________________________________

The ??fname.txt  files are all the same 640 random 5 ascii char groups  The Qsignals text file is made up of commonly used amateur radio Q-code rather than the full
ICAO international and Marine Service Q-code mast set. Punctuation collection includes period, comma, question mark, hyphen, slash, parenthesis and Q-codes have assertive sent as well as interrogative format.

I use a linux command line random ascii text generator used for passwords; but specify groupings of 5 chars and save it to a csv file then use that to narrow it down to 640 separate groups. Below is actual file contents

I was wondering if the idle tag maybe is what is hanging things up and maybe I should use just an ascii "/" in those cells to delineate separation of word equiv groups


lJu0V <!IDLE:0.5> bylB7 <!IDLE:0.5> Ed7Uy <!IDLE:0.5> yMz1j <!IDLE:0.5>
Rl3nU <!IDLE:0.5> o1OV6 <!IDLE:0.5> USId7 <!IDLE:0.5> RkMY4 <!IDLE:0.5>
ClzI6 <!IDLE:0.5> wDO4x <!IDLE:0.5> lOA7X <!IDLE:0.5> sJB31 <!IDLE:0.5>
3LQPw <!IDLE:0.5> Oy3rQ <!IDLE:0.5> f8Yek <!IDLE:0.5> wDw0u <!IDLE:0.5>
do1cI <!IDLE:0.5> 4Kwka <!IDLE:0.5> c7dGS <!IDLE:0.5> qmUT1 <!IDLE:0.5>



*****************************************************************







On 2020-06-12 12:20 p.m., Dave wrote:

ARRL uses fldigi for it's broadcasts

http://www.w1hkj.com/FldigiHelp/inline_macro_page.html#arrl_style_broadcast

Attached find ARRL macros that I assisted in writing for W1AW.

73, David, W1HKJ

On 6/12/20 10:39 AM, Andy_VE4PER wrote:
 Does anyone know if there is a command in the FLDigi repertoire that
I can use in a macro to command the CW Mode to change sending speed
automatically so that the CW test macro can be used as a code practice
macro that emulates what W1AW uses for code practice sessions.

See extra info in the twitter posts below as well. I have it running on
40 M 7.005.70 MHz QRP 5 watts at the moment while I work on it.

https://twitter.com/CdnARS_VE4PER/status/1271463176802992128?s=20

https://twitter.com/CdnARS_VE4PER/status/1271463675296022528?s=20

https://twitter.com/CdnARS_VE4PER/status/1271464078867787779?s=20

appreciate any feedback.





Re: FLDigi transmit text file contents application question

Andy_VE4PER
 

Hi Dave,

I managed to get one working using fldigi macro on a windows box, but when I tried to move it to the fldigi on my Linux box It would do the tone set up, key the transmitter, but then not send any file contents. It appeared to send some EOF control character after each file name , although it did not sequence through all the listed files as there wasn't the same number of EOF characters showing as there were files listed to send.

I was wondering if it was related to actual file contents as explained below, or how I specified the filenames in the macro listing as it differs between windows and linux. I looked through the docs for fldigi and noticed that the repertoire of commands for doing macros seems to be limited, since some of the macro tags in the ARRL macro code that you had att for ref had some not listed in the docs or the embedded list in the macro editor window; I searched about for what one could consider a more complete programmers code ref manual for fldigi macro coding and didn't have much luck finding one.

I had hoped if I found one it might have an explanation of how to modify the filespec syntax to use in linux boxes; but no luck. I included what I came up with below in hopes you or someone else in the group might be able to point me in right direction. Maybe need a Nifty Minimanual for fldigi macro code ref manual hihi


cheers & thanks for your time and tips 73

Andy

*****************************************************************

<# CW STEPPED CODE PRACTICE>
<MODEM:CW>                                                                           <# CODE PRACTICE TRANSMISSION set MODEM to CW Mode>

<TX>                                                                                 <# Start OF CODE PRACTICE TRANSMISSION set PGM to XMT Mode>

<!GOFREQ:650> <!WPM:11> <FILE: "/home/UserID/.fldigi/Infofname.txt">                    <# 11 WPM CODE PRACTICE Info TRANSMISSION >
<!WAIT:2>

<!GOFREQ:650> <!WPM:11> <FILE: "/home/UserID/.fldigi/Introfname.txt">                   <# 11 WPM CODE PRACTICE Intro TRANSMISSION >
<!WAIT:2>

<!GOFREQ:650> <!WPM:40> <FILE: "/home/UserID/.fldigi/40fname.txt">                       <# 40 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (16 mins) >
<!WAIT:2>

<!GOFREQ:650> <!WPM:35> <FILE: "/home/UserID/.fldigi/35fname.txt">                       <# 35 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (19 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:30> <FILE: "/home/UserID/.fldigi/30fname.txt">                       <# 30 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (22 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:25> <FILE: "/home/UserID/.fldigi/25fname.txt">                       <# 25 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (26 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:20> <FILE: "/home/UserID/.fldigi/20fname.txt">                       <# 20 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (32 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:15> <FILE: "/home/UserID/.fldigi/15fname.txt">                        <# 15 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (44 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:10> <FILE: "/home/UserID/.fldigi/10fname.txt">                        <# 10 WPM CIPHER Groups CODE PRACTICE TRANSMISSION (64 mins) >
<!WAIT:2>

<!GOFREQ:650> <!WPM:10> <FILE: "/home/UserID/.fldigi/Qsignalsfname.txt">                  <# 10 WPM Q-codes & Punctuation CODE PRACTICE TRANSMISSION (14 mins)>
<!WAIT:2>

<!GOFREQ:650> <!WPM:11> <FILE: "/home/UserID/.fldigi/BDCST_EOF_practicestringfname.txt">  <# END OF STEPPED CODE PRACTICE Message String TRANSMISSION ( Total ET 3.5 HRs) >

<RX>                                                                                   <# END OF CODE PRACTICE TRANSMISSION return PGM to RCV Mode>

___________________________________________________________________________________________________________________________________________________________________________

The ??fname.txt  files are all the same 640 random 5 ascii char groups  The Qsignals text file is made up of commonly used amateur radio Q-code rather than the full
ICAO international and Marine Service Q-code mast set. Punctuation collection includes period, comma, question mark, hyphen, slash, parenthesis and Q-codes have assertive sent as well as interrogative format.

I use a linux command line random ascii text generator used for passwords; but specify groupings of 5 chars and save it to a csv file then use that to narrow it down to 640 separate groups. Below is actual file contents

I was wondering if the idle tag maybe is what is hanging things up and maybe I should use just an ascii "/" in those cells to delineate separation of word equiv groups


lJu0V <!IDLE:0.5> bylB7 <!IDLE:0.5> Ed7Uy <!IDLE:0.5> yMz1j <!IDLE:0.5>
Rl3nU <!IDLE:0.5> o1OV6 <!IDLE:0.5> USId7 <!IDLE:0.5> RkMY4 <!IDLE:0.5>
ClzI6 <!IDLE:0.5> wDO4x <!IDLE:0.5> lOA7X <!IDLE:0.5> sJB31 <!IDLE:0.5>
3LQPw <!IDLE:0.5> Oy3rQ <!IDLE:0.5> f8Yek <!IDLE:0.5> wDw0u <!IDLE:0.5>
do1cI <!IDLE:0.5> 4Kwka <!IDLE:0.5> c7dGS <!IDLE:0.5> qmUT1 <!IDLE:0.5>



*****************************************************************







On 2020-06-12 12:20 p.m., Dave wrote:

ARRL uses fldigi for it's broadcasts

http://www.w1hkj.com/FldigiHelp/inline_macro_page.html#arrl_style_broadcast

Attached find ARRL macros that I assisted in writing for W1AW.

73, David, W1HKJ

On 6/12/20 10:39 AM, Andy_VE4PER wrote:
 Does anyone know if there is a command in the FLDigi repertoire that
I can use in a macro to command the CW Mode to change sending speed
automatically so that the CW test macro can be used as a code practice
macro that emulates what W1AW uses for code practice sessions.

See extra info in the twitter posts below as well. I have it running on
40 M 7.005.70 MHz QRP 5 watts at the moment while I work on it.

https://twitter.com/CdnARS_VE4PER/status/1271463176802992128?s=20

https://twitter.com/CdnARS_VE4PER/status/1271463675296022528?s=20

https://twitter.com/CdnARS_VE4PER/status/1271464078867787779?s=20

appreciate any feedback.





Re: import log to FLdigi

Cliff
 

Fldigi Menu - Logbook/ADIF/Merge

73,
Cliff, AE5ZA

On Oct 23, 2020, at 14:35, Dave Tucker Nu4N <dwtucker19@...> wrote:

I must be dumb but I see where u can export but not import. Where is the import tab ??
--
nu4n


Flrig

 

I am using FLrig as computer control. Is there a way to keep FLrig on my Kenwood TS 2000 from starting with my noise blanker blanker on  and swr. I use ALC more than he SWR. and I dont   use t noise blanker
73 Dave
--
nu4n


Re: import log to FLdigi

 

I must be dumb but I see where u can export but not import. Where is the import tab ??
--
nu4n


Re: import log to FLdigi

Cliff
 

Dave,

If you can "export as ADIF" from the other logging program then importing that ADIF file into fldigi log, either to a new fldigi log or into an existing log, should be no problem. 

73,
Cliff, AE5ZA

On Oct 23, 2020, at 12:59, Dave Tucker Nu4N <dwtucker19@...> wrote:

I there a  to import logs from another logging program like HRD or AClog.
Thanks
73 Dave
--
nu4n


import log to FLdigi

 

I there a  to import logs from another logging program like HRD or AClog.
Thanks
73 Dave
--
nu4n


Auto-Cq

Rien Aarden
 

Good afternoon,

I've been working with FLdigi for a while now and before that with Mixw3
What I liked about Mixw3 is that if I do Auto-Cq and a station comes back with my call that the Auto-CQ stops.
Now my question is is this also possible in FLdigi?
and how can I do this?
thanks in advance and above all stay healthy
73, Rien, PA7RA