Forum Replies Created

Viewing 10 posts - 371 through 380 (of 420 total)
  • Author
    Posts
  • in reply to: BeagleBone Black Beta2 #1404
    Aaron, N3MBH
    Forum Administrator

    The simple COS circuit would be external to the pre-made Easy Digi board. Probably could just assemble it on a perf board. We are working on our own board design so stay tuned. It would be geared more towards the Raspberry Pi form factor, but could be adapted to connect to a BBB. Let us know if you have any other questions. Thanks.

    73,
    Aaron – N3MBH / WRFV871

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

    in reply to: BeagleBone Black Beta2 #1400
    Aaron, N3MBH
    Forum Administrator

    Greetings,
    Thanks for trying out the project and your valuable feedback. Well it sounds like there might be an issue with Beta 2 if you are getting the Beaglebone 101 page. That service should have been disabled during the build. For the BBB I don’t believe there is any fundamental change in functionality between Beta 1 and Beta 2. Perhaps stick with Beta 1 for now unless you want to disable the BBB 101 services so that they don’t conflict with the ORP web server. We are working on the next Beta that will add some more functionality. I am also trying to make sure that the team test things more thoroughly before we push out a public release.

    As for the RX and TX and GPIO pins, the instructions are geared more toward the RPI2 version since this is the more popular board at the moment. I would also recommend adding the COS circuit (shown on hardware page) and not use the software VOX mode. In that case you would be using 4 pins on the GPIO header: Ground, 3.3v (for pull up resister), Input GPIO for RX/COS curcuit, and Output GPIO for TX/PTT.

    For my BBB I use GPIO 7 for TX/PTT and GPIO 30 for RX/COS. Make sure that you set the RX mode to COS. It also won’t start up unless you have your sound card configured properly. This might be a good form thread to read regarding that: https://openrepeater.com/forums/topic/errors-help

    It would either be alsa:plughw:1 or alsa:plughw:0. Just use “lsusb -l” to determine what it would be. i.e. if your card shows up as “Card 1” then it will be alsa:plughw:1. We are working to make it more of an “auto detect” process and remove some of the complication factors of SVXLink. Hope that helps.

    73,
    Aaron – N3MBH / WRFV871

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

    in reply to: Use with two FT2900R's ? #1395
    Aaron, N3MBH
    Forum Administrator

    Greetings and welcome to the forums. I would assume that you’d be using one Yaesu FT-2900R as your receive and one as your transmit. If that is so, then you are fine with one Easy Digi. You may need to add some inline attenuation resistors if needed. I would also recommend trying to pull a COS line off the receive radio, or you may need to modify it to get a COS line. Then build a simple COS circuit to active the RX GPIO pin. This is much more reliable then using the software vox. Hope this is of help.

    73,
    Aaron – N3MBH / WRFV871

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

    in reply to: usb sound card chipsets? #1392
    Aaron, N3MBH
    Forum Administrator

    No problem Joe. Yes number starts at 0 usually. I have seen that vary on two different boards (BBB and RPI2). I am working on an “auto detect” script that will query the system to see what is available and populate a dropdown list. This should make it a little more user friendly.

    73,
    Aaron – N3MBH / WRFV871

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

    in reply to: no logics available, bailing out (error) #1390
    Aaron, N3MBH
    Forum Administrator

    Joe, here is an example with an optocoupler.

    opto-pullup-circuit

    73,
    Aaron – N3MBH / WRFV871

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

    in reply to: echolink ID issue #1385
    Aaron, N3MBH
    Forum Administrator

    Thanks Joe for all your debugging and testing. I have pointed this out to Richard so he can track down the issue and make fixes for the next release. In the meantime, I have changed my password for Echolink so you shouldn’t be able to log into with those credentials any longer. I have been out of town for almost a week now, so sorry I missed your connection. My dev setup right now isn’t tied into a live repeater system, just a speaker and some simple test hardware. I have used it to serve Echolink connections which I can connect to via my phone client. I’d say if you found a work around and you are showing up in the Echolink Directory, then there should be problems with you keeping echolink active.

    73,
    Aaron – N3MBH / WRFV871

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

    in reply to: EchoLink Connection…And now? #1384
    Aaron, N3MBH
    Forum Administrator

    There may be some issue with core system reading the correct echolink config files built by the front end. We are looking into it and should have it ironed out in the next release.

    73,
    Aaron – N3MBH / WRFV871

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

    in reply to: remote control #1383
    Aaron, N3MBH
    Forum Administrator

    Richard is working on a shell configuration menu. He said he is going to add this in.

    73,
    Aaron – N3MBH / WRFV871

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

    in reply to: completely disable the courtesy tone via the web interface #1368
    Aaron, N3MBH
    Forum Administrator

    Hello Dimitri,
    Welcome to the Forums. Yes, that is already in the works and is planned to be added to the next beta release. I already have the code done for that. It will allow you to set set a mode for the courtesy tone. Either: Disabled, Beep, or Custom. Custom being the options right now.

    One way to get around it right now would be to recored blank audio file (500ms) and upload that and select that. Thanks for your support!

    73,
    Aaron – N3MBH / WRFV871

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

    in reply to: COS/COR and CTCSS Logic #1366
    Aaron, N3MBH
    Forum Administrator

    No problem…sorry I misunderstood your comment. That is already supported. Under ports you set a GPIO pin for RX and set the RX mode to COS instead of VOX. As for hardware we are incorporating that into our interface board we are designing. If you are using something like the Easy Digi. You just need to do a little extra side hardware right now. The COS is active when the GPIO pin goes low. You will need some kind of pull up resister to pull the pin high when it is inactive…this keeps it from floating in value. It depends on the board you are using, on the BBB black some of it’s pins are already configured with pull up resisters, on the RPI2 it is best to add them externally. My recommendation is to use an optocoupler with a pull up resister. When you active the optocoupler LED, the phototransitor side will make the pin go low. It also isolates the board to keep you from frying the GPIO pin inadvertently.

    It will take me a little while, but I will need to find or make a diagram to add to the hardware page. Bare with us as we are still developing the project and working to build documentation. Thanks for your interest.

    73,
    Aaron – N3MBH / WRFV871

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

Viewing 10 posts - 371 through 380 (of 420 total)