YSF to WiresX Bridge causing ILS error

Post Reply
KE8O
Posts: 10
Joined: Tue Jul 04, 2017 7:44 pm

YSF to WiresX Bridge causing ILS error

Post by KE8O » Wed Oct 24, 2018 12:43 am

This is a strange one. I’m using an OpenSpot to bridge our YSF reflector to our WiresX room via simplex WiresX node. The YSF reflector is also bridged to a Brandmeister TG via IP bridging setup by one of the BM admins. All of this has been in place since February 2018 and has worked flawlessly. The computer that hosts our main WiresX room and the computer that hosts the YSF reflector are at the same location and we’re fortunate to be in data center environment. We have one user who has a WiresX node and two different PiStar hotspots. He also has two different FT70DR handhelds. When he comes to our room using his WiresX node there are no issues. However, when he comes in using the YSF reflector with either of his PiStar hotspots or either FT70DR the WiresX node running the simplex node for the bridging receivers ILS errors and crashes. We also notice in the box that shows the uplink / downlink information on the WiresX node his callsign and radio type will vanish and changes from his callsign/radio type to Openspot right before the WiresX node crashes. When he configures his hotspot to use YSF2DMR and comes in using the BM TG it works fine. The OpenSpot is running the latest firmware I believe released in July. This is a real head scratcher and this problem only surfaced within the last 4 to 6 weeks.

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 3731
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: YSF to WiresX Bridge causing ILS error

Post by HA2NON » Wed Oct 24, 2018 7:09 am

Is the C4FM call confirmation turned off in the openSPOT?
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

KE8O
Posts: 10
Joined: Tue Jul 04, 2017 7:44 pm

Re: YSF to WiresX Bridge causing ILS error

Post by KE8O » Wed Oct 24, 2018 4:37 pm

Yes otherwise when anyone unkeyed it would say OpenSpot after their transmission.

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 3731
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: YSF to WiresX Bridge causing ILS error

Post by HA2NON » Wed Oct 24, 2018 5:15 pm

What does the openSPOT's USB serial console log show?
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

KE8O
Posts: 10
Joined: Tue Jul 04, 2017 7:44 pm

Re: YSF to WiresX Bridge causing ILS error

Post by KE8O » Sat Nov 10, 2018 11:48 am

We have noticed other users causing this error. The user who causes this most frequently has been away on holiday. He has returned and we will capture the USB log details soon.

KE8O
Posts: 10
Joined: Tue Jul 04, 2017 7:44 pm

Re: YSF to WiresX Bridge causing ILS error

Post by KE8O » Mon Dec 03, 2018 12:55 pm

Sorry it’s taken so long. Here’s the USB log for one of the users that caused the ILS error in our WiRESX bridge to crash and restart.

