Date   
Re: Receiving computer detects and changes operating modem to match incoming message?

Sarah
 

Larry - I believe what you're saying (forgive me, I'm still relatively new to NBEMS) is that the  sweet spot and the high and low brackets on either side of it at 1500 for MT63-2KL   adjust when the modem changes -- is that correct?  (The High / Low brackets being the red, vertical lines on the waterfall.)

Assuming so  - Yes - we experienced that in the situation I mentioned at the start of this topic.  Both for the folks who received and me as the person who sent a transmission with the wrong modem setting.  In fact when I corrected the modem to the right setting to retransmit the message I had to manually go in and reset the sweet spot back to 1500. 

Our group decided the moral of the story was this:  if an NBEMS message is accidentally transmitted on the wrong modem then everyone needs to double check their modem and sweet spot settings and set them back to MT63-2KL and 1500 before new traffic proceeds.  

73, Sarah N6OPE


On 2/19/2018 3:43 AM, Larry Levesque wrote:
Another thing that get's overlooked is if your transmitted signal moves when you switch modes to outside of where thew receiving station would normally expect to see it with the RsID on.

In these cases, setting the "Searches passband" check box would look in the entire audio passband for the signal.
Also if you have the "Disables detector" check box set, it will disable the RsID after each successful decode and you will need to manually enable it again.



On Sun, Feb 18, 2018 at 10:53:18PM -0500, Charles Hargrove wrote:
A very simple rule is to turn on the receive and transmit ID for all
modes except SSB, CW, null and WWV.  Limit all of your connections to
1500 Hz by permanently setting it and leave RxID/TxID on at all times.

On 2/18/2018 10:48 PM, Greg Depew wrote:
I believe you also have to have Configure>ID>receive modes and transmit
modes all checked.   Even then our group still has trouble with modes
always shifting like they are supposed to.
-- 
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.

NYC-ARECS/RACES Nets 449.025/123.0 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org

NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32

"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan

"The more corrupt the state, the more it legislates." - Tacitus

"Molann an obair an fear" - Irish Saying
(The work praises the man.)

"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan




    

Re: Receiving computer detects and changes operating modem to match incoming message?

Larry Levesque
 

That is exactly what I am was trying to say.
Of course setting the "Searches entire passband" has it's own issues.
If another station appears well away from your conversation, and sends an TxID, your receiver could lock onto that signal and you could miss the message you were waiting for.

On Mon, Feb 19, 2018 at 07:04:49PM -0800, Sarah wrote:
Larry - I believe what you're saying (forgive me, I'm still relatively new
to NBEMS) is that the  sweet spot and the high and low brackets on either
side of it at 1500 for MT63-2KL   adjust when the modem changes -- is that
correct? (The High / Low brackets being the red, vertical lines on the
waterfall.)

Assuming so  - Yes - we experienced that in the situation I mentioned at the
start of this topic.  Both for the folks who received and me as the person
who sent a transmission with the wrong modem setting.  In fact when I
corrected the modem to the right setting to retransmit the message I had to
manually go in and reset the sweet spot back to 1500.

Our group decided the moral of the story was this:  if an NBEMS message is
accidentally transmitted on the wrong modem then everyone needs to double
check their modem and sweet spot settings and set them back to MT63-2KL and
1500 before new traffic proceeds.

73, Sarah N6OPE


On 2/19/2018 3:43 AM, Larry Levesque wrote:
Another thing that get's overlooked is if your transmitted signal moves when you switch modes to outside of where thew receiving station would normally expect to see it with the RsID on.

In these cases, setting the "Searches passband" check box would look in the entire audio passband for the signal.
Also if you have the "Disables detector" check box set, it will disable the RsID after each successful decode and you will need to manually enable it again.



On Sun, Feb 18, 2018 at 10:53:18PM -0500, Charles Hargrove wrote:
A very simple rule is to turn on the receive and transmit ID for all
modes except SSB, CW, null and WWV. Limit all of your connections to
1500 Hz by permanently setting it and leave RxID/TxID on at all times.

On 2/18/2018 10:48 PM, Greg Depew wrote:
I believe you also have to have Configure>ID>receive modes and transmit
modes all checked.   Even then our group still has trouble with modes
always shifting like they are supposed to.
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.

NYC-ARECS/RACES Nets 449.025/123.0 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org

NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32

"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan

"The more corrupt the state, the more it legislates." - Tacitus

