Forum Replies Created
-
AuthorPosts
-
Aaron, N3MBHForum Administrator
SVXLink does have voip linking feature that is yet to be incorporated into ORP. It is called svxreflector. You may see this crop up first before Allstar. If you are just using Allstar to link your repeaters, then this may be all you need.
http://www.svxlink.org/doc/man/man1/svxreflector.1.html
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorGlad to hear and thanks for reporting back so others that wish to do the same know how.
At some point, I would like to make language switching a part of the UI, but it will still require some level of customization and obtaining/creating the appropriate language packs and maybe modifying some localization settings, so that is one reason that it’s not on the top of the list. Then there is adding translation options to the UI as well which is a whole other animal. Having been trying to work that way slowly such as separating the back-end functions from the front end code…is a progression for sure.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorGeorg,
Glad to hear you got it working! Sorry I wasn’t able to get back with you last night. I was going to question some settings as it sound like some COS and or PTT behaviors may had been inverted along with your other issues. Reimaging a new card with a fresh download was going to be another suggestion to try. I have seen in some cases where it just seemed to be a bad burn or something is out of wack that is hard to track down.Yeah, I think renaming the directory de_DE to en_US is the easiest fix for now and just modifying the locale.tcl to your requirements.
Thanks for the update.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorOK, after you change it back to another pin like 506, then make sure you click the update ports button, then rebuild/restart. It is the rebuild/restart that writes the GPIO config.
-So the settings get saved into the SQLite database.
-Then when a Rebuild/Restart is initiated, the config files get regenerated and a request is send for SVXLink to restart.
-When SVXLink restarts, it should read the updated gpio.conf file and handle pin registration. There has been some glitches seen here in the past with their setup/teardown scripts. Sometimes a restart is required to get around this.Note: There are two tables in the DB that the GPIO pin gets logged into. There is the main ports table, then there is also a gpio pins table that keeps track of all GPIO pins and their direction and what they are used for. The gpio.conf file is built from that table.
What version of ORP are you using? Was it a downloaded IMG file, or did you build it with our script?
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorSeems odd to me. GPIO config seems to be OK. Why again were you changing the PTT to 504 from 506?
I am not even sure that GPIO 504 is an available pin on the expender chip according to their documentation:
Port 1 PINS:
PTT – GPIO506 Active high
COS – GPIO26 Active Low
CTCSS – GPIO24 Active Low
Audio input – FE Pi Right Channel
Audio output – FE PI Right ChannelGPIO PINS:
GPA0 – GPIO496
GPA1 – GPIO497
GPA2 – GPIO498
GPA3 – GPIO499
GPA4 – GPIO500
GPA5 – GPIO501
GPA6 – GPIO502
GPA7 – GPIO503The pins shown above are broken out on the 16 pin header?
Do you have the manual for the board?
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorGeorg,
Dan with ICS is on vacation this week and he usually answers the questions pertaining to the ICS boards…but I will see what I can do to assist you.Let try to pinpoint where the issue is occurring:
Go to your /sys/class/gpio folder and try to manually register the GPIO pin and toggle it. You can register it with the following two commandsecho 506 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio506/direction…and toggle it with these two commands…
echo 1 > /sys/class/gpio/gpio506/value
echo 0 > /sys/class/gpio/gpio506/valueThis will tell us if the GPIO expander is properly setup and working correctly. If you cannot setup and toggle the pins then there may be other issues. In that case, try issues “i2cdetect -y 1” at the command line and post the results back here. That will tell us which ICs are being recognized on the I2C bus.
Also if you could, please post the contents of your “/etc/svxlink/gpio.conf” file. That will tell me if ORP is able to write to this file.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
- This reply was modified 5 years, 6 months ago by Aaron, N3MBH.
Aaron, N3MBHForum AdministratorTamas,
If you were not aware, ORP 2.1.1 was release not too long ago. This has support for add on modules. I am currently working on building out a FRN module. Let me know if you’d be interested in testing it. FRN is not really used over here in the states and is likely not a good legal option for Ham Radio in the US. I am trying to get a module available for our European users since SVXLink already has the Frn code.73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorOK, the “/usr/share/svxlink/events.d/local/locale.tcl” is not written to by ORP so that should remain unchanged. If you look at the “/usr/share/svxlink/events.d/local/Logic.tcl” in the same folder, that gets written to by ORP. Any TCL or CONG files that get written to by ORP should have a custom comment headers at the top stating so. Take a look at the Logic.tcl in that folder or the svxlink.conf file and you will see what I mean.
My guess at this point is ORP is not breaking your locale.tcl file as it should not be writing to it. I have not used it before, so I don’t know off hand if you have to declare the file in a different file like svxlink.conf that does get overwritten by ORP.
I would imagine that you are changing your DEFAULT_LANG in the svxlink.conf from “en_US” to “de_DE”, in that case, yes that would get overwritten by ORP. 1) you could modify the PHP class that writes this as the language is currently hard coded. This is located at “/var/www/openrepeater/includes/classes/SVXLink.php”. There are two occurrences of “en_US” in this file that would need replaced. 2) A simpler alternative that should work is to just rename your language sound folders. Maybe change “en_US” to “en_US_orig” and change “de_DE” to “en_US”
Let me know where that gets you.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorI just wanted to confirm you meant:
/usr/share/svxlink/events.d/local/locale.tcland not
/usr/share/svxlink/events.d/local/Logic.tcl
This file is modified by ORP.The path for the locale.tcl above doesn’t exist on ORP by default. There is a locale.tcl in the directory above that though. If it is the Logic.tcl file instead that is modified by a PHP class, so you may need to modify that. If it is a locale.tcl file then we will need to figure out how that would be implemented.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorWhat file are you trying to modify the TCL in? Once I know that, I can probably offer some direction.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
-
AuthorPosts