• Home

    • Latest Current Emergency Frequencies
  • About

    • Splatter : Club Newsletter
    • Meetings
    • Membership
    • Repeaters
    • President's Page
    • Club By-Laws
    • YRARC Silent Keys
    • Contact Us
    • YRARC Members only
    • YRARC Board Members ONLY
    • Privacy Policy
  • Our Community

    • Community Service
    • EMCOMM / ARES
    • Social Media Feeds
  • Club Activities

    • Become a Ham
    • YRARC Hamfest
    • Field Day
    • Projects
    • Club Trailer
  • Interest Groups

    • Satellites and beyond
    • Fox Hunting
    • 6M and Up
    • Antenna Building
    • FLDigi
    • APRS
    • Winlink
  • Resources and Links

  • Calendar of Events

  • Forum

  • Members

  • Blog

  • More

    Use tab to navigate through the menu items.
    yrarc_logo_tran.png
    Click here to Join or Renew Membership
    For YRARC Club Members Only
    To see this working, head to your live site.
    • Categories
    • All Posts
    • My Posts
    Jack Dodds VE3UKD
    May 24, 2019

    IRLP problems

    in Repeaters

    I've been trying to use the repeater at 147.225 MHz to access the repeater in Dwight, Ontario via IRLP. The IRLP node is 2460 and I did successfully work VA3XOR in Dorset a few months ago this way.


    If I transmit and then key 2460, there is no voice response. IIRC, the time that I did this successfully, the connection to the distant IRLP node was confirmed with a voice message.

    If I transmit and then key 2203 (another VE3MUS repeater in Muskoka) I get a voice response "The node number that you dialed does not exist. Please check the code and try again."

    Clearly I am reaching the Aurora repeater because I do get the response to the 2203 code. Also I have QSO'd through the Aurora repeater locally.

    Checking repeaterbook.com, it lists IRLP 2460 as "On Air" and "IDLE for 0 days, 6 hours, 7 minutes, 7 seconds." implying that somebody used it 6 hours ago.

    Also repeaterbook.com lists IRLP 2203 as "On Air" and "IDLE for 0 days, 0 hours, 37 minutes, 9 seconds."

    Any suggestions?

    3 comments
    0
    3 Comments

    Share Your ThoughtsSign up to leave a comment.

    Jack Dodds VE3UKD
    Nov 23, 2019

    Hello Brian,


    Thanks for your work on this. I thought that perhaps my handheld was not generating the DTMF codes correctly. I was able to record the DTMF codes into an audio file and then input the file to a spectrum analyzer program that I found on the Internet. The frequencies look correct. Based on that, and the fact that others have experienced problems, it looks like my handheld is OK.


    I'll be away for the next two weeks (won't be at the December meeting) but after that, if there is any way that I can help, please let me know.


    Jack VE3UKD

    Like

    Jack Dodds VE3UKD
    Aug 23, 2019

    No responses to my last post - I would really appreciate some help here!


    I tried once again to work VA3XOR in Dorset. He was able to link from a repeater in Dwight to the Aurora repeater (IRLP 2920) and I copied his transmissions by listening to the Aurora repeater on 147.225 MHz. However, when I responded on 147.825 MHz, he did not hear me.


    When I try to initiate the IRLP link from my end, I get dead air when I link to Dwight IRLP 2460, and a voice error message when I link to Dwight IRLP 2203, just as described in my previous post.


    Any news about the status of the Aurora repeaters would be appreciated.


    Jack VE3UKD


    Like
    brian.waterworth
    Nov 23, 2019
    Replying to

    Hi Jack,


    Sorry the very long delay in responding. I am just getting into the forums more and subscribing. So hopefully I will see future posts faster. I know we have spoke personally about this in the intervening months, but I thought I should record something in the forums for others.


    The IRLP node is having some trouble. Troubleshooting is going slowly as I still have a day job. Steve UT and Bruce BV have been providing some troubleshooting tips, but many things conspire to keep me from looking at the node.


    Symptoms I have seen so far is that DTMF codes are not being properly decoded by the system. I think the IRLP board is seeing each transmitted code and then when it communicates that code to the node computer, something goes wrong and the codes don't properly decode for all codes. Some do, most don't.


    I was also made aware that Echolink is also not working. One side of the conversation is heard, but the other is not. Based on your observations as well, something is up with the HW of the IRLP/Echolink node. I have played around with the sound levels to no avail. All the IRLP node tests come back positive (especially those with regards to Network connectivity). I even did some DTMF audio level tests and all where within acceptable limits as reported by the node's diagnostic tools.


    I am hoping to get some time in December (when on Christmas break) to get serious about troubleshooting. Some articles I have read suggest a bad parallel port on the node computer. Being that the SW has had no adjustments from whence the node was active and operational earlier this year, it is possible that a HW problem has arisen.


    Anyway, again sorry for the delay and the inconvenience. The Club's IRLP/Echolink is sick, but not forgotten.


    regards,

    Brian

    VE3IBW

    Like
    3 comments
    ve3yra @ QRZ
    Splatter
    Contact Us

    If you require updates to this website, or are having problems with login, then please contact infotech@yrarc.org

    • Facebook - Black Circle
    • Twitter - Black Circle

    © 2018 by CrabtreeTech.  Proudly created with Wix.com