"Molann an obair an fear" - Irish Saying
(The work praises the man.)

"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan


--
Larry Levesque
KA1VGM

flrig alpha posted

Dave
 

Date:   Fri Feb 23 08:53:54 2018 -0600

    Mode change
    
      * Fix seg fault in xml_server
        - occurred for specific mode changes when
          bandwidth selection is maximum value

Posted to http://www.w1hkj.com/alpha/flrig/

and Source Forge.

Fault only occurs when flrig and fldigi are connected and user changes transceiver mode at flrig: flrig closes without warning.

73, David, W1HKJ


Shortwave Radiogram, 24-25 Feb 2018

kd9xb
 

Shortwave Radiogram this weekend is all MFSK32.

The show includes all of the passages pertaining to shortwave in the Broadcasting Board of Governors FY2019 budget request.

And an item about how artists can render non-visible light detected by telescopes exploring outer space

Details:

http://swradiogram.net/post/171207198092/shortwave-radiogram-24-25-february-2018-digital



Kim
KD9XB

VARA virtual modem for HF and VHF

KC9SGV
 
Edited

Feb 15    
Edited Feb 18

First there were these digital data modes for Winlink....
Amtor, Pactor, Packet, Winmor, ARDOP...
Now VARA...
(< 300 baud, < 2.4 KHz bandwidth)

Maybe also for NBEMS ?

Very high quality Milspec thruput as fast as P3.
https://youtu.be/ke4V0pWVPawi

 Download VARA here:
https://rosmodem.wordpress.com

Bernie,
KC9SGV

 

Re: flrig 1.3.39 posted

W. T. Jones
 

I have noticed on .38 and .39 that there is a long latency when going from RX to TX with the FT-991. That latency is not present when using rigcat in Fldigi.

OS - Ubuntu 16.04 LTS.

Anyone noticing anything similar?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Fri, Feb 9, 2018 at 11:51 AM, Dave <w1hkj@...> wrote:
at http://www.w1hkj.com/files/flrig/

and Source Forge.

Version 1.3.39 - Maintenance release

  Memory delete
    * fix segfault when deleting single entry in list

  OS X build script
    * Modify to only create dmg with dylibs

  IC7850
    * addition of 7850 transceiver class

  IC706MKG
    * Update bandwidth set/get
    * Update split operation
    * Added special 706MKIIG bandwidth status parameter
      - file IC-706MKIIG.prefs must be manually edited
        to effect filter selection
    * Changes by David, W1HKJ and Steve, AG7GN

  civ tests
    * debugging code for testing CI-V interface

  restore ab
    * correction to vfoA/B restore on program exit

  TT550
    * fix start up seg fault, vfo pointer not initialized

73, David, W1HKJ




Re: flrig 1.3.39 posted

W. T. Jones
 

Never Mind! Found the problem. Too much polling in the FT-991 profile.

Will there be a new manual for Flrig .39?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Sun, Feb 25, 2018 at 2:28 PM, W. T. Jones <wn3lif@...> wrote:
I have noticed on .38 and .39 that there is a long latency when going from RX to TX with the FT-991. That latency is not present when using rigcat in Fldigi.

OS - Ubuntu 16.04 LTS.

Anyone noticing anything similar?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Fri, Feb 9, 2018 at 11:51 AM, Dave <w1hkj@...> wrote:
at http://www.w1hkj.com/files/flrig/

and Source Forge.

Version 1.3.39 - Maintenance release

  Memory delete
    * fix segfault when deleting single entry in list

  OS X build script
    * Modify to only create dmg with dylibs

  IC7850
    * addition of 7850 transceiver class

  IC706MKG
    * Update bandwidth set/get
    * Update split operation
    * Added special 706MKIIG bandwidth status parameter
      - file IC-706MKIIG.prefs must be manually edited
        to effect filter selection
    * Changes by David, W1HKJ and Steve, AG7GN

  civ tests
    * debugging code for testing CI-V interface

  restore ab
    * correction to vfoA/B restore on program exit

  TT550
    * fix start up seg fault, vfo pointer not initialized

73, David, W1HKJ





Re: flrig 1.3.39 posted

Dave
 

You can submit recommendations for manual changes to me at the bellsouth email address.  What are your settings for the FT-991 polling that provide satisfactory performance?

73, David, W1HKJ

On 02/25/2018 10:10 PM, W. T. Jones wrote:
Never Mind! Found the problem. Too much polling in the FT-991 profile.

