Bug #4069

Memories upload to unexpected locations on Leixen VV-898S

Added by Michael Nelson almost 4 years ago. Updated about 1 month ago.

Status:In Progress Start date:09/25/2016
Priority:Normal Due date:
Assignee:Brian Dickman % Done:

70%

Category:-
Target version:-
Chirp Version:daily Platform:All
Model affected:Leixen VV-898S Dual Bank

Description

Using Nightly CHIRP 20160924 on Fedora linux, the upload to the radio creates memories and labels in unexpected positions.

The unit has an A & B channel. When I upload a bunch of entries, the odd-numbered CHIRP location #s loosely go into A channel, and the even #s into the B channel. Futhermore, radio stored memory numbers 10 and below I am unable to write to, even when setting all 199 memories to something. The resulting radio memory numbers are in sequence -- that is, CHIRP locations 1, 3, and 5 become like 10, 11, and 12 on the A channel. CHIRP locations 2, 4, and 6 become something like 10, 11, and 12 on the B channel. And so on.

The other part of this is that CHIRP writes the labels to the radio disassociated from the actual CHIRP memory rows. In this case, it appears CHIRP locations 10 and below are used and written in a similar manner as above. So the label from CHIRP memory location #1 becomes the label for radio memory # 12 or so, and #3 becomes #13.

Re-downloading the memories from the radio creates an image that is identical to the correct one I uploaded originally.

I am working on trying the stock editing software to see if it can upload memories in correct locations. That would tell us if it's CHIRP or a defective radio.

Can't find anyone else talking about this, so I'm leaning toward a defective radio. But who knows.

Leixen_VV-898E_20161007.img - stock after reset (8 kB) sean head, 10/07/2016 10:40 pm

Leixen_VV-898E_20161007-gmrs-murs.img - bank a gmrs+murs (8 kB) sean head, 10/07/2016 10:40 pm

Screen Shot 2016-10-07 at 10.38.53 PM.png - screen shot of windows utility (86.9 kB) sean head, 10/07/2016 10:40 pm

Screen Shot 2016-10-07 at 10.56.47 PM.png - screen shot of chirp after programing with leixen 1.07 tool (555.4 kB) sean head, 10/07/2016 10:57 pm

LeixenVV898ETestFrequencies.img (8 kB) Michael Nelson, 10/09/2016 11:56 am

LeixenVV898ETestFrequenciesOnRadio.csv - Mapping from radio bank/location into chirp's #s (850 Bytes) Michael Nelson, 10/09/2016 11:56 am

Screenshot from 2016-10-09 11-50-07.png - CHIRP screenshot (78.9 kB) Michael Nelson, 10/09/2016 11:56 am

Leixen_VV-898S107_20161011.img (8 kB) Michael Nelson, 10/11/2016 01:03 pm

leixen_107.py (36.4 kB) Brian Dickman, 10/12/2016 10:10 pm

RadioVersionLabel.jpg (32.1 kB) Michael Nelson, 10/13/2016 08:24 am

leix.jpg (100 kB) Lari Palander, 11/07/2017 07:41 am

leixen_dualbank.py (36.5 kB) Brian Dickman, 03/10/2018 04:01 pm

leixen_oem_107_20180506.lx19 (24.1 kB) Rob Owens, 05/06/2018 10:18 am

Leixen_VV898SDualBank_20180506.img (8 kB) Rob Owens, 05/06/2018 10:18 am

IMG_0062.JPG (121.4 kB) Niamh Holding, 06/27/2018 05:07 am

IMG_0063.JPG (118.6 kB) Niamh Holding, 06/27/2018 05:07 am

leixen_dualbank.py (36.5 kB) Alessandro Dogliotti, 12/10/2019 02:30 pm


Related issues

related to Bug #7673: Leixen VV898E V1.08 - Factory CPS no longer able to acces... Closed 03/05/2020
duplicated by Bug #4793: Leixen vv898-e ver 1.05 Closed 05/03/2017
duplicated by Bug #4637: Leixen VV-898-E Firmware v1.08b / alias for model VV-898-... Closed 03/17/2017
duplicated by Bug #7445: Leixen 898 >1.07 firmware - Also JetStream and other re-b... Closed 12/11/2019
duplicated by New Model #7283: Leixen VV-998s New 11/14/2019
duplicated by Bug #4455: New firmware version on the Leixen VV-898S Closed 01/24/2017

History

Updated by Michael Nelson almost 4 years ago

