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

Larry Levesque
 

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

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

Charles Hargrove
 

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?

Greg Depew
 

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. 



Greg KB3KBR Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Sarah <n6ope@...>
Date: 2/18/18 22:23 (GMT-05:00)
To: nbems@groups.io
Subject: Re: [nbems] Receiving computer detects and changes operating modem to match incoming message?

Hi Jim --  thanks for writing back.  Your explanation is exactly what I was told and it makes sense.  And I do understand why that feature exists.  I was just puzzled that I couldn't duplicate it in tests. 

I don't think the fact that I was just sending messages back and forth between two laptops on a table without doing actual radio transmissions would have had any effect.  After all the computer doesn't know whether the sound entering its microphone comes from a radio speaker or another computer speaker or me just whistling ....   I'll have to try the tests again. 

73, Sarah N6OPE


On 2/18/2018 7:04 PM, Jim Jones wrote:
When you have both of the boxes (RxID and TxID) ticked marked, then when you
transmit, the TxID will send a code of what mode your using. The receiving station
would need to have there RxID ticked on and then if they are not on the same mode
it will automatically change to the mode your sending in.  The same would happen to
your station, if you have the RxID ticked and the sending station has his TxID ticked and
is sending in a different mode to you, your FLdigi will change to the correct mode and
you will copy the traffic.  I use them all the time.
73
Jim N9DIX



On 2/18/2018 20:44, Sarah wrote:

A couple of weeks ago I inadvertently transmitted a message during an NBEMS net with the operating modem set to one of the MFSK protocols instead of MT63-2KL.   Three or four people received that transmission and they all had the same experience:  their computers apparently recognized the incoming modem protocol and “automatically” changed from MT63 to MFSK.  We chalked it up to good experience but weren’t sure why it happened.  A ham with a lot more experience than me later explained that FLDIDI will automatically make this adjustment – i.e., it will change to match the operating modem of an incoming message when the and TxID buttons [top, right corner of the FLDIGI screen] are both clicked on. 


<snip>

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

Sarah
 

Hi Jim --  thanks for writing back.  Your explanation is exactly what I was told and it makes sense.  And I do understand why that feature exists.  I was just puzzled that I couldn't duplicate it in tests. 

I don't think the fact that I was just sending messages back and forth between two laptops on a table without doing actual radio transmissions would have had any effect.  After all the computer doesn't know whether the sound entering its microphone comes from a radio speaker or another computer speaker or me just whistling ....   I'll have to try the tests again. 

73, Sarah N6OPE


On 2/18/2018 7:04 PM, Jim Jones wrote:
When you have both of the boxes (RxID and TxID) ticked marked, then when you
transmit, the TxID will send a code of what mode your using. The receiving station
would need to have there RxID ticked on and then if they are not on the same mode
it will automatically change to the mode your sending in.  The same would happen to
your station, if you have the RxID ticked and the sending station has his TxID ticked and
is sending in a different mode to you, your FLdigi will change to the correct mode and
you will copy the traffic.  I use them all the time.
73
Jim N9DIX



On 2/18/2018 20:44, Sarah wrote:

A couple of weeks ago I inadvertently transmitted a message during an NBEMS net with the operating modem set to one of the MFSK protocols instead of MT63-2KL.   Three or four people received that transmission and they all had the same experience:  their computers apparently recognized the incoming modem protocol and “automatically” changed from MT63 to MFSK.  We chalked it up to good experience but weren’t sure why it happened.  A ham with a lot more experience than me later explained that FLDIDI will automatically make this adjustment – i.e., it will change to match the operating modem of an incoming message when the and TxID buttons [top, right corner of the FLDIGI screen] are both clicked on. 


<snip>

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

Jim Jones
 

When you have both of the boxes (RxID and TxID) ticked marked, then when you
transmit, the TxID will send a code of what mode your using. The receiving station
would need to have there RxID ticked on and then if they are not on the same mode
it will automatically change to the mode your sending in.  The same would happen to
your station, if you have the RxID ticked and the sending station has his TxID ticked and
is sending in a different mode to you, your FLdigi will change to the correct mode and
you will copy the traffic.  I use them all the time.
73
Jim N9DIX



On 2/18/2018 20:44, Sarah wrote:

