forum.pistar.uk

If you have a hotspot - its MMDVM_HS in the modem list, not STM32-DVM, there are a couple of vendors incorrectly suggesting to use STM32-DVM incorrectly.

If you have a repeater with dual radios then STM32-DVM is a sane choice.

HTH.

I doubt that is the fix - since they both use the same settings, to some extent the modem choice is cosmetic, there are some that have really different settings, but we'll also be using that selection during the firmware upgrades soon so it's a good idea for the choice to reflect reality

Depends entirely on what/where you are trying. If you are using DMR, you need to have the TG you want to use in your RX list, the TG number / colour code etc need to match up or the radio will ignore it. If you are using reflectors - make sure you have TG9 in the RX list, for dynamic TGs, the ones y...

modified the YFS link code for the dashboard; update and see if its any better.

Unable to re-produce, I've done some work on the dashboard recently that *may* have already cured this, but when I set FCS00411 and reboot - it boots up normally, connects to FCS00411 etc without issue.

The FCS log shows the connection happened OK when the service started.

Checking into this at the moment...

Bug removed

bug confirmed - looking at it...

Are the APs on 5GHz only? All the Pi models with the exception of the new Pi 3B+ are 2.4GHz only.

1. Can you link to REFs OK ? 2. "XRF121CL" will probably be what you need in the UR field to link (XLXs are mostly XRF protocol, some are now multi-protocol too). XLX is the software, the protocols are still REF(D-Plus)/DCS (DCS)/XRF (DExtra), the radio will not understand XLX. I hope I am...