After upgrading to 4.1.3 both of my hotspots have gone deaf

[AF6FB]

Hello,
I'm having a problem with my hotspots. Both are on Pi 3B+ boards and have ZUMSpot boards. One is configured for DMR and the other for P25.

I upgraded both from 4.1.2 to 4.1.3, at the same time I upgraded one of the ZUMSpot boards to v1.5.2 firmware. When testing this hotspot I found it to no longer receive signals from my radio. No lights, nothing in the log.

My initial reaction was to try the other hotspot to see of things were different with v1.4.17 firmware. I found the same issue.

My hotspots were both working well and had regular use. Both will transmit network traffic and the radios receive this without any issues. I've been using Jim's ZUMSpot boards since they were first available. I've never encountered an issue like this before.

Does anyone have a suggestion to help me out here? I'm at a loss.

Thanks in advance,
Michael AF6FB

[AF6FB]

I pulled out my third hotspot. It is still running 4.1.2/1.4.17. It seems to work fine still. So, I have a backup for a net I'm doing tonight.

I still need to get the others fixed.

Michael AF6FB

[AF6FB]

Thank you, but I have hotspot security setup and enable, I have for a while. my hotspot can connect to brandmeister, it just doesn't hear RF activity any longer.

I wonder if I should create a new image based on 4.1.2 and give that a try?

Michael AF6FB

[AF6FB]

Offsets were the answer. I've never had offsets change after an update before. What's worse, I went back to older software and was still having problems.

Process;
Put 4.1.2 onto uSD restarted and reconfigured software
Swapped out ZUMSpot board with one still running v1.4.17

Result, same issue

Ran MMDVMCal and user the P25 BER test, found that my offset moved from 330 to -350. (thanks KE7FNS)

Changed values in MMDVMHost

Result, works great

Ran pistar-update, pistar-upgrade to put 4.1.3 back on the system.

Result, works great

Ram pistart-ZUMSpotflash RPI to put 1.5.2 on the ZUMSpot

Result, works great

I have no idea why the offset changed, or why it changed when I ran the update. But, it did and now it's working.

Thanks for helping me with ideas, now it's time to do the same thing to my other hotspot.

Michael AF6FB

[G8SEZ]

It is surprising that an offset change of 20Hz would cause this problem, it seems very small in comparison with inner deviation of the order of 600Hz for C4FM.

[G8SEZ]

It is surprising that an offset change of 20Hz would cause this problem, it seems very small in comparison with inner deviation of the order of 600Hz for C4FM.

Actually it was 680 (went from 330 through zero to -350)

No idea why it would of changed that much either, maybe the OP is using a different radio or something.

Ah, I missed the minus sign. Yes, 680Hz is quite a lot but as you say it suggests that something was right on the edge previously too.