Skip to content

Is the EAS modem encode/decode and fully functional in "dev" branch? #468

Closed
@guitarpicva

Description

@guitarpicva

I have been streaming UDP data from GQRX or SDR++ into direwolf to try and decode the EAS Codec which is sent by the minimodem application from Kamal Mustaffa.

Has EAS been fully tested for rx and tx as currently implemented in the dev branch? So far, direwolf gives no indication that it hears the data coming in. It DOES show that it is set up for the Codec upon startup. I have verified with wireshark that the samples are on UDP:localhost:7355.

Direwolf seems to bind directly to port 7355 also which seems odd to me. (Maybe I am just used to using multicast).

mitch@ondev:~/src$ netstat -anu
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
udp 0 0 0.0.0.0:7355 0.0.0.0:*

mitch@ondev:~$ direwolf -t 0 -b 16
Dire Wolf DEVELOPMENT version 1.7 F (Apr 27 2023)
Includes optional support for: hamlib cm108-ptt

Reading config file direwolf.conf
Audio input device for receive: UDP:7355 (channel 0)
Audio out device for transmit: default (channel 0)
Channel 0: FIX_BITS option has been turned off for EAS.
Channel 0: 521 baud, AFSK 2083 & 1563 Hz, A+, 48000 sample rate / 3.
Note: PTT not configured for channel 0. (Ignore this if using VOX.)
Disabled AGW network client port.
Ready to accept KISS TCP client application 0 on port 8001 ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions