Open Repeater & PI-Repeater 1x Software settings

Home Forums ICS Controllers Open Repeater & PI-Repeater 1x Software settings

This topic contains 14 replies, has 3 voices, and was last updated by  Aaron, N3MBH 10 months, 1 week ago.

Viewing 5 posts - 11 through 15 (of 15 total)
  • Author
    Posts
  • #2415

    Aaron, N3MBH
    Forum Administrator

    That appears to be why you are not seeing your sound channels. They are not being detected on the i2c bus. You should have two items showing in this table: the sound chip and the GPIO expander chip. They should show under 0x20 and Ax00.

    This leads me to believe that either your i2c on your Pi may be fried, or there is an issue with the connection or the 1X board itself. I believe Dan tests these for basic functionality before they ship out.

    If you want to rule out software and something with my IMG file, then try ICS basic start IMG and run the same i2cdectect command. If you get the same thing, try running this with a different Pi board. Hope that helps.

    I understand Dan is emailing with you as well, he is also welcome to join in here.

    73,
    Aaron – N3MBH

    OpenRepeater is offered free of charge. Find out how you can support us.

    #2416

    Aaron, N3MBH
    Forum Administrator

    Without the i2c working you are also not going to have the 500 number gpio pins available either. Meant to mention that in my last post.

    73,
    Aaron – N3MBH

    OpenRepeater is offered free of charge. Find out how you can support us.

    #2417

    Dan Loranger
    Forum Moderator

    Yes we do test the boards before shipping, specifically for the audio and gpio expanders functionality.

    You suggestions are right Aaron, the next step is to confirm which board is bad if possible by installing on another pi and running the i2cdetect command again. This should be the last test to confirm which board is having problems

    #2418

    Hello Aaron,

    Worked with Dan today & it looks like bad GPIO pins.
    Here is the email exchange we had.

    Customer Service <support@ics-ctrl.com>
    To:
    Edward Donnelly

    May 15 at 9:13 AM

    From this info I can see the i2c device bus is gone. Now to establish if it’s the pi or the controller board.

    Do you have access to a second raspberry pi that you could move the board and sd card image to long enough to run the i2cdetect command again?

    I have had other customers that have had problems find their pi boards were bad from various gpio damage so I would like to confirm this first before I send you a new board.

    Dan

    Show original message

    Edward Donnelly <vteddie13@yahoo.com>
    To:
    Customer Service

    May 15 at 4:49 PM

    Hello Dan,

    I think you hit the nail on the head!

    Please see the output from another raspberry pi:

    pi@RBPI-K2WMA-R:~ $ sudo aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: Audio [Fe-Pi Audio], device 0: Fe-Pi HiFi sgtl5000-0 []
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    card 1: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM]
    Subdevices: 8/8
    Subdevice #0: subdevice #0
    Subdevice #1: subdevice #1
    Subdevice #2: subdevice #2
    Subdevice #3: subdevice #3
    Subdevice #4: subdevice #4
    Subdevice #5: subdevice #5
    Subdevice #6: subdevice #6
    Subdevice #7: subdevice #7
    card 1: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM]
    Subdevices: 8/8
    Subdevice #0: subdevice #0
    Subdevice #1: subdevice #1
    Subdevice #2: subdevice #2
    Subdevice #3: subdevice #3
    Subdevice #4: subdevice #4
    Subdevice #5: subdevice #5
    Subdevice #6: subdevice #6
    Subdevice #7: subdevice #7
    pi@RBPI-K2WMA-R:~ $ i2cdetect -y 1
    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: — — — — — — — UU — — — — —
    10: — — — — — — — — — — — — — — — —
    20: UU — — — — — — — — — — — — — — —
    30: — — — — — — — — — — — — — — — —
    40: — — — — — — — — — — — — — — — —
    50: — — — — — — — — — — — — — — — —
    60: — — — — — — — — — — — — — — — —
    70: — — — — — — — —
    pi@RBPI-K2WMA-R:~ $
    So it does see the Fe-Pi Audio now…..
    I took a heat gun & re-flow the raspberry pi GPIO pins and now that seems to work now.
    So it was a bad GPIO after all! Very nice tech work!

    I will replace the raspberry pi 3 with a new one. I see the 3+ is out. Have to see if Aaron can make a new image of open-repeater with the Fe-Pi Audio and the new 3+

    I will hook up the repeater tomorrow as a bad thunderstorm in upon us.

    Thanks again,

    73

    Ed — KB2UNZ

    #2419

    Aaron, N3MBH
    Forum Administrator

    Glad you were able to get it working. A Pi3b+ should be supported in the next release. I’m working on build scripts now.

    73,
    Aaron – N3MBH

    OpenRepeater is offered free of charge. Find out how you can support us.

Viewing 5 posts - 11 through 15 (of 15 total)

You must be logged in to reply to this topic.