Which Radio/Moden to choose
Which Radio/Moden to choose
I'm seeing red on Modes enabled and Network Status and incomplete Radio Info, so I'm doing something wrong.
sudo pistar-findmodem gives MMDVM_HS_Hat-v1.4.6 20180720 14.7456MHz ADF7021
I've selected MMDVM_HSHat (DB9MAT & DF2ET) for Pi (GPIO) but is that right?
sudo pistar-findmodem gives MMDVM_HS_Hat-v1.4.6 20180720 14.7456MHz ADF7021
I've selected MMDVM_HSHat (DB9MAT & DF2ET) for Pi (GPIO) but is that right?
Re: Which Radio/Moden to choose
Suggestion: skip the basic "dashboard" page and use the Admin page. It shows a lot more status indicators at the top. Those might reveal something.
--
AF6VN
Dennis L Bieber
Re: Which Radio/Moden to choose
I've just disabled D-Star mode on my system to determine what items are needed...
Comparing to your image, the main thing I see is that MMDVMHost is not green. You'll have to check the log files to see what may be causing it to fail. (I had to disable modes on mine as D-Star activates ircDDBGateway along with MMDVMHost). At the simplest, the RF board you have is NOT compatible with the modem selection you made. You'll have to examine the board carefully for any identification markings. Excluding specific manufacturers there are SEVEN MMDVM GPIO boards in the list -- and then one gets named manufacturers...
I can't really tell you what to look for /on/ the board -- I'm running an older DV-MEGA board. If the identification was correct, you are running fairly old firmware (2018), though that's probably the age of my DV-MEGA (I've never updated its firmware; it seems to be working fine, so why go through the hassle of jumpers to enable the update).
Check for date of log file, and it may help to reboot first so the logs are "clean"
Comparing to your image, the main thing I see is that MMDVMHost is not green. You'll have to check the log files to see what may be causing it to fail. (I had to disable modes on mine as D-Star activates ircDDBGateway along with MMDVMHost). At the simplest, the RF board you have is NOT compatible with the modem selection you made. You'll have to examine the board carefully for any identification markings. Excluding specific manufacturers there are SEVEN MMDVM GPIO boards in the list -- and then one gets named manufacturers...
I can't really tell you what to look for /on/ the board -- I'm running an older DV-MEGA board. If the identification was correct, you are running fairly old firmware (2018), though that's probably the age of my DV-MEGA (I've never updated its firmware; it seems to be working fine, so why go through the hassle of jumpers to enable the update).
Code: Select all
pi-star@pi-star-3b(ro):~$ more /var/log/pi-star/MMDVM-2022-08-08.log
Code: Select all
I: 2022-08-08 15:15:46.964 This software is for use on amateur radio networks only,
I: 2022-08-08 15:15:46.964 it is to be used for educational purposes only. Its use on
I: 2022-08-08 15:15:46.964 commercial networks is strictly prohibited.
I: 2022-08-08 15:15:46.965 Copyright(C) 2015-2020 by Jonathan Naylor, G4KLX and others
M: 2022-08-08 15:15:46.965 MMDVMHost-20210617_PS4 is starting
M: 2022-08-08 15:15:46.965 Built 16:32:57 Jun 17 2021 (GitID #9106fd6)
I: 2022-08-08 15:15:46.965 General Parameters
I: 2022-08-08 15:15:46.965 Callsign: AF6VN
I: 2022-08-08 15:15:46.965 Id: 1126104
I: 2022-08-08 15:15:46.965 Duplex: no
I: 2022-08-08 15:15:46.965 Timeout: 240s
I: 2022-08-08 15:15:46.965 D-Star: enabled
I: 2022-08-08 15:15:46.965 DMR: enabled
I: 2022-08-08 15:15:46.965 YSF: disabled
I: 2022-08-08 15:15:46.965 P25: disabled
I: 2022-08-08 15:15:46.965 NXDN: disabled
I: 2022-08-08 15:15:46.965 POCSAG: disabled
I: 2022-08-08 15:15:46.965 FM: disabled
I: 2022-08-08 15:15:46.965 Modem Parameters
I: 2022-08-08 15:15:46.965 Port: /dev/ttyAMA0
I: 2022-08-08 15:15:46.965 Protocol: uart
I: 2022-08-08 15:15:46.965 RX Invert: no
I: 2022-08-08 15:15:46.965 TX Invert: yes
I: 2022-08-08 15:15:46.965 PTT Invert: no
I: 2022-08-08 15:15:46.965 TX Delay: 100ms
I: 2022-08-08 15:15:46.965 RX Offset: 0Hz
I: 2022-08-08 15:15:46.965 TX Offset: 0Hz
I: 2022-08-08 15:15:46.965 RX DC Offset: 0
I: 2022-08-08 15:15:46.965 TX DC Offset: 0
I: 2022-08-08 15:15:46.965 RF Level: 100.0%
I: 2022-08-08 15:15:46.965 DMR Delay: 0 (0.0ms)
I: 2022-08-08 15:15:46.965 RX Level: 50.0%
I: 2022-08-08 15:15:46.965 CW Id TX Level: 50.0%
I: 2022-08-08 15:15:46.965 D-Star TX Level: 50.0%
I: 2022-08-08 15:15:46.965 DMR TX Level: 50.0%
I: 2022-08-08 15:15:46.965 YSF TX Level: 50.0%
I: 2022-08-08 15:15:46.965 P25 TX Level: 50.0%
I: 2022-08-08 15:15:46.965 NXDN TX Level: 50.0%
I: 2022-08-08 15:15:46.965 POCSAG TX Level: 50.0%
I: 2022-08-08 15:15:46.965 FM TX Level: 50.0%
I: 2022-08-08 15:15:46.965 TX Frequency: 446250000Hz (446250000Hz)
I: 2022-08-08 15:15:46.965 Use COS as Lockout: no
M: 2022-08-08 15:15:46.966 Opening the MMDVM
I: 2022-08-08 15:15:56.189 MMDVM protocol version: 1, description: DVMEGA HR3.19
--
AF6VN
Dennis L Bieber
Re: Which Radio/Moden to choose
Code: Select all
pi-star@pi-star-5(ro):~$ ls /var/log/pi-star
pi-star@pi-star-5(ro):~$
Code: Select all
pi-star@pi-star-5(ro):~$ ls /var/log/
auth.log daemon.log lastlog php7.0-fpm.log syslog wtmp
boot.log debug messages pi-star unattended-upgrades
btmp kern.log nginx private user.log
Re: Which Radio/Moden to choose
How long did you wait after a reboot? The logs are kept in a small RAM drive, so do not survive reboots. I'd have expected to see at least the start of the log files.
ircDDBGateway is D-STAR, wouldn't expect it for a DMR-only config.
Does /var/log/syslog show anything Pi-Star related? (I show a lot of futile activity from the watchdog -- stopping and restarting various services). Somewhere in all those logs there should be information regarding MMDVM(host) showing why it isn't starting. If nothing even attempts to start it you may need to burn a new SD card with a fresh Pi-Star install, force all upgrades (pistar-update and pistar-upgrade), and THEN reconfigure for your call sign, DMR ID, etc.
Code: Select all
pi-star@pi-star-3b(ro):~$ ls /var/log/pi-star
Headers.log ircDDBGateway-2022-08-08.log MMDVM-2022-08-07.log STARnet.log
ircDDBGateway-2022-08-07.log Links.log MMDVM-2022-08-08.log
Does /var/log/syslog show anything Pi-Star related? (I show a lot of futile activity from the watchdog -- stopping and restarting various services). Somewhere in all those logs there should be information regarding MMDVM(host) showing why it isn't starting. If nothing even attempts to start it you may need to burn a new SD card with a fresh Pi-Star install, force all upgrades (pistar-update and pistar-upgrade), and THEN reconfigure for your call sign, DMR ID, etc.
--
AF6VN
Dennis L Bieber
Re: Which Radio/Moden to choose
Still nothing in /var/log/pi-star after 12 hours
This might be significant-
This might be significant-
Code: Select all
Aug 9 07:31:49 pi-star-5 systemd[1]: Starting MMDVMHost Radio Servce...
Aug 9 07:31:50 pi-star-5 mmdvmhost.service[24685]: /usr/local/bin/MMDVMHost: error while loading shared libraries: libArduiPi_OLED.so.1: cannot open shared object file: No such file or directory
Aug 9 07:31:50 pi-star-5 mmdvmhost.service[24685]: MMDVMHost started as PID
Aug 9 07:31:50 pi-star-5 mmdvmhost.service[24707]: MMDVMHost is not running
Aug 9 07:31:50 pi-star-5 systemd[1]: mmdvmhost.service: Succeeded.
Aug 9 07:31:50 pi-star-5 systemd[1]: Started MMDVMHost Radio Servce.
Re: Which Radio/Moden to choose
Significant of a corrupted OS...
I'll repeat myself -- you may be better off downloading the most recent Pi-Star image, burning a new SD card, running pistar-update and pistar-upgrade until there are no more changes found, THEN reconfigure the hotspot settings.
Code: Select all
pi-star@pi-star-3b(ro):~$ sudo find / -iname "libarduipi_oled.*"
/usr/local/lib/libArduiPi_OLED.so
/usr/local/lib/libArduiPi_OLED.so.1.0
/usr/local/lib/libArduiPi_OLED.so.1
find: ‘/proc/19576/task/19576/net’: Invalid argument
find: ‘/proc/19576/net’: Invalid argument
pi-star@pi-star-3b(ro):~$
pi-star@pi-star-3b(ro):~$ ls -l /usr/local/lib/libArduiPi_OLED.so*
lrwxrwxrwx 1 root staff 37 Dec 22 2018 /usr/local/lib/libArduiPi_OLED.so -> /usr/local/lib/libArduiPi_OLED.so.1.0
lrwxrwxrwx 1 root staff 37 Dec 22 2018 /usr/local/lib/libArduiPi_OLED.so.1 -> /usr/local/lib/libArduiPi_OLED.so.1.0
-rwxr-xr-x 1 root staff 62696 Dec 22 2018 /usr/local/lib/libArduiPi_OLED.so.1.0
pi-star@pi-star-3b(ro):~$
--
AF6VN
Dennis L Bieber
Re: Which Radio/Moden to choose
I get the same as you-
Code: Select all
pi-star@pi-star-5(ro):~$ sudo find / -iname "libarduipi_oled.*"
find: ‘/proc/787/task/787/net’: Invalid argument
find: ‘/proc/787/net’: Invalid argument
/usr/local/lib/libArduiPi_OLED.so
/usr/local/lib/libArduiPi_OLED.so.1
/usr/local/lib/libArduiPi_OLED.so.1.0
pi-star@pi-star-5(ro):~$ ls -l /usr/local/lib/libArduiPi_OLED.so*
lrwxrwxrwx 1 root staff 37 Dec 22 2018 /usr/local/lib/libArduiPi_OLED.so -> /usr/local/lib/libArduiPi_OLED.so.1.0
lrwxrwxrwx 1 root staff 37 Dec 22 2018 /usr/local/lib/libArduiPi_OLED.so.1 -> /usr/local/lib/libArduiPi_OLED.so.1.0
-rwxr-xr-x 1 root staff 62696 Dec 22 2018 /usr/local/lib/libArduiPi_OLED.so.1.0
pi-star@pi-star-5(ro):~$
It'll probably be quicker in the long run.I'll repeat myself -- you may be better off downloading the most recent Pi-Star image, burning a new SD card, running pistar-update and pistar-upgrade until there are no more changes found, THEN reconfigure the hotspot settings.