Date   

Re: Switching to Phoenix at command line

Derek William Haden <facebook@...>
 

So I think I went off on the wrong track, what I need to connect to is

DMR+ not Phoenix, sorry real new to DMR.

In the script I have to change to BM this command is implemented

/opt/Analog_Bridge/dvswitch.sh tune passw0rd@...:62031

What I am looking for is a similar command but to switch to DMR+

As always appreciate support and time and effort involved.


Re: Switching to Phoenix at command line

Derek William Haden <facebook@...>
 

Thanks Steve, I'll give it a try.

I am assuming Enable needs to be 1?


On Tue, Jul 14, 2020 at 09:40 AM, Steve N4IRS wrote:
[DMR Network]
Enable=0
Address=hblink.dvswitch.org
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0


Re: Switching to Phoenix at command line

Steve N4IRS
 

From what I can Google, you will need the login for that network. I am guessing when I say, put the login info in MMDVM_Bridge.ini

[DMR Network]
Enable=0
Address=hblink.dvswitch.org
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0

Steve N4IRS

On 7/14/2020 12:05 PM, Derek William Haden wrote:

Well connect to the DMR phoenix network.

If in DMR mode I believe that *D from DVswitch mobile switches to Phoenix.

I have some scripts installed that were written by WA3LXD I beleive, these switch between DStar, DMR TGIF, DMR BM, and YSF, and load up a customised TG list for each mode.

I want to add Phoenix to the scripts so they switch to that system. All my local Repeaters are on Phoenix, if they were on BM I wouldn't need this.



Re: Switching to Phoenix at command line

Derek William Haden <facebook@...>
 

Well connect to the DMR phoenix network.

If in DMR mode I believe that *D from DVswitch mobile switches to Phoenix.

I have some scripts installed that were written by WA3LXD I beleive, these switch between DStar, DMR TGIF, DMR BM, and YSF, and load up a customised TG list for each mode.

I want to add Phoenix to the scripts so they switch to that system. All my local Repeaters are on Phoenix, if they were on BM I wouldn't need this.


Re: Switching to Phoenix at command line

Steve N4IRS
 

I don't know anything about Phoenix. Tell us what you are trying to do.

Steve N4IRS

On 7/14/2020 6:21 AM, Derek William Haden wrote:

what would be the command or sequence of commands to Switch to Phoenix at the command line?

I have looked in the Wiki but don't see it



Switching to Phoenix at command line

Derek William Haden <facebook@...>
 

what would be the command or sequence of commands to Switch to Phoenix at the command line?

I have looked in the Wiki but don't see it


Re: enabling an AMBE dongle

Derek William Haden <facebook@...>
 

OK understood.

Thanks again.


Re: DVSwitch Dashboard

Jason - WY7JT
 

There is a bug in the code of the page. What works for me is when it shows someone transmitting, I hit reload and then the rest of the page loads.

Jason - WY7JT

On Mon, Jul 13, 2020 at 8:22 AM Stavros Papas via groups.io <sv2hwl=yahoo.gr@groups.io> wrote:
I have problem with Dashboard.
I have copy the files from Download folder to Webroot /var/www/html 
where I have Problem I don’t know.


Re: DVSwitch Dashboard

Stavros Papas
 

I have problem with Dashboard.
I have copy the files from Download folder to Webroot /var/www/html 
where I have Problem I don’t know.


Re: enabling an AMBE dongle

Steve N4IRS
 

No.
true = on
false = off

On 7/12/20 2:27 PM, Derek William Haden wrote:
So could I just rem the lines out?


Re: enabling an AMBE dongle

Derek William Haden <facebook@...>
 

So could I just rem the lines out?


Re: enabling an AMBE dongle

Steve N4IRS
 

decoderFallBack = true ; You can turn this off

useEmulator = true ; You can turn this off

emulatorAddress = 127.0.0.1:2500 ; this does not matter if use emulator is off

On 7/11/20 12:19 PM, Derek William Haden wrote:

I have now installed ambeserver and all seems to be working ok.

There are some settings in the Analog_Bridge.ini file that confuse me.

Do I need to change anything here?
---------------------------------------

decoderFallBack = true

useEmulator = true

emulatorAddress = 127.0.0.1:2500
-------------------------------------
Or lease as default?



Re: enabling an AMBE dongle

Derek William Haden <facebook@...>
 

I have now installed ambeserver and all seems to be working ok.

There are some settings in the Analog_Bridge.ini file that confuse me.

Do I need to change anything here?
---------------------------------------

decoderFallBack = true

useEmulator = true

