It turns out this didn't work:
http://ozreport.com/23.78#1.

I still got the warning for danger zones even after I made the change to not get
that warning on the Flytec 6030. That's because the danger zones in
Flytec Airspace formatted file for Florida don't have a designation after
AT.

See here:

AC Q

AT

AD

AN DZ PFL017 DAILY

AL 0

AH 4571

AR1

WD 121

CO

V D=+

V X=28:48.833 N 082:02.033 W

DB 28:51.831 N 082:02.033 W , 28:51.831 N 082:02.033 W

Danger zone warning appears on Flytec 6030 when
crossing through this area despite D on the airspace menu on the 6030 marked as
“No.”

AC Q

AT

AD

AN PALATKA 1 INT 08

AL 914

AH 5486

AR1

WD 121

CO

AC Q

AT

AD

AN PALATKA 2 INT 08

AL 914

AH 5486

AR1

WD 121

CO

AC Q

AT

AD

AN LAKE PLACID NORT

AL 2133

AH 5486

AR1

WD 121

CO

Steve Kroop has removed all the danger zones from the Florida airspace file. You
can download it
here. He writes:

Once the danger Zones are eliminated there are 97 remaining airspaces:

14 class B, 16 class C, 35 class D, 32 restricted

Joerg Ewald <<joerg.ewald>>
writes:

I was not involved in
the FAF integration in the 6030. From what I gather from the code, and from some
documentation I found on our servers, one big difference between OpenAir and FAF
is the use of the "AT" records.

In OpenAir, "AT" is optional and defines where on a map labels are printed. I don't think this is used much.

In FAF, "AT" defines the airspace "type" (AWY, CTR, etc.). No idea why they used something that is in use by OpenAir.

At any rate, in the 6030, when interpreting an FAF file read from the SD card,
the vario's behavior is controlled by the AT record. The possible values can be
seen in the 6030's airspace settings page (D, AWY, FIZ etc.).

As far as I can see, the files used by Davis did not have any values assigned to
the AT records. My guess would be that if you change the line that says "AT" to
"AT D", the alarm would be suppressed if you set the CTR Alarm for "D" to "No".