M7GSX wrote: ↑

Sun Nov 17, 2019 10:04 pm

Thanks Brian. Do you have a link?

I saw it on the MMDVM mailing list, which is on Yahoogroups. It's to do with UDP loss in recent Linux kernels.

Subject contains "Re: MMDVM/BM Loss"

I don't have a web link as I receive the list via email.

I saw something about problems with UDP packets in the latest mmdvmhost with Brandmeister.

It could be related to this.

vocoder wrote: ↑

Mon Oct 07, 2019 4:59 am

The "pi-star programmers they locked out those freqs", they did not. I just switched over on my Pi-Star.

They have done so if you use the mmdvmhat firmware for things like Jumbospot, Zumspot, DVMega etc. which use Andy CA6JAU's modem code.

For other hardware, bets are off.

A recent comment somewhere on this forum said that the OS2 only has enough storage for a few seconds of local echo recording in DSTAR mode, so you only hear the last part of your transmission. Try only saying 1-2-3 or 1-2...

KD6QFO wrote: ↑

Sat Aug 03, 2019 2:40 am

I agree with adding 5ghz wifi chipset......

You would need to substitute a dual band WiFi module, the effort of supporting WiFi is way beyond the resources available to SharkRF which is why they use a module in the first place. The WiFi firmware would deal with the band-switching as necessary.

G4AON wrote: ↑

Wed Jul 24, 2019 8:21 am

In beta v48 the MCW CW ID works fine, great news!

73 Dave

Good news. At least that should make those that care happy.

Don't think MCW is possible using the ADF7021 modem, it's not intended for analogue modes. There’s an ADF7021 in my MMDVM hat sitting on a Raspberry Pi, running under Pi-Star. That sends FM MCW which sounds fine on an FM handy. 73 Dave I have 3 Pi Zero Ws with HS_HATs, but I've never enabled the CW...

The currently transmitted unmodulated carrier wave satisfies regulatory requirements. It might well do, but as a seasoned ex professional Morse operator, even I find it hard to work out my own ID from a Shark using an FM hand held... 73 Dave Don't think MCW is possible using the ADF7021 modem, it's...

The changelog for v34 (which is a beta) shows that the WiFi module firmware has been updated in this release.

I would suggest that you downgrade to fix it, I think v32 is the latest non-beta version.

OK thanks.