Showing posts with label MD-380G. Show all posts
Showing posts with label MD-380G. Show all posts

Thursday, May 31, 2018

Teardown & Comparison: TYT MD-UV380 Part 1

The dual band TYT MD-UV380 has just been released and promises much of the same functionality of the TYT MD-2017 and Retevis RT-82, but in the same form factor as the ever popular mono-band MD-380 and MD-390 series of radios.

This review goes under the hood of this latest $149.99 priced DMR & analog FM dual band handheld radio.

RF deck top view of the MD-UV380

Basic Overview


The MD-380 has been well reviewed elsewhere plus in past articles here on HVDN like the 2017 DMR entry level radio review.

The new MD-UV380 and MD-UV390 look identical to the mono-band versions and also include options with or without GPS.

Here are some side shots of the MD-UV380 (GPS) box which is somewhat informative on specifications.




Out Of The Box Differences

The firmware version out of the box for this sample was S15.021.  The latest version as of the date of this article appears to be S16.06 based on the TYT website download from May 23rd 2018.

While scrolling through the features in the CPS 1.03 and then updated into the radio to unlock certain menus, the major feature add on with the MD-UV380 is the ability to have up to 3 radio ID's and to change the mic gain.

Everything else is pretty much the same as the MD-380 stock firmware flow, not including the obvious addition of VHF and UHF coverage, like the MD-2017.

One feature introduced in the MD-2017 was built in "promiscuous" mode that allows monitoring of all DMR traffic on a specific time slot and correct color code. This has also made its way into the MD-UV380.



Also, like the MD-2017, the MD-UV380 can either allow audio to be recorded in DMR mode or provide the user with more contact storage space for the entire DMR ID database. Different firmware exists for either option for the MD-UV380 or MD-UV390.



From an outside hardware perspective, the MD-UV380 uses all the same accessories as the MD-380.  Same goes for the MD-390, which is just slightly larger than the MD-380. This is nice in order to recycle things like chargers, batteries and programming cords between the old and new radios.  The GD-77 by Radioddity also uses the same charger as the MD-380, so for users looking for a new dual band radio may want to consider the MD-UV380 over other similar radios.

The included stock dual band antenna seems to be of slightly higher quality compared to the antennas included with the mono-band MD-380/390 radios. The base of the MD-UV380 has an extended ferule to provide a little more waterproofing on the antenna connector on the radio.

Navigating the MD-UV380

Compared to the MD-2017 with its roller ball navigation, the MD-UV380 uses the arrow buttons below the display to flip between the upper and lower band assignments. This makes the UV-MD380 more like the Radioddity GD-77 or Anytone D868A from a navigation factor which is slightly less cumbersome than the MD-2017 roller-ball and will likely hold up better over time and prevent accidental band swaps or channel changes.

Channel selection in either the upper or lower band on the MD-UV380 is done through the top mount multi-selector knob. Compared to the MD380, there is no more limitation to 16 channels per zone which was sort of hard coded against the 16 position channel selector knob.  On the MD-UV380, as many as 64 channels per zone and possibly more is possible.


There will be more to talk about when it comes to the firmware updates, upgrades, channel management and overall user features, but that is not the main goal of this tear-down and comparison.

On the outside of the MD-UV380 from a distance, it would be hard to tell the difference between the MD-380, MD-380G, MD-390 and MD-390G. They all look the same and the only differences is the multi-selector knob, the label under the battery showing the model name and button coloration differences.

Inside the MD-UV380 and compared to the MD-380G

This is where things get interesting because the outside looks the same, but the inside does not.  Here are side by side comparisons of the MD-380G and the MD-UV380 (GPS). The outer-casing on the MD-UV380 seems to be styled like the earlier TYT versions whereas later ones had a more rounded speaker grill and colored buttons.

MD-UV380 on the left and MD-380G on the right

Things get interesting when looking at the two parts of the radio side by side after opening both up.

The MD-380G and MD-UV380 share the same exact board numbering for the user interface side of the radio as noted by KEY-V2.0-160329 text.   In the upper left corner near the speaker you can see the GPS antenna.

MD-UV380 on the left. MD-380G on the right.
Note the colored orange and blue buttons on the right side of the MD-380G

Swapping the RF deck from either radio with the UI board from the other confirms there is only one tiny difference.   The flat cable connector on both is slightly different which may just be a sourcing reason.  The connector on the MD-380 was a "piano hinge" type and the MD-UV380 was "compression lock" type. The flat ribbon cable fits the same way. Its possible over time that the "compression lock" version may be more reliable and limit the potential "white screen" issues some users have experienced when the connector and cable are not mated tightly at the factory.

Both radios upon re-assembly with the UI board and RF deck from both models confirmed identical operation and functionality. 