Cannot get stock programming software to work, unfortunately. :-(

Updated by Mark Jeffs almost 4 years ago

I can confirm this label and memory location CHIRP error on my new 898E model, daily build 20161005 Mac OSX 10.10.5.

I got the stock Leixen software ( for this more recent model I used the latest version available v1.07 I think it was) to work on Win 7 and it correctly applied the channel labels, so it looks like a CHIRP issue.

Updated by Michael Nelson almost 4 years ago

Ahhhh, great that you were able to reproduce. I sent my original one back and have a replacement on the way -- oops. I eventually convinced myself the unit itself was defective. They must have made a hardware revision that broke CHIRP, and we just happen to be the first lucky ones to encounter it.

Updated by Mark Jeffs almost 4 years ago

Yes I think the S & E models are the same, higher power etc, it's likely the new 2 separate memory banks are causing the issue. Do report back when you have the replacement!

Updated by sean head almost 4 years ago

I'm seeing the same issue on a 898e that arrived yesterday.

Updated by Michael Nelson almost 4 years ago

Replacement arrived today and as predicted, same issue. Now, whether to opt for that compact BTECH or wait..

Updated by Brian Dickman almost 4 years ago

Michael, sorry a barrage of questions/requests here:

- Could you upload an .img file with this issue?
- Does the image look different if you upload and then download again?
- Could you also capture a screenshot of how the memories look in the CHIRP GUI before upload (or a CSV export)?
- What Version does the radio label show? The radio I used is an 898S V1.05 and seems to work fine, but it also doesn't have memories under both A and B Stated better, it has an A and B VFO, and both can run in memory mode, but they both display the exact same memory set. Is there an updated radio that maintains the memories differently between VFOs?

Updated by sean head almost 4 years ago

Here's a base image (factory reset), and bank A programed via the windows tool with GMRS/FRS+MURS in channels 1 through 27.

Updated by sean head almost 4 years ago

My radio says 898e 1.07 with different memory banks

Updated by Brian Dickman almost 4 years ago

  • Status changed from New to In Progress
  • Assignee set to Brian Dickman
  • Platform changed from Linux to All

Thanks for the files Sean. This looks workable. As I only have the older 1.05 radio, I'll need your help (and Michael and Mark if you're willing?) to test. Will probably take a few days to hack up a module to try out.

If willing, could you setup and capture a new image:

Use the radio itself or Windows software to configure thusly:
- On VFO A, set each of the bands (144, 220, 440) to known values, like 144.1, 220.1, etc. Also save a memory to the top position 99
- Same on VFO B, with different values. Also save some VFO B memories to the radio (just a couple is fine but with labels please), and the top position

Capture the img, and upload along with a description of what to expect in each VFO/memory. A screenshot of the Windows software would probably suffice, along with description of the VFOs.

I get the general idea of how the VFO and memories are laid out, but this should be enough to confirm my assumptions and not screw anything up too badly. :-) Thanks!

Updated by Michael Nelson almost 4 years ago

Brian,

Here is the img and a CSV that shows 2 mappings of what I programmed manually into the radio, and what it became on CHIRP.

Specs:
- VV-898E
- V1.05 on the label
- Chirp daily-20160819

The first mapping shows the frequencies I programmed into each VFO channel (A/B) & channel number into which location # CHIRP shows it after downloading.

The second mapping shows the labels I programmed into each VFO channel (A/B) & channel number into the row # of where CHIRP shows it in the Name field.

Before downloading this img, I set VFO A to 136.0125/200.0125/400.0125, and VFO B to 174.000/260.000/520.000.

Apologies but I don't have easy access to a Windows laptop, so I've included a screenshot of the Linux version.

Let me know if I can help out any more. Thanks.

Updated by Brian Dickman almost 4 years ago

  • File leixen_107.py added
  • % Done changed from 0 to 50

Thank you Michael! Those were a huge help.

Alright, here's a first attempt at a driver fix. Call this a beta.

1) Download the attached leixen_107.py file
2) Start chirp. If you haven't turned them on before, goto menu Help->"Enable Developer Functions".
3) With Developer functions enabled, goto menu File->"Load Module" and choose the leixen_107.py file
4) Download from radio using the "Leixen VV898S107" model.

It's entirely possible the old/existing driver screwed up some memory channel areas of the radios if you uploaded previously. I suggest doing a factory wipe/reset before starting to use this driver, or you may have some garbage left over in some of the memories. I also think there may still be an issue with memories toward the end of the set (around 90+). Please test and report findings, with images uploaded where possible. Thanks.

Also please note: I have an upcoming business trip out of the country for a week. You may not hear from me for a little while, but I'll try to come back and keep on this with any additional fixes needed and submit the patch to nightly once it appears to be fully working.

Updated by Michael Nelson almost 4 years ago

Awesome.

After some testing this morning, it looks like the frequency (& non-label fields) CHIRP location to radio channel # is still pretty off. I will test further to determine how they've changed.

The labels appear to be corrected. However, I believe the banks are flipped. The labels from the VFOa tab show up in memory bank B on the radio for me.

There is some weirdness around location 95 or 96 to 99, and 1 to 8. Randomly the first range is cleared out with "ERROR" for the label, and the second range randomly gets replaced by garbage values in odd locations or even locations only.

Attached is the image I'm testing with.

Updated by Brian Dickman almost 4 years ago

  • File deleted (leixen_107.py)

Updated by Brian Dickman almost 4 years ago

  • File leixen_107.py added
  • % Done changed from 50 to 70

Ah, thanks for that feedback about the flipped banks and the locations. I think I've fixed both those now. New driver attached, give it a try.

Updated by Michael Nelson almost 4 years ago

