forum.pistar.uk

Posted: **Sat Feb 02, 2019 6:41 pm**

VK2YMU wrote: ↑Fri Feb 01, 2019 10:25 pm Fantastic feature.
I have a problem with it, Radio is a FTM100D
Using YSF2P25 on the Pi-Star, Ysfgateway is patched with WiresXCommandPassthrough=1 and WiresXMakeUpper=1

I place the radio in Wirex by pressing the Dx button then pressing with a long press of the Band button
This opens the selection screen, I select All then press the Disp button, the screen populates with the available hosts, I select the desired host, the radio acknowledges that this was ok.

Here is the problem, I place the radio in VW (Wide Mode) TX or RX is not working, the Pi-Star did not link according to the radio, dashboard indicates it has yet when returning to wirex mode on the radio the selected talkgroup is flashing, this is an unlinked indication.
Repeating the Wires search, now only results in the YSF host list and not the P25 list as before.

Only way to return to normal is to do an Apply Changes, then I can repeat the above.

If we an get this to work it will be a great feature, thank you for the efforts applied to this.

I think you're seeing the same thing I am - maybe works once and then goes back to thinking everything is a YSF/FCS reflector.

Posted: **Sat Feb 02, 2019 8:59 pm**

Dashboard tells me I am linked to the selected group, yet the radio says its not, no TX or RX from the selected group.
I be interested if its Radio Model issue or not.

Posted: **Sun Feb 03, 2019 11:59 am**

K5MRE wrote: ↑Sat Feb 02, 2019 6:20 pm Andy,

I added a link to pull TGList_TGIF if you want to update to add it when users select TGIF.

http://tgif.network/tglist.php

K5MRE

Thank you - I'll need that soon

Posted: **Sun Feb 03, 2019 12:03 pm**

K5MRE wrote: ↑Sat Feb 02, 2019 6:39 pm It seems to be a bit flakey.

See the log below. Notice the initial connection to TG 103 went through YSF2DMR fine. However, hanging then over to TG 101, it treated it like it was a FCS reflector. Same with the next two tries to TG 102 and even back to TG 103 again.

I'm testing from an FTM-100D. I've been running direct to YSF2DMR for a while without issues, so it seems to be related to whatever was added to try and detect whether the group I'm giving it is supposed to be YSF/FCS or a YSF2DMR talk group.

pi-star@mmdvm(rw):pi-star$ tail -f YSF2DMR-2019-02-02.log
M: 2019-02-02 18:25:27.137 DMR ID of K5MRE: 3123589, DstID: TG 201
M: 2019-02-02 18:25:27.939 YSF received end of voice transmission, 0.8 seconds
M: 2019-02-02 18:25:43.487 Received YSF Header: Src: K5MRE/MIKE Dst: 00201F5TSF
M: 2019-02-02 18:25:43.487 DMR ID of K5MRE: 3123589, DstID: TG 201
M: 2019-02-02 18:25:45.715 YSF received end of voice transmission, 2.2 seconds
M: 2019-02-02 18:29:46.238 DMR ID of K5MRE: 3123589
M: 2019-02-02 18:29:46.238 Connect to TG 103 has been requested by K5MRE/MIKE
M: 2019-02-02 18:29:46.300 DMR ID of K5MRE: 3123589
M: 2019-02-02 18:29:46.300 Connect to TG 103 has been requested by K5MRE/MIKE
M: 2019-02-02 18:29:47.504 Sending PTT: Src: K5MRE/MIKE Dst: TG 103

pi-star@mmdvm(rw):pi-star$ tail -f YSFGateway-2019-02-02.log
M: 2019-02-02 18:25:44.212 0010: 72 20 03 34 *r .4*
M: 2019-02-02 18:25:44.212 GPS Position from K5MRE/MIKE of radio=FTM-100D lat=32.978333 long=-97.411331
M: 2019-02-02 18:25:50.770 APRS ==> K5MRE>APDPRS,C4FM*,qAR,K5MRE-N:!3258.70N/09724.68W> FTM-100D via MMDVM
M: 2019-02-02 18:29:51.241 Disconnect has been requested by K5MRE/MIKE
M: 2019-02-02 18:30:10.431 Connect to 00101 - "FCS00230 " has been requested by K5MRE/MIKE
M: 2019-02-02 18:30:10.513 Linked to FCS002-30
M: 2019-02-02 18:30:29.681 Connect to 00102 - "FCS00231 " has been requested by K5MRE/MIKE
M: 2019-02-02 18:30:29.727 Linked to FCS002-31
M: 2019-02-02 18:30:47.881 Connect to 00103 - "FCS00232 " has been requested by K5MRE/MIKE
M: 2019-02-02 18:30:48.100 Linked to FCS002-32
^C