Should someone want the slightly more rounded housing and colored buttons from a MD-380G, but with the functions of the MD-UV380, this may be good to know.

The UI is the same but not the RF deck

As you would expect, the design of a dual-band radio would be just a little different than a mono-band version. Here is a side by side of both radios from the inside.

MD-UV380 at left and MD-380G at right

The major differences here get sort of fun. The same STM32F405 is used across both radios, but gone is the HR C5000 base band chip on the front side as in the MD-380.

In the MD-380G, the ST Microelectronics STM32F405VG is used which sports an ARM Cortex M4 core, up to 168MHz clock speed and 1024 KB of on board RAM. A more detailed spec sheet can be found on the STM website here.

The new MD-UV380 has the same STM32F405VG, but with slightly different date codes. It is unknown without further dissection if there are any small changes in the MCU since there is likely 2-3 time difference between the manufacture of both radios.

The "527" version was found in the MD-380 and the "664" version was found in the MD-UV380

Both radios also have the same Winbond 128K memory (W25Q128FV), but you may notice an empty pad for possibly an additional memory expansion on the MD-UV380.  This may be helpful as the user database for DMR ID's soon surpasses 100,000 which is the current limitation of many radios. As more DMR uses experiment with GPS, SMS and other mode translations such as those just introduced in Pi-Star, having additional memory will be a useful thing to have.

Note the empty pads for additional memory such as the 128k Winbond chip to left of  STM32F4055VG

For those that remember, the VHF versions of the MD-380 had less memory compared to the UHF versions which limited further alternative firmware development made popular by Travis Goodspeed, Ty Weaver, Warren Merkel and many others.

Perhaps lessons have been learned with the MD-UV380 to allow for future memory upgrades without complete redesign.  Its clear that TYT used the same UI board to simplify construction and offer a lower priced radio.

It seems all they really needed to do was just redesign the RF deck on the MD-UV380 after learning from the success and failures of the MD-2017 user interface and overly sized casing.

RF Front End

The RF front end is a combination of filtering for radio transmit and receive functions. On the MD-UV380 we can see some of that by looking at the SMD capacitors, resistors and inductors between the antenna connector and the copper pad which is a heat spreader for the RFPA on the underside of the RF deck board.

The MD-UV380 is a 136-174 MHz and 400-480 MHz radio, so its filtering would be more complex as expected compared to the UHF only version of the MD-380G.

MD-UV380 on left. MD-380G on right. It appears here that that the MD-380G is more complex on the rear of the RF unit compared to the MD-UV380. There has to be additional components on the underside of the RF deck board


Is That It? 

Clearly the top side of the  MD-UV380 seems more simple from a base-band perspective compared to that of the MD-380, but that is likely not the case.  All we have learned so far without further disassembly is the following:

  • Both radios appear to use the same STM MCU
  • Both radios have the same Winbond flash memory
  • The MD-UV380 seems to have the ability to increase on board memory due to empty pads.
  • The MD-UV380 may be using something else for base-band RF compared to the MD-380
  • The UI boards are common across both radios
  • The older style  and slightly larger housing from earlier MD-380 radios is used for the MD-UV380
Next Steps

The intent here was a basic under the hood look at the MD-UV380. Future coverage will include the underside of the RF deck and more about how the radio functions on the air plus other "deeper under the hood" analysis. 

One quick comment: Its possible to save a VHF or UHF frequency for transmit and the other band for receive.  Its also possible to save frequencies in as small as 2.5KHz steps. This may be of interest for those interested in satellite communications.

Stay tuned for more MD-UV380 coverage here on HVDN.  

Register for updates on the HVDN Notebook, become a member of HVDN or simply bookmark the following URL for anything posted here to do with DMR.


The most popular tags are visually represented on the Notebook for easy understanding on what is most popular at HVDN.  Most of HVDN active membership can be found on talk group 31368. 














Saturday, May 19, 2018

A National DMR Location Services Proposal


On the way back today from the Southern Berkshire Amateur Radio Club’s hamfest at the Goshen Fairgrounds of Connecticut proved a good opportunity to try out mobile location enablement via DMR.




Here is what was involved to make this work:
  • TYT MD-380G radio
  • JumboSpot Hotspot device
  • Mobile hotspot for internet via smartphone
  • Correctly programmed radio and Brandmeister account setup.
Some Lessons Learned

Compared to using APRS, which uses 144.39 MHz as a common national US frequency and a network of stations to ingest users packet transmissions directly or via digipeaters and igateways that can route data from "over the air" and onto the internet. Using DMR and “APRS like” functionality is different in how that same function is accomplished since it does not use AX.25 1200 baud packet..

The only way to get user reported location or messages to the aprs.fi website and back to other radios  is via your own DMR hotspot or a local repeater that is set up to allow private data calls to be passed through to the internet.

Smart Beaconing & Power Savings