A couple of weeks ago I inadvertently transmitted a message during an NBEMS net with the operating modem set to one of the MFSK protocols instead of MT63-2KL.   Three or four people received that transmission and they all had the same experience:  their computers apparently recognized the incoming modem protocol and “automatically” changed from MT63 to MFSK.  We chalked it up to good experience but weren’t sure why it happened.  A ham with a lot more experience than me later explained that FLDIDI will automatically make this adjustment – i.e., it will change to match the operating modem of an incoming message when the and TxID buttons [top, right corner of the FLDIGI screen] are both clicked on. 


<snip>

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

Sarah
 

A couple of weeks ago I inadvertently transmitted a message during an NBEMS net with the operating modem set to one of the MFSK protocols instead of MT63-2KL.   Three or four people received that transmission and they all had the same experience:  their computers apparently recognized the incoming modem protocol and “automatically” changed from MT63 to MFSK.  We chalked it up to good experience but weren’t sure why it happened.  A ham with a lot more experience than me later explained that FLDIDI will automatically make this adjustment – i.e., it will change to match the operating modem of an incoming message when the and TxID buttons [top, right corner of the FLDIGI screen] are both clicked on. 

 

I tested this explanation and could not duplicate an “automatic” change by FLDIGI.  [Testing method explained below.]  Therefore I suspect there is some other configuration setting at work.  Any ideas or explanations would be appreciated!

 

Test set up:  Two laptop computers – one running Windows 7 Professional, one running Windows 7 Home Premium.  For these test I am not transmitting NBEMS over radio; just accoustic sound transfer between the two computers set across from each other on a table. Both computers running FLDIGI version 4.0.11 and FLMSG version 4.0.3.

Re: fldigi alpha posted 4.0.17.17

Dave
 

Thank  you for the report Frank, and glad to hear that your health permits.

Dave

On 02/17/2018 05:21 PM, Frank Olaughlin wrote:
Dave,

We conducted a fast arranged test session using Fldigi-4.0.17.17 today (02-17-18)

Computers used:

Dell Lattitude E4310 I5 Win 7
Dell D630 T7500 Win 7
Dell E5410 I3 Win 7

VHF 2 meter FM simplex Signals S5-S7

All using Signalink USB

All 8PSK modems were tested on Flmsg 4.05 and Flamp-2.2.03

Results:

27 messages and files passed on Flmsg and Flamp.

No errors occurred.

Notes:

Noted that earlier issues with 8PSK125F and 8PSK250F were no longer present

Despite a noisy signal path, 8PSK1200 and 8PSK1000F worked as well as they normally have. The pilot tone on 1200F has really been of great benefit for some time now

We continue to use 8PSK1200F as a standard for Cape Cod and Islands ARES. 8PSK1000F is our secondary

In sum, alpha version performed well, at least in the 8PSK modems tested. I'm sure others will submit their results for other modems and other features of the program. Thanks for all the great work!

73'
Frank
WQ1O
Cape Cod and Islands ARES DEC


Re: fldigi alpha posted 4.0.17.17

Frank Olaughlin
 

Dave,

We conducted a fast arranged test session using Fldigi-4.0.17.17 today (02-17-18)

Computers used:

Dell Lattitude E4310 I5 Win 7
Dell D630 T7500 Win 7
Dell E5410 I3 Win 7

VHF 2 meter FM simplex Signals S5-S7

All using Signalink USB

All 8PSK modems were tested on Flmsg 4.05 and Flamp-2.2.03

Results:

27 messages and files passed on Flmsg and Flamp.

No errors occurred.

Notes:

Noted that earlier issues with 8PSK125F and 8PSK250F were no longer present

Despite a noisy signal path, 8PSK1200 and 8PSK1000F worked as well as they normally have. The pilot tone on 1200F has really been of great benefit for some time now

We continue to use 8PSK1200F as a standard for Cape Cod and Islands ARES. 8PSK1000F is our secondary

In sum, alpha version performed well, at least in the 8PSK modems tested. I'm sure others will submit their results for other modems and other features of the program. Thanks for all the great work!

73'
Frank
WQ1O
Cape Cod and Islands ARES DEC

fldigi alpha posted 4.0.17.17

Dave
 

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

Shortwave Radiogram, 17-18 Feb

kd9xb
 

Shortwave Radiogram this weekend is all MFKS32.


Minutes into the show ...

 1:32  Program preview
 2:38  New Twitter feed tracks FCC experimental licenses*
 6:55  Search for an ionosphere for signs of planetary life*
16:58  Astronomers image 40-light-year-wide space donut*
23:12  Olympics image*
25:33  Closing announcements