emulatorAddress = 127.0.0.1:2500
-------------------------------------
Or lease as default?


Re: enabling an AMBE dongle

Derek William Haden <facebook@...>
 

I have now installed ambeserver, and now have it working fine.

The dongle (DVmega version).

My question now is about this section of Analog_Bridge.ini file

-----------------------------------

decoderFallBack = true

useEmulator = true

emulatorAddress = 127.0.0.1:2500

------------------------===

Do I have to change these settings when using the ambeserver, or will it simply use the dongle and ignore these settings?


Re: Error, DVSwitch.ini file not found.. But it's right there?!

sigmazgfx@...
 

So now the new battle will be to get ircddbgateway into arch ... 


Some ini files missing after installing on Rpi

Derek William Haden <facebook@...>
 

I have just installed dvswitch on a Rpi following the instructions in DVSM_02_17_2020.pdf

All went well till it came to editing
YSFGateway.ini
Quantar_Bridge.ini 
ircddbgateway
none of which existed, so I made my own in the appropriate folders.

also the systemctl service files for these services did not exist either.

Is there a resource I can download them from?

Also the ini files for NXDN P25 were also not there, however I won't be running those so that is not an problem.

 


Re: Error, DVSwitch.ini file not found.. But it's right there?!

sigmazgfx@...
 

Whoops that was my fault..
Here we go
[root@AllstarNode MMDVM_Bridge]# ./dvswitch.sh getEnabledModes
Enabled Modes: DMR D-Star




Re: Error, DVSwitch.ini file not found.. But it's right there?!

sigmazgfx@...
 
Edited

Ok... so I moved the comments down a line on the TXPort and RXPort lines.. it appears that for some reason it doesnt honor the ; comment delimiter

anyway, ran it again and this is what we see..

parseIniFile "$DVSWITCH_INI" "$_MODE" "TXPort"
++ parseIniFile /opt/MMDVM_Bridge/DVSwitch.ini DSTAR TXPort
++ python -
+ _MBTX=32100
parseIniFile "$DVSWITCH_INI" "$_MODE" "RXPort"
++ parseIniFile /opt/MMDVM_Bridge/DVSwitch.ini DSTAR RXPort
++ python -
+ _MBRX=32103
+ '[' '!' -z 32100 ']'
+ sendMessage 'Setting mode to DSTAR'
+ '[' -z 'Setting mode to DSTAR' ']'
+ remoteControlCommand 'message=Setting mode to DSTAR'
+ '[' '!' -z '' ']'
+ PYTHON_ARG='message=Setting mode to DSTAR'
+ python -
+ setAmbeMode DSTAR
+ '[' 1 -eq 0 ']'
+ remoteControlCommand ambeMode=DSTAR
+ '[' '!' -z '' ']'
+ PYTHON_ARG=ambeMode=DSTAR
+ python -
+ setTLVTxPort 32103
+ '[' 1 -eq 0 ']'
+ remoteControlCommand txport=32103
+ '[' '!' -z '' ']'
+ PYTHON_ARG=txport=32103
+ python -
+ setTLVRxPort 32100
+ '[' 1 -eq 0 ']'
+ remoteControlCommand rxport=32100
+ '[' '!' -z '' ']'
+ PYTHON_ARG=rxport=32100
+ python -
+ sleep 1
getTLVPort
++ getTLVPort
++ getABInfoValue tlv rx_port
getABInfoFileName
+++ getABInfoFileName
+++ '[' -z '' ']'
ls -t /tmp/ABInfo_*.json 2>/dev/null | head -1
++++ ls -t /tmp/ABInfo_34001.json
++++ head -1
+++ declare _json_file=/tmp/ABInfo_34001.json
+++ echo /tmp/ABInfo_34001.json
++ declare _json_file=/tmp/ABInfo_34001.json
++ python -
+ TLV_PORT=32100
+ getInfo
+ '[' 0 -eq 0 ']'
+ remoteControlCommand info
+ '[' '!' -z '' ']'
+ PYTHON_ARG=info
+ python -
exit $_ERRORCODE
+ exit 0

./dvswitch.sh mode DSTAR

But .. getEnabledModes is angry now.. 
 
