FIXED-Companion doesn't download voice pack for m128

[Flaps 30]

Thanks again Kilrah.

Last file downloaded a while back went up to 509. Latest was up to 503. Now to try it all out..

[jhsa]

then is fixed..

[mbanzi]

I'm attaching the voice pack renamer script in case anyone has a custom version of an older open9x voice pack they want to retain. It's written for Mac, but will work on Linux and will need to be modified to work on Windows. It's pretty crude but simple. You may see error messages depending on how many models you have. All old files are renamed to 9999_old.wav, so they won't be overwritten.

[Flaps 30]

This is not looking good guys.. Running stock board with M128 with version 2168 firmware with the new sound files as posted. In custom functions. Unable to select any track that is below 256.

Tried playing a value (A1) got "gear up" combined with something else. In fact playing any sort of value gets the same response..

No inactivity alarm given or TX battery low.. Playing track 288 gives me "32" followed by "hour", I doubt that much else works as it should.

[jhsa]

I think the changes affect versions 2212 and newer..
you must update the fw

[Kilrah]

Normal, the new pack is there to mirror the latest changes in the firmware - so if you update the pack you also need to update the firmware (2215)!

[Flaps 30]

Heck! ... It's getting late.. Yes I missed that on the software version... Fehh... Let me download the correct version.. Back soon.

[jhsa]

After you flashed the fw and while you are testing, try creating a new mix somewhere, edit the mix, highlight the source field and just move some sticks and switches.. you'll see the source for that mix change to what you move.. really cool and easy to work with..

João

[Flaps 30]

I'm sure it's cool João. The main functions do seem to be okay.

After flashing the firmware version 2215 using Companion 1.22 things started to look better.. Not for long though. playing a value (TRN switch A1) gave me "zero five volts nine" on audio with a splash of noise after the five.. Change soundcard for another known good one (as has been used before) and a whole new set of sounds hit me which was "zero (unknown track noise) volts enabled" the enabled was the end part of track 0042. The welcome message also comes with another file sound at the end of it.

Attached is the model file (my vario test file) that gave me these errors.

Just as a reminder. Emartee card in use here on a stock card with the M128. I am wondering if any timing changes have happened that might have lead to this situation?

Ohh.. One last thing in custom functions (on the TX) the rudder switch plays track 47. On companion that track is shown as track 303 ...

[jhsa]

You will have to reprogram the voices. I did. I think that Bertrand tried that the fw adjust our ptogramming automatically to the new file numbers but I think it is shifted by 6 numbers.. it was in at least one of my files..

If you look at the new list, file number 0303.wav is number 47
What are you supposed to havge there? Throttle cut?

[jhsa]

And that is weird.. mine seem to be working fine now..

João

[Flaps 30]

Fehh... Okay.. So line number 47 on the CSV file that shows on the TX.. Nice one.. That is confusing. The file there says 'launch mode -- On' Glider guiding ya know!

The voice files are the latest ones as we talked about earlier. Even if that was a problem. It doesn't explain the odd things that are going on like trying to play two tracks when only one is called up, or the odd voice readout of A1 (which was at zero volts).

I can revert back to the original FW and sound files of course. Now would that work with the new Companion I wonder? Ohh I do love a challenge.. Preferably in small chunks. Not big bites like this.

[jhsa]

save your eeprom and try.. I think the eeprom version is still the same? 214?

[Flaps 30]

Yes the eeprom is still version 214. Been there done that with saving it and making a new file in companion, then burning back to the TX.. No change.

[jhsa]

but didn't you want to flash an older version back to the radio? I think companion always download the latest version

[Flaps 30]

Flashed back to version 2168 along with writing back my original voice files to the SD card. Normality has resumed.

[jhsa]

strange

EDIT: Companion 1.22, play file doesn't work and it doesn't allow to select files smaller than 256

[bertrand35]

Oops, I forgot to change in companion!

[Flaps 30]

Earlier today I looked back at my posts. Noted that I had used tx fw version 2168 with the new sound pack and that gave a scrambled output but was fine with my original pack that I have been using for ages. So I flashed my TX with version 2215 again and tried that with a renamed voice pack (thanks goes to mbanzi for that renaming file) of my original files. That worked!! Okay my custom files have gone AWOL.. I will sort that out later.

So all I have to do is to relate back to the line numbers in the CSV files to work out how to label my WAV files to add to the SD card. This IMO needs to be sorted guys

It still leaves a question as to why the voice pack that is posted for the 16Khz Emartee card should still be giving the strange results that it does, along with nasty clicks at the end of the files. Ohh.. I think that maybe in the future as the numbers of MegaSound cards increase that we will need that as an option as against the Emartee card in the preferences of companion, so that the right voice packs get downloaded.

TX is charging at present. So unable to do further work for a while.. Housework time I reckon.

[MikeB]

I'd say it was time to get a second Tx battery, 1 to use, 1 to charge, saves on the housework

Mike.

[Flaps 30]

It gave me a break Mike.. Much needed.

I have finally given up with version 2215 and the new sound pack for the Emartee card. For some reason 2215 started playing up by intermittent actuations of the haptic (it wasn't selected anywhere on the model file in use or in setup) followed by blank screen along with being unresponsive. Combine that with other things that went on as described above was the final straw.

So for now my stable version is 2168 along with the old sound pack that is well behaved. Yes I burned back the original sounds to the three SD cards I have and they all worked without any problems.

Perhaps the next time it may work better. Wish I could have got to the bottom as to why the new sound pack played up the way that it did. That was the same on all three SD cards.

[bertrand35]

Thanks for the report, it seems that Kilrah and jhsa succeeded to reproduce it, there is something obviously wrong with all these options enabled in the same time. Hopefully a fix today if I can find the time ...

[jhsa]

Bertrand.. I don't think it is all the options at the same.. I went back to 2168 with the same options except autosource and all seems to be fine..
The latest version, even without autosource has the problem and the radio starts all those gameboy sound thingy..
Well, I know nothing about all this obviously. I just report what happens to my radio.

João

[bertrand35]

I didn't say that you choosed too many options, just that there is a problem in one of these ones or when all these are enabled together. For the moment I have no clue, but I will find for sure! We already know that 2168 is good and 2215 is wrong. 47 revisions to review... If somebody was able to reproduce the bug in an intermediate revision, it would help me!

Flaps30 is also on ATmega128, right?

[jhsa]

Thanks for the report, it seems that Kilrah and jhsa succeeded to reproduce it, there is something obviously wrong with all these options enabled in the same time. Hopefully a fix today if I can find the time ...

I do apologise. I might have misunderstood this little part of your post..
But all I can do is report, and I must have the facts right so it's easier for you to find the problems..
Thank you for your time, it is much appreciated..

João

[bertrand35]

For João (or anybody else who would like to help):

In the File Explorer (Windows) you select your SVN directory, let's say opentx/src, then right-click with the mouse to display the menu.
In the menu, you select "TortoiseSVN" and then "Update to revision..."
You have now a dialog box. Normally "Head revision" should be selected by default. You select "Revision" and at the right a revision number (I suggest 2190). And you press Ok. It will retrieve from SVN this revision.

Then you compile as usual and flash the Tx. If 2190 is wrong, then we know in which range of revisions the bug was introduced and I will only search in this range, it helps a lot!

[jhsa]

will do.. thanks

[Flaps 30]

Flaps30 is also on ATmega128, right?

That is correct. The system went into meltdown/lockup/blank display whilst I was changing a track in custom functions.