Details:
http://swradiogram.net/post/170946115007/shortwave-radiogram-17-18-february-2018

Kim
KD9XB

Re: Fldigi - N1MM - CW Reader issues

vu2ae@...
 

Yes, the com ports were different in the new laptop and I have used the right port numbers!

Re: Fldigi - N1MM - CW Reader issues

k4pwo <k4pwo@...>
 

Did you change your COM ports to the ones setup in the new laptop?  They probably won’t be the same, especially if they are virtual USB serial ports.  Look at Device Manager to be sure.

 

Perry K4PWO

 

From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of vu2ae@...
Sent: Friday, February 16, 2018 12:02 AM
To: nbems@groups.io
Subject: [nbems] Fldigi - N1MM - CW Reader issues

 

I have been using Fldigi ver 3.23.07.03 on my pc running Windows 7 for over 3 years.  I use rig blaster advantage, and I have split the ports for Radio control, CW/FSK control and PTT Control.  My rig is a TS 480 SAT. It is just working very well standalone as well as when I use it within N1MM plus for CW.  I have copied Fldigi.exe to another folder which I have referenced to and use when I call it up from within N1MM logger.

 

My old hard disk has developed a problem and now I am trying to shift a new laptop running Windows 10.  I downloaded Fldigi ver 4.0.16 and set it up exactly the way I had done it earlier.  I have two problems - (1) When I connect to Fldigi standalone, the software is not reading the frequency from my rig (2) When I try to pull up Fldigi within N1MM plus for CW, the s/w just doesn't come up and N1MM stops responding.

 

I have attached 3 pics for my old setup which is working fine and the same setup is just not working with Fldigi ver 4.0.16. 

 

I would appreciate it if you could guide me to get things working ;  also, if you can send me a link to download the old version Fldigi ver 3.23.07.03, I can try that as well on my new laptop

Fldigi - N1MM - CW Reader issues

vu2ae@...
 

I have been using Fldigi ver 3.23.07.03 on my pc running Windows 7 for over 3 years.  I use rig blaster advantage, and I have split the ports for Radio control, CW/FSK control and PTT Control.  My rig is a TS 480 SAT. It is just working very well standalone as well as when I use it within N1MM plus for CW.  I have copied Fldigi.exe to another folder which I have referenced to and use when I call it up from within N1MM logger.

 

My old hard disk has developed a problem and now I am trying to shift a new laptop running Windows 10.  I downloaded Fldigi ver 4.0.16 and set it up exactly the way I had done it earlier.  I have two problems - (1) When I connect to Fldigi standalone, the software is not reading the frequency from my rig (2) When I try to pull up Fldigi within N1MM plus for CW, the s/w just doesn't come up and N1MM stops responding.

 

I have attached 3 pics for my old setup which is working fine and the same setup is just not working with Fldigi ver 4.0.16. 

 

I would appreciate it if you could guide me to get things working ;  also, if you can send me a link to download the old version Fldigi ver 3.23.07.03, I can try that as well on my new laptop

Re: Help with port audio problems IC-7200

Edward Kasprowicz
 

Sri late getting back Jeff. 1st, always try another cable. 2nd, check Device manager and make sure you have no
little light bulbs with a ring around them, called glitches and sure U know this! 3rd, try uninstalling and reinstalling program. If all those fail, U may have a sound card problem, a driver ?  Set up and settings too. Really hard to tell without seeing it.
Russ is pretty good at PC problems as well as Jay. May want to reach out to one of them or hopefully some one else got back to U. For All U do to help Us in the Club. Wud think some one would step up, hope so and Thanks too for all you do.
Ltr/73s
EdK/N0EK


On Tuesday, February 13, 2018 9:53 PM, Jeff <jmonty@...> 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






Re: Help with port audio problems IC-7200

k4pwo <k4pwo@...>
 

Update Windows 7 to SP1... sounds like the none working laptop my be behind.

Perry K4PWO

-----Original Message-----
From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Jeff
Sent: Tuesday, February 13, 2018 8:53 PM
To: nbems@groups.io
Subject: [nbems] Help with port audio problems IC-7200


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

Help with port audio problems IC-7200

Jeff
 

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

Custom Form question - New Hampshire HICS-213 Form

George Blakeslee
 

de N1GB   George