Will there be a new manual for Flrig .39?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Sun, Feb 25, 2018 at 2:28 PM, W. T. Jones <wn3lif@...> wrote:
I have noticed on .38 and .39 that there is a long latency when going from RX to TX with the FT-991. That latency is not present when using rigcat in Fldigi.

OS - Ubuntu 16.04 LTS.

Anyone noticing anything similar?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Fri, Feb 9, 2018 at 11:51 AM, Dave <w1hkj@...> wrote:
at http://www.w1hkj.com/files/flrig/

and Source Forge.

Version 1.3.39 - Maintenance release

  Memory delete
    * fix segfault when deleting single entry in list

  OS X build script
    * Modify to only create dmg with dylibs

  IC7850
    * addition of 7850 transceiver class

  IC706MKG
    * Update bandwidth set/get
    * Update split operation
    * Added special 706MKIIG bandwidth status parameter
      - file IC-706MKIIG.prefs must be manually edited
        to effect filter selection
    * Changes by David, W1HKJ and Steve, AG7GN

  civ tests
    * debugging code for testing CI-V interface

  restore ab
    * correction to vfoA/B restore on program exit

  TT550
    * fix start up seg fault, vfo pointer not initialized

73, David, W1HKJ






Re: flrig 1.3.39 posted

W. T. Jones
 

Good Afternoon Dave,

It was really a brute force experiment. The "Additional Controls" were all set to 1. I simply set them all to 0.

That left the Meters and Operating Controls set to 1. That brought the latency to 0 as far as a human could tell. So I was just asking for too much information that really wasn't necessary.

I will PM you on the recommendations for the manual.

Thanks again.


Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Mon, Feb 26, 2018 at 6:40 AM, Dave <w1hkj@...> wrote:
You can submit recommendations for manual changes to me at the bellsouth email address.  What are your settings for the FT-991 polling that provide satisfactory performance?

73, David, W1HKJ

On 02/25/2018 10:10 PM, W. T. Jones wrote:
Never Mind! Found the problem. Too much polling in the FT-991 profile.

Will there be a new manual for Flrig .39?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Sun, Feb 25, 2018 at 2:28 PM, W. T. Jones <wn3lif@...> wrote:
I have noticed on .38 and .39 that there is a long latency when going from RX to TX with the FT-991. That latency is not present when using rigcat in Fldigi.

OS - Ubuntu 16.04 LTS.

Anyone noticing anything similar?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Fri, Feb 9, 2018 at 11:51 AM, Dave <w1hkj@...> wrote:
at http://www.w1hkj.com/files/flrig/

and Source Forge.

Version 1.3.39 - Maintenance release

  Memory delete
    * fix segfault when deleting single entry in list

  OS X build script
    * Modify to only create dmg with dylibs

  IC7850
    * addition of 7850 transceiver class

  IC706MKG
    * Update bandwidth set/get
    * Update split operation
    * Added special 706MKIIG bandwidth status parameter
      - file IC-706MKIIG.prefs must be manually edited
        to effect filter selection
    * Changes by David, W1HKJ and Steve, AG7GN

  civ tests
    * debugging code for testing CI-V interface

  restore ab
    * correction to vfoA/B restore on program exit

  TT550
    * fix start up seg fault, vfo pointer not initialized

73, David, W1HKJ







Re: flrig 1.3.39 posted

Dave
 

Try running the CAT port at the highest baud rate available.  Do not use auto baud rate detection on the transceiver.  I usually run my IC-7200 with Meters and Operating Control selections at 1, and Additional Controls all at 4.  The CAT baud is 19200, the highest available on that transceiver.

Retries : 2
Retry Interval : 50
Cmds: 5
Poll intvl: 50
Byte intvl: 0

Changes made at flrig all take priority over polling, so those should appear almost immediately at the transceiver.

Dave

On 02/26/2018 12:39 PM, W. T. Jones wrote:
Good Afternoon Dave,

It was really a brute force experiment. The "Additional Controls" were all set to 1. I simply set them all to 0.

That left the Meters and Operating Controls set to 1. That brought the latency to 0 as far as a human could tell. So I was just asking for too much information that really wasn't necessary.

I will PM you on the recommendations for the manual.

Thanks again.


Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Mon, Feb 26, 2018 at 6:40 AM, Dave <w1hkj@...> wrote:
You can submit recommendations for manual changes to me at the bellsouth email address.  What are your settings for the FT-991 polling that provide satisfactory performance?

