[arm-allstar] MDC1200 selective calls

Stephen - K1LNX k1lnx at k1lnx.net
Sun Mar 18 18:24:49 EST 2018


Hoping someone with some experience might be able to confirm if this works
as expected, or this is a possible bug?

I am playing around with MDC and attempting to use it to channel steer a
CDM radio. The idea works like this, I have this setup in functions:

; remote base channel selection
831=cmd,/usr/local/sbin/bcd_control_usb_fob.sh 1 1440
832=cmd,/usr/local/sbin/bcd_control_usb_fob.sh 2 1440
833=cmd,/usr/local/sbin/bcd_control_usb_fob.sh 3 1440
834=cmd,/usr/local/sbin/bcd_control_usb_fob.sh 4 1440

I mapped these under [mdcmacro]:

; remote base channel selection
; channels are selected using MDC call method
C3360-1441=*831         ; CDM channel 1
C3360-1442=*832         ; CDM channel 2
C3360-1443=*833         ; CDM channel 3
C3360-1444=*834         ; CDM channel 4

If I send a select call from my radio however, it "sees" it as a status
packet, and not a "call" packet:

Got MDC-1200 (double-length) packet on node 2335:
op: 35, arg: 89, UnitID: 1442
ex1: 80, ex2: 15, ex3: 33, ex4: 60
Got MDC-1200 data S3360-1442 from local system (2335)

I was going off examples to make this work from here (decode):

http://docs.allstarlink.org/drupal/node/104

example I'm using:

CXXXX-YYYY=*something   ; will match unit XXXX calling unit YYYY

Should this work as expected? I don't think it will parse correctly unless
it sees a "C" in the decoded packet.

73
Stephen
K1LNX


More information about the arm-allstar mailing list