127

GW4VRO
Posts: 22
Joined: Sat Mar 04, 2017 5:10 pm

Re: 127

Post by GW4VRO » Mon Oct 09, 2017 8:58 am

Hi Nonoo, have been using 430.025 but have changed to 433.500 with the same issue persisting. The receive reference is set to medium in the code plug and this issue also seems to affect the Parrot 9999 so it looks like an issue with the modem side. Once again with local parrot and 9990 if I make a long call the audio will generally kick in after approx 10 seconds.

GW4VRO
Posts: 22
Joined: Sat Mar 04, 2017 5:10 pm

Re: 127

Post by GW4VRO » Mon Oct 09, 2017 9:01 am

Everything continues to work perfectly on firmware v 0123

G4LZV
Posts: 1
Joined: Mon Oct 09, 2017 9:28 am

Re: 127

Post by G4LZV » Mon Oct 09, 2017 9:47 am

On my TYT MD-380 running both the stock firmware and the MD380Tools firmware I am getting similar results the those others are reporting. The announcements on 9998 are never heard with v0127, though the green LED is lit. Other channels are heard sometimes, but not reliably, and are never heard from the start of transmission.
My own echo on 9999 works slightly more reliably but it too doesn't always decode. Have run AutoCAL and this returns mode C regardless of firmware/frequency combination.
On v0123, everything works exactly as expected.
I have swapped back and forth between v0123 and v0127 on the Openspot and firmware on the radio and the common factor is v0127. Sorry guys, it might work for you, but it isn't working reliably for some of us.

Keith

IK8JHL
Posts: 162
Joined: Tue Dec 13, 2016 4:29 pm

Re: 127

Post by IK8JHL » Mon Oct 09, 2017 10:02 am

With 126 work corretly , im using 437.9875 , i have tested with original firmware on MD380 d13.020, Md380tools and MD380toolz ,
My suggest is to remove rapidly 127 from stable firmware. I have update and used in Dstar without problem a week ago . Yesterday i switch to DMR and i lost many time to understand where is the problem .
Thanks

WA6NHC
Posts: 43
Joined: Wed Dec 28, 2016 9:16 pm
Location: Naples, ID
Contact:

Re: 127

Post by WA6NHC » Mon Oct 09, 2017 2:48 pm

I use 446.5275 tx/rx.

Rick

User avatar
G7EQM
Posts: 19
Joined: Tue May 02, 2017 3:34 pm
Location: Hellidon, UK

Re: 127

Post by G7EQM » Tue Oct 10, 2017 9:43 am

Just found this posting...... had previously commented here but have experienced exactly the same thing this morning after upgrading to v1.27.

Regressed to 1.23 (the version I was previously running) and everthing is now fine

Using 438.50000 and an MD-380 with MD380 tools

73 Nick G7EQM

Tyrbiter
Posts: 292
Joined: Thu Dec 22, 2016 11:25 pm

Re: 127

Post by Tyrbiter » Tue Oct 10, 2017 12:52 pm

It's difficult to understand why this is happening to some and not others.

I have an MD-380, MD-390, RT-82 and PD785, all running different firmware, none of them is affected. I have been running 0127 firmware since it first became available as a beta version.

I wonder if this is somehow related to a particular batch of openSPOTs, FWIW I have had mine since late December 2016 but it wasn't bought direct, it came via a UK dealer's stock.
Brian

GW4VRO
Posts: 22
Joined: Sat Mar 04, 2017 5:10 pm

Re: 127

Post by GW4VRO » Wed Oct 11, 2017 7:53 am

For info, I have found that changing the demod to 4FSK Raised Cosine seems to have cleared the problem for me. This may or may not work for others but definitely something changed between firmware v0126 and 0127

IK8JHL
Posts: 162
Joined: Tue Dec 13, 2016 4:29 pm

Re: 127

Post by IK8JHL » Thu Oct 12, 2017 6:58 am

Tyrbiter wrote:
Tue Oct 10, 2017 12:52 pm
It's difficult to understand why this is happening to some and not others.

I have an MD-380, MD-390, RT-82 and PD785, all running different firmware, none of them is affected. I have been running 0127 firmware since it first became available as a beta version.

I wonder if this is somehow related to a particular batch of openSPOTs, FWIW I have had mine since late December 2016 but it wasn't bought direct, it came via a UK dealer's stock.
I dont not why happenning this , but its not normal that a Stable release have all this issue ,Sorry for Norbert but the stable version must be Tested before relase

Tyrbiter
Posts: 292
Joined: Thu Dec 22, 2016 11:25 pm

Re: 127

Post by Tyrbiter » Thu Oct 12, 2017 9:56 am

GW4VRO wrote:
Wed Oct 11, 2017 7:53 am
For info, I have found that changing the demod to 4FSK Raised Cosine seems to have cleared the problem for me. This may or may not work for others but definitely something changed between firmware v0126 and 0127
I have now loaded 0128, but on checking I note that my modem mode is set to 4FSK Raised Cosine, which it always has been since I got my openSPOT. I have never used plain 4FSK.

FW 0121 changed the default DMR modem mode to plain 4FSK, perhaps this is where this problem originated.

It's probably worth considering allowing the 4FSK RRC to be selectable between alpha=0.5 and alpha=0.7, the latter produces less aggressive filtering but still suppresses most of the spectral sidelobes whereas plain 4FSK does not. Plain 4FSK does not minimise inter-symbol interference which could be upsetting the demodulators in various radios.
Brian

Post Reply