Re: Where did the modulation go . . .


Jeremy McDermond <mcdermj@...>
 

On Nov 28, 2016, at 10:06 PM, ab9ca@... wrote:

OK, it looks like ambeserver is running.



I tried to kill it but it would not die. It kept changing its PID.
So I did the:



sudo systemctl disable dstarrepeaterd@1
sudo systemctl mask dstarrepeaterd@1



and then rebooted.



Then ran the following:



pi@compass:~ $ sudo systemctl status dstarrepeaterd@1 ircddbgatewayd
● dstarrepeaterd@1.service
Loaded: masked (/dev/null)
Active: inactive (dead)

Nov 29 05:45:54 compass systemd[1]: Stopped dstarrepeaterd@1.service.

● ircddbgatewayd.service - D-STAR Gateway Daemon
Loaded: loaded (/lib/systemd/system/ircddbgatewayd.service; enabled)
Active: inactive (dead) since Tue 2016-11-29 05:45:54 UTC; 1min 11s ago
Process: 560 ExecStart=/usr/sbin/ircddbgatewayd (code=killed, signal=TERM)
Main PID: 560 (code=killed, signal=TERM)

Nov 29 05:43:25 compass systemd[1]: Started D-STAR Gateway Daemon.
Nov 29 05:45:54 compass systemd[1]: Stopping D-STAR Gateway Daemon...
Nov 29 05:45:54 compass systemd[1]: Stopped D-STAR Gateway Daemon.
pi@compass:~ $
pi@compass:~ $
pi@compass:~ $ sudo gpio readall
+-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| | | 3.3v | | | 1 || 2 | | | 5v | | |
| 2 | 8 | SDA.1 | ALT0 | 1 | 3 || 4 | | | 5V | | |
| 3 | 9 | SCL.1 | ALT0 | 1 | 5 || 6 | | | 0v | | |
| 4 | 7 | GPIO. 7 | IN | 0 | 7 || 8 | 1 | ALT5 | TxD | 15 | 14 |
| | | 0v | | | 9 || 10 | 1 | ALT5 | RxD | 16 | 15 |
| 17 | 0 | GPIO. 0 | IN | 0 | 11 || 12 | 0 | ALT0 | GPIO. 1 | 1 | 18 |
| 27 | 2 | GPIO. 2 | OUT | 0 | 13 || 14 | | | 0v | | |
| 22 | 3 | GPIO. 3 | OUT | 0 | 15 || 16 | 0 | IN | GPIO. 4 | 4 | 23 |
| | | 3.3v | | | 17 || 18 | 0 | OUT | GPIO. 5 | 5 | 24 |
| 10 | 12 | MOSI | ALT0 | 0 | 19 || 20 | | | 0v | | |
| 9 | 13 | MISO | ALT0 | 0 | 21 || 22 | 1 | IN | GPIO. 6 | 6 | 25 |
| 11 | 14 | SCLK | ALT0 | 0 | 23 || 24 | 1 | OUT | CE0 | 10 | 8 |
| | | 0v | | | 25 || 26 | 1 | OUT | CE1 | 11 | 7 |
| 0 | 30 | SDA.0 | IN | 1 | 27 || 28 | 1 | IN | SCL.0 | 31 | 1 |
| 5 | 21 | GPIO.21 | IN | 1 | 29 || 30 | | | 0v | | |
| 6 | 22 | GPIO.22 | OUT | 0 | 31 || 32 | 0 | IN | GPIO.26 | 26 | 12 |
| 13 | 23 | GPIO.23 | OUT | 1 | 33 || 34 | | | 0v | | |
| 19 | 24 | GPIO.24 | ALT0 | 0 | 35 || 36 | 0 | IN | GPIO.27 | 27 | 16 |
| 26 | 25 | GPIO.25 | IN | 0 | 37 || 38 | 0 | ALT0 | GPIO.28 | 28 | 20 |
| | | 0v | | | 39 || 40 | 0 | ALT0 | GPIO.29 | 29 | 21 |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+
pi@compass:~ $
pi@compass:~ $
pi@compass:~ $
pi@compass:~ $ ps -ef | grep ambeserver
pi 1102 1033 0 05:47 pts/0 00:00:00 grep --color=auto ambeserver

This is just your grep command in the line above. ambeserver isn’t running.

Looks like pin 7 is still an IN pin and ambeserver is still running, if I'm reading this right.



The ambeserver must be being started somewhere in the boot sequence. How do I find out where? Would the log show this?
Something that you have installed is grabbing pin 7 on boot. It’s not dstarrepeaterd because we’ve told it not to start on boot. It’s difficult for me to debug over email. If you do a:

systemctl status

it’ll show you the daemons that systemd have started. That being said, there could be a startup script somewhere that’s snagging the pin. Did you install any new packages when you switched the networking to wireless?

73, dave

ab9ca/4
--
Jeremy McDermond
nh6z@...

Join udrc@nw-digital-radio.groups.io to automatically receive all group messages.