73, David, W1HKJ

On 02/25/2018 10:10 PM, W. T. Jones wrote:
Never Mind! Found the problem. Too much polling in the FT-991 profile.

Will there be a new manual for Flrig .39?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Sun, Feb 25, 2018 at 2:28 PM, W. T. Jones <wn3lif@...> wrote:
I have noticed on .38 and .39 that there is a long latency when going from RX to TX with the FT-991. That latency is not present when using rigcat in Fldigi.

OS - Ubuntu 16.04 LTS.

Anyone noticing anything similar?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Fri, Feb 9, 2018 at 11:51 AM, Dave <w1hkj@...> wrote:
at http://www.w1hkj.com/files/flrig/

and Source Forge.

Version 1.3.39 - Maintenance release

  Memory delete
    * fix segfault when deleting single entry in list

  OS X build script
    * Modify to only create dmg with dylibs

  IC7850
    * addition of 7850 transceiver class

  IC706MKG
    * Update bandwidth set/get
    * Update split operation
    * Added special 706MKIIG bandwidth status parameter
      - file IC-706MKIIG.prefs must be manually edited
        to effect filter selection
    * Changes by David, W1HKJ and Steve, AG7GN

  civ tests
    * debugging code for testing CI-V interface

  restore ab
    * correction to vfoA/B restore on program exit

  TT550
    * fix start up seg fault, vfo pointer not initialized

73, David, W1HKJ








Re: flrig 1.3.39 posted

W. T. Jones
 

I will give these a try. Tnx.

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Mon, Feb 26, 2018 at 3:08 PM, Dave <w1hkj@...> wrote:
Try running the CAT port at the highest baud rate available.  Do not use auto baud rate detection on the transceiver.  I usually run my IC-7200 with Meters and Operating Control selections at 1, and Additional Controls all at 4.  The CAT baud is 19200, the highest available on that transceiver.

Retries : 2
Retry Interval : 50
Cmds: 5
Poll intvl: 50
Byte intvl: 0

Changes made at flrig all take priority over polling, so those should appear almost immediately at the transceiver.

Dave

On 02/26/2018 12:39 PM, W. T. Jones wrote:
Good Afternoon Dave,

It was really a brute force experiment. The "Additional Controls" were all set to 1. I simply set them all to 0.

That left the Meters and Operating Controls set to 1. That brought the latency to 0 as far as a human could tell. So I was just asking for too much information that really wasn't necessary.

I will PM you on the recommendations for the manual.

Thanks again.


Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Mon, Feb 26, 2018 at 6:40 AM, Dave <w1hkj@...> wrote:
You can submit recommendations for manual changes to me at the bellsouth email address.  What are your settings for the FT-991 polling that provide satisfactory performance?

73, David, W1HKJ

On 02/25/2018 10:10 PM, W. T. Jones wrote:
Never Mind! Found the problem. Too much polling in the FT-991 profile.

Will there be a new manual for Flrig .39?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Sun, Feb 25, 2018 at 2:28 PM, W. T. Jones <wn3lif@...> wrote:
I have noticed on .38 and .39 that there is a long latency when going from RX to TX with the FT-991. That latency is not present when using rigcat in Fldigi.

OS - Ubuntu 16.04 LTS.

Anyone noticing anything similar?

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Fri, Feb 9, 2018 at 11:51 AM, Dave <w1hkj@...> wrote:
at http://www.w1hkj.com/files/flrig/

and Source Forge.

Version 1.3.39 - Maintenance release

  Memory delete
    * fix segfault when deleting single entry in list

  OS X build script
    * Modify to only create dmg with dylibs

  IC7850
    * addition of 7850 transceiver class

  IC706MKG
    * Update bandwidth set/get
    * Update split operation
    * Added special 706MKIIG bandwidth status parameter
      - file IC-706MKIIG.prefs must be manually edited
        to effect filter selection
    * Changes by David, W1HKJ and Steve, AG7GN

  civ tests
    * debugging code for testing CI-V interface

  restore ab
    * correction to vfoA/B restore on program exit

  TT550
    * fix start up seg fault, vfo pointer not initialized

73, David, W1HKJ









Re: fldigi alpha posted 4.0.17.17

Ron
 

Dave,

I wanted to report that a group of us have been testing Fldigi version 4.0.17.17, primarily with the 8PSK125F and 8PSK250F.  Decoding has been very good.  Thanks for your hard work.

73, Ron NY3J

