Dovolím si přeposlat tahák, který udělal VA3CZK pro vytvoření autostart YSFGatewy do RPI s WD.
7b. Create Service YSFGateway
# sudo nano /lib/systemd/system/ysfclient.service
[Unit]
Description=YSFGateway Service
After=syslog.target network.target
[Service]
User=root
WorkingDirectory=/opt/YSFClients/YSFGateway
ExecStart=/usr/bin/screen -S YSFGateway -D -m /opt/YSFClients/YSFGateway/YSFGateway /opt/YSFClients/YSFGateway/YSFGateway.ini
ExecStop=/usr/bin/screen -S YSFGateway -X quit
[Install]
WantedBy=multi-user.target
-----------------------------------------------------------------------------------------------------------------------------------------
# sudo chmod 755 /lib/systemd/system/ysfclient.service
Create a symbolic link between your script and a special location under /etc:
# sudo ln -s /lib/systemd/system/ysfclient.service /etc/systemd/system/ysfclient.service
-----------------------------------------------------------------------------------------------------------------------------------------
8. Create Timer
# sudo nano /lib/systemd/system/ysfclient.timer
[Timer]
OnStartupSec=65
[Install]
WantedBy=multi-user.target
-------------------------------------------------------------------------------------------------------------------------------------------
# sudo chmod 755 /lib/systemd/system/ysfclient.timer
Create a symbolic link between your script and a special location under /etc:
# sudo ln -s /lib/systemd/system/ysfclient.timer /etc/systemd/system/ysfclient.timer
9. Make systemd aware of your new service
# sudo systemctl daemon-reload
# sudo systemctl enable ysfclient.timer
# sudo reboot
Service should start 60 sec after bootup.
--------------------------------------------------------------------------------------------------------------------------------------------
Appendix A
Start Service manually
# sudo systemctl start ysfclient.service
Stop Service manually
# sudo systemctl stop ysfclient.service
Restart Service manually
# sudo systemctl status ysfclient.service
Service Status
# sudo systemctl status ysfclient.service
Connect to Screen Output
# sudo screen -r YSFGateway
Ctrl+a then d to disconnect from screen and keep the service running.
Run MMDVMHost
# sudo /opt/YSFClients/YSFGateway/YSFGateway /opt/YSFClients/YSFGateway/YSFGateway.ini
------------------------------------------------------------------------------------------------------------------------------------------
MMDVM.ini -
------------------------------------------------------------------------------------------------------------------------------------------
[System Fusion]
Enable=1
RemoteGateway=0
.
.
.
.
[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=3200
GwyAddress=127.0.0.1
GwyPort=4200
Debug=0
---------------------------------------------------------------------------------------------------------------------------------------
YSFGateway.ini
---------------------------------------------------------------------------------------------------------------------------------------
General]
Callsign=VA3xxx
Suffix=RPT
# Suffix=ND
RptAddress=127.0.0.1
RptPort=3200
LocalAddress=127.0.0.1
LocalPort=4200
Daemon=0
[Info]
RXFrequency=436000000
TXFrequency=436000000
Power=1
Latitude=0.0
Longitude=0.0
Height=0
Name=Toronto
Description=Multi-Mode Repeater
[Log]
# Logging levels, 0=No logging
DisplayLevel=1
FileLevel=1
FilePath=.
FileRoot=YSFGateway
[aprs.fi]
Enable=1
# Server=noam.aprs2.net
Server=euro.aprs2.net
Port=14580
Password=9999
[Network]
Enable=1
Port=42000
DataPort=42000
StatusPort=42001
Hosts=./YSFHosts.txt
ReloadTime=60
#ParrotAddress=127.0.0.1
#ParrotPort=42000
# Startup=
Debug=0
-------------------------------------------------------------------------------------------------------------------------------------------
Ahoj, Milan ma poprosil o skusenosti s prestavbou na MMDVM.
HW:
2x UHF Motorola GM350, z toho 1ks 12k5 a druhy 20k
RPi B+, 8GB mSD, image 2016-10-25_mmdvm_pixel_dmr-utah (obsahuje priamo soft pre "napalenie" Arduina), doinstalovana IRCDDBGW, MMDVM host 20161021
Arduino DUE, verzia MMDVM radia 20161021
MMDVM V6 (6.1) podla navrhu SP8NTH, vyrobene hamshop.cz
Najvacsie zdrzanie s Arduinom DUE, kupene v GME, klon, nefunguje korektne programing port, tvari sa sice ako funkcny seriak, ale data netecu. Spociatku obcas fungoval, potom prestal uplne. Native USB port funguje korektne, cezen vsak MMDVM nefunguje. Druhe DUE z UK funguje hned.
Dalsie laborovanie bod pripojenia modulacie do GM350, po dvoch dnoch pokusov a omylov je najvhodnejsi bod piny 14 a 15 U0103 (AFIC) cez 10uF keramiku. C0176 odstranit, R0173 nebol zapojeny. (Milan navrhol aj spolocny bod R0181 a R0182, ale ukazalo sa na SDRku ze je strhavany zaves az 3kHz vedla a DMR tak obcas slo a obcas nie).
Zaujimave je nastavovanie RX trimra na MMDVM modeme, nakolko dokaze fungovat len v urcitom rozsahu, tak treba vstup do MMDVM dovybavit delicom, po laborovani PIN1 SV3 470R voci GND a do serie medzi flat out GM350 a PIN1 SV3 MMDVM odpor 4k7.
Arduino DUE napajam priamo z 12V. RPi rovnako ako Milan cez GPIO z DCDC menica.
Pre kontrolu signalu a nastavenie zdvihu odporucam SDR dongel, MD380 dokaze fungovat aj pri znacnom presiahnuti normovaneho zdvihu, takze "od ucha" to je nemozne spravne nastavit. Prinscreeny v prilohe je tam vystup z radii a vystup z prevadzaca.
A este D-star, C4FM nemam...
Prikladam este namerane hodnoty z prijimaca, zaujimala ma sirka prenasaneho pasma DMR je viac ako 12k5.
Pouzite samodomo NWT500, naberane cez 47pF kondik z pinu 35 U5201 (vystup filtra FL5202 a vstup do limitera). NWT500 ma 50R vstup, spolu s kondikom to vychadza pri 455kHz na pridanie 7k5 paralelne k fitru, tak bol FL5202 mierne nespravne prisposobeny, ale riesit impedancny transformator sa mi volako nechcelo 🙂
Zde: https://www.f5uii.net/en/installation-calibration-adjustment-tunning-mmdvm-mmdvmhost-raspberry-motorola-gm360/5/ je velmi poěkný popis jak nastavit MMDVM modem.
