Multimode MMDVM Reflector - YSF P25 NXDN M17 Reflector - How To Install YSF P25 NXDN M17 Reflector

แชร์
ฝัง
  • เผยแพร่เมื่อ 19 ธ.ค. 2024

ความคิดเห็น • 29

  • @batoniarz
    @batoniarz 2 หลายเดือนก่อน +2

    Thanks for mentioning M17!

  • @moormoor4281
    @moormoor4281 2 หลายเดือนก่อน +1

    English England says thanking you most kindly

  • @ModernHam
    @ModernHam หลายเดือนก่อน +1

    Great stuff. Might have to check this software stack out. How does it compare to XLX? Does it do DMR/YSF transcoding internally?

    • @hamradionetworking
      @hamradionetworking  หลายเดือนก่อน

      No transcoding, slight chance of it coming in the future.

  • @bradhurd6472
    @bradhurd6472 หลายเดือนก่อน +1

    How or where do I configure the P25 TG and YSF reflector that I want it connected to?

  • @systech911
    @systech911 2 หลายเดือนก่อน +2

    Awesome

  • @John-jb1jv
    @John-jb1jv 2 หลายเดือนก่อน +2

    Other than the config files shown on the video, are there any other places that need to be config for YSF? Any other ports need to be open besides the port for YSF itself? When I run the status, it shows that the reflector is running, no errors reported, but I am not getting through to the.YSF registration server.

    • @hamradionetworking
      @hamradionetworking  2 หลายเดือนก่อน

      Thanks, this issue has been resolved in the code, please delete your reflector and reinstall it. rm -r MMDVM_Reflector within the /opt directory and reinstall it

    • @John-jb1jv
      @John-jb1jv 2 หลายเดือนก่อน

      @@hamradionetworking Thanks, worked perfectly.

  • @MikeCameron-r1v
    @MikeCameron-r1v 25 วันที่ผ่านมา +1

    Can't seem to get the install to work. I keep getting this error at the end. "Failed to enable unit: Unit file mmdvm_reflector.service does not exist." But I can see the file in the debian directory. Working with Debian 12 on a cloud instance on vultr. Any help greatly appreciated !!

    • @hamradionetworking
      @hamradionetworking  25 วันที่ผ่านมา

      You didn't follow instructions, your path is in the wrong directory.

    • @MikeCameron-r1v
      @MikeCameron-r1v 25 วันที่ผ่านมา

      @@hamradionetworking You are exactly right ! I wiped the server and started over and found my mistake. Thank you for your reply!

  • @GioTurano53
    @GioTurano53 2 หลายเดือนก่อน +1

    What app did you use on your phone to test it?

  • @Ragnar_75
    @Ragnar_75 หลายเดือนก่อน

    hi and thanks for your video ,why i have this error message.I m running debian via wsl on windows 10 .
    System has not been booted with systemd as init system (PID 1). Can't operate.
    Failed to connect to bus: Host is down

  • @DanFeeney-g5c
    @DanFeeney-g5c 2 หลายเดือนก่อน +1

    Will this install as you have demonstrated on a Pi4 ?

    • @hamradionetworking
      @hamradionetworking  2 หลายเดือนก่อน

      Yes, you need preferably debian 12 bookworm but debian 11 buster should work too. The installation is the same

    • @DanFeeney-g5c
      @DanFeeney-g5c 2 หลายเดือนก่อน +1

      @@hamradionetworking Thanks. I've tried the exact install using a Pi4 with 64-bit Bookworm, 32-bit Bookworm, 64-bit Bullseye, and 32-bit bullseye only to get the exact same result. The process needs to include installation of the Microsoft dotnet library in order to compile the code correctly.

    • @hamradionetworking
      @hamradionetworking  2 หลายเดือนก่อน

      @@DanFeeney-g5c Interesting, it should install dotnet and compile. Send me a email of images of the errors collin@k0nnk.com

    • @DanFeeney-g5c
      @DanFeeney-g5c 2 หลายเดือนก่อน

      @@hamradionetworking I'll address the issue next week when I get time again. I tried to manually install dotnet libraries and it was not found, as I mentioned previously.

    • @hamradionetworking
      @hamradionetworking  2 หลายเดือนก่อน

      @@DanFeeney-g5c If your using the asl3 image it will not work, please use straight debian12 bookworm. ASL3 image does not work with dotnet 8.

  • @akiddoo8113
    @akiddoo8113 2 หลายเดือนก่อน

    I continued to protest digital modes. It is great for tinkers and wasting money. Digital fragments the hobby. The audio is substandard and grating to listen to. Many repeaters set idle with little use so bandwidth argument is void. I'm sticking with my good old FM, saving money, and let the tinkers have at it. To each his own. And don't forget the SEIA hamfest in Columbus Jct, IA on Oct 6th. KT0TT

    • @hamradionetworking
      @hamradionetworking  2 หลายเดือนก่อน

      I don't know why you feel like protesting your opinion on digital modes will make you feel better about yourself? I don't care what you think and you shouldn't be crying to people how FM is better, quit being what we call 'sad hams' who only complain.

    • @akiddoo8113
      @akiddoo8113 2 หลายเดือนก่อน

      @@hamradionetworking Some day you will grow up. Nothing 'sad' about it - if you want to waste time and money on digital, have at it. I'm looking at it from a practical point of view. Digital is not necessary or needed. In an emergency situation analog wins. Hip Hip Ho-ray and 3 cheers for Allstar where everyone is.

    • @hamradionetworking
      @hamradionetworking  2 หลายเดือนก่อน

      @@akiddoo8113 Actually digital is way more popular then allstar, anyways. Digital has it's place, analog has it's place, and allstar has it's place. They all serve a purpose and all are unique and cool, your obviously not cool enough to get into the public safety side of ham radio which is digital. I love all parts of ham radio including allstar, you can't stand other people's opinions and have to voice your own like you're the only right ham on this planet. Everyone has their own likes and dislikes and that's ok, not everyone needs to have your opinion and your only! P.S. Allstar doesn't work in emergencies! Just like analog works in emergencies so does digital (locally)!

    • @motorolalover2552
      @motorolalover2552 2 หลายเดือนก่อน

      @@akiddoo8113 Yeah since allstar will work so well in an emergency. Grow up and don't watch the video if you don't like digital. No one cares about your opinions.

  • @roblerman5015
    @roblerman5015 2 หลายเดือนก่อน +1

    Any thoughts about this, I followed your instructions:
    root@node620301:/opt/MMDVM_Reflector/debian# systemctl start mmdvm_reflector
    root@node620301:/opt/MMDVM_Reflector/debian# systemctl status mmdvm_reflector
    × mmdvm_reflector.service - MMDVM Reflector Daemon
    Loaded: loaded (/etc/systemd/system/mmdvm_reflector.service; enabled; preset: enabled)
    Active: failed (Result: exit-code) since Thu 2024-09-26 19:22:37 PDT; 2s ago
    Duration: 4ms
    Process: 171469 ExecStart=/opt/MMDVM_Reflector/MMDVM_Reflector/bin/Debug/net8.0/MMDVM_Reflector --config=/opt/MMDVM_Reflector/MMDVM_Reflector/configs/config.yml (code=exited, status=203/EXEC)
    Main PID: 171469 (code=exited, status=203/EXEC)
    CPU: 3ms
    Sep 26 19:22:37 node620301 systemd[1]: mmdvm_reflector.service: Scheduled restart job, restart counter is at 5.
    Sep 26 19:22:37 node620301 systemd[1]: Stopped mmdvm_reflector.service - MMDVM Reflector Daemon.
    Sep 26 19:22:37 node620301 systemd[1]: mmdvm_reflector.service: Start request repeated too quickly.
    Sep 26 19:22:37 node620301 systemd[1]: mmdvm_reflector.service: Failed with result 'exit-code'.
    Sep 26 19:22:37 node620301 systemd[1]: Failed to start mmdvm_reflector.service - MMDVM Reflector Daemon.
    root@node620301:/opt/MMDVM_Reflector/debian#

    • @hamradionetworking
      @hamradionetworking  2 หลายเดือนก่อน

      run it without the daemon (so straight in the terminal) and see what it says.