Perhaps I live in the perfect County. We have been using FLDIGI/FLMSG for about 12 years now for Countywide and Regionwide exercises and our County has no problem using our FLMSG ICS-213 form, it

You guys realize that literally no one said not to use an ICS-213, right? Even if you read only the first line of my message after the salutation, you'd see the point of my message, and if you read

I agree.. If we can learn to use fast digital modes we can certainly learn to use current message formats (ICS-213) etc.

Ken AD5XJ This is the first time I have heard of this. Since we are on SSB, there is no RF "carrier" (like CW, AM, or FM) The "carrier" was suppressed in the radio (along with the lower

One additional thing I have discovered (which does not prevent FLDIGI from operating otherwise) is the carrier center is offset -31.1 Hz on both send and receive. Meaning a received signal from

Just to tie things up for anyone wondering what's going on, and we can discuss any of this off-list. (Probably QTC is the right place, see below.) I've been working on various methods to unify the

I guess the confusion came from watching the (overly IMHO) complex system you've been pushing for ARES and Ohio NTS since last summer. Sorry for misunderstanding. If the FLMSG

We switch back and forth between 160m at night and 80m at night winter to summer. Winter, 80 does have the tendency to go long. Yes, there are modes that offer much faster check-ins and I'm a big fan

Ed AI1R WA1YZN And folks who have tested OFDM modes this weekend: TU for reports. The testing on Saturday and Sunday morning on 80m SSB NVIS paths with the current version of OFDM500F showed

I'm sorry if my examples confused you. This problem came to light in a serious form during the VIGILANT GUARD 19 exercise with Ohio National Guard, MARS, Ohio EMA, and TSA were attempting to relay

Try unchecking the "Flrig PTT keys modem" setting in Fldigi's configuration for Flrig. Or, in Flrig's Poll settings, set "PTT" to '0' in the Additional Controls selection. But if you need to do

With all due respect to Mr. Curtin and the work he put into his proposal, I must disagree and state that he has the problem exactly backwards. It's time for ARRL/NTS to quit trying to

All: TL;DR: FLMSG uses incompatible field numbers on forms purporting to support origination and delivery of formats with numbers, such as the HICS-213. This leads to misunderstanding and undermining

Robin and the Ohio Digital Net When I listen to and check into the OHDN on 80m in the evening hours I notice that Olivia often has both deep fades for 1-3 seconds, and I hear stations from a great

That would be super. I've been focused on Olivia and never noticed the display of the FEC-overhead value in THOR. A display of 0 to 100% would work well. It makes sense to use the same display format

We know MFSK32 and THOR22 work well on 80m NVIS paths in the morning hours - our gold standards. We also know that background "noise" is the killer on 80m all day long. Today my noise

Hi Dave My guess is you are seeing stray RF in the shack, maybe try some clip on chokes would help. Marty kd8bj

I just started using Flrig instead of Hamlib. On a few occasions when I switched from Fldigi to a voice frequency and keyed up with my hand mic, it would stay keyed until I clicked “receive” on

John and all, We did a two person test on OFDM on Friday March 12th using Fldigi 4.1.18.17 Tester 1: Win 10 Laptop, FT-8900 radio, Newer Signalink, 2m VHF FM Tester 2: Win 7 laptop, FT-8900 radio,

Hi Robin, For some modes in Fldigi there already is an indication of the quality or FEC-headroom as a 0% - 100% value For PSK-based modes like PSKR, 8-PSK, and OFDM there is the Phase-Accuracy display