DMR Chan Chg problem on RPi4


Chris K7AZ
 

I hope to upgrade my nodes to RTCM and RPi4 soon.  All parts in hand.  Just need to stuff the 1's and 0's in the right place.  :)



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Steve N4IRS <szingman@...>
Date: 3/22/21 13:48 (GMT-08:00)
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR Chan Chg problem on RPi4

No problem

Sent by smoke signal (AT&T)

From: main@... <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Monday, March 22, 2021 4:29:44 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR Chan Chg problem on RPi4
 
My repeater uses RTCM and thus "rxchannel=Voter/27610".
I created a separate node and link to it for DMR, etc:
[1973]
rxchannel=USRP/127.0.0.1:34001:32001
duplex=0



See any problems with this approach?

de W5BI Gary


Steve N4IRS
 

No problem

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Monday, March 22, 2021 4:29:44 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR Chan Chg problem on RPi4
 
My repeater uses RTCM and thus "rxchannel=Voter/27610".
I created a separate node and link to it for DMR, etc:
[1973]
rxchannel=USRP/127.0.0.1:34001:32001
duplex=0
.
.

See any problems with this approach?

de W5BI Gary


Gary
 

My repeater uses RTCM and thus "rxchannel=Voter/27610".
I created a separate node and link to it for DMR, etc:
[1973]
rxchannel=USRP/127.0.0.1:34001:32001
duplex=0
.
.

See any problems with this approach?

de W5BI Gary


Steve N4IRS
 

Good, question. That imag was a proof of concept quickie. Next one will be more complete.

So, if you are going to start with the AllStarLink beta:
Boot the image and go through their complete setup. Make sure the node is working correctly
reboot
wget http://dvswitch.org/buster
chmod +x buster
./buster
apt install dvswitch-server
Use the dvs menu to setup DVSwitch Server
Make sure everything is working.
apt install analog-reflector
cd /opt/Analog_Reflector
cd ssl
./mkcerts.sh
cd /opt/Analog_Reflector
edit Analog_Reflector.json (change as little as possible)
edit DMR ID etc
Put in your AllStar node number (in place of 1999)
 edit /etc/asterisk/rpt.conf
Change you node to use the rxchannel chan_usrp (unless the ASL menu let you do this already.)
enable chan_usrp in modules.conf

Steve N4IRS

On 3/22/2021 3:34 PM, Gary wrote:
Thanks fer reply Steve.

BTW, "rpt fun 27610 *327580" does work with good audio telem response. No idea why the "*09xxxx" autopatch trick fails.
Further debug req'd.

If I use ASL 2.0x Beta image on RPi4 as starting point,
  what are proper install steps fer DVSwitch-Server & Analog-Reflector?

de W5BI Gary


Gary
 

Thanks fer reply Steve.

BTW, "rpt fun 27610 *327580" does work with good audio telem response. No idea why the "*09xxxx" autopatch trick fails.
Further debug req'd.

If I use ASL 2.0x Beta image on RPi4 as starting point,
  what are proper install steps fer DVSwitch-Server & Analog-Reflector?

de W5BI Gary


Steve N4IRS
 

Gary,
I would say yes, it looks like there is problem with the current DVSwitch-Server-Allstar-lite based on your error. Once we complete the next software release, we will be revisiting the images. (menus, dashboard etc) There are a few upgrades that need to be made.

Steve N4IRS

On 3/22/2021 2:02 PM, Gary wrote:
Installed on RPi4 using 2021-02-14-DVSwitch-Server-Allstar-lite.zip
All  AOK until attempt to chg DMT TG...(using autopatch hook) ...NO audio spoken and system hangs
Cud this be issue with kernel on RPi4?? Should I start with ASL Beta 2.xx image??
BTW, running FB on RPi3.
Snippet here...

W5BIRPTR*CLI> rpt fun 27610 *093135
    -- Executing [3135@tgtune:1] NoOp("DAHDI/pseudo-1726154610", "1") in new stack
    -- Executing [3135@tgtune:2] SayAlpha("DAHDI/pseudo-1726154610", "dmr|3135") in new stack
    -- <DAHDI/pseudo-1726154610> Playing 'letters/d' (language 'en')
W5BIRPTR*CLI>
Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219444] Internal error: Oops: 207 [#1] SMP ARM

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219860] Process asterisk (pid: 31385, stack limit = 0xa771d5fd)

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219866] Stack: (0xc4b4fdc0 to 0xc4b50000)

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219876] fdc0: c024f42c c032dfbc 00000000 c0247594 60000013 c4b4fdd8 0000800c 0000800e
.
.
.


Gary
 
Edited

Installed on RPi4 using 2021-02-14-DVSwitch-Server-Allstar-lite.zip
All  AOK until attempt to chg DMT TG...(using autopatch hook) ...NO audio spoken and system hangs
Cud this be issue with kernel on RPi4?? Should I start with ASL Beta 2.xx image??
BTW, running FB on RPi3.
Snippet here...

W5BIRPTR*CLI> rpt fun 27610 *093135
    -- Executing [3135@tgtune:1] NoOp("DAHDI/pseudo-1726154610", "1") in new stack
    -- Executing [3135@tgtune:2] SayAlpha("DAHDI/pseudo-1726154610", "dmr|3135") in new stack
    -- <DAHDI/pseudo-1726154610> Playing 'letters/d' (language 'en')
W5BIRPTR*CLI>
Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219444] Internal error: Oops: 207 [#1] SMP ARM

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219860] Process asterisk (pid: 31385, stack limit = 0xa771d5fd)

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219866] Stack: (0xc4b4fdc0 to 0xc4b50000)

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219876] fdc0: c024f42c c032dfbc 00000000 c0247594 60000013 c4b4fdd8 0000800c 0000800e
.
.
.
EDIR: rpt fun 27610 *3xxxxx works and produces good audio telem.