Please consider adding MX as an instance for sending EAS alerts via aprs.

[xe1gbs]

Seismic alerts in Mexico City follow the ANSI/CTA-2009-B R-2016 standard and are triggerd by a lot of sensors installed all around the west coast of Mexico, they measure the activity of 3 tectonic plates (Cocos, Rivera and Pacific). These EAS alarms are only sent in Mexico City and conurbation in the same RF frequencies used by NWS. A given county catalog/region is not used as it is in the US and CA since it is sent as general announcement by our authorities as can be seen in PSSCCC = 000000.

This is an actual real example of the test sent every 3 hours:

EZCZC-ORG-EEE-PSSCCC+TTTT-JJJHHMMM-LLLLLLLL-
DEZCZC-CIV-RWT-000000+0300-832300-XDIF/005-
DENNNN

Direwolf screen
EAS audio level = 42(8/8) |||||||__
[2.3] EAS>APDW17:{DEZCZC-CIV-RWT-000000+0300-832300-XDIF/005-
User-Defined Data, DireWolf, WB2OSZ

EAS audio level = 41(8/8) |||||||__
[2.3] EAS>APDW17:{DEZCZC-CIV-RWT-000000+0300-832300-XDIF/005-
User-Defined Data, DireWolf, WB2OSZ

EAS audio level = 39(8/8) ||||||___
[2.2] EAS>APDW17:{DEZCZC-CIV-RWT-000000+0300-832300-XDIF/005-
User-Defined Data, DireWolf, WB2OSZ

EAS audio level = 38(8/7) ||||||___
[2.2] EAS>APDW17:{DENNNN
User-Defined Data, DireWolf, WB2OSZ

EAS audio level = 39(8/7) |||||||__
[2.3] EAS>APDW17:{DENNNN
User-Defined Data, DireWolf, WB2OSZ

EAS audio level = 39(8/7) |||||||__
[2.3] EAS>APDW17:{DENNNN
User-Defined Data, DireWolf, WB2OSZ

DEZCZC - origin of the message
CIV - Civil Authority
RWT - Weekly Test
000000 - test (all zones)
+0300 - Indicates the valid period of the message in segments of 15 minutes
832300 -Day in Julian Calendar JJJHHMM
XDIF/005 - Station identifier
DENNNN - end of message

''Earthquake Alert" in spanish "Alerta Sismica" < this is the message that should be sent as WX emergency announcement via APRS locally.

DEZCZC-CIV-EQW-000000+030-832300-XDIF/005-

CIV - Civil Authority
EQW- Earthquake Alert
000000 - test (all zones)
+0300 - Indicates the valid period of the message in segments of 15 minutes
832300 - Day in the Julian Calendar of the alert JJJHHMM
XDIF/005 - Station identifier
DENNNN - end of message

Thank You so much for yur support!!!! a los of HAMS here in Mexico appreciate your extraordinary work!
my APRS and WX stations are XE1GBS-10 / XE1GBS-13

73!

[wb2osz]

I'm very happy to hear that you found it to be useful.
Too many people think APRS is just a vehicle tracking system but it can be used for so much more!

The translation from the cryptic codes to plain text can be found here: https://github.com/nivex/dsame/blob/master/defs.py

Perhaps the author of the dsame application can be convinced to upgrade it for the MX location.

if that fails, someone could probably figure out what needs to be added from the protocol information here:
https://www.weather.gov/nwr/nwrsame

The location codes here https://www.weather.gov/nwr/counties only include the US. dsame also contains information for Canada so that information must be available somewhere. Perhaps there is a list for Mexico somewhere.

Even if the dsame author is not willing to do the work he/she has clearly done a lot of research and could probably point you in the right direction.

Keep us informed of your progress.

[xe1gbs]

Got it! thank you so much for your quick response. Another question : ) its possible to transfer this EAS alerts from one direwolf to another one running on the same network? i dont want to buy a unique radio, antenna, coaxialI and so on.... I want to use my main station which is already on the air.

DW2 (EAS) <--> DW1 (APRS/WX)--->Radio---> Air.

[wb2osz]

Not at the current time.
A number of people have asked for a way to map a direwolf "channel" to something external, over the network, rather than a builtin modem.
Remind me in another month or so.
I would have to think about it (when I'm not half asleep) but there might be some creative use of two instances of kissutil, one talking to the local direwolf instance, and the other going over the network to the other direwolf instance.

[xe1gbs]

Excellent, thank you! De: wb2osz ***@***.***> Enviado el: Thursday, January 20, 2022 9:11 PM Para: wb2osz/eas2aprs ***@***.***> CC: xe1gbs ***@***.***>; Author ***@***.***> Asunto: Re: [wb2osz/eas2aprs] Please consider adding MX as an instance for sending EAS alerts via aprs. (Issue #1) Not at the current time. A number of people have asked for a way to map a direwolf "channel" to something external, over the network, rather than a builtin modem. Remind me in another month or so. I would have to think about it (when I'm not half asleep) but there might be some creative use of two instances of kissutil, one talking to the local direwolf instance, and the other going over the network to the other direwolf instance. — Reply to this email directly, view it on GitHub <#1 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXMWJF5CMOQKN3ZRCD2JO4LUXDFEJANCNFSM5MOIIYLA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AXMWJF5NTJGIC5NTRRYQVETUXDFEJA5CNFSM5MOIIYLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHSXWCII.gif> Message ID: ***@***.*** ***@***.***> >

…

-- This email has been checked for viruses by AVG. https://www.avg.com

[xe1gbs]

Hello again!, I didnt get any response from dsame yet so i mod the code myself and now its working for Mx as well,- lot of coffee btw hehehe-. I have a question, when the messages are processed and transmitted, the radios only beep twice (yaesu) and nothing more, no messages area saved/displayed with the notification (text). just a screen message like this : OM>xe1gbs-13 is that normal?

[wb2osz]

APRS "messages" can be used in many ways.
The most obvious case is sending to a specific station.
They are used for Telemetry Metadata which makes no sense at all to me.
They can also be used for bulletins to larger audiences.
See http://www.aprs.org/doc/APRS101.PDF
The receiving system can have a filter to display only messages of interest based on pattern matching of the addressee field.

So you might need to set some sort of message filter, in the radio.
As an example, page 85 talks about setting message filters.

https://www.yaesu.com/downloadFile.cfm?FileID=8042&FileCatID=150&FileName=FTM%2D400DR%5FAPRS%5Fmanual%5F1309%2DA0.pdf&FileContentType=application%2Fpdf

[xe1gbs]

You were right! the radio filters had to be modified. We are already receiving them but I saw that the message does not have a wide1-1,2-1 path and the digipeaters do not retransmit them; they are sent as DM and limited to the RF coverage of the sending radio. Is there any way that these can be relayed by the different DPs in an area?

[wb2osz]

Look for this line
msg = aprs_msg (mycall, product_id, '', 'NWS', "[" + str(i+1) + "/" + str(n) + "] " + text2[i])

Change it to
msg = aprs_msg (mycall, product_id, 'WIDE1-1,WIDE2-1', 'NWS', "[" + str(i+1) + "/" + str(n) + "] " + text2[i])

[xe1gbs]

thx