SOLVED - Help.. New firmware has broken my Kemper

So just to update..

I've tried the following now:

1) System reset followed by install of V2.7.3 - The system boots up fine all profiles working
2) Upgraded to V2.7.4 - as above, all working fine
3) Just downloaded 3.0.0.10856 using chrome, its installed, performed screen checks, rig checks, pedal checks, effects etc.. it then looks like its going to load and I get a load of errors again

Not to worry, If I get a resolution via support I will let you know in case anyone else gets the same problem.

Mine is quite an early Kemper, I don't know if that makes a difference, I've also got the failing LED issue as well which to be honest doesn't bother me much unless its the cause of this issue

Cheers
Steve

Latest update...

OK, so now I'm up and running using v3

I'm not sure what the problem is, but its pointing to something either with the bundled factory rigs or one of my rigs (I'm suspecting the bundled rigs based on the following).

Basically I performed a flash wipe (back up your rigs before doing this as it cleans them all out)

1) push and hold soft button 1 (top left above display) while switching on the unit into Tuner Mode;
2) keep pushing the button until the Booting Maintenance Mode message appears;
3) in Maintenance mode push Maintenance, Memory, Init Flash, Yes, Ok, and shut down

Once I did this, the Kemper booted up fine using the latest firmware.

However, I then tried to install the factory rigs using the system/factory rigs method and it threw up an "unexpected error occured" message, and then another "software error take a picture etc".. message I was getting before the flash wipe.

When I rebooted the Kemper it loaded error free but still I still had no rigs.

I then installed a couple of my own rigs and they installed OK, sound like they should and all is well in the world.

I downloaded the "merged rig pack" and they also installed OK.

I'm just about to download the factory rig pack and try that... keeping my fingers crossed, but at least I know how to recover it if this fails !

Support are also looking into it, I've sent all this info to them as well so hopefully they will find out why I'm having to restore my rigs like this rather than via the firmware.

Cheers
Steve

EDIT: Factory rigs using the download version rather than the system/facroty rig option gave me the message that the rigs already existed.

Also.. I tried to install by back-up and it failed saying it was corrupt, although I could restore using the same back-up when running v2.7.4

I'm basically up and running but I've lost some of my rigs in the process as I only had a few backed up as rigs rather than in the system back up

OK.. so here is the latest..

I managed to get v3 up and running however as soon as I tried to install the factory rigs I started to get software error messages again.

If I tried to install them via a USB stick, it told me they already exist, but don't show up in the rig manager or via the brower.

I performed a factory restore (init and Factory rigs) which said it was sucessful, but then threw up software errors again when I rebooted.

If I do the same but just init, its fine until I try and install the factory rigs.

I've just rolled back to v2.7.4, performed a factory restore (init and factory rigs) and its back working fine.

so in my limited understanding there is something still amiss with V3 in terms of the factory rigs element.

Support are still on the case, so fingers crossed I will get to upgrade to V3 soon.

Can anyone else confirm that they have upgraded to V3 with the factory rigs ok ?

Cheers
Steve

afraid not.. it comes up with a bunch of error messages.

If I go into the maintenance option and just select init (not init&factory rigs) it boots up fine, I can install my own patches and other user patches just fine too. However it will not let me install the factory rigs at all. It either says they are already there (if I put them on a USB stick and try and install them) or it throws software errors if I try from the system/factory rig method

Hi Merman

I did raise a ticket with Kemper to fix the LED's but it was going to cost me approx £150 to ship it to Germany to be fixed (with insurance) and to be honest I don't need the LED's fixing that badly to justify that kind of shipping fee.

Saying that, if I can't get this issue fixed it may have to go back anyway.

I'm just wondering if I have different chip set or some other components (I think my Kemper is one of the early builds.. I might be wrong though)

It's odd that I can run the new firmware fine as long as I don't try to install the factory rigs.

Bit of a long one this.. but I thought I would share some of the testing I've done to try and get to the bottom of my v3 problems. I hope the devs don't mind me posting this here, I have also sent it to them via the support ticket.

I started off by installing V3.0.0.10856 using the USB boot method
I performed an init flash to clear out all existing rigs.

Once it was rebooted I connected the Kemper up to my PC and started
rigmanager

Test 1) Installed Merged Rig Pack

I unzipped the contents of the merged rig pack into a folder on my PC
then dragged and dropped them into "my profiler" in rig manager.

They transfered over fine and I could swap between rigs either via the
Kemper direct or by using rig manager

Test 2) manual transfer of Factory rig pack using Rig Manager