Once you choose YSF2DMR form the first connection, from that point, all commands are sent to the YSF2DMR gateway until you send a disconnect, if you are sending the disconnect when you swap talk group - that will take you back to the YSF/FCS list, there is no need to send the disconnect each time, the gateway handles that.

If you have been playing with this before, make sure you have

Code: Select all

[DMR Network]
EnableUnlink=1
TGUnlink=4000

in the /etc/ysf2dmr config.

Posted: **Sun Feb 03, 2019 12:24 pm**

VK2YMU wrote: ↑Sat Feb 02, 2019 8:59 pm Dashboard tells me I am linked to the selected group, yet the radio says its not, no TX or RX from the selected group.
I be interested if its Radio Model issue or not.

Radio model - its possible, I don't have one of those to work with, but we didn't change the command structure, the only thing I can think of, is that the radio send a WiresX disconnect when you turn off WiresX - that would be crazy but its possible.

Posted: **Sun Feb 03, 2019 12:28 pm**

Just to add here, when you choose YSF2P25, the radio will then say unlinked as it moves to YSF2P25 gateway, do another search to find the room you want to connect to, or dial the ID, 10200 etc.. The radio should then tell you you linked - and you should get the link confirmed back via audio on P25 mode.

Posted: **Sun Feb 03, 2019 3:54 pm**

MW0MWZ wrote:Just to add here, when you choose YSF2P25, the radio will then say unlinked as it moves to YSF2P25 gateway, do another search to find the room you want to connect to, or dial the ID, 10200 etc.. The radio should then tell you you linked - and you should get the link confirmed back via audio on P25 mode.

You'll get the same behaviour from NXDN as well, for every TG you change to, you get an announcement. P25 unfortunately only reports back on 10100, 10101, 10200, 10201, 10300, 10301, 10400, 10401 & 9999 (disconnect) it would be great if p25 used the same announcement as NXDN then you would get confirmation of a successful connection.

I realise that asking for the P25 announcement changes isn't the place here it needs to be on github!

Sent from my Pixel 2 XL using Tapatalk

Posted: **Sun Feb 03, 2019 7:19 pm**

VK7HSE wrote: ↑Sun Feb 03, 2019 3:54 pm
MW0MWZ wrote:Just to add here, when you choose YSF2P25, the radio will then say unlinked as it moves to YSF2P25 gateway, do another search to find the room you want to connect to, or dial the ID, 10200 etc.. The radio should then tell you you linked - and you should get the link confirmed back via audio on P25 mode.
You'll get the same behaviour from NXDN as well, for every TG you change to, you get an announcement. P25 unfortunately only reports back on 10100, 10101, 10200, 10201, 10300, 10301, 10400, 10401 & 9999 (disconnect) it would be great if p25 used the same announcement as NXDN then you would get confirmation of a successful connection.

I realise that asking for the P25 announcement changes isn't the place here it needs to be on github!

Sent from my Pixel 2 XL using Tapatalk

I'd honestly never noticed that... I don't use P25 that much myself... I'll bring it up with Jonathan and see if he's prepared to change the way the announcements are done.

Posted: **Sun Feb 03, 2019 8:13 pm**

MW0MWZ wrote: ↑Sun Feb 03, 2019 7:19 pm
I'd honestly never noticed that... I don't use P25 that much myself... I'll bring it up with Jonathan and see if he's prepared to change the way the announcements are done.

TGIF doesn't provide announcements on 4000 with unlink, which also throw YSF2DMR off since it waits for it. In fact, the concept of a 'disconnect' is simply just changing it to a talkgroup (4000) that is configured on the server to not repeat since you can only be on one talkgroup at a time on that platform.

For that reason, I had turned off EnableUnlink. I'll talk to Ty about adding an announcement when someone transmits on 4000 if EnableUnlink is a requirement for this method of passthru to work right.

K5MRE

Posted: **Sun Feb 03, 2019 11:23 pm**

I did some testing in YSF mode (no ysf2 bridge)
I turned the two new switches off "Uppercase and Wirex pass"
I assume that this would allow me to select ysf hosts as if without the additions.
I made a video that shows this is now broken.

Please look at the video. It could just be that this is where the problem is..

I will test with another unit that has not been patched, but I note the extra buttons are now present, so you must have done an update for this. I confirm that the same issue exists with another hot spot.
It first links then unlinks, the status of the two extra switches don't seem to make any difference.

Link to Video
https://drive.google.com/open?id=1t4Oqz ... Y6jnWZK2vg

forum.pistar.uk

WiresX Auto Passthrough

Re: WiresX Auto Passthrough

Re: WiresX Auto Passthrough

Re: WiresX Auto Passthrough

Re: WiresX Auto Passthrough

Re: WiresX Auto Passthrough

Re: WiresX Auto Passthrough

Re: WiresX Auto Passthrough

Re: WiresX Auto Passthrough

Re: WiresX Auto Passthrough

Re: WiresX Auto Passthrough