Okay had a chance to look further and actually the frequency information appears to be very close. Same weirdness with 1-8. The entire set of memories appears to be just shifted up by 8. So Chirp location # 1 becomes radio channel # 9, 2 to 10, etc.

Updated by Brian Dickman almost 4 years ago

I'm not sure if you saw my newer driver, since it posted just before your reply (we must have been editing posts at basically the same time). I believe this version fixes the 1-8 offset problem along with the 95-98 spots as well. With this version, your images finally look all correct on my machine.

Updated by Michael Nelson almost 4 years ago

Ah, yes we were lol. Okay tested again, and yes, the frequencies are correct now! Except instead of 1-8 being untouchable, it's now 1-6. Channels 7 & 8 are now working properly on both memory banks.

Updated by Brian Dickman almost 4 years ago

  • File deleted (leixen_107.py)

Updated by Brian Dickman almost 4 years ago

I'm adding another version attachment, but it does't really change any underlying functionality from yesterday's version. Just rearranges the definitions under the covers.

What do you mean by 1-6 being untouchable? I was able to see them with "show empty" as expected, and assign values into them. Your 161011 image looks a little screwy, but I think that's because it was uploaded and re-downloaded using the old driver? The TestFrequencies image looks good when I load it, and Sean's GMRS/MURS image looks correct as well.

Michael, can you also double-check that your model label is v1.05? I have been calling this v1.07 because the newer software is called that, but now I'm afraid that it's actually 107 on the S model, and 105 on the E.

Updated by Michael Nelson almost 4 years ago

Re-uploaded my TestFrequency image to the radio & tested again. When I change any of 1-6 on the radio, the frequency info and label is read correctly by CHIRP. When I change it in CHIRP, the label is correctly set on the radio, but the frequency info remains unchanged from what I last set manually on the radio. Hmmmm.

Yea, the label says v1.05 (see attachment). And it's an E.

Updated by Brian Dickman almost 4 years ago

Ah, interesting. Okay, I'll take a look at the 1-6 frequency area and see what's going on there. I wonder if we're unintentionally dropping those changes because of something in the older memory layout.

It's especially awesome that they decided to add this new layout in two different model/firmware versions. I'm not quite sure how I'm going to describe this model so people can find the right one in the future.

Updated by Michael Nelson almost 4 years ago

Ah yeah, I get that. I guess since Sean and I both have 898Es, we could start there and try and find an E without separate memory banks?

Updated by Brian Dickman almost 4 years ago

David McIntyre filed one of the original 898E feature requests, and his does not have dual banks. He didn't list the label version but I can follow up with him on email and see what it says.

I'm hoping to add auto-discovery in a near-term update, so we might be able to avoid any mention of versions or banks and just let the app figure it out. Still not quite sure if that's possible but I'll certainly try.

Updated by Mark Jeffs over 3 years ago

Sorry folks, been abroad. My E model serial label says v1.07 and I have 2 memory banks, theres an addendum sheet in the manual to that effect.

Updated by Jarmo Wilkman over 3 years ago

To check the firmware version in your radio: Power the radio off. Press and hold P3, power on the radio. Keep pressing P3. After the usual messages the firmware level is displayed. Serial number label in bottom can state v1.05 and the actual firmware in the radio can be v1.07. I believe v1.07B is the latest.

Updated by Brian Dickman over 3 years ago

Thanks for the info Jarmo, that makes a lot more sense. I've been able to identify the 1.07 firmware by the memory data, so I don't think there's any risk of mis-parsing the downloads. It will still be a little confusing, but this explanation shows there is some logic behind it. I can also add a pre-download message with this info to help identify versions.

I plan to commit some more work to the patch this week and hope to have something released to nightly soon. Please provide feedback on the current patch if you have opportunity to try it out (use the leixen_107.py patch attached to this issue, and the instructions in update 13).

Updated by Michael Nelson over 3 years ago

Oh, good call Jarmo. Turns out the label is wrong. Holding P3 & powering up, it shows V1.07B.

Updated by Mark Jeffs over 3 years ago

On P3 boot my 898e shows V1.07B. Label says V1.07.

Updated by Jarmo Wilkman over 3 years ago

I can now confirm that loading the PY 107 module writes correctly to my Leixen VV-25HX, labeled v1.05 but actually contains v1.07B firmware. I had the same problem as Michael Nelson, that the stock software could not read or write to the radio. After being in contact with the support, Leixen has released new stock software, 2016-11-07 version for 1.07 radio's. Now i can compare Chirp and Leixen writing. And they match.

Updated by John LaMartina over 3 years ago

Is it safe to say that the latest version of CHIRP now supports the VV-898 V1.07 with the Dual Memory Banks?
or is this still a work in progress?

Updated by Jim Unroe over 3 years ago

John is referring to the patch that makes leixen.py driver support dual banks of the JT-270MH.

[Dan Smith <>] Make Jetstream JT-270MH properly a dual-bank radio

#4241

Are the VV-898S and JT-270MH variants of one another like the VV-898 and JT-720M?

Jim KC9HI

Updated by Brian Dickman over 3 years ago

