Topics

Macro with modem changes

Randy
 

Greetings,

 

I was attempting to create a testing macro for different modems.  I do not get the expected results.  I start with fldigi set to mt63-2kl and transmit the macro shown below.  It starts in mt63 as expected, changes to 8psk1000f as expected but then reverts to mt63, then to 8psk500f to transmit the final “Modem returned to MT63-2KL” and finally leaves the system in 8psk500f.

 

Attempting to use a <TIMER:60> at the end is ignored. 

 

// Macro # 26

/$ 25 TESTINGMACROORDER

 

    <INCR>

    THIS IS A TEST OF RSID WITH FLDIGI STARTING IN\n

    MT63-2KL AND SEQUENCING 3 MODES\n

    8PSK1000F NEXT 8PSK500F TO FOLLOW THAT\n

    \n

 

    <!IDLE:2>    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:8PSK1000F>

 

    THIS SHOULD NOW BE TRANSMITTING 8PSK1000F\n

    \n

    8PSK500F NEXT AND RETURN TO MT63-2KL\n

    \n

 

    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:8PSK500F>

 

    THIS SHOULD NOW TRANSMIT 8PSK500F\n

    \n

    AND NEXT SHOULD RETURN THE SYSTEM TO MT63-2KL AS WE STARTED

 

    <!IDLE:2>    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:MT63-2KL>

   

    Modem returned to MT63-2KL\n

    <TX><RX>   

 

Do I interpret the instructions incorrectly? Is there a max length to macros? Do inline commands negate repeating timer commands?

 

Randall L. Pratt

KJ0RE

Http:\\mit.midco.net\rpratt

 

 

Frank Olaughlin
 

Shannon,

 

Is this for the vehicle  or to be used for the base antenna?

 

From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Randy
Sent: Monday, November 05, 2018 6:59 PM
To: nbems@groups.io
Subject: [nbems] Macro with modem changes

 

Greetings,

 

I was attempting to create a testing macro for different modems.  I do not get the expected results.  I start with fldigi set to mt63-2kl and transmit the macro shown below.  It starts in mt63 as expected, changes to 8psk1000f as expected but then reverts to mt63, then to 8psk500f to transmit the final “Modem returned to MT63-2KL” and finally leaves the system in 8psk500f.

 

Attempting to use a <TIMER:60> at the end is ignored. 

 

// Macro # 26

/$ 25 TESTINGMACROORDER

 

    <INCR>

    THIS IS A TEST OF RSID WITH FLDIGI STARTING IN\n

    MT63-2KL AND SEQUENCING 3 MODES\n

    8PSK1000F NEXT 8PSK500F TO FOLLOW THAT\n

    \n

 

    <!IDLE:2>    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:8PSK1000F>

 

    THIS SHOULD NOW BE TRANSMITTING 8PSK1000F\n

    \n

    8PSK500F NEXT AND RETURN TO MT63-2KL\n

    \n

 

    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:8PSK500F>

 

    THIS SHOULD NOW TRANSMIT 8PSK500F\n

    \n

    AND NEXT SHOULD RETURN THE SYSTEM TO MT63-2KL AS WE STARTED

 

    <!IDLE:2>    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:MT63-2KL>

   

    Modem returned to MT63-2KL\n

    <TX><RX>   

 

Do I interpret the instructions incorrectly? Is there a max length to macros? Do inline commands negate repeating timer commands?

 

Randall L. Pratt

KJ0RE

Http:\\mit.midco.net\rpratt

 

 

Frank Olaughlin
 

My apologies....hit the wrong group reply

Bob Cameron
 

Hi Randy

Basically any modem change resets/clears the timer. I ended up using fldigi-shell and a bash script to create timed events with multiple modem types.

I'll admit I haven't fully read your post, I only saw the TIMER problem.

Cheers Bob VK2YQA


On 06/11/18 10:59, Randy wrote:

Greetings,

 

I was attempting to create a testing macro for different modems.  I do not get the expected results.  I start with fldigi set to mt63-2kl and transmit the macro shown below.  It starts in mt63 as expected, changes to 8psk1000f as expected but then reverts to mt63, then to 8psk500f to transmit the final “Modem returned to MT63-2KL” and finally leaves the system in 8psk500f.

 

Attempting to use a <TIMER:60> at the end is ignored. 

 

// Macro # 26

/$ 25 TESTINGMACROORDER

 

    <INCR>

    THIS IS A TEST OF RSID WITH FLDIGI STARTING IN\n

    MT63-2KL AND SEQUENCING 3 MODES\n

    8PSK1000F NEXT 8PSK500F TO FOLLOW THAT\n

    \n

 

    <!IDLE:2>    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:8PSK1000F>

 

    THIS SHOULD NOW BE TRANSMITTING 8PSK1000F\n

    \n

    8PSK500F NEXT AND RETURN TO MT63-2KL\n

    \n

 

    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:8PSK500F>

 

    THIS SHOULD NOW TRANSMIT 8PSK500F\n

    \n

    AND NEXT SHOULD RETURN THE SYSTEM TO MT63-2KL AS WE STARTED

 

    <!IDLE:2>    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:MT63-2KL>

   

    Modem returned to MT63-2KL\n

    <TX><RX>   

 

Do I interpret the instructions incorrectly? Is there a max length to macros? Do inline commands negate repeating timer commands?

 

Randall L. Pratt

KJ0RE

Http:\\mit.midco.net\rpratt

 

 


Randy
 

Thank you for the reply.  The other part of my problem seems to be connected to the file structure of the macro.  By carefully placing line returns and separating all the commands to individual line breaks seems to improve things.  I have still not been able to set the initial modem type from the macro and the sequence that follows startup changes with the fldigi originally set modem type or the previous fldigi transmission.  A clean restart of fldigi before macro execution gives my intended sequence as long as I only repeat the same macro.

 

