forum.pistar.uk

My Fusion stopped working all of a sudden several weeks ago. I've tried every suggestion suggested, factory reset my radio, bought new Pis,, burnt new cards, tried different hats, and still can't get Fusion to work the way it did before it suddenly stopped. Clearly pizstar is not communicating with the hats as nothing but the usual two LED are lit. Here are my logs in case someone can help. I am short on funds and high on medical bills and can't afford to keep radios that don't work, whatever the cause. I love Fusion and have made lot of friends on it, making it my link to the outside world as I'm stuck at home disabled. I just can't figure out what's wrong. Here are the logs, which are identical for each card, hat, and Pi I try. I should note that I bricked the hats some time ago even though I always triple check the FW upgrade command before running it. Anyhow, I was able to revive them after reflashing them a few times and they work fine on Dstar and on DMR but not using DMR GW. That's a problem I need to work on further once I solve the Fusion one or donate my FTM-7250 to charity and sell my FT5DR, or vice versa.

I: 2022-01-11 20:25:30.560 This software is for use on amateur radio networks only,
I: 2022-01-11 20:25:30.560 it is to be used for educational purposes only. Its use on
I: 2022-01-11 20:25:30.560 commercial networks is strictly prohibited.
I: 2022-01-11 20:25:30.560 Copyright(C) 2015-2020 by Jonathan Naylor, G4KLX and others
M: 2022-01-11 20:25:30.560 MMDVMHost-20210617_PS4 is starting
M: 2022-01-11 20:25:30.560 Built 16:32:57 Jun 17 2021 (GitID #9106fd6)
I: 2022-01-11 20:25:30.560 General Parameters
I: 2022-01-11 20:25:30.560 Callsign: KE2SJ
I: 2022-01-11 20:25:30.560 Id: 3124585
I: 2022-01-11 20:25:30.560 Duplex: no
I: 2022-01-11 20:25:30.560 Timeout: 240s
I: 2022-01-11 20:25:30.560 D-Star: disabled
I: 2022-01-11 20:25:30.560 DMR: disabled
I: 2022-01-11 20:25:30.560 YSF: enabled
I: 2022-01-11 20:25:30.560 P25: disabled
I: 2022-01-11 20:25:30.560 NXDN: disabled
I: 2022-01-11 20:25:30.560 POCSAG: disabled
I: 2022-01-11 20:25:30.560 FM: disabled
I: 2022-01-11 20:25:30.560 Modem Parameters
I: 2022-01-11 20:25:30.560 Port: /dev/ttyAMA0
I: 2022-01-11 20:25:30.560 Protocol: uart
I: 2022-01-11 20:25:30.560 RX Invert: no
I: 2022-01-11 20:25:30.560 TX Invert: yes
I: 2022-01-11 20:25:30.560 PTT Invert: no
I: 2022-01-11 20:25:30.560 TX Delay: 100ms
I: 2022-01-11 20:25:30.560 RX Offset: 0Hz
I: 2022-01-11 20:25:30.560 TX Offset: 0Hz
I: 2022-01-11 20:25:30.560 RX DC Offset: 0
I: 2022-01-11 20:25:30.560 TX DC Offset: 0
I: 2022-01-11 20:25:30.560 RF Level: 100.0%
I: 2022-01-11 20:25:30.560 DMR Delay: 0 (0.0ms)
I: 2022-01-11 20:25:30.560 RX Level: 50.0%
I: 2022-01-11 20:25:30.560 CW Id TX Level: 50.0%
I: 2022-01-11 20:25:30.560 D-Star TX Level: 50.0%
I: 2022-01-11 20:25:30.560 DMR TX Level: 50.0%
I: 2022-01-11 20:25:30.560 YSF TX Level: 50.0%
I: 2022-01-11 20:25:30.560 P25 TX Level: 50.0%
I: 2022-01-11 20:25:30.560 NXDN TX Level: 50.0%
I: 2022-01-11 20:25:30.560 POCSAG TX Level: 50.0%
I: 2022-01-11 20:25:30.560 FM TX Level: 50.0%
I: 2022-01-11 20:25:30.560 TX Frequency: 446250000Hz (446250000Hz)
I: 2022-01-11 20:25:30.560 Use COS as Lockout: no
M: 2022-01-11 20:25:30.561 Opening the MMDVM
E: 2022-01-11 20:25:43.380 Unable to read the firmware version after six attempts

KE2SJ wrote: ↑Wed Jan 12, 2022 6:51 am
I: 2022-01-11 20:25:30.560 TX Frequency: 446250000Hz (446250000Hz)

You are in the Satellite lockout frequency range.
cf: viewtopic.php?p=16778#p16778

Thanks for the response. I copied and pasted the firmware upgrade command from the hat's manufacturer's web site, it's the same command that I've used for years with these hats. I haven't been fiddling around, I've been using fresh cards without changing anything unless it was suggested by someone that I try it.

I followed your algorithm, reflashed the firmware for the hats I have, and tried multiple Pis (3Bs). I'm still getting the same logs.

Yes, the hats were bricked. But I reflashed using the same command and the were revived. I am sorry if you think that is Groundhogs Day. I am grateful for the suggestions I've been given and always ask questions if there's something I don't understand. I just want to get my Fusion up and working again. But please don't make assumptions about me or how I probably messed things up. I'm working really hard to try to fix this and have followed every lead given to me. I greatly appreciate your help and advice. I bought a new Pi and new hat and will see if that helps. But as the problem persiss with all three hats I have and all three Pis on YSF (dstar works great, DMR BM works fine But having trouble with DMR GW and will work on that later), I don't know if this will work. But will give it a try.

There is no need to raise your voice or yell at me. I am trying my best. I am sorry I used the term "bricked" incorrectly.

When I flash the FW, all of the LEDs blink three times upon completion of the upgrade (not when pi-star restarts).

First, do the LED's on the hat blink 3 times when you power the hotspot up? If YES continue on to the next question, if NO reflash the proper firmware (1.5.2) for your hat. YES, they blink three times when I power up.

Are you trying to use an RPi 4? if NO, continue on, if YES, make sure you DO NOT HAVE "STM32-DVM / MMDVM_HS - Raspberry Pi Hat (GPIO)" selected as the modem configuration in Pi-Star. NO, I am using Pi 3Bs.

Does the SRV LED blink on and off after the LED's blink 3 times on powerup?? If YES , continue on to the next question, if NO reflash the firmware again.
NO, when I power up, all of the LEDs blink three times. But the SVC LED does not subsequently blink three times on its own. It never has.

Does the SRV LED blink faster after a minute or two? If YES then the log will no longer display "Unable to read the firmware version after six attempts". If NO then double check your modem configuration in Pi-Star, or swap out the RPi for a different one. THE SVC LED blinks faster after a minute on modes other than YSF. After reflashing, on YSF mode, the logs go straight to the unable to read firmware after 6 times message and no longer read anything else before hand. My live logs aren't reading anything with my D-star card although D-star works fine. I have tried all three of my Pis

I have done my best to answer your questions. If I can provide more info, just let me know.