127

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

127

Post by WA6NHC » Wed Sep 13, 2017 4:49 pm

I loaded 127. The TYT radio does not decode 9998 readily with 127, so even the wake up transmission is not heard. Moving back to 126 fixed that.

Also, somewhere in the last couple upgrades, the static group display (status) was lost, not being shown now. The active connection is shown. The static groups are announced on boot up, Brandmeister shows them but not the status page.

Thank you,
Rick wa6nhc/7

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

Re: 127

Post by HA2NON » Thu Sep 14, 2017 6:49 am

Please re-run DMR autocal after the upgrade.

The linked TG/reflector information is downloaded by your browser from the BrandMeister API, if it's unreachable by some reason by the browser, it won't display it.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

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

Re: 127

Post by WA6NHC » Fri Sep 15, 2017 6:02 pm

I re-did the cal, no change in setting.

The TYT is still not getting the audio from 127 (9998).

The display is still not showing the static groups from BM, although BM reports correctly.
Attachments
BM display
BM display
2.png (8.89 KiB) Viewed 2546 times
Status display
Status display

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

Re: 127

Post by HA2NON » Fri Sep 15, 2017 6:30 pm

Please use the Homebrew connector in Homebrew protocol mode to connect to BrandMeister servers, and then it will show TG link information.

Have you added TG9 to your radio's RX group list, and assigned that list to the radio's current channel?
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

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

Re: 127

Post by WA6NHC » Fri Sep 15, 2017 8:58 pm

If you look at the information I've given you, you will see that it IS connected as a homebrew to a Brandmeister server and that it was working correctly (on TG9) in all versions prior to 127.

I've rerun calibrate (no change, same result, D), nothing has changed in the radio, only the OpenSPOT, which tells me that something is not correct in 127. Until this is resolved, I'll continue to use 126, which works correctly.

Thank you
Rick

TYT MD380 with the current firmware

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

Re: 127

Post by HA2NON » Sat Sep 16, 2017 8:37 am

The status page does not show if you use Homebrew protocol or MMDVM protocol. We've only changed the modem firmware between v126 and v127, the web interface is untouched, so I suggest you to do a full web interface reload. We can't reproduce the issue on 446.527500 with our Tyt MD380, but we'll investigate.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

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

Re: 127

Post by WA6NHC » Sat Oct 07, 2017 3:45 pm

I've tried this again since .127 has been made the current stable release apparently. I ask you to carefully review the differences from .126 and .127 modem again. Something is slightly off with the OpenSPOT transmitter timing under .127 that is not happening with .126.

.126 near flawless decoding on the TYT MD-380, only the very random dropout.

.127 loads fine (re-downloaded it from your server to ensure a clean copy). NO changes on the radio.

Results are that the MD-380 (stock firmware D013.032, CPU v01.32) no longer reliably decodes what the OpenSPOT transmits with .127 loaded. Changing to 4FSK (Raised Cosine), [9600/648] seems to improve the radio decode but it's still unreliable.

Auto Cal rerun, no change. D

Modem: DMR Hotspot
Connector: Homebrew/MMDVM
Protocol: Homebrew

I know I'm not the only one with the decoding problem, please recheck your mods. There is a subtle timing issue apparently with this OpenSPOT. Thank you,

Rick nhc

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

Re: 127

Post by IK8JHL » Sun Oct 08, 2017 1:56 pm

Same problem
WA6NHC wrote:
Sat Oct 07, 2017 3:45 pm
I've tried this again since .127 has been made the current stable release apparently. I ask you to carefully review the differences from .126 and .127 modem again. Something is slightly off with the OpenSPOT transmitter timing under .127 that is not happening with .126.

.126 near flawless decoding on the TYT MD-380, only the very random dropout.

.127 loads fine (re-downloaded it from your server to ensure a clean copy). NO changes on the radio.

Results are that the MD-380 (stock firmware D013.032, CPU v01.32) no longer reliably decodes what the OpenSPOT transmits with .127 loaded. Changing to 4FSK (Raised Cosine), [9600/648] seems to improve the radio decode but it's still unreliable.

Auto Cal rerun, no change. D

Modem: DMR Hotspot
Connector: Homebrew/MMDVM
Protocol: Homebrew

I know I'm not the only one with the decoding problem, please recheck your mods. There is a subtle timing issue apparently with this OpenSPOT. Thank you,

Rick nhc

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

Re: 127

Post by GW4VRO » Sun Oct 08, 2017 6:42 pm

Same situation here, running MD380 perfectly on v123...since changing to v127 will not produce audio on mmdvm. connector. Openspot is transmitting, green light on mD380 is lit. Sometimes audio will start after between 5 - 10 seconds. When station drops carrier then same situation again. Have tried manually changing demod from A to F with no improvement

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

Re: 127

Post by HA2NON » Mon Oct 09, 2017 7:23 am

What RX/TX frequency do you use? We can't reproduce the issue with our MD380 and MD390s.
Norbert "Nonoo" Varga, HA2NON
SharkRF Team

Post Reply