On 2/17/2018 12:03 PM, Dave wrote:
at http://www.w1hkj.com.  Please report test results back to this forum.  The tinyFSK interface code has been tested on Linux, OS X and Windows by W1HKJ and HA2OS.

Includes the following changes from 4.0.16

    tinyFSK
      * Add interface and support code for tinyFSK Arduino FSK keyer
      * Modify waterfall frequency display for transceiver FSK
      * Modify dxcluster qsy operations to provide correct QSY
        for transceiver FSK
      * Add TTY transceiver mode recognition if transceiver mode
        string contains RTTY or FSK

    fsq/ifkp audit logs
      * Enable audit log open/close from configuration panel
      * Correct date-time stamp in logs

    RTTY browser decode
      * fix browser decoder sense when transceiver is in LSB
        type mode, i.e. FSK, LSB, LSB-D etc.

    8pskF
      * Fixed bug in 8psk 125F/250F init code
        - Bad constraint length was causing decoder to fail
      * New preamble for 8PSK FEC modes
        - FEC modes preamble is now a continuous tone at center-frequency
        - Gives reference for clicking &  selecting signal on waterfall.
        - Is backwards compatible with  previous-version 8psk preambles
      * Adjusted 8PSK-F modes flush/postamble length much longer
       - Can visually see the inlv flush and postamble "tail" on  waterfall
       - New flust/postamble extends beyond data, to prevent cutoff
      * Code, formatting, and comments cleaned-up for 8PSK code

User Interface Changes to support both Transceiver FSK and the tinyFSK Arduino unit





73, David, W1HKJ


Re: fldigi alpha posted 4.0.17.17

Dave
 

You're welcome Ron and thanks for the feedback.

Dave

On 02/26/2018 08:58 PM, Ron wrote:
Dave,

I wanted to report that a group of us have been testing Fldigi version 4.0.17.17, primarily with the 8PSK125F and 8PSK250F.  Decoding has been very good.  Thanks for your hard work.

73, Ron NY3J

Re: Help with port audio problems IC-7200

Dave
 

Have you resolved this issue?

David, W1HKJ

On 02/13/2018 08:52 PM, Jeff wrote:
Hello and thanks in advance for any possible help.

My buddy and I both have IC-7200 radios and are using the latest version
of FLDigi.
Although our laptops are different brands, we are both using windows 7.
My radio and laptop operate fine with both rig control and usb audio
connecting to FLDigi. My laptop also works fine with his radio. His
laptop on the other hand will rig control the radio but the problem comes
with the audio connection. In windows device manager, usb audio shows up
when the usb cable is plugged in. But in FLDigi, under sound card settings,
when the port audio box is checked, a large box pops up and says Port
Audio Device Not Available.
Any thoughts on where to look for this problem?

Thanks and 73
Jeff Montgomery
WB4WXD

Navigator FSK support added to fldigi

Dave
 

FSK control and data stream i/o for both the Navigator and a tinyFSK device has been added to this version of fldigi.

alpha version 4.0.17.32

  Logbook read
    * Make Rx panel announcement of read user optional

  Navigator
    * Add Navigator terminal unit support for FSK
      - options setting panel

  tinyFSK
    * Add interface and support code for tinyFSK Arduino FSK keyer
    * Modify waterfall frequency display for transceiver FSK
    * Modify dxcluster qsy operations to provide correct QSY
      for transceiver FSK
    * Add TTY transceiver mode recognition if transceiver mode
      string contains RTTY or FSK

  Modem start frequency
    * Change initialization of modem start up frequency
      - prevent unintended start @ 1000 Hz for every change in mode

  fsq/ifkp audit logs
    * Enable audit log open/close from configuration panel
    * Correct date-time stamp in logs

  RTTY browser decode
    * fix browser decoder sense when transceiver is in LSB
      type mode, i.e. FSK, LSB, LSB-D etc.

  8pskF
    * Fixed bug in 8psk 125F/250F init code
      - Bad constraint length was causing decoder to fail
    * New preamble for 8PSK FEC modes
      - FEC modes preamble is now a continuous tone at center-frequency
      - Gives reference for clicking &  selecting signal on waterfall.
      - Is backwards compatible with  previous-version 8psk preambles
    * Adjusted 8PSK-F modes flush/postamble length much longer
     - Can visually see the inlv flush and postamble "tail" on  waterfall
     - New flust/postamble extends beyond data, to prevent cutoff
    * Code, formatting, and comments cleaned-up for 8PSK code