I unzipped the v3 factory rig pack onto my PC and started to copy them
over to "my profiler" folder within rig manager.

I selected the following rigs (I ordered the rigs in alphabetical order
and selected a few at a time):

1962-electo through to Bass Driver - All transfered ok

Broken Heart through to FP-sun three hundred T - Software
error occured

I rebooted the kemper and within rig manager I could see most of the
last batch had transfered but the block converter distortion to FP-Fan
BM 1959 were missing

Test 3) - copied the next rig FP-voice acethirty using rig manager and
the Kemper instantly threw up the following error:

expr=DABT PC A02B6004

file=unknown

line=0

swvs="release:3.0.0.10856"(CRC=D4f027D7)

Pressed exit to reboot

The Kemper reloaded ok and I could see that there were 75 rigs installed.

I then performed another init flash to clear out all the rigs and reset
the Kemper.

This time I tried only the factory rigs rather than starting with the
Merged Rig Pack

Using rig manager again, I started to move rigs over to the Kemper in
small blocks

1) Broken Heart to Convertor Crunch - OK

2) Convertor Distortion to Engle Powerfall Hi Sue - OK

3 ) Fat Ed to FP-voice ace thirty - OK

4) Gadda da vida to Hey Jim - OK

5) Highway-201502-13-57.39 to KM Thrash - Produced software error on Kemper

expr=DABT PC=A004F574

file=unknown

line=0

swvs="release:3.0.0.10856"(CRC=4B007270)

I pressed exit which caused the Kemper to freeze with a blank lit screen

I then rebooted, total number of rigs = 105

I checked to see what rigs were missing from step 5
(Highway-201502-13-57.39 to KM Thrash) and could see KM Arrival Clean
through to KM retrospecial were missing, however KM Sea Nymph to KM
Thrash were present.

I then tried to transfer 1 more rig - KM TOP Romulan, this caused the
Kemper to fail showing just the Green Screen with the Kemper Profiler
display

Rebooted and I could now see 106 rigs, including KM Top Romulan.

I then transfered 1 more rig - little pop prince, I didn't see it
transfer on the Kemper screen but no error occured.

I tried to select a rig using rig manager which caused the same fault..
Kemper froze with the Kemper Profiler display

I then rebooted Rig Manager and the Kemper

On restart the Kemper is showing 107 rigs and little pop prince is
installed.

I selected little pop prince in rig manager and the kemper loaded it ok,
sounded ok.

I then moved the next rig Little Prince MD421 over to the Kemper using
rig manager which caused the following software error:

expr=DABT PC=17CED8D8?

file=unknown

line=0

swvs="unavailable"(CRC=010D2D30)

I pressed exit and got the next error:

expr=DABT PC=A000DEAC

file=unknown

line=0

swvs="unavailable"(CRC=01002D30)

I pressed exit and got the following error

expr=DABT PC=9FDC0150

file=unknown

line=0

swvs="unavailable"(CRC=01002D30)

I pressed exit and got the following error

expr=(regindex>=)&&(regindexx<BOARD_NMBREGS)

file=../arn/board/board.c

line=120

func=boardGetRegByIndex

swvs="unavailable"(CRC=010D2D30)

I pressed exit and got the following error

expr=DABT PC=400048B0

file=unknown

line=0

swvs="unavailable"(CRC=010D2D30)

I pressed exit and the Kemper froze on a blank lit green screen

Rebooted the Kemper and it loaded OK with 108 rigs

Little Prince MD421 is in the kemper, I tried to load it but got the
following error

expr=DABT PC=A0000084

file=unknown

line=0

swvs="unavailable"(CRC=071B086F)

Pressed Exit and got another error

expr=DABT PC=A0000090

file=unknown

line=0

swvs="unavailable"(CRC=01002D30)

Pressed exit and the Kemper rebooted itself

I tried to select a different rig and I got the following error

expr=instance <mMultiplicity

file=

line=843

func=const int Access::logicEngine::Expression::GetLastResult(int)

swvs="unavailable"(CRC=A100F408)

Pressing exit just repeats the same error.

Powered off.... end of testing

Just wanted to update this thread to say that the issue wasn't actually related to the firmware as such, I had to return the Kemper to the Factory where the fault was diagnosed as being a faulty flash memory which only showed itself when V3 came out. It's now safley back home and running the latest firmware with no issues so far (with fixed LED's as a bonus !).

I want to take this oppertunity to say a huge thanks to the Kemper Support team, Hans in partcular kept me updated all throughout the process and even replied to emails at the weekend. Superb support from the team all round... I can't praise them enough.

Cheers
Steve