Welcome to DVSwitch

Hi Ben, Yes your Hat Hotspot will be the equivalent of my Tait setup.

I used to use a pi-star image but I prefer my own setup so when I set settings etc they stays as I set them allways,

73 Doug

Bingo Mike. I had to try all available screen size to find out that «Smaller» was the only one working  :-)

Thank you Mike.

Change "Screen Scale"

This the config on my sreen (see attached pics).

I am not using the side PTT but rather trying to access the screen PTT. Impossible to access the screen PTT because I cannot reach/go down the PTT (in reference to accahed pic). Unable to move the sreen.

BTW, this is not happening in IAX2. I am facing that problem only in USRP.

Yes okay !! Fine fine business you’ve done !
Great ! I understood. The no-loop condition is assured by the simplex hotspot as it can’t receive when transmitting. 

 it’s like the repeater have 2 Network inputs and of course one for mobile stations. 

ok many thanks again. 

So if i put a simplex hat hotspot setup in dual frequencies mode locally at the repeater qth that will be your TAIT equivalent as we have internet access on site. 

And why not running a pi-star distribution ? Because it’s an Arduino board connected to your TAIT ? 

Ben

Hi Ben,

(Robin Uses a pistar Hat Hotspot (single antenna) set in duplex mode so he can set TX and RX (Reversed) Frequencies in his situation..)


In our working situation running perfectly since September 2020

If the Tait hotspot is TX up to the repeater the FTM-100 is RX from the Repeater.

If the FTM-100 is TX up to the Repeater the Tait hotspot is RX from the Repeater.

There is NO loop as TX + RX are Different..

Working example:

Repeater      TX = 146.750 Mhz    RX = 146.150 Mhz

FTM-100      TX = 146.150 Mhz    RX = 146.750 Mhz 

Tait Hotspot  TX = 146.150 Mhz    RX = 146.750 Mhz



Therefore if a Mobile station TX to the Repeater The FTM-100 and the Tait hotspot both RX and pass to (WiresX room for FTM-100) + (NZ-Canterbury-NZ Reflector for Tait Hotspot)

If someone connected to th NZ-Canterbury-NZ Reflector TX the Tait Hotspot will TX to the Repeater The FTM-100 will RX from the Repeater and pass to WiresX and the Mobile Station will RX from the Repeater.

If someone Connected to FTM-100 WiresX room TX the FTM-100 Will TX to the Repeater the Tait hotspot will RX from Repeater and Pass to NZ-Canterbury-NZ Reflector and the Mobile station will RX from the Repeater.


My Tait Hotspot is using a F5UII MMDVM (kitset) on an Arduino Due board connected to a Raspberry Pi 3B
Running on the Raspberry Pi 3B is MMDVMHost + YSFGateway and also the NZ-Canterbury-NZ Reflector. (not Pi-Star).

I hope this brings the workings clearer to you Ben.

73 Doug

HI Doug 
yes thanks for infos. 

ok for the duplex hat, yes of course frequencies are different. But it rise me another question : says there is a net call from ysf then your hotspot transmit on the tx qrg to the repeater, the repeater then transmit on his tx qrg which is the rx qrg of your hotspot. Is this condition does not make a loop ?
Or is the RemoteGateway option doing this unloop condition ?
In fact the hotspot rx qrg would be disabled when transmitting : how do you manage that ?
Okay i think i see, that is managed by your TAIT but what is the mmdvm board model connected to the TAIT ?

We are currently installing a DR-1X repeater with it’s hri-200 at a local airport here. And I would setup a Rpi on site for the ysf reflector but still not know how to do it to not create loops. Hope you understand me. 

Thanks for info Doug 
73, Ben

Steve,
P25 with either Analog_Bridge.  Thought it was fixed in later update to DVSwitch Server as I did not get these error messages on startup of the bridge and then for an unknown reason after running P25 bridge for a couple of weeks the bridge stopped and when I looked into the problem the partition on the cloud server which stores log files was filled and it was the same repeating entries as in the above thread.  Deleted the log files to recover memory and set the logging in both Analog_Bridge.ini files to 0(zero) and have not seen any problems since.
Sorry for the late response.
--
Dave WB6DTB