Randy

KJ0RE

http://mit.midco.net/rpratt

 

-----Original Message-----

From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Bob Cameron
Sent: Tuesday, November 06, 2018 4:39 AM
To: nbems@groups.io
Subject: Re: [nbems] Macro with modem changes

 

Hi Randy

Basically any modem change resets/clears the timer. I ended up using fldigi-shell and a bash script to create timed events with multiple modem types.

I'll admit I haven't fully read your post, I only saw the TIMER problem.

Cheers Bob VK2YQA

 

On 06/11/18 10:59, Randy wrote:

Greetings,

 

I was attempting to create a testing macro for different modems.  I do not get the expected results.  I start with fldigi set to mt63-2kl and transmit the macro shown below.  It starts in mt63 as expected, changes to 8psk1000f as expected but then reverts to mt63, then to 8psk500f to transmit the final “Modem returned to MT63-2KL” and finally leaves the system in 8psk500f.

 

Attempting to use a <TIMER:60> at the end is ignored.  

 

// Macro # 26

/$ 25 TESTINGMACROORDER

 

    <INCR>

    THIS IS A TEST OF RSID WITH FLDIGI STARTING IN\n

    MT63-2KL AND SEQUENCING 3 MODES\n

    8PSK1000F NEXT 8PSK500F TO FOLLOW THAT\n

    \n

 

    <!IDLE:2>    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:8PSK1000F>

 

    THIS SHOULD NOW BE TRANSMITTING 8PSK1000F\n

    \n

    8PSK500F NEXT AND RETURN TO MT63-2KL\n

    \n

 

    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:8PSK500F>

 

    THIS SHOULD NOW TRANSMIT 8PSK500F\n

    \n

    AND NEXT SHOULD RETURN THE SYSTEM TO MT63-2KL AS WE STARTED

 

    <!IDLE:2>    <!MODEM:NULL>    <!IDLE:2>    <!MODEM:MT63-2KL>

    

    Modem returned to MT63-2KL\n

    <TX><RX>    

 

Do I interpret the instructions incorrectly? Is there a max length to macros? Do inline commands negate repeating timer commands?

 

Randall L. Pratt

KJ0RE

Http:\\mit.midco.net\rpratt

 

 

 

Sean Smith
 

Hi Andy,

Probably your best route is to use an external script  that accesses FLdigi’s XML-RPC interface. 

http://www.w1hkj.com/FldigiHelp-3.21/html/xmlrpc_control_page.html

I’ve written a beacon timing script in Perl that changes the mode and transmits the beacon. Its deployed on several stations and is rock solid. 


Sean VE6SAR 

David Ranch
 

Hello Sean,

Are you willing to post your code somewhere so people can take a look?  Speaking for myself, I always like to learn from other examples that work and expand from there.

--David
KI6ZHD


Hi Andy,

Probably your best route is to use an external script  that accesses FLdigi’s XML-RPC interface. 

http://www.w1hkj.com/FldigiHelp-3.21/html/xmlrpc_control_page.html

I’ve written a beacon timing script in Perl that changes the mode and transmits the beacon. Its deployed on several stations and is rock solid.

Sean VE6SAR 

Randy
 

Thanks!  I’ll look at that.  I have continued experimenting with this and I believe the end of line/ line return format within my macros is causing the problem I have.  Minor changes to a working macro will create random operation until I again methodically format the text within the macro.  I’m using WinXP and Notepad.

 

Randy

KJ0RE

http://mit.midco.net/rpratt

 

-----Original Message-----
From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Sean Smith
Sent: Wednesday, November 07, 2018 7:47 AM
To: nbems@groups.io
Subject: Re: [nbems] Macro with modem changes

 

Hi Andy,

Probably your best route is to use an external script  that accesses FLdigi’s XML-RPC interface. 

http://www.w1hkj.com/FldigiHelp-3.21/html/xmlrpc_control_page.html

I’ve written a beacon timing script in Perl that changes the mode and transmits the beacon. Its deployed on several stations and is rock solid. 


Sean VE6SAR 

Dave
 

I cannot emphasize this any more vigorously ... DO NOT USE WINDOWS NOTEPAD ... it mangles end-of-line character sequences ... especially on the antique operating system WINDOWS-XP.

Instead, use the built in macro editor that is integral to fldigi.



If you insist on using an external text editor, then you should install either "Geany", or "NotePad++", both excellent text editors that do not mangle the file contents.

73, David, W1HKJ


On 11/7/18 5:25 PM, Randy wrote:

Thanks!  I’ll look at that.  I have continued experimenting with this and I believe the end of line/ line return format within my macros is causing the problem I have.  Minor changes to a working macro will create random operation until I again methodically format the text within the macro.  I’m using WinXP and Notepad.

 

 

-----Original Message-----
From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Sean Smith
Sent: Wednesday, November 07, 2018 7:47 AM
To: nbems@groups.io
Subject: Re: [nbems] Macro with modem changes

 

Hi Andy,

Probably your best route is to use an external script  that accesses FLdigi’s XML-RPC interface. 

http://www.w1hkj.com/FldigiHelp-3.21/html/xmlrpc_control_page.html

I’ve written a beacon timing script in Perl that changes the mode and transmits the beacon. Its deployed on several stations and is rock solid. 


Sean VE6SAR 


Sean Smith
 

For sure David,

I just posted the script to GitHub. 
https://github.com/ve6sar/FLdigi_Scheduler

I wrote this for a 60m propagation project so it has extra code to insert when it beacons into a database. If anyone is curious about the project the check out the web page at http://auroralpower.ca

Sean VE6SAR