c4fmcalltracker: got header
c4fmpacket: header
dst: 48038E5NCr src: K8JPL
dl: K8JPL ul: K8JPL
c4fmcalltracker: call started, dst: 48038E5NCr src: K8JPL
ysfref: rx seqnum: 0
ysfref: call started
ysfref: rx seqnum: 1
ysfref: rx seqnum: 2
ysfref: rx seqnum: 3
ysfref: received poll
ysfref: rx seqnum: 4
ysfref: rx seqnum: 5
ysfref: rx seqnum: 6
ysfref: rx seqnum: 7
ysfref: rx seqnum: 8
ysfref: rx seqnum: 9
ysfref: rx seqnum: 10
ysfref: rx seqnum: 11
ysfref: rx seqnum: 12
ysfref: rx seqnum: 13
ysfref: rx seqnum: 14
ysfref: rx seqnum: 15
ysfref: rx seqnum: 16
ysfref: rx seqnum: 17
ysfref: rx seqnum: 18
ysfref: rx seqnum: 19
ysfref: rx seqnum: 20
ysfref: rx seqnum: 21
ysfref: rx seqnum: 22
ysfref: rx seqnum: 23
ysfref: rx seqnum: 24
ysfref: rx seqnum: 25
ysfref: rx seqnum: 26
ysfref: rx seqnum: 27
ysfref: rx seqnum: 28
ysfref: rx seqnum: 29
ysfref: rx seqnum: 30
ysfref: rx seqnum: 31
ysfref: rx seqnum: 32
ysfref: rx seqnum: 33
ysfref: rx seqnum: 34
ysfref: rx seqnum: 35
ysfref: rx seqnum: 36
ysfref: rx seqnum: 37
ysfref: rx seqnum: 38
ysfref: rx seqnum: 39
ysfref: rx seqnum: 40
ysfref: rx seqnum: 41
ysfref: rx seqnum: 42
ysfref: rx seqnum: 43
ysfref: rx seqnum: 44
ysfref: rx seqnum: 45
ysfref: rx seqnum: 46
ysfref: rx seqnum: 47
ysfref: rx seqnum: 48
ysfref: rx seqnum: 49
ysfref: rx seqnum: 50
ysfref: rx seqnum: 51
ysfref: rx seqnum: 52
ysfref: rx seqnum: 53
ysfref: received poll
ysfref: rx seqnum: 54
ysfref: sending poll
ysfref: received poll
ysfref: rx seqnum: 55
ysfref: rx seqnum: 56
ysfref: rx seqnum: 57
ysfref: rx seqnum: 58
ysfref: rx seqnum: 59
ysfref: rx seqnum: 60
ysfref: rx seqnum: 61
ysfref: rx seqnum: 62
ysfref: rx seqnum: 63
ysfref: rx seqnum: 64
ysfref: rx seqnum: 65
ysfref: rx seqnum: 66
ysfref: rx seqnum: 67
ysfref: rx seqnum: 68
ysfref: rx seqnum: 69
ysfref: rx seqnum: 70
ysfref: rx seqnum: 71
ysfref: rx seqnum: 72
ysfref: rx seqnum: 73
ysfref: rx seqnum: 74
ysfref: rx seqnum: 75
ysfref: rx seqnum: 76
ysfref: rx seqnum: 77
ysfref: rx seqnum: 78
ysfref: rx seqnum: 79
ysfref: rx seqnum: 80
ysfref: rx seqnum: 81
ysfref: rx seqnum: 82
ysfref: rx seqnum: 83
ysfref: rx seqnum: 84
ysfref: rx seqnum: 85
ysfref: rx seqnum: 86
ysfref: rx seqnum: 87
ysfref: rx seqnum: 88
ysfref: rx seqnum: 89
ysfref: rx seqnum: 90
ysfref: rx seqnum: 91
ysfref: rx seqnum: 92
ysfref: rx seqnum: 93
ysfref: rx seqnum: 94
ysfref: rx seqnum: 95
ysfref: rx seqnum: 96
ysfref: rx seqnum: 97
ysfref: rx seqnum: 98
ysfref: rx seqnum: 99
ysfref: rx seqnum: 100
ysfref: rx seqnum: 101
ysfref: rx seqnum: 102
ysfref: rx seqnum: 103
ysfref: received poll
ysfref: rx seqnum: 104
ysfref: rx seqnum: 105
ysfref: rx seqnum: 106
ysfref: rx seqnum: 107
ysfref: rx seqnum: 108
ysfref: rx seqnum: 109
ysfref: rx seqnum: 110
ysfref: rx seqnum: 111
ysfref: rx seqnum: 112
ysfref: rx seqnum: 113
ysfref: rx seqnum: 114
ysfref: rx seqnum: 115
ysfref: sending poll
ysfref: received poll
ysfref: rx seqnum: 116
ysfref: rx seqnum: 117
ysfref: rx seqnum: 118
ysfref: rx seqnum: 119
ysfref: rx seqnum: 120
ysfref: rx seqnum: 121
ysfref: rx seqnum: 122
ysfref: rx seqnum: 123
ysfref: rx seqnum: 124
ysfref: rx seqnum: 125
ysfref: rx seqnum: 126
ysfref: rx seqnum: 127
ysfref: rx seqnum: 0
ysfref: rx seqnum: 1
ysfref: rx seqnum: 2
ysfref: rx seqnum: 3
ysfref: rx seqnum: 4
ysfref: rx seqnum: 5
ysfref: rx seqnum: 6
ysfref: rx seqnum: 7
ysfref: rx seqnum: 8
ysfref: rx seqnum: 9
ysfref: rx seqnum: 10
ysfref: rx seqnum: 11
ysfref: rx seqnum: 12
ysfref: rx seqnum: 13
ysfref: rx seqnum: 14
ysfref: rx seqnum: 15
ysfref: rx seqnum: 16
ysfref: rx seqnum: 17
ysfref: rx seqnum: 18
ysfref: rx seqnum: 19
ysfref: rx seqnum: 20
ysfref: rx seqnum: 21
ysfref: rx seqnum: 22
ysfref: rx seqnum: 23
ysfref: rx seqnum: 24
ysfref: rx seqnum: 25
ysfref: received poll
ysfref: rx seqnum: 26
ysfref: rx seqnum: 27
ysfref: rx seqnum: 28
ysfref: rx seqnum: 29
ysfref: rx seqnum: 30
ysfref: rx seqnum: 31
ysfref: rx seqnum: 32
ysfref: rx seqnum: 33
ysfref: rx seqnum: 34
ysfref: rx seqnum: 35
ysfref: rx seqnum: 36
ysfref: rx seqnum: 37
ysfref: rx seqnum: 38
ysfref: rx seqnum: 39
ysfref: rx seqnum: 40
ysfref: rx seqnum: 41
ysfref: rx seqnum: 42
ysfref: rx seqnum: 43
ysfref: rx seqnum: 44
ysfref: rx seqnum: 45
ysfref: rx seqnum: 46
ysfref: rx seqnum: 47
ysfref: rx seqnum: 48
ysfref: sending poll
ysfref: received poll
ysfref: rx seqnum: 49
ysfref: rx seqnum: 50
ysfref: rx seqnum: 51
ysfref: rx seqnum: 52
ysfref: rx seqnum: 53
ysfref: rx seqnum: 54
ysfref: rx seqnum: 55
ysfref: rx seqnum: 56
ysfref: rx seqnum: 57
ysfref: rx seqnum: 58
ysfref: rx seqnum: 59
ysfref: rx seqnum: 60
ysfref: rx seqnum: 61
ysfref: rx seqnum: 62
ysfref: rx seqnum: 63
ysfref: rx seqnum: 64
ysfref: rx seqnum: 65
ysfref: rx seqnum: 66
ysfref: rx seqnum: 67
ysfref: rx seqnum: 68
ysfref: rx seqnum: 69
ysfref: rx seqnum: 70
ysfref: rx seqnum: 71
ysfref: rx seqnum: 72
ysfref: rx seqnum: 73
ysfref: rx seqnum: 74
ysfref: rx seqnum: 75
ysfref: received poll
ysfref: rx seqnum: 76
ysfref: rx seqnum: 77
ysfref: rx seqnum: 78
ysfref: rx seqnum: 79
ysfref: rx seqnum: 80
ysfref: rx seqnum: 81
ysfref: rx seqnum: 82
ysfref: rx seqnum: 83
ysfref: rx seqnum: 84
ysfref: rx seqnum: 85
ysfref: rx seqnum: 86
ysfref: rx seqnum: 87
ysfref: rx seqnum: 88
ysfref: rx seqnum: 89
ysfref: rx seqnum: 90
ysfref: rx seqnum: 91
ysfref: rx seqnum: 92
ysfref: rx seqnum: 93
ysfref: rx seqnum: 94
ysfref: rx seqnum: 95
ysfref: rx seqnum: 96
ysfref: rx seqnum: 97
ysfref: rx seqnum: 98
ysfref: rx seqnum: 99
ysfref: rx seqnum: 100
ysfref: rx seqnum: 101
ysfref: rx seqnum: 102
ysfref: rx seqnum: 103
ysfref: rx seqnum: 104
ysfref: rx seqnum: 105
ysfref: rx seqnum: 106
ysfref: rx seqnum: 107
ysfref: rx seqnum: 108
ysfref: rx seqnum: 109
ysfref: sending poll
ysfref: received poll
ysfref: rx seqnum: 110
ysfref: rx seqnum: 111
ysfref: rx seqnum: 112
ysfref: rx seqnum: 113
ysfref: rx seqnum: 114
ysfref: rx seqnum: 115
ysfref: rx seqnum: 116
ysfref: rx seqnum: 117
ysfref: rx seqnum: 118
ysfref: rx seqnum: 119
ysfref: rx seqnum: 120
ysfref: rx seqnum: 121
ysfref: rx seqnum: 122
ysfref: rx seqnum: 123
ysfref: rx seqnum: 124
ysfref: rx seqnum: 125
ysfref: received poll
ysfref: rx seqnum: 126
ysfref: rx seqnum: 127
ysfref: rx seqnum: 0
ysfref: rx seqnum: 1
ysfref: rx seqnum: 2
ysfref: rx seqnum: 3
ysfref: rx seqnum: 4
ysfref: rx seqnum: 5
ysfref: rx seqnum: 6
ysfref: rx seqnum: 7
ysfref: rx seqnum: 8
ysfref: rx seqnum: 9
ysfref: rx seqnum: 10
ysfref: rx seqnum: 11
ysfref: rx seqnum: 12
ysfref: rx seqnum: 13
ysfref: rx seqnum: 14
ysfref: rx seqnum: 15
ysfref: rx seqnum: 16
ysfref: rx seqnum: 17
ysfref: rx seqnum: 18
ysfref: rx seqnum: 19
ysfref: rx seqnum: 20
ysfref: rx seqnum: 21
ysfref: rx seqnum: 23
ysfref: invalid seqnum received, got 23 expected 22, missing 1 packets
ysfref: rx seqnum: 24
ysfref: rx seqnum: 26
ysfref: invalid seqnum received, got 26 expected 25, missing 1 packets
ysfref: rx seqnum: 27
ysfref: rx seqnum: 28
ysfref: rx seqnum: 29
ysfref: rx seqnum: 30
ysfref: rx seqnum: 32
ysfref: invalid seqnum received, got 32 expected 31, missing 1 packets
ysfref: rx seqnum: 35
ysfref: invalid seqnum received, got 35 expected 33, missing 2 packets
ysfref: rx seqnum: 37
ysfref: invalid seqnum received, got 37 expected 36, missing 1 packets
ysfref: rx seqnum: 38
ysfref: rx seqnum: 39
ysfref: rx seqnum: 40
ysfref: rx seqnum: 41
ysfref: rx seqnum: 42
ysfref: sending poll
ysfref: received poll
ysfref: rx seqnum: 43
ysfref: rx seqnum: 45
ysfref: invalid seqnum received, got 45 expected 44, missing 1 packets
ysfref: rx seqnum: 47
ysfref: invalid seqnum received, got 47 expected 46, missing 1 packets
ysfref: received poll
ysfref: rx seqnum: 48
ysfref: rx seqnum: 50
ysfref: invalid seqnum received, got 50 expected 49, missing 1 packets
ysfref: rx seqnum: 51
ysfref: rx seqnum: 53
ysfref: invalid seqnum received, got 53 expected 52, missing 1 packets
ysfref: rx seqnum: 54
ysfref: rx seqnum: 55
ysfref: rx seqnum: 56
ysfref: rx seqnum: 57
ysfref: rx seqnum: 58
ysfref: rx seqnum: 59
ysfref: rx seqnum: 60
ysfref: rx seqnum: 61
ysfref: rx seqnum: 62
ysfref: rx seqnum: 63
ysfref: rx seqnum: 64
ysfref: rx seqnum: 65
ysfref: rx seqnum: 66
ysfref: rx seqnum: 67
ysfref: rx seqnum: 69
ysfref: invalid seqnum received, got 69 expected 68, missing 1 packets
ysfref: rx seqnum: 70
ysfref: rx seqnum: 71
ysfref: rx seqnum: 72
ysfref: rx seqnum: 73
ysfref: rx seqnum: 74
ysfref: rx seqnum: 75
ysfref: rx seqnum: 76
ysfref: rx seqnum: 77
ysfref: rx seqnum: 78
ysfref: rx seqnum: 79
ysfref: rx seqnum: 80
ysfref: rx seqnum: 81
ysfref: rx seqnum: 82
ysfref: rx seqnum: 83
ysfref: rx seqnum: 84
ysfref: rx seqnum: 85
ysfref: rx seqnum: 86
ysfref: rx seqnum: 87
ysfref: rx seqnum: 88
ysfref: rx seqnum: 89
ysfref: rx seqnum: 90
ysfref: rx seqnum: 91
ysfref: rx seqnum: 92
ysfref: rx seqnum: 93
ysfref: rx seqnum: 94
ysfref: rx seqnum: 95
ysfref: rx seqnum: 96
ysfref: rx seqnum: 97
ysfref: received poll
ysfref: rx seqnum: 98
ysfref: rx seqnum: 99
ysfref: rx seqnum: 100
ysfref: rx seqnum: 101
ysfref: rx seqnum: 102
ysfref: rx seqnum: 103
ysfref: sending poll
ysfref: received poll
ysfref: rx seqnum: 104
c4fmcalltracker: got terminator
c4fmpacket: header
dst: 48038E5NCr src: K8JPL
dl: K8JPL ul: K8JPL
c4fmcalltracker: call ended
ysfref: call ended