Hi Ben,
We have here in christchurch a DR2X (VHF) on a mountain (No Internet) in north canterbury which is 48km away from my qth.

I have at my QTH a FTM-100 connected to a HRI-200 which RX + TX on the repeater frequency (low power TX-5w).

I also have here at my QTH a high power simplex  hotspot (Tait TM8110 connected to a MMDVM) this is also RX + TX (low power TX-5w) on the Repeater frequency and the MMDVM is conected to the YSF59115 NZ-Canterbury-NZ Reflector.

All of this works Perfectly well but I found I have to have Remotegateway=1 set in the Fusion connector setting in mmdvmhost.for the audio to work in both directions properly.

I prefer using a seperate radio as a hotspot radio because I can set the TX and RX frequency seperately to what I want and the unit can be many Km's away, where as on a hat hotspot in simplex  mode it only has setting for 1 frequency so a Duplex hat as Robin is using will let you set the TX and Rx frequency and it has to be next to the DR2X Repeater and internet needs to be available also.

I hope this has been of some Help to you.

73, Doug

On Sat, May 15, 2021 at 01:17 PM, Komkit Listisard wrote:

Steve, very good and thank you for your time and support.  I won't know how to fix it.

Also what need to happen in P25 Net field to lit up instead of "Not Linked"

I have the similar dashboard with NXDN bridge, the NXDN Net is showing Linked to TG 910,  not with the P25 dashboard.

Otherwise it no big issue as it does not stop anything.

73, Kit

P25 Net "not linked" has been resolved.

Since my P25 <> DMR is using MB2 (mmdvm2) directory for logs.  I have to tell p25gateway to put the logs in mmdvm2 instead of mmdvm directory.

73, Kit

HI Doug 

what’s the function of that RemoteGateway option ?

And is a duplex hat mandatory because rx and tx never comes together 

73, Ben

Steve, very good and thank you for your time and support.  I won't know how to fix it.

Also what need to happen in P25 Net field to lit up instead of "Not Linked"

I have the similar dashboard with NXDN bridge, the NXDN Net is showing Linked to TG 910,  not with the P25 dashboard.

Otherwise it no big issue as it does not stop anything.

73, Kit

The change to fix the log fill and high CPU was a "hot patch" to Analog_Bridge. I will be building updated apt packages on Monday for all platforms.

Steve,

so far so good.  The only remain issue is the "P25 Net" never showed up as linked.  Most likely is on my dashboard setup. Otherwise all seem to be working now.  Any new was change to the Analog_Bridge binary?

Again, thank you for the help.  73, Kit

Okay, P25 is now fixed as well. 

All seem well now, both AB does not use much CPU now.  Both are now down at the bottom of top -o %CPU

Thank you for sticking around and help with the issue. 

73, Kit

Okay, I did that.  Brought MB/ABs back up, seem to be okay.  

Now seem like my P25 is not working but that probably have nothing to do with it.  I have DVSwitch dashboard up for P25, I can see data coming in but hear nothing on the radio and I could not transmit out from P25 side.

But as long as my CPU does not goes up and log size does not go up, I am okay for now.  Just have to debug the P25 reflector now.

73, Kit

OK,
Stop ALL instances of AB.
cd /tmp
wget https://github.com/DVSwitch/Analog_Bridge/raw/master/bin/Analog_Bridge.amd64
chmod +x Analog_Bridge.amd64
mv Analog_Bridge.amd64 Analog_Bridge
copy Analog_Bridge over the top of each Analog_Bridge binary.

Steve N4IRS

Oh, not all Steve.  

No, I do not have any AB running at all.  I do not use AB outside of trying to bridge P25 <> DMR.

If you wish and do not mind or have time.  I can send you the access to my TeamViewer and you can have at it.

73, Kit

I am not saying you are doing anything wrong. I'm trying to understand your config. With the MMDVM_Bridge to XLX shut down, how many instances of AB do you have running?