dsame.py dies processing messages, worked fine in 2019, doesn't work in 2020.
Have attached a screen shot of the error.

Starting with audio from numerous activations, I used minimodem to decode the messages. Starting with #11, there are 12 actual EAS messages, including some valid, and some invalid. I fed the decoded data to dsame, and it couldn't process any of it.

The code runs flawlessly in Python 2.x, but just goes awry in Python 3.x. Are there any plans on updating the code to be compatible with Python 3.x? I was trying to make some modifications to the code so I could make a semi-automated system using a random computer I had laying around, but I can't make the proper modifications inside Python 2.x, probably because everything has been depreciated.

With the Windows application, dsame only works when "Start dsame" is checked after the installer runs. When this is checked, dsame runs just fine. When launched any other way, dsame does not do anything. I can display help text through cmd, but not actually decode anything.

Any ideas for what to try?

Thanks in advance.

(By the way, when this application works, it works REALLY WELL. Thank you for making such a great application open source!)

I have no issues piping output of rtl_fm into multimon-ng on linux but on windows, multimode-ng throws an "open: No such file or directory" error. Any ideas?

INPUT: rtl_fm Device
multimonNG (C) 1996/1997 by Tom Sailer HB9JNX/AE4WA
(C) 2012 by Elias Oenal
available demodulators: POCSAG512 POCSAG1200 POCSAG2400 EAS UFSK1200 CLIPFSK AFS
K1200 AFSK2400 AFSK2400_2 AFSK2400_3 HAPN4800 FSK9600 DTMF ZVEI
Enabled demodulators: EAS

open: No such file or directory

Found 2 device(s):
0: Failed to query data
1: Realtek, RTL2838UHIDIR, SN: 10000007

Using device 1: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
Tuner gain set to 42.10 dB.
Tuned to 162753575 Hz.
Oversampling input by: 46x.
Oversampling output by: 1x.
Buffer size: 8.08ms
Exact sample rate is: 1014300.020041 Hz
Sampling at 1014300 S/s.
Output at 22050 Hz.

1 3#!/usr/bin/env python

When i try and run a command through it, example dsame.py --msg "ZCZC-EAS-DMO-036000+0100-1311208-ZZTV/NY -" It gives the error "DNS server not authoritative for zone." no clue why it does this. I tried running it as an administrator and nothing.

Seismic alerts in Mexico City (SASMEX/SARMEX) 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 4 tectonic plates (Caribe, 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!

73!

Hi Everyone!

First off, I want to say this project is fantastic so thank you to anyone who has contributed especially cuppa-joe. I have setup an SDR on my RPi3 using multimon and dsame exactly as described in these examples. I am getting all EAS alerts and decoding them with dsame properly. However, I am trying to call an alert.sh script that will then POST the alert data to my server so I can trigger follow on actions. The script gets called correctly and the POST happens correctly but the parameters are empty. Here are a few more details.

The command I run is:
python dsame.py --source rtl_source.sh --call alert.sh --command "{event}" "{EEE}" "{MESSAGE}"

The contents of rtl_srouce.sh are the exact same as the rtl source file in this repo, with one slight adjustment (the frequency in my area is 162.550M instead of 162.500M).

The contents of alert.sh are as follows:
#!/bin/bash

URL=localhost:1880/v1/weather/alert
EVENT=$1
CODE=$2
MSG=$3

curl -X POST --header "Content-Type: application/json" --data-binary "{"event":"$EVENT","code":"$CODE","msg":"$MSG"}" $URL

As yo can see, I am just trying to read in the 3 parameters and curl to a local service (for now).

What I see when I run this is the proper alert text printed to stdout as well as the following object:
{"event":"","code":"","msg":""}
Naturally, that same object is what gets POSTed to my API service.

Am I missing something obvious to get the parameters to be passed into alert.sh?

Thank you!
Jason

Just a quick little thing...code 051095 should be just "James City", not "City of James City". Despite the name, it is a county.

Thank you for an awesome program! :)

There are several issues with dsame, including the fact that it cannot decode EAS headers that are statewide, For instance, trying to decode the following EAS alert using the --msg argument, simply results in blank output.
ZCZC-EAS-RMT-025000+0400-2501633-Comcast

This needs to be set up so that we can decode statewide tests and other alerts.

Also, I have noticed several cities are missing from the list, which needs to be updated. If anybody wants to work on these projects, you can make a pull request over at my fork of dsame so that I can get notified, and then you can make a fork or response here, since it appears the author for this project has quit or ceased operations. My fork can be found here https://github.com/RadarFolf/dsame

This is a list of NOAA NWS offices to replace the ICAO list in the program.
https://en.wikipedia.org/wiki/List_of_National_Weather_Service_Weather_Forecast_Offices

If you prefix the the call sign with K and use the names as given this should cover all forecast offices in the USA, since SAME is transmitted with a call sign instead of an ICAO code.

Hello. I love dsame so far, but I am wondering if it is possible to change the output from:

The National Weather Service in Milwaukee, Wisconsin has issued a Required
Weekly Test valid until 01:30 PM for the following counties in Wisconsin:
Calumet, Dodge, Fond du Lac, Green Lake, Manitowoc, Sheboygan, Washington,
Waushara, Winnebago. (KMKX/NWS)

to:
** ALERT ** ** ALERT **

AGENCY: The National Weather Service in Milwaukee, Wisconson
EVENT: Required Weekly Test
EXPIRE: 01:30 PM
COUNTIES: Calumet, Dodge, Fond du Lac, Green Lake, Manitowoc, Sheboygan, Washington,
Waushara, Winnebago. (KMKX/NWS)

I tried editing MSG__TEXT in defs.py, but it just kept giving me errors. Plus it looks like it doesn't like the triple '/" or \n\r so it creates a new line.

I have very limited Python experience, so any help will be extremely appreciated!!

Thank you
-bigginksu

This repository hasn't been updated since 2015, and it looks like there will be no more updates. Saddening.