User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 3731
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: YSF to WiresX Bridge causing ILS error

Post by HA2NON » Mon Dec 03, 2018 4:19 pm

Are voice announcements turned off? (besides C4FM call confirmation)

The openSPOT only transmits it's product name as the C4FM callsign in voice announcement and call confirmation calls.

What hotspot the user uses? Is an openSPOT in cross mode from DMR radio to YSFReflector?
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

KE8O
Posts: 10
Joined: Tue Jul 04, 2017 7:44 pm

Re: YSF to WiresX Bridge causing ILS error

Post by KE8O » Tue Dec 18, 2018 9:59 am

Yes voice announcements are turned off. These are Yaesu C4FM users coming in with MMDVM based hotspots running PiStar to our YSF reflector. What is very interesting is we have discovered if these users switch their configuration from YSF to YSF2DMR and come is using our link DMR talkgroup 31399 the ILS errors stop and the node does not crash.

KE8O
Posts: 10
Joined: Tue Jul 04, 2017 7:44 pm

Re: YSF to WiresX Bridge causing ILS error

Post by KE8O » Wed Jan 23, 2019 2:11 am

Upon further investigation the problem is with MMDVM users who leave their WiresX control screen up on their radios after switching YSF reflectors or when they query the YSF server. Apparently this causes some data to get passed to the bridged WiresX room that the Yaesu software does not like. It will be interesting to see if this problem will exist with the OpenSpot2 when WiresX control becomes available in a future update. It would also be nice if SharkRF would allow some configuration setting to allow those who are using their OpenSpot or OpenSpot2 products to bridge YSF to WiresX to filter out WiresX control data from getting passed to the Yaesu Wiresx software.

73,
...Gary

KE8O
Posts: 10
Joined: Tue Jul 04, 2017 7:44 pm

Re: YSF to WiresX Bridge causing ILS error

Post by KE8O » Thu Jan 24, 2019 4:03 pm

Here’s another discovery. We recently added a new repeater to our network. While we await delivery of an HRI200 we installed a OpenSpot(original) on the repeater frequency to bridge that repeater into our YSF reflector. Anyone who hits the WiRESX button on their radio connected to the new repeater causes the WiRESX software to crash.

Post Reply