dhoover
I'm in c4fm to DMR mode. I've set "C4FM settings/ Default callsign for cross mode calls:" to my dmr ID.
I'm sending codes by keying the MH-36 mic and entering # followed by the talkgroup, example "#310" for TAC-310. It's a Yaesu ft-991a radio that lists that mic as an option for dtmf.
What am I missing? I know it's a setting I've overlooked. Everything else is working as expected
Thanks,
Dave KC3NEJ
dhoover
Here's a little more info; portion of the log from openspot2 where I tried to get to TG 3142
19:43:51 dst: *****G0KjH src: KC3NEJ
19:43:51 dl: ul:
19:43:51 c4fmcalltracker: voice call started, dst: *****G0KjH dgid: 0 src: KC3NEJ id: 0c1adc78b644f0a4
19:43:51 nvmm-csd: looking up callsign *****G0KjH
19:43:51 nvmm-csd: ignoring special callsign *****G0KjH
19:43:51 nvmm-csd: looking up callsign KC3NEJ
19:43:51 nvmm-csd: dmr ids 3135477 call "KC3NEJ" name "David" city "" state "" country "us"
19:43:51 homebrew-c4fm: call started
19:43:51 homebrew-c4fm: using ids dst 9 src 3135477 for this grp call
19:43:52 c4fmpacket: got unknown radio code 27
19:43:52 c4fmpacket: got unknown radio code 27
19:43:53 c4fmpacket: got unknown radio code 27
19:43:54 c4fmpacket: got unknown radio code 27
19:43:55 c4fmpacket: got unknown radio code 27
19:43:56 c4fmpacket: got unknown radio code 27
19:43:56 c4fmcalltracker: got terminator
19:43:56 c4fmpacket: header
19:43:56 dst: *****G0KjH src: KC3NEJ
19:43:56 dl: ul:
19:43:56 c4fmcalltracker: call ended, dur 5.4s ber 0.1% loss 0.0% rssi -46
dhoover
After ? hours, I think I've traced this problem to a defective mic. I sent the dtmf codes to the parrot group and the tones were all distorted and wonky. So I tried sending the dtmf tones with a different radio (ft-70dr) and everything worked perfectly.
Time for an adult beverage!