Project

General

Profile

Actions

New Model #3997

open

TYT MD-390 GPS

Added by Paul St. Amand over 7 years ago. Updated over 7 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
09/07/2016
Due date:
% Done:

0%

Estimated time:
Equipment Loan/Gift Offered:
No
I read the instructions above:

Description

Hello,

I just purchased a TYT MD-390 and starting to work with the vendor provided software.

http://www.amateurradio.com/first-look-tytera-tyt-md-390-dmr-ht/

What help can I provide to get this unit supported within CHIRP.

Paul


Files

TYTMD-390 20160906ManualWZonesChannelsScan.rdt (257 KB) TYTMD-390 20160906ManualWZonesChannelsScan.rdt Paul St. Amand, 09/07/2016 06:52 PM
CT CS700 Code Plug 22.rdt (257 KB) CT CS700 Code Plug 22.rdt Paul St. Amand, 09/07/2016 06:52 PM
TYTMD-390 20160906.rdt (257 KB) TYTMD-390 20160906.rdt Paul St. Amand, 09/07/2016 06:52 PM

Related issues

Related to New Model #3755: TYT/Tytera MD-380In ProgressTom Hayward06/18/2016

Actions
Has duplicate New Model #3999: TYT MD-390 GPSRejected09/07/2016

Actions
Has duplicate New Model #5287: TYT Tytera MD-380 MD-390 DMRClosed10/28/2017

Actions
Actions #1

Updated by Paul St. Amand over 7 years ago

This is a duplicate and I cant find a place to close it.

Actions #2

Updated by Paul St. Amand over 7 years ago

This one isnt the duplicate, the other was flagged by someone else.

Actions #3

Updated by Paul St. Amand over 7 years ago

I took a look at the files in a hex editor and this file is structured very close to the CS-700 file. I've been able to get a cs700 parts extract and pasted into a file the software and radio tolerates. The GPS details toggle a few of the bits ending at FF FF FF FF 00 00 FC where GPS sewnd and rx are set and FC is FF where the is not set, same as the CS700 plug. I've been able to get the zones, channels, and contacts transferred from a CS 700 file into a MD-390 GPS model. I've only taken the Contacts, Zones, and Channels sections and replaced the bit into the file I extracted from the initial radio file.

Actions #4

Updated by Tom Hayward over 7 years ago

Can you post the .rdt here?

Actions #5

Updated by Paul St. Amand over 7 years ago

The CS700 AREA codeplug file was my starting point... The TYT I started with reading from the radio fresh out of the box, and the TYT after some hexedit and alignment and pasted, hoped for very little list length checking or anything else... And, the TYT software seemed happy, I tried writing, and the radio seemed happy... Being very new to DMR I'm still trying to figure all the channels and talkgroups and user activated activation...

Actions #6

Updated by Paul St. Amand over 7 years ago

Paul St. Amand wrote:

The CS700 ARES codeplug file was my starting point... The TYT I started with reading from the radio fresh out of the box, and the TYT after some hexedit and alignment and pasted, hoped for very little list length checking or anything else... And, the TYT software seemed happy, I tried writing, and the radio seemed happy... Being very new to DMR I'm still trying to figure all the channels and talkgroups and user activated activation...

Actions #7

Updated by Tom Hayward over 7 years ago

You lost me... Were these generated by the official software or not? Before I study them I want to make sure there are no errors or incorrect assumptions in them.

Actions #8

Updated by Paul St. Amand over 7 years ago

This was a read with official software. If you've looked at CS700 files , you'll see this one is very similar. Looking at the interface aside from some minor screen window sizes and GPS setting not in the CS700 software they are very similar.

TYTMD-390 20160906.rdt is a read of the radio directly out of the box

This I assume was created with the official software

CT CS700 Code Plug 22.rdt was generated by a member of the local ARES club for the CS700

This is my merge of above file with the 1st file

TYTMD-390 20160906ManualWZonesChannelsScan.rdt is my hex edit of the ARES CS700 plug into the factory read file above, so ignore this one if you want to avoid any potential errors. I copied the zone channel and scan sections from the CS700 and pasted them at what appeared to be the appropriate offset. The software and the radio seem happy.

Actions #9

Updated by Tom Hayward over 7 years ago

  • Status changed from New to In Progress
  • Assignee set to Tom Hayward

Great, thanks. I tried opening the TYTMD-390 file with my work-in-progress MD-380 driver. It opened fine, the channel list, zone list, and group lists all populated. It looks like I'll be able to support both of these once the driver is complete.

The CS-700 file opened and read the frequencies and names correctly. A number of channels reported errors, so apparently a few bits are different. At least the basic structure is the same. I can probably suss these out and support this radio too.

Actions #10

Updated by Paul St. Amand over 7 years ago

I can look over the screens between the cs700 and md390 GPS for differences.

So far...

General Settings Add on the CPS MD-390 w GPS
Radio Program password, looks for max 8 characters
Back light time: Always, 5 10, 15
Set keypad lock time: never, 5, 10, 15

Intro screen section
Intro Screen: Picture, char string
Intro Screen line 1: 20 chars
Intro Screen line 2: 20 chars

Let me know if you need the offsets for any of these of set values and send the before and after files

In channel info

3 fields are additional:
Send GPS Info: check box These are both in the FF that became FC
Receive GPS Info: check box

GPS System: none, 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16

Actions

Also available in: Atom PDF