Modem replies NAK to the SET_CONFIG command

[G3VEK]

I'm trying to bring up my first DMR hotspot. I have the dual MMDVM unit connecting through GPIO, and with only DMR enabled I see the following in my log:

I: 2023-05-04 09:05:21.393 This software is for use on amateur radio networks only,
I: 2023-05-04 09:05:21.393 it is to be used for educational purposes only. Its use on
I: 2023-05-04 09:05:21.393 commercial networks is strictly prohibited.
I: 2023-05-04 09:05:21.393 Copyright(C) 2015-2020 by Jonathan Naylor, G4KLX and others
M: 2023-05-04 09:05:21.393 MMDVMHost-20210617_PS4 is starting
M: 2023-05-04 09:05:21.393 Built 16:32:57 Jun 17 2021 (GitID #9106fd6)
I: 2023-05-04 09:05:21.393 General Parameters
I: 2023-05-04 09:05:21.393 Callsign: G3VEK
I: 2023-05-04 09:05:21.393 Id: 2354978
I: 2023-05-04 09:05:21.393 Duplex: yes
I: 2023-05-04 09:05:21.393 Timeout: 240s
I: 2023-05-04 09:05:21.393 D-Star: disabled
I: 2023-05-04 09:05:21.393 DMR: enabled
I: 2023-05-04 09:05:21.393 YSF: disabled
I: 2023-05-04 09:05:21.394 P25: disabled
I: 2023-05-04 09:05:21.394 NXDN: disabled
I: 2023-05-04 09:05:21.394 POCSAG: disabled
I: 2023-05-04 09:05:21.394 FM: disabled
I: 2023-05-04 09:05:21.394 Modem Parameters
I: 2023-05-04 09:05:21.394 Port: /dev/ttyAMA0
I: 2023-05-04 09:05:21.394 Protocol: uart
I: 2023-05-04 09:05:21.394 RX Invert: no
I: 2023-05-04 09:05:21.394 TX Invert: yes
I: 2023-05-04 09:05:21.394 PTT Invert: no
I: 2023-05-04 09:05:21.394 TX Delay: 100ms
I: 2023-05-04 09:05:21.394 RX Offset: 0Hz
I: 2023-05-04 09:05:21.394 TX Offset: 0Hz
I: 2023-05-04 09:05:21.394 RX DC Offset: 0
I: 2023-05-04 09:05:21.394 TX DC Offset: 0
I: 2023-05-04 09:05:21.394 RF Level: 100.0%
I: 2023-05-04 09:05:21.394 DMR Delay: 0 (0.0ms)
I: 2023-05-04 09:05:21.394 RX Level: 50.0%
I: 2023-05-04 09:05:21.394 CW Id TX Level: 50.0%
I: 2023-05-04 09:05:21.394 D-Star TX Level: 50.0%
I: 2023-05-04 09:05:21.394 DMR TX Level: 50.0%
I: 2023-05-04 09:05:21.395 YSF TX Level: 50.0%
I: 2023-05-04 09:05:21.395 P25 TX Level: 50.0%
I: 2023-05-04 09:05:21.395 NXDN TX Level: 50.0%
I: 2023-05-04 09:05:21.395 POCSAG TX Level: 50.0%
I: 2023-05-04 09:05:21.395 FM TX Level: 50.0%
I: 2023-05-04 09:05:21.395 TX Frequency: 438800000Hz (438800000Hz)
I: 2023-05-04 09:05:21.395 Use COS as Lockout: no
M: 2023-05-04 09:05:21.396 Opening the MMDVM
I: 2023-05-04 09:05:23.407 MMDVM protocol version: 1, description: MMDVM_HS_Hat-v1.3.3 20180224 ADF7021 FW by CA6JAU GitID #62323e7
E: 2023-05-04 09:05:23.428 Received a NAK to the SET_CONFIG command from the modem

Is there some way to debug this in more detail? I tried increasing the logging level to 2 but it seemed to make no difference to the output. Or if you know what the issue is, please tell me!

[KN2TOD]

I would bring your HAT's firmware up to date first:

Code: Select all

I: 2023-05-04 09:05:23.407 MMDVM protocol version: 1, description: MMDVM_HS_Hat-v1.3.3 20180224 ADF7021 FW by CA6JAU GitID #62323e7

It should be:

Code: Select all

I: 2023-05-04 08:00:19.380 MMDVM protocol version: 1, description: MMDVM_HS_Hat-v1.5.2 20201108 14.7456MHz ADF7021 FW by CA6JAU GitID #89daa20

[G3VEK]

Thanks! Does this mean I need to short JP1 first? I'm using the GPIO interface.

[KN2TOD]

Probably, but try an update first, and then if it fails, short it and try again.

[G3VEK]

OK, got the firmware upgraded, and still seeing the same error.

I'm a bit lost here, as I can't seem to extract any lower-level debugging information.

I: 2023-05-05 06:41:21.973 FM TX Level: 50.0%
I: 2023-05-05 06:41:21.973 TX Frequency: 439950000Hz (439950000Hz)
I: 2023-05-05 06:41:21.973 Use COS as Lockout: no
M: 2023-05-05 06:41:21.981 Opening the MMDVM
I: 2023-05-05 06:41:23.992 MMDVM protocol version: 1, description: MMDVM_HS_Hat-v1.5.2 20201108 14.7456MHz ADF7021 FW by CA6JAU GitID #89daa20
E: 2023-05-05 06:41:24.012 Received a NAK to the SET_CONFIG command from the modem

[KN2TOD]

Don't know what any debug would look like (I've never tried/had to turn it on), but my guess would be you won't see much, if any, if the routine is not communicating with the HAT properly.

Are you sure you have the correct modem type specified? Dual/Duplex vs Simplex? GPIO? etc. If you've loaded the wrong firmware for the type, who knows what results you'll get.

The log you provided shows you've flagged the modem as "duplex" yet the the firmware message indicates you are running it as simplex. Something's off in your config here.

[W0CHP]

You mentioned in your very first post, that you have a duplex/dual hat modem.

However, it looks like you may have flashed the modem with the single hat firmware; as the modem version string does not contain the “dual hat” version signature.

Try flashing the dual hat firmware onto the modem and see if that helps.