Installation and source files may be downloaded at http://www.w1hkj.com

and at Source Forge.


Navigator:



Select the serial port (COM device on Windows) for both the FSK and Configuration ports on the Navigator.  Press the Config button and modify the interface controls for the intended RTTY usage.  After configuration adjustment the Config button can be pressed again to remove that connection to the Navigator (or leave it connected).  Press the FSK button to connect to the FSK port.  Your transceiver should be in an RTTY mode not a sideband mode.

tinyFSK interface:



Select the serial/COM port, set the baud rate and whether or not the RTTY signal is a Plus or Minus polarity (to the transceiver port).  Press the Connect button.  As with the Navigator, the transceiver should be in an RTTY mode and not a sideband mode.

Both control and data stream i/o with the tinyFSK will appear in the serial I/O text panel.

Both:
On the TTY/Tx tab, set the Mark frequency and shift



Most modern transceivers will allow the operator to select a Mark frequency of 1275 and 2125.  fldigi needs that information to correctly decode and adjust for fldigi implemented QSY operations.

73, David, W1HKJ

Not Receiving Files in FlAmp

Chuck Farrell
 

I participate in a digital training net and a curious thing keeps happening with one of our members. He is running the latest version of FlDigi and FlAmp under Windows 7, but does not receive any FlAmp files where the file name contains a (valid) but non alphanumeric character. For example a file named file_name is not received by FlAmp for him but the rest of us receive it just fine. It shows 0 blocks received. Save the file without the underscore and resend and he receives it perfectly. We thought maybe character set in FlDigi, but that's the same as the rest of us. Ideas?

Thanks,

Chuck
W3AFV

Re: Not Receiving Files in FlAmp

Larry Levesque
 

Could it be his Windows character set?
Does he have a notifier set that would cause an issue?
Did he try it with his antivirus software/ firewall off (highly recommend physically disconnecting from internet when trying this last part)

On Tue, Feb 27, 2018 at 01:14:06PM -0800, Chuck Farrell wrote:
I participate in a digital training net and a curious thing keeps happening with one of our members. He is running the latest version of FlDigi and FlAmp under Windows 7, but does not receive any FlAmp files where the file name contains a (valid) but non alphanumeric character. For example a file named file_name is not received by FlAmp for him but the rest of us receive it just fine. It shows 0 blocks received. Save the file without the underscore and resend and he receives it perfectly. We thought maybe character set in FlDigi, but that's the same as the rest of us. Ideas?

Thanks,

Chuck
W3AFV
--
Larry Levesque
KA1VGM

Re: Navigator FSK support added to fldigi

Frank Olaughlin
 

Dave,

Just wanted to drop a note to you before it got too busy here. We had a test of 4.0.17.32 a couple of days ago.....tested all of 8PSK and used flamp and flmsg successfully oh VHF simplex....no errors. It's going to get busy in my area.....expecting 90mph winds and damaging coastal surge to batter my area for long duration event.....will be setting up NBEMS for actual operations on Friday morning here on Cape Cod/Islands

73'
Frank WQ1O

Re: Navigator FSK support added to fldigi

Dave
 

Good luck with the bad WX Frank.  We just finished 11 days of straight rain.  Our rain gauge showed over 10" of rain in that period.  We only had 3 days without rain in February.  Thank goodness there were no tornadoes.

Dave

On 03/01/2018 05:42 PM, Frank Olaughlin wrote:
Dave,

Just wanted to drop a note to you before it got too busy here. We had a test of 4.0.17.32 a couple of days ago.....tested all of 8PSK and used flamp and flmsg successfully oh VHF simplex....no errors. It's going to get busy in my area.....expecting 90mph winds and damaging coastal surge to batter my area for long duration event.....will be setting up NBEMS for actual operations on Friday morning here on Cape Cod/Islands

73'
Frank WQ1O

Re: VARA virtual modem for HF and VHF

la7um
 

Bernie,
Fldigi is running on Linux, Mac OSX and Windows, maybe even more recently.
For me the ability of running on the MAC is a winner.
I do run Winlink RMS Trimode as server and RMS Express a client, both on Windows machines, but I miss greatly the great FLDIGI ability of running on all platforms.
AFAIK VARA may remain on Windows only.
Perhaps the Open Source  ARDOP also can run on MAC out of the box and thus later has a greater possible future as part  of Fldigi?

LA7UM Finn