Project

General

Profile

Actions

New Model #9037

open

Retevis RT46

Added by Marian Giesen over 3 years ago. Updated almost 2 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/01/2021
Due date:
% Done:

0%

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

Description

Hallo, gibt es für das RT46 Ggf. Einen Ersatztypen?

Hello, is there any RT46 compatible radio [Chirp supports]?


Files

debug.log (28.1 KB) debug.log Marian Giesen, 05/07/2021 10:34 PM
debug.log (28.1 KB) debug.log Marian Giesen, 05/07/2021 10:34 PM
debug.log (28.1 KB) debug.log Marian Giesen, 05/07/2021 10:34 PM
debug.log (28.1 KB) debug.log Marian Giesen, 05/07/2021 10:35 PM
Actions #1

Updated by Bernhard Hailer over 3 years ago

  • Description updated (diff)
  • Status changed from New to Feedback

Probieren Sie mal die folgenden Einstellungen in Chirp:
Hersteller: Baofeng
Modell: BF-888
und lassen Sie uns wissen, ob's geht!

Please try this Chirp selection:
brand: Baofeng
model: BF-888
and let us know whether it works!

Actions #2

Updated by Marian Giesen over 3 years ago

Bernhard Hailer wrote:

Probieren Sie mal die folgenden Einstellungen in Chirp:
Hersteller: Baofeng
Modell: BF-888
und lassen Sie uns wissen, ob's geht!

Hello, and many thanks for the quick response.
I tested and it tells:
Radio refused to enter programming mode

So, it does not Download the Data...

Actions #3

Updated by Bernhard Hailer over 3 years ago

Okay, that's already something. Could you please provide a debug log as described in the Wiki: "How To Report Issues"? Thanks!

Actions #4

Updated by Marian Giesen over 3 years ago

Hello, here is the Debug Log.
I guess... this is the intresting part:
[2021-05-08 07:31:25,727] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'

Thanks for supporting!

Actions #5

Updated by Marian Giesen over 3 years ago

Hello, here is the Debug Log.
I guess... this is the intresting part:
[2021-05-08 07:31:25,727] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'

Thanks for supporting!

Actions #6

Updated by Marian Giesen over 3 years ago

Hello, here is the Debug Log.
I guess... this is the intresting part:
[2021-05-08 07:31:25,727] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'

Thanks for supporting!

Actions #7

Updated by Marian Giesen over 3 years ago

Hello, here is the Debug Log.
I guess... this is the intresting part:
[2021-05-08 07:31:25,727] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'

Thanks for supporting!

Actions #8

Updated by Bernhard Hailer over 3 years ago

No, the interesting part is actually above (the object attribute issue is a follow-up error). This looks more like a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
Windows notes: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
On older MacOS versions, you must have the KK7DS Python runtime for Mac OSX installed. I don't have information yet what to do on new versions (like Big Sur).
Big Sur is a problem on its own, because basically all USB drivers need to be rewritten. FTDI is still working on it.
Also see MacOS Tips!
Linux notes: Linux generally is quite good with USB to Serial converter drivers. The most likely cause for grief is a connector which doesn't provide good electrical contact.
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.

Actions #9

Updated by Bernhard Hailer almost 2 years ago

So, did the BF-888 driver do the trick?

Actions #10

Updated by Marian Giesen almost 2 years ago

Hello, unfortunately not so I guess it is a cheap-china-cable issue and until now, I did not buy a new one.

Actions

Also available in: Atom PDF