It's a little more nuanced. VV-898S (and 898E) have 2 major firmware versions, pre-1.07 and post-1.07. Pre-107 is already supported properly. The 1.07 and later firmware adds the dual-bank/vfo feature of the JT-270MH, and the ident matches. However the manufacturer printed label shows the hardware version, not firmware version. Users must hold down P3 during powerup to identify the firmware version and be able to use the right model.

So we're really 90% of the way to fixing this issue and closing it for all associated models. We should probably just add them as some kind of alias (although a good way to name them escapes me), and add a download message to check firmware version before using. Could also add an interlocked ident check during download similar to some of the Baofeng models.

Updated by John LaMartina over 3 years ago

Brian/Jim, Thank you for the quick follow up. Your efforts are truly appreciated. Pre-1.07/Post-107? Ouch... As always, thank yo for all the work you guys do.

Updated by Bryan Tanis over 3 years ago

For what it's worth, I just got my Leixen VV-989E v1.07 working thanks to this thread.

I started with CHIRP but had all the problems you had already stated. It's almost impossible to explain. Even experiencing the same problems, its still hard to understand your descriptions.

Thanks to the P3 button trick I learned my v1.05 is actually a v1.07. After downloading the Leixen software for the v1.07, it finally worked. It can be found here, http://www.miklor.com/VV898/VV-Software.php

Very confusing to say the least.

Even after doing the factory reset numerous times, there was still remnants of channel data from my previous attempts of programming using CHIRP when reading the radio with the factory software.

I hope CHIRP will soon work for this model version. Its awesome software. I love the export/import option.

After working and scratching my head for hours, I finally have a working radio thanks to you guys and your hard work.

Thanks again,
Bryan

Updated by Stan Hall over 3 years ago

Any further updates? I have a VV-898E with firmware version 1.07B. I am using the leixen_107.py from post 21 above with Chirp 20170311. It is almost working except for two things that I have noticed.
1) The first 5 memories are getting mangled.
2) The ability to directly enter a channel via keypad for Bank A is disabled.

In regards to 1, I need to create a test file, upload it and then download it again. That should help show what is happening to the first few channels. My first download appeared to download all stock channels correctly, so I think it is an upload problem.

For 2, I can get the direct entry to work by using the stock Leixen VV-898S 107 software with a new configuration. I cannot find any setting that will enable/disable this behavior. From Chirp or the Leixen software.

If someone is willing to continue working on this, I will do what I can to provide files.

Updated by Pete Ed about 3 years ago

I have just bought a Leixen VV-898S with FW version 1.08B

I have successfully programmed it with the Factory Software for v1.07 (I have not tried CHIRP with this radio as yet)

What might be of interest to the CHIRP staff, is that the Factory Software uses 2 separate banks of 99 memories (a separate programming window for each one), and within each bank, the FIRST 3 MEMORIES of each bank are allocated to the VFO. They seem to be TEMP storage areas for band switching. Down the left hand side of the window, which is the first column and labelled [No.], the numbers begin this way: 136, next is 245, then 400, after those the 'normal' channel numbering (rows) begins, 01, 02, 03 .... 99.

Cheers --Pete

Updated by Niamh Holding about 3 years ago

Stan Hall wrote:

2) The ability to directly enter a channel via keypad for Bank A is disabled.

For 2, I can get the direct entry to work by using the stock Leixen VV-898S 107 software with a new configuration. I cannot find any setting that will enable/disable this behavior. From Chirp or the Leixen software.

If someone is willing to continue working on this, I will do what I can to provide files.

Same here. And I really want to upload my own channels without having to manually enter them into the Leixen software.

Updated by Scouter Donn almost 3 years ago

Hello Everyone
I am new the CHIRP forum and hope that someone out there can help us. I am just a HAM volunteer scout leader setting up several small ham bases in my camps and outposts and I bought several VV-898E radios, many are great but 2 are dead and I am not getting any support from the seller or emailing Leixen direct after a month. First I bought the 898E thinking the hi-med-lo power was a nice option verse just hi-lo but I thought this was 200 channel one bank radio but what I have is a two bank radio. So as I mentioned one radio is dead, once powered up it just displays 22.9vdc and no buttons work. The factory software says either the port is busy or the radio refused to communicate, yet CHIRP can read and write however the radio still only displays the voltage? Anyone know any tips or tricks? We looked high and low on the internet with no luck. We opened the radio and pulled the CR2032 thinking the radio would lose all programming and default to factor setting but no luck. So if anyone would like to help the boggled ham scouter I would love to hear from you in this forum or email direct: many thanks for this forum.

Updated by Lari Palander over 2 years ago

Hello to everyone,

Pete Ed wrote:

I have just bought a Leixen VV-898S with FW version 1.08B
I have successfully programmed it with the Factory Software for v1.07 (I have not tried CHIRP with this radio as yet)

I've got the same FW version, however according to S/N plate, this radio seems to be VV-898 (not S)? But, it does have 3 power settings and A+B memory banks. Chirp does read the radio, but memory bank data is corrupted. Radio also accepts the upload ok, but doesn't change settings, or if it does, the memory banks are again corrupted. So far I have managed to restore the factory defaults by pressing M-key while booting up the radio. I cannot get the stock software to work either! It doesn't want to communicate with the radio. So an update for Chirp for FW 1.08B would be much appreciated, thank you!

Updated by Rob Owens over 2 years ago

I have a VV-898E v1.08b that I would be willing to loan to a developer.

Updated by Rob Owens over 2 years ago

I found a problem:

Downloading from my radio seems to work fine (version 1.08b).
Making changes, then uploading to my radio seems to work fine -- but I've done very limited testing.

Saving the downloaded file works, but when it is opened later on it is identified as "Jetstream JT270MH: <my filename>". The values in the "Name" field are then all offset by 3 lines (Name4 shows up in the field for Name1, and so on). This makes it useless for uploading later on.

Updated by Rob Owens over 2 years ago

Workaround: If I delete the stock leixen.py, and replace it with Brian's leixen_107.py (but rename it to leixen.py), I don't experience that weirdness with the saved file being identified as "Jetstream JT270MH: <my filename>".

Perhaps the issue is that in the standard leixen.py, Jetstream JT270MH has a _model_ident of 'LX-\x89\x85\x85', and in Brian's leixen_107.py, Leixen VV-898S107 has the same _model_ident. Does anybody know how to address that?

Updated by Niamh Holding over 2 years ago

Any progress on fixing the direct entry of channels on bank A?

Updated by Rob Owens over 2 years ago

Niamh, I haven't made any changes to the driver (I don't know how), but I can test to see if I get the same behavior you are seeing. Just to be clear: Is the problem that after uploading with Chirp, you can no longer manually input frequencies and/or channels on bank A? And this problem goes away if you upload an image with the stock Leixen software?

Updated by Niamh Holding over 2 years ago

That's it exactly, If I upload the factory defauls with the stock Leixen software then the numeric keys on the mic work on channel A

Updated by Rob Owens over 2 years ago

Niamh, I have the same results on my radio. I saved Leixen files with the radio in both conditions (normal and locked channel A) and found "Functiom Enable" (note the spelling error) set to 0 for the normal condition, and set to 1 for the locked condition. "Functiom Enable" appears in the Leixen software in Special Function / Wireless Change Channel. This was the only difference between the two files.

I'm out of time now, but I'll try figuring out the memory address for that feature later on.

Updated by Rob Owens over 2 years ago

Real quick update -- When I turn "Functiom Enable" on and off in the Leixen software, upload it to the radio, then download the image with Chirp, the two images are identical. Chirp is not detecting any difference. Could it be that Chirp is not reading the entire memory of the radio?

Updated by Rob Owens over 2 years ago

Just to clarify my last post, I did a hexdiff on two Chirp images downloaded from the radio. One where the radio had "Functiom Enable" on, and one where the radio had that off. There was no difference between the two images, so it seems to me (a non-expert) that Chirp is not downloading the memory address where that setting is stored.

Updated by Rob Owens over 2 years ago

I asked Leixen tech support to tell me the memory address where "Functiom Enable" is stored. The lady who emailed me indicated that their engineer would be able to help me, but I have not had a response for the last 2 weeks. So I sent them a reminder email today.

Updated by Rob Owens over 2 years ago

I got the following response from Leixen:

0x0187,B3:Wirelsee start,B2:function enable

Updated by Rob Owens over 2 years ago

I've done some more testing. I bumped the memsize from 2000 up to 8000 and did a hexdump. I found that all the memory addresses repeat after each 2000. So address 00000000 contains the same information as address 00002000, 00004000, and so on. But address 00000187 is different. If "Functiom Enable" gets turned on/off, address 00000187 does not change, but its "twin" address 00002187 does change. Addresses 00004187 and 00006187 change as well (they are the same as 00002187).

At this point I think I need someone more experience to step in here and tell us how to solve this.

Updated by Brian Dickman over 2 years ago

  • File leixen_dualbank.py added
  • Model affected changed from Leixen VV-898S to Leixen VV-898S Dual Bank

I'm attaching a new beta driver for the VV-898S with newer firmware. This only applies to the 1.07+ firmware, where the memories are split into bank A and bank B. If you have a single-bank radio with all 200 memories in one place, this is not for you.

It adds a new radio called "Leixen 898S Dual Bank". It has been tested by one user and had good results.

Specifically, this fixes the problems where these images are loaded and the name presents wrong in CHIRP (a Leixen image appears as a Jetstream image), and the problem where memories downloaded/uploaded are in the wrong location.

Please test and provide feedback. Thanks.

To use:
- Start CHIRP, and go to the help menu. Enable Developer features
- Go to the file menu and choose "load module". Point the file picker to the leixen_dualbank.py.
- Download your radio image

Updated by Niamh Holding over 2 years ago

Does this address the issue of direct chanel entry in bank A?

Updated by Rob Owens over 2 years ago

Niahm, yes it does.

Updated by Rob Owens over 2 years ago

Just confirming that I tested a few settings today by making a change in Chirp, uploading to the radio, then checking the setting in the radio's menu. The following are all I tested, and they all work properly:

Key Beep
Dual Watch
MR/CHA
Scan Mode
P1 thru P3 long and short key

One thing I'd like to see added to the Settings menu is the ability to turn off the Tail Elimination feature (Menu 43). Here is a hexdiff of an image with the feature turned on vs an image with the feature turned off:

128c128
< 00000c70 40 01 00 00 40 01 00 00 ff 00 ff 00 ff fe b0 fc |..............|
---

00000c70 40 01 00 00 40 01 00 00 ff 00 ff 00 ff ee b0 fc |..............|

Updated by Rob Owens over 2 years ago

I've tested memories 1-99 (skipping only a few) on both banks A and B. Uploading and re-downloading from the radio all looks good.

One problem I found which I think is a bug in the radio: I can manually enter any memory number from the hand mic except for 099. When I enter that memory, it acts as if that memory is blank so it stays on the existing memory number. It behaves the same on bank A and B, and behaves the same whether I uploaded memory 99 with chirp or programmed it manually with the radio's menu system. I'd be interested to know if others see the same behavior, particularly if they haven't uploaded to their radio with Chirp yet.

Updated by John Devine about 2 years ago

Hi, does anyone have a template I can upload to a version 1.08b radio, I can't seem to set the enable reset option, so cannot reset the radio, it seems to have been corrupted by v 1.07 of the leixen software......why is there no v1.08 from leixen OOI?

Thanks in anticipation

JD

Updated by Rob Owens about 2 years ago

John Devine, not sure if you wanted a Chirp image or a Leixen image, so I uploaded both. They have the date code "20180506" in their names. Also, according to Leixen technical support, the v1.07 software is usable on the v1.08 firmware. I have confirmed that with my radio, which is v1.08

Updated by John Devine about 2 years ago

Hi Rob, thank you so much, I actually got one from another radio a few hours ago and have managed to recover it, I will keep your images for safety.......Its odd that Leixen say the software is usable, as if I upload to the software, I have one bank of 199 memories, and when I tried to write back, I got an error, and the radio was trashed......Mine is a 1.08b

JD

Updated by John Devine about 2 years ago

Hmmm....discoveries so far.....I have lifted an image from a new unit and successfully used chirp with the updated dual memory template to upload to the corrupt unit, I was then able to master reset the unit to factory defaults......but it will not let me read or write to it from the Leixen v1.07 software, I can read/write from chirp ok. The same Leixen software will read from the new unit, I havn’t tried write yet until I know what is going on, is there a value that isn’t reset by the factory reset like device ID that is preventing read/write to the once corrupted unit?

JD

Updated by Rob Owens about 2 years ago

I had intermittent trouble with the Leixen software that turned out to be related to the COM port. Windows sometimes didn't like switching between Chirp and Leixen accessing the same COM port. A reboot fixed the issue for me whenever it occurred.

Updated by John Devine about 2 years ago

Yeh I don't think that is causing this specific issue, like I say, I can read from the good unit ok, just swap the radio out to the bad one, and it can't read it, swap to the good one and its ok again......Its now in an amazon locker awaiting a refund, maybe its is a faulty unit, I have a good one here now bit am really scared to flash it :( Its a VV-898 E, not sure what the E suffix dictates, maybe European ?

JD

Updated by Niamh Holding about 2 years ago

OK sorry it's taken me a while, but having downloaded and uploaded to the radio I still get no direct channel entry on bank A.

Updated by Rob Owens about 2 years ago

Niamh, I confirmed yesterday that after using leixen_dualbank.py to update my radio, I am still able to do direct channel entry (and direct VFO entry) on bank A.

Updated by Niamh Holding about 2 years ago

Are you doing anything more than downloading from the radio and reuploading?

Updated by Rob Owens about 2 years ago

I downloaded, changed a bunch of memories, changed one setting (time out timer), then uploaded.

Updated by Niamh Holding about 2 years ago

Tried downloading changing a few settings and uploading and still no direct chanel entry on A, and in fact no channel number on the display when A is selected, see photos

Updated by Rob Owens about 2 years ago

Are you sure you're in channel mode and not VFO mode? Still, you should have direct frequency entry in VFO mode, but that would explain why there's no channel number on the display.

Updated by Niamh Holding about 2 years ago

I was, so the puzzle is even greater, it isn't accepting input in VFO mode, Channel B does.

Updated by Geoffrey Hicks about 2 years ago

Using the "dualbank" python script addresses many of the Chirp programming issues for v1.08... thank you...

I've just encountered a scenario of Leixen VV-898E lockup... when the following settings are applied...

Settings Menu, Basic Settings...

VFO/MR set to MR
MR/CHA set to MR CHA

After uploading to radio, the display seems to lock with CHANNEL 128... and squelch is open. No control of radio until power removed and re-applied. Radio returns to same display, however... squelch seems to be back on... and the radio will accept a new upload.

Updated by Geoffrey Hicks almost 2 years ago

UPDATE: A replacement radio has corrected this issue... apparently, the original radio had issues!

Updated by Eric Lyons almost 2 years ago

Just confirming that the leixen_dualbank.py module works on a brand-new VV-898 I got a couple of weeks ago. Without it, just got a mess.

Worth adding to the mainline?

Updated by David Reichard almost 2 years ago

No luck here. I'm fairly new to CHIRP and brand new to the Leixen VV-898S version 1.08. Channels scrambled as reported above using chirp-daily-20181009. Loaded module leixen_dualbank.py, looks the same. Changed name and freq in CHIRP for channels 2-11 then uploaded to the radio. Channels 1-7 that I had manually programmed still there (CHIRP should have overwritten them but did not. Channels 11 & 12 were overwritten by CHIRP. Any suggestions?
I ordered a cable & software from RT Systems; they say theirs works with V1.08. We will see...
BTW I'm using Windows 10.

Updated by Niamh Holding over 1 year ago

Are we still using leixen_dualbank.py with the 18/10/2018 nightly?

Updated by Niamh Holding over 1 year ago

Just got a new VV-898S and noticed that out of the box direct channel entry doesn't work on bank A nor do the up/down keys.

Faulty, or are they all like that?

Will be talking to Moonraker on Monday.

Updated by Rob Owens over 1 year ago

Niahm,

As far as I know, we still need to use leixen_dualbank.py for the latest build.

I just uploaded an image using Chirp to my radio and I seem to have direct channel entry available for anything except channel 99 (for both banks A and B). After I enter the three digits (099), the radio stays on the current channel and does not change. I'm not sure if it always did this, if it's a defect in my radio, or if Chirp somehow caused it.

If direct channel entry doesn't work for you on a brand new radio, use the Leixen software and see if "Functiom Enable" is checked. I think that disables direct channel entry.

Updated by Rob Owens over 1 year ago

David, my only suggestion for you is to close Chirp, open Chirp, load module leixen_dualbank.py, download from the radio, make changes to the Chirp file, then upload to the radio. From your description, it's not clear to me if you uploaded/downloaded before loading leixen_dualbank.py. In my testing, that would sometimes screw things up. I needed a new Chirp session with leixen_dualbank.py loaded in order to ensure things worked smoothly.

Good luck!

Updated by Niamh Holding over 1 year ago

Rob Owens wrote:

Niahm,

If direct channel entry doesn't work for you on a brand new radio, use the Leixen software and see if "Functiom Enable" is checked. I think that disables direct channel entry.

It works fine on Bank B, on Bank A it doesn't nor do the up/down keys on the microphone although the up/down keys on the radio do work.

The latest Leixen softwat appears to be V107 and it seems not to download from v1.08B firmware, CHIRP reads the radio fine.

Updated by Niamh Holding about 1 year ago

Looks like we still need to use leixen_dualbank.py with the latest CHIRP.

Any plans to get this included in CHIRP itself?

Updated by Tim Fox about 1 year ago

Hi, I'm a new Leixen VV 898S user. My new radio reports firmware version 1.08B. I'm using Windows 10 and the latest daily update of Chirp, 20190626. I can successfully read from and write to the radio. I've been using Chirp for some time with Baofeng UV-3R and UV-5R radios very succcesfully.

Having come across a number of problems programming this radio I looked through the list of Issues on the Chirp website and found this thread. This seems to be describing the issues I'm having, mainly:
- Chirp doesn't handle the 2 memory banks (A and B) that the radio uses. I find the Odd numbered Chirp memories equate to the A bank in the radio and the even numbered memories equate to the B bank.
- I can seem to be able to program memories below 7 in the A Bank and 8 in the B bank.
- If I try to program a memory above about 56 (Chirp memory), nothing appears on the radio.
- I can't give the memories in the radio a name. If I try, all I get is a blank display (no frequency or name on the display for that memory).

I see that this has been ongoing for some time but that there seems to be some sort of workaround using a supplementary Python file called "leixen_dualbank.py" which I have found at the top of this thread.

Could I please ask if someone could let me know how to use this file, where should I put it, etc. Can I leave it in place when I use Chirp to program other radios?

Does it fix all known issues or are there still some "gotchas" to be aware of?

Many thanks in advance for any assistance provided.

Tim

Updated by John Kitchener 11 months ago

Tim Fox wrote:

Hi, I'm a new Leixen VV 898S user. My new radio reports firmware version 1.08B. ....

Could I please ask if someone could let me know how to use this file, where should I put it, etc. Can I leave it in place when I use Chirp to program other radios?

Does it fix all known issues or are there still some "gotchas" to be aware of?

Many thanks in advance for any assistance provided.

Tim

Hi Tim,

I have also just got hold of a Leixen VV-898S.

After fumbling around with the dual bank problem; I found this thread.

The answer to how to deal with the leixen_dualbank.py file is found above. https://chirp.danplanet.com/issues/4069#change-15597 and then read on.

.

.

Now for my problem ... in a similar vein.

Following the above link for 'how to load the python script' and using the latest daily Chirp proggie for Windows '24-Aug-2019 00:07',

I get the following error when loading the python script:

Any tips?

Updated by John Kitchener 11 months ago

John Kitchener wrote:

Any tips?

My bad. I did a poor job of downloading the python script. Hint it's only 36.5kB

Looks good

Updated by John Kitchener 11 months ago

Updated by John Kitchener 11 months ago

Another question.

Is the Leixen VV-898S Dual Bank build sufficiently stable for inclusion in the CHIRP daily build?

Updated by John Kitchener 10 months ago

Hi,

There are bugs in the Chirp Lexion dual band python script.

1. This radio supports UHF from 400-480, however the script limits the range to 400-470Mhz.

2. When adding a memory for a frequency that falls on a 12.5 khz step, chirp says that 12.5 is not a valid step, however it is valid for this radio.

Updated by John Kitchener 10 months ago

John Kitchener wrote:

Hi,

There are bugs in the Chirp Lexion 898S dual band python script.

1. This radio supports UHF from 400-480, however the script limits the range to 400-470Mhz.

2. When adding a memory for a frequency that falls on a 12.5 khz step, chirp says that 12.5 is not a valid step, however it is valid for this radio.

Updated by Niamh Holding 10 months ago

I think I saw the second problem and it seems to have been with a "Nightly" I reverted to an older nightly and 12.5kHz wasn't a problem.

Updated by Alessandro Dogliotti 7 months ago

Niamh Holding wrote:

I think I saw the second problem and it seems to have been with a "Nightly" I reverted to an older nightly and 12.5kHz wasn't a problem.

Problem is still present in linux daily builds, 6.25 and 12.5 kHz are not working as expected. Also, I really would appreciate if the .py script workaround will be integrated into main release, maybe with a separate dualbank menu choice or even with auto sensing..

Updated by Alessandro Dogliotti 7 months ago

tried to modify the leixen_dualbank.py script by looking at

https://danplanet.com/projects/chirp/repository/revisions/c869c5cfc623/diff/chirp/drivers/leixen.py

after

https://danplanet.com/issues/6523

now the attached file allows to use all the radio programmable steps.

Updated by Niamh Holding 7 months ago

Unable to load module: invalid syntax leixen_dualbank.py, line 1

Updated by Niamh Holding 7 months ago

User error!

Updated by Michael Ford 6 months ago

Just bought the VV-898E, kinda bumbed to find out about the "dual memory" shenanigans - which effectively halfs the memory for some. I can however confirm the that the script leixen_dualbank.py modified by Alessandro Dogliotti in Note 91 of this thread works with the VV-898E, but has to be used with VV898SDualBank available in the daily builds - I was using daily-20200107."

Updated by Bernhard Hailer 3 months ago

  • Chirp Version changed from 0.4.0 to daily

Has this been completed? Thanks.

Updated by Michael Nelson 3 months ago

Hah, I see years later this is still ongoing. It seems like the original fix got very close, all that was left was channels 1-6 not working properly. Seems like the current fix could at least be merged, under a new "dual bank" version of the radio. At least it would get the radio mostly working for users without having to load a module?

Updated by Bernhard Hailer 3 months ago

Actually I was just testing whether the ticket is still valid (I'm on a crusade to weed out stale tickets from the database).
So, if there's still activity (or activity requested), then we'll keep this open. Thanks!

Updated by Chris Keller 3 months ago

I can confirm with a Leixen VV-898S v1.08 radio, the built-in Chrip profile still does not work, but the module from Alessandro Dogliotti in Note 91 does work.

Updated by Alessandro Dogliotti 2 months ago

Bernhard, is it possible to implement the module in a daily release? It's actually working, and i don't see a reason why we should keep a 3 yrs ticket open without any more work demanded.

I tried to get in touch with Brian, the original mantainer (his work has been very helpful on his topic) but he doesn't log in since october, so i guess he either had personal problems or lost interest in the topic.

I also opened a request for giving this issue a new mantainer but it got closed without explications.

Thanks for your time.

Updated by Bernhard Hailer 2 months ago

This requires that the creator of that module checks it in.
In order to be included, it must pass certain tests.
Hopefully, one of the developers familiar with the Leixen VV-898S can take this task.

Updated by Alessandro Dogliotti about 1 month ago

Bernhard Hailer wrote:

This requires that the creator of that module checks it in.
In order to be included, it must pass certain tests.
Hopefully, one of the developers familiar with the Leixen VV-898S can take this task.

I understand, but Brian did a couple posts in 2018 and rest of his activity is back to 2016.
I don't know how we can find an active developer with leixen availability and experience, i opened a ticket to ask for one to have a look here and was closed without further informations.

That makes me sorry, because we (well, i just edited the py script to accept new style offsets, following what Tom Hayward did on main script) actually have a working solutions and the one in the daily DOESN'T work with dual bank radios and doesn't even specify that dual band radios are not supported, or doesn't give a tip about >=1.07 firmwares, so users without familiarity with this topic actually don't have the tools to understand that the default model doesn't work and the solution is here requesting approval.

Updated by Bernhard Hailer about 1 month ago

Hi Alessandro, you could do it yourself, actually. Please review the Wiki: Developers, and join the developers mailing list. If the changes are minor, then you can try to post it just there. If you wish to continue developing for Chirp, then you will find the necessary instructions also in said Wiki article. Thanks!

Also available in: Atom PDF