• To anyone looking to acquire commercial radio programming software:

    Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.

    If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.

    To obtain Motorola software see the Sticky in the Motorola forum.

    The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.

    For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).

    This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.

Tytera TYT MD-380 DMR receive issue

dazzler8985

Newbie
Joined
Aug 16, 2025
Messages
1
Reaction score
0
I've acquired a pair of TYT MD-380 radios, decommissioned from a school setting. The 'net' in the school consisted of five radios of this exact type.

The 'as supplied' codeplug in each radio is simple, the radio is given a 'contact name', one frequency, list of five contacts and use of basic encryption. My two radios were 'Headteacher' and 'Field'. One radio, 'Field' has issues, 'Headteacher' is the good guy and functions perfectly.

As obtained, 'Field' will not play any audio on DMR at all. It receives a signal from it's counterpart, shown on the screen, but no speech comes through. It will transmit perfectly though, audio is clear and well modulated. The speaker works fine, power on tone and keyboard tones work. Retested with my MD-390, DM-1701, fault persists on DMR rx only.

I've completed the following steps in order to fault find:

Antenna swapped, battery swapped and fully charged. Speaker/mic plugged in and attached, fault persists.

Firmware loaded: Factory MD380-D3.20, original was D2.24. Blank codeplug installed via 'tyt_kd4z_4.0'.
New codeplug, single PMR446 frequency set both on digital and analogue. No encryption set on digital, no CTCSS/DCS set on analogue. Digital contact list set as Local 9, slot 1, colour code 1, admit criteria 'always', in call criteria 'always'.

Analogue tx/rx works perfectly fine, good clear audio both ways. Digital still good tx, no audio on rx but radio shows the presence of an expected transmission.

Known working codeplug from my MD-390 installed in both MD-380s. 'Headteacher' all good, 'fault in 'Field' still persists.

Loaded various version of MD380 Tools and TYT toolz firmware, problem still the same. Loaded Voice Crypt 1.0a & 1.4p alpha. All this firmware functioned perfectly in terms of menu operations, non-encryption setting, etc, but still no audio coming through on DMR even when promiscuous mode was set. I did notice that 'Field' would sometimes display the incorrect time slot on the aforementioned forked firmwares. TX from 'Field' would always work as expected.

Now, sister radio 'Headteacher' was subjected the above procedures and worked perfectly well as part of a mirroring process. No time slot display errors.

So, am I looking at a software/firmware fault or something that it at a hardware level?

Observations and advice greatly appreciated, thank you.
 
Top