APRS and much of the equipment available today supports a feature called “smart beaconing” which allows a user’s radio to transmit location data more often while traveling at higher speed compared to sitting stationary. The number of "beacon transmissions" are reduced thanks to smart beaconing to create less congestion on the dedicated national APRS frequency. More about smart beaconing can be found here and its other benefits.

The current implementation of location services on GPS enabled DMR radios such as the TYT MD-380G do not support smart beaconing, but can be user programmed to always beacon at preset intervals.  Smart beaconing provides the major benefit of better battery life and better route accuracy for APRS. 

Wish List Item #1: Location enabled DMR needs this same capability, especially for portable/handheld radios.

GPS location is only sent at a present interval or during PTT on a DMR radio, so there is no "smart" capability at present time.  Accurate travel routes can thus only be created based on how frequent the user transmits which explains the rather strange route shown on aprs.fi for this experiment. Not having smart beaconing makes DMR location enablement to be less accurate for route tracking and efficient spectrum management.

Routing & Prediction

The second lesson learned is that the APRS.fi website does not fill in better predicted routes if DMR location enabled transmissions are missed. In the case of the route 199 in New York, there is horrible mobile phone connectivity and my mobile phone did not have internet access the whole time, which prevented any GPS transmissions sent from the MD-380 to the JumboSpot from being reported.  Since there are no repeaters that cover this particular area or offer private data calls, the only way to use location enabled DMR is via a mobile hotspot. 

Wish List Item #2:  More capable repeaters are needed to fully realize DMR benefits.
Even when entering back into better mobile coverage areas on parts of routes 199 and 308, it was not safe and appropriate to continue pressing the PTT to send location packets to better report accurate “breadcrumbs” on the route since it would congest the frequency I was using with my hotspot.

Even during a discussion with another DMR user via TG 310, my  DMR radio only transmits the location data at the start of transmission. Having 30-45 seconds of my own transmit speech and then listening to a reply for as long a period spreads out the rate of GPS transmissions, which inhibits quicker location reporting via TG 310999.

National Proposal on using DMR and GPS

Some ideas to aid in adoption of using GPS via DMR  includes:
  • Add functions at the radio level that support smart beaconing rather than just setting a high rate of transmission or just via PTT. 
  • Have the radio acknowledge when its transmissions are not confirmed as being sent to the internet and to “buffer” them for later transmission to fill in gaps on possible routing.  This involves saving GPS locations with speed of travel and altitude which is available on the radio. This solves the gap issue and is not far different how many automotive GPS's work when loss of sky coverage happens. 
  • Create a network of receive only gateways on VHF or UHF to listen for data packets on common frequencies for the purpose of location messaging that will only pass traffic on a certain time slot (TS2) and destination talk group (TG 262993). 
  • Adding on transmit capability for a repeater that will broadcast private data calls to users that will not impact voice users at the same time.
  • Challenge repeater owners to add an additional equipment to support this function and make use of great siting available at repeater sites. Many repeater sites already host APRS digipeaters and have internet access so this should be easy to add and expand value offered by DMR.
  • Decide on two national frequencies for GPS messaging and reporting use for VHF and UHF.
Why do this with DMR rather than just use APRS?

APRS does many things well and is fairly simple which makes it appealing, but its age is starting to  show.

A shortcoming of APRS is the inability to easily deliver an actual street address level of resolution to a radio. All APRS radios can only show coordinates, bearing and distance to another user which is limiting at times.

Location enabled DMR provides the ability to match coordinates to a physical street address and see that on the screen of the radio.  This works simply by addressing a private message to TG 262993 by sending "gps" as a message.  The reply message takes your radio GPS coordinates, matches it against mapping API's via Google Maps or Open Street Mapping project where it finds the street address and then sends that back to your radio.



Other commands summarized in a previous article also allows you to see distance, bearing and street address closest to another location enabled DMR user.

Location enabled DMR also lets the user request weather conditions the same way by messaging to "wx gps". The resulting reply matches up the GPS enabled DMR radio with closest weather conditions found on the internet. Temperature, humidity and barometric pressure is than easily viewed on relatively inexpensive DMR radios. 



If using an APRS radio, the user needs to spend much more money to see this level of detail or sacrifice some level of portability if not using some of the advanced APRS handhelds currently available. 

Weather and location are just two easy examples of how to use location data as a source for value added information.  Sending email, local frequency information for voice communication and other data are easily routed or sent from a DMR radio.

These are some modern ways in which ham radio can remain relevant in a world of smart phone dominated but mobile network dependent messaging.

Wish List Item #3: Adding functions like this are what ham radio is all about, so perhaps more DMR repeater owners will start considering adding a simple weather station, offline mapping database and secondary receivers to support some of this functionality. 

Here is some further related reading on HVDN if this sounds of interest: