MPAD not replying

[9M2PJU]

Hello OM, I have re-correct the wrongs. But my MPAD didnt reply if i send "atm" from 9M2PJU-5 using aprsdroid.

Can you help?

[9M2PJU]

Do I need to open any incoming ports ?

[joergschultzelutter]

You can give this attempt a try:

• clone https://github.com/joergschultzelutter/aprstest This is a repo with two single test scripts: one that sends a single message (and then terminates) and another one that receives a message and prints it to stdout.
• modify ´aprs_listen.py´ and change the filter setting in line 22 (documentation)
• start aprs_listen and send a message to the call sign that you have specified as filter
• your message should then appear on the console

When you can see your message getting printed to stdout, we can confirm that your APRS-IS filter works as designed.

Now open MPAD's mpad_config.py file and modify BOTH settings:

#
# APRS-IS server filter setting (This is the program's PRIMARY message filter)
# Syntax: see http://www.aprs-is.net/javAPRSFilter.aspx
# If you remove/disable this filter, MPAD will 'see' all aprs-is messages
# (the whole APRS-IS traffic)
aprsis_server_filter = "g/MPAD"  # server filter criteria for aprs.is
#
#############################
# Secondary filter settings #
#############################
#
#
# MPAD SECONDARY filter setting. This filter will be applied to those
# messages which have made it past the PRIMARY filter (from APRS-IS)
# If that secondary filter is also passed, then we will have a look
# at the user's message and try to process it
#
mpad_callsigns_to_parse = ["MPAD"]  # (additional) call sign filter
#

First setting is the APRS-IS filter whereas the 2nd one acts as an internal safeguard.

Once that is done, your local MPAD instance should be able to process incoming messages.

Kindly note that in order to run your local instance on a permanent basis, you are required to retrieve your very own APRS TOCALL identifier and change this section here:

#
# APRS "TOCALL" identifier - see http://aprs.org/aprs11/tocalls.txt
# The original MPAD instance has its own TOCALL identifier - if you clone & modify
# the program, you might request a new one for yourself via WP4APR
mpad_aprs_tocall: str = "APMPAD"  # APRS "TOCALL"
#

WB4APR is SK, so now you have to get in touch with Hessu via https://github.com/aprsorg/aprs-deviceid

You do not need to open any incoming ports.

[joergschultzelutter]

Closing issue due to inactivity; please feel free to reopen in case of questions.