dtrac_quansheng_uv-k6
差别
这里会显示出您选择的修订版和当前版本之间的差别。
| 两侧同时换到之前的修订记录前一修订版后一修订版 | 前一修订版 | ||
| dtrac_quansheng_uv-k6 [2025/10/15 17:51] – [隐藏校准菜单] BG6UD | dtrac_quansheng_uv-k6 [2025/10/19 19:27] (当前版本) – [实现功能] BG6UD | ||
|---|---|---|---|
| 行 4: | 行 4: | ||
| ===== 实现功能 ===== | ===== 实现功能 ===== | ||
| - | 仅需使用APP连接对讲机,抛弃繁琐全搞定,业余卫星通联操作更智能,实现以下功能: | + | 仅需使用APP连接对讲机,抛弃繁琐一个手机全搞定,业余卫星通联操作更智能,实现以下功能: |
| * 自动获取位置; | * 自动获取位置; | ||
| * 自动更新星历; | * 自动更新星历; | ||
| 行 11: | 行 11: | ||
| * 实时同步通联模式参数; | * 实时同步通联模式参数; | ||
| * 实时同步发射亚音参数; | * 实时同步发射亚音参数; | ||
| - | * 卫星入境时自动关闭静噪,离境后自动开启静噪; | + | * 卫星入境时自动开启监听,离境后自动关闭监听; |
| 注:由于泉盛UV-K5/ | 注:由于泉盛UV-K5/ | ||
| ===== 硬件改造 ===== | ===== 硬件改造 ===== | ||
| 行 35: | 行 35: | ||
| ===== 定制固件 ===== | ===== 定制固件 ===== | ||
| - | 定制的固件在egzumer最新固件上轻微修改,完整保留了原功能。 | + | 定制的固件在egzumer最新固件上轻微修改,完整保留了原功能。注: [[https:// |
| ===== 刷机方法 ===== | ===== 刷机方法 ===== | ||
| 行 64: | 行 63: | ||
| ===== 隐藏校准菜单 ===== | ===== 隐藏校准菜单 ===== | ||
| 进入固件隐藏校准菜单的方法如下:先按住“PTT”键和“按钮1”,然后打开对讲机,接着松开所有按键,即可进入隐藏菜单。进入后,找到与电池校准相关的选项,如“BatCal”,即可进行电压校准等操作。 | 进入固件隐藏校准菜单的方法如下:先按住“PTT”键和“按钮1”,然后打开对讲机,接着松开所有按键,即可进入隐藏菜单。进入后,找到与电池校准相关的选项,如“BatCal”,即可进行电压校准等操作。 | ||
| + | |||
| + | ===== 相关协议 ===== | ||
| + | |||
| + | ==== Protocol for UV-K6 ==== | ||
| + | |||
| + | The programming protocol used by this software has been reverse engineered | ||
| + | by observing communications between the radio and the original programming | ||
| + | software. It is not a variation of the typical Baofeng-like protocol. | ||
| + | |||
| + | |||
| + | The format of the datagram sent to the radio is: | ||
| + | |||
| + | 0xAB 0xCD len 0x00 <data bytes> <2 bytes CRC> 0xDC 0xBA | ||
| + | |||
| + | The length is the length of the data bytes. | ||
| + | |||
| + | The data is protected by a typical CRC-16 xmodem algorithm. | ||
| + | The data bytes and the CRC are obfuscated by xor-in it with an 8-byte | ||
| + | sequence. | ||
| + | |||
| + | Fortunately the EEPROM data contains a lot of 0xFF and 0x00 bytes, so the XOR | ||
| + | sequence is easy to find by observing the traffic. | ||
| + | |||
| + | |||
| + | The datagram sent from the radio is the same, but the CRC field is set to | ||
| + | 0xFFFF. This shows that the CRC is not for data integrity, but for further | ||
| + | obfuscation (same as the XOR). | ||
| + | |||
| + | |||
| + | I intend to publish a further description of the protocol, and the EEPROM | ||
| + | contents, meanwhile the sources can be used as documentation. | ||
| + | |||
| + | ==== Data for DTrac APP ==== | ||
| + | |||
| + | === for DTrac app CTCSS_CODE === | ||
| + | |||
| + | typedef struct { | ||
| + | Header_t Header; | ||
| + | uint8_t CTCSS_CODE; | ||
| + | } CMD_9999_t; | ||
| + | |||
| + | === for DTrac app downFreq === | ||
| + | |||
| + | typedef struct { | ||
| + | Header_t Header; | ||
| + | uint32_t DownFrequency; | ||
| + | } CMD_8888_t; | ||
| + | |||
| + | === for DTrac app upFreq === | ||
| + | |||
| + | typedef struct { | ||
| + | Header_t Header; | ||
| + | uint32_t UpFrequency; | ||
| + | } CMD_7777_t; | ||
| + | |||
| + | === for DTrac app mode === | ||
| + | |||
| + | typedef struct { | ||
| + | Header_t Header; | ||
| + | char Mode; | ||
| + | } CMD_6666_t; | ||
| + | |||
| + | === for DTrac app MonitorStatus === | ||
| + | |||
| + | typedef struct { | ||
| + | Header_t Header; | ||
| + | char MonitorStatus; | ||
| + | } CMD_5555_t; | ||
| + | |||
| + | |||
dtrac_quansheng_uv-k6.1760521893.txt.gz · 最后更改: 2025/10/15 17:51 由 BG6UD
