Bug #8829: Problems with Leixen Two way radio VV-898s - CHIRP

Custom queries

All CHIRP-next Bugs
All CHIRP-next Feature Requests
All closed issues
All open issues
New Model Requests
Open bugs by Developer
Open bugs by Target Version
Potentially Stalled Bugs

Bug #8829

closed

Problems with Leixen Two way radio VV-898s

Added by Fred PA3ETM almost 4 years ago. Updated almost 2 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

02/20/2021

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

Leixen VV-898S

Platform:

Windows

Debug Log:

I read the instructions above:

Description

Hi,
I use CHIRP for several radios, but I have now problems with my new radio.
The transceiver is a dual watch radio with A and B channels.
Downloading and writing to and from the set is working without problems.

The problem now is that I don't know how to define a channel to A or to B.
In the picture you see the settings, but I don't see A or B

Files

Download all files

print-01.jpg (232 KB) print-01.jpg		Fred PA3ETM, 02/20/2021 06:54 AM
IMG_1243.jpg (249 KB) IMG_1243.jpg		Fred PA3ETM, 02/27/2021 05:54 AM

Related issues 1 (0 open — 1 closed)

Is duplicate of Bug #4069: Memories upload to unexpected locations on Leixen VV-898S

Closed

Brian Dickman

09/25/2016

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Fred PA3ETM almost 4 years ago

I don't know what is wrong with the radio but the channels are not confirm the settings in CHIRP.
Reading and writing is no problem, but the channels are a mess.
I think there is a communication problem between CHIRP and the set.
The original software is not connecting with W10 even when I installed the drivers.

Actions

Copy link

Updated by Bernhard Hailer over 3 years ago

Status changed from New to Feedback
Model affected changed from (All models) to Leixen VV-898S

This is likely to be a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
If there's no solution to be found in any of them, please read: How To Report Issues and provide a debug log. Thank you!
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

Copy link

Updated by John LaMartina over 3 years ago

Several years ago, I believe the 898 series changed from a single channel bank to dual. It's possible the radio is not indicating which model is being programmed.

Actions

Copy link

Updated by Fred PA3ETM over 3 years ago

File IMG_1243.jpg IMG_1243.jpg added

This is the cable I use from the set.!!
I don't know what kind of cable it is.
I tried several drivers, but there is no change.
I send a mail to the seller, but he wants me to react on a website full of Trojans..... :)

Manually everything is programmed well but when I download it, its still a mes

Actions

Copy link

Updated by Bernhard Hailer over 3 years ago

Well, it's a USB cable... Not much else to determine from your picture.
But John is right. From what I heard, the VV-8898S has been altered by the manufacturer over the years, without really updating the version information in the firmware. Unfortunately, that means that Chirp can't really tell how to deal with the data correctly. Until we found a way to deal with these various firmware versions, I'm afraid you're out of luck.

Actions

Copy link

Updated by Fred PA3ETM over 3 years ago

Thanks for your support and its now clear to me that it won't work.
I used several USB-drivers for W10 but the result is the same.
The set works fine and so I have change frequenties manually.
No problem.

Actions

Copy link