[root@AllstarNode MMDVM_Bridge]# ./dvswitch.sh getEnabledModes
./dvswitch.sh: line 894: configparser: command not found
./dvswitch.sh: line 896: configparser: command not found
./dvswitch.sh: line 898: [: ==: unary operator expected
./dvswitch.sh: line 894: configparser: command not found
./dvswitch.sh: line 896: configparser: command not found
./dvswitch.sh: line 898: [: ==: unary operator expected
./dvswitch.sh: line 894: configparser: command not found
./dvswitch.sh: line 896: configparser: command not found
./dvswitch.sh: line 898: [: ==: unary operator expected
./dvswitch.sh: line 894: configparser: command not found
./dvswitch.sh: line 896: configparser: command not found
./dvswitch.sh: line 898: [: ==: unary operator expected
./dvswitch.sh: line 894: configparser: command not found
./dvswitch.sh: line 896: configparser: command not found
./dvswitch.sh: line 898: [: ==: unary operator expected
 


Re: Error, DVSwitch.ini file not found.. But it's right there?!

sigmazgfx@...
 

interesting thing though. 
I manually invoked python and tried the ConfigParser myself and sure enough it can read it.. 

>>> import configparser
>>> config = configparser.ConfigParser()
>>> config.read("/opt/MMDVM_Bridge/DVSwitch.ini")
['/opt/MMDVM_Bridge/DVSwitch.ini']
>>> for sect in parser.sections():
...    print('Section:', sect)
...    for k,v in parser.items(sect):
...       print(' {} = {}'.format(k,v))
...    print()
...
Section: QUANTAR
 logfilepath = /var/log/Quantar_Bridge.log
 address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
 txport = 34103                  ; Port to send AMBE TLV frames to (export)
 rxport = 34100                  ; Port to listen on (import)
 quantarport = 1994              ; HDLC frames To/From the Quantar repeater
 loglevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
 debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)
 
Section: DMR
 address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
 txport = 31100                  ; Port to send AMBE TLV frames to (export)
 rxport = 31103                  ; Port to listen on (import)
 slot = 2                        ; Export slot
 
Section: DSTAR
 address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
 txport = 32100                  ; Port to send AMBE TLV frames to (export)
 rxport = 32103                  ; Port to listen on (import)
 fallbackid = 1234567            ; In case we can not find a valid DMR id in the database, export this one
 exporttg = 9                    ; Which TG to export
 slot = 2                        ; Export slot
 
Section: NXDN
 address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
 txport = 33100                  ; Port to send AMBE TLV frames to (export)
 rxport = 33103                  ; Port to listen on (import)
 fallbackid = 1234567            ; In case we can not find a valid DMR id in the database, export this one
 nxdnfallbackid = 12345         ; Use this ID when the input DMR ID is not found in the database
 translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirectional)
 slot = 2                        ; Export slot
 
Section: P25
 address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
 txport = 34100                  ; Port to send AMBE TLV frames to (export)
 rxport = 34103                  ; Port to listen on (import)
 slot = 2                        ; Export slot
 
Section: YSF
 address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
 txport = 35100                  ; Port to send AMBE TLV frames to (export)
 rxport = 35103                  ; Port to listen on (import)
 fallbackid = 1234567            ; In case we can not find a valid DMR id in the database, export this one
 exporttg = 1234                 ; Which TG to export
 slot = 2                        ; Export slot
 
I came to realize that the parser section defines the import as ConfigParser and config = ConfigParser.ConfigParser when I tried that manually Python would get quite angry and complain that there is no module named "ConfigParser".
Also realizing that the unable to read DVSwitch.ini error message is just the default fail out message..

Changed the parseINIFile() function to reflect the name of the module it was happy with:

function parseIniFile() {
python - <<END
#!/usr/bin/env python
try:
    import sys, configparser
    config = configparser.ConfigParser()
    config.read("$1")
    print( config.get('$2', '$3') )
except:
    exit(1)
END
}

So with these changes I get this output now.. which is promising because it is reading and parsing... albeit still with an error further down the line, 
-----
parseIniFile "$DVSWITCH_INI" "$_MODE" "TXPort"
++ parseIniFile /opt/MMDVM_Bridge/DVSwitch.ini DSTAR TXPort
++ python -
+ _MBTX='32100                  ; Port to send AMBE TLV frames to (export)'
parseIniFile "$DVSWITCH_INI" "$_MODE" "RXPort"
++ parseIniFile /opt/MMDVM_Bridge/DVSwitch.ini DSTAR RXPort
++ python -
+ _MBRX='32103                  ; Port to listen on (import)'
+ '[' '!' -z 32100 ';' Port to send AMBE TLV frames to '(export)' ']'
./dvswitch.sh: line 812: [: too many arguments
+ echo 'Error, DVSwitch.ini file not found'
Error, DVSwitch.ini file not found
 


Re: Error, DVSwitch.ini file not found.. But it's right there?!

sigmazgfx@...
 

Will do, I'll await your command.

Thanks

3361 - 3380 of 10158