---------- Forwarded message ----------
From: Jay Taft <jltaft@...>
Date: Fri, Feb 9, 2018 at 10:09 AM
Subject: HICS-213 Question
To: George Blakeslee <george.blakeslee@...>
Cc: "Ed Leduc Sr. KA1IJN" <ham1radio@...>, Jay Taft K1EHZ <jltaft@...>


Hi George,

We have a question perhaps you can help with.

When an HICS-213 is received we get the error message shown below. When the error message is closed, the skeleton HICS-213 opens ok. Do you know how to avoid getting the error? I can't find anything about it on-line.


I should mention that I am using FLdigi 4.0.10 and FLmsg 4.0.3.  

This happens on a Win10 laptop but not on a Win7 laptop. I have compared the settings on both and can't find a difference.

Many thanks,

Jay
K1EHZ






--
George Blakeslee

Shortwave Radiogram, 10-11 Feb

kd9xb
 

Shortwave Radiogram includes an item about World Radio Day on 13 February. 

Most of the show is in MFSK32, with four images.  There will also be an experiment comparing the Olivia 8-2000, 8-1000, and 8-500 modes: does it help to concentrate the data in narrower slices of bandwidth within the 2000+ Hz available in a shortwave broadcast sideband?  

Details and schedule:
http://swradiogram.net/post/170688809937/shortwave-radiogram-10-11-february-2018

Kim
KD9XB

Re: Remote operation with ICOM 7300

Dave
 

On Windows I would recommend installing
  • Team Viewer on server and remote computer
  • flrig
  • fldigi
Control the 7300 with flrig and connect it to fldigi iaw flrig as fldigi xcvr controller.

Run Team Viewer on the server and then connect to the server from any computer, Linux, Windows, OS-X, Android running a Team Viewer client.  The client will have full control over the remote computer/transceiver combination.  Access to the TV server can be over LAN or WAN.

I have used Team Viewer to debug flrig/fldigi on user computers over WAN.  It works very well.

73, David, W1HKJ

On 02/09/2018 12:29 PM, Lew wrote:
A lot has happened at Brooklyn Tech / W2CXN since this original
posting.  We seem to have gotten the 7300 working remotely with the
RS-BA1 package on SSB.  Our next step is to get FLDIGI installed and
working.

I assume that we should install FLDIGI on the "server" PC, near the radio.
Should we be using FLRIG or will the RS-BA1 package run FLDIGI?

Up to now, we have been running FLRIG and FLDIGI LINUX versions, but the
new configuration requires Windows.

Suggestions are welcome.

73, Lew
n2rq@...



On 10/28/2017 12:07 PM, Lew wrote:
If we only wanted to run digital modes, we understand that FLRIG and
FLDIGI are fine. The reason for using RS-BA1 is to also run phone (SSB
and FM).

The remote operation is necessitated by the radio being on the 10th
floor and the club meeting space on the 2nd floor of the school.

As the students and I get familiar with the software, I suppose we
would have choices like:
control FLDIGI with RS-BA1;
shut down RS-BA1 and start up FLRIG and visa versa;
phone via FLRIG.

I have posted a similar question to the IC-7300 yahoo group.
So far we have had no responses from anyone with a challenge similar
to ours.

Suggestions are welcome.

Thanks
73 de Lew
n2rq@...







Re: Remote operation with ICOM 7300

Lew
 

A lot has happened at Brooklyn Tech / W2CXN since this original
posting.  We seem to have gotten the 7300 working remotely with the
RS-BA1 package on SSB.  Our next step is to get FLDIGI installed and
working.

I assume that we should install FLDIGI on the "server" PC, near the radio.
Should we be using FLRIG or will the RS-BA1 package run FLDIGI?

Up to now, we have been running FLRIG and FLDIGI LINUX versions, but the
new configuration requires Windows.

Suggestions are welcome.

73, Lew
n2rq@...

On 10/28/2017 12:07 PM, Lew wrote:
If we only wanted to run digital modes, we understand that FLRIG and
FLDIGI are fine. The reason for using RS-BA1 is to also run phone (SSB
and FM).

The remote operation is necessitated by the radio being on the 10th
floor and the club meeting space on the 2nd floor of the school.

As the students and I get familiar with the software, I suppose we
would have choices like:
control FLDIGI with RS-BA1;
shut down RS-BA1 and start up FLRIG and visa versa;
phone via FLRIG.

I have posted a similar question to the IC-7300 yahoo group.
So far we have had no responses from anyone with a challenge similar
to ours.

Suggestions are welcome.

Thanks
73 de Lew
n2rq@...