This might not be a widely-used feature, but I wanted to post it here first versus directly to Jim (to follow the rules).
There is a feature within App_rpt where you can send MDC1200 status messages and have commands acted upon. I've used a MCS2000 mobile and Astro Saber successfully for a very fast and efficient control method. Recently I sold my Astro Saber and bought an XTS3000. I can still send MDC statuses and get them acted upon, but no longer get the "ACK" back from Allstar.
No changes in software and the logs show the op=46 like before and the proper Unit ID and status sent...so I'm at a loss of why Allstar stops trying to ACK these statuses for this one type of radio (my mobile still works fine). Debug suggestions and code testing welcome.
I have the same issues between two radios. My XTS-5000 responds properly
but my XTS-3000 does not. I'll do some digging this weekend to see where
the issue is. Because my XTS-5000 functions properly, it's probably a
codeplug issue.
Paul
ยทยทยท
On 8/12/11 4:18 PM, "Tony KT9AC" <kt9ac@ameritech.net> wrote:
This might not be a widely-used feature, but I wanted to post it here
first versus directly to Jim (to follow the rules).
There is a feature within App_rpt where you can send MDC1200 status
messages and have commands acted upon. I've used a MCS2000 mobile and
Astro Saber successfully for a very fast and efficient control method.
Recently I sold my Astro Saber and bought an XTS3000. I can still send
MDC statuses and get them acted upon, but no longer get the "ACK" back
from Allstar.
No changes in software and the logs show the op=46 like before and the
proper Unit ID and status sent...so I'm at a loss of why Allstar stops
trying to ACK these statuses for this one type of radio (my mobile still
works fine). Debug suggestions and code testing welcome.
Thanks,
Tony
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org