BUMP log upload never finishes

[KevinB]

When trying to upload my battery logs from the BUMP to my tablet, it won't finish???
It starts on 0 of 47 logs to upload equalling about 100kb. The bytes start increasing and the percent complete starts climbing. It never gets off of 0 of 47. The percent reaches 100 when the byte count reaches the total......but then it just keeps going. I let it climb to 800kb uploaded and it was still going.
How do I fix this? And can it be done without losing my 47 charge cycles stuck on the BUMP?
Thanks.
KevinB

[RevoKelly]

I assume youre using the Apple version of the app ....
There was a bugfix applied to 1.12 app release (still in beta testing) that fixed a problem the upload could get stuck in a loop.
You will see the 1.13 version available in the next day or two, so upgrade to that version and see if it succeeds. Note that the 1 time i was able to reproduce, the root cause was a corrupt record in the Bump, and in that case, the history on the Bump was lost, but that isnt always the case.

[KevinB]

No. Android
It seemed to break a couple firmware updates ago.
Thanks for the quick reply!
KevinB

[KevinB]

I'm on the latest ccs and the BUMP is at 3.08

KevinB

[Fauropitotto]

I complained about this exact issue some time ago, and was ignored.

https://www.helifreak.com/showpost.p...&postcount=149

The only way I was able to get uploads to be completed again was to "clean all battery history" from the bump charger itself, and make sure that I upload after every charge cycle I do. I suspect maybe I waited too long between uploads, and it got too large for the bump to handle.

[KevinB]

Originally Posted by Fauropitotto

I complained about this exact issue some time ago, and was ignored.

https://www.helifreak.com/showpost.p...&postcount=149

The only way I was able to get uploads to be completed again was to "clean all battery history" from the bump charger itself, and make sure that I upload after every charge cycle I do. I suspect maybe I waited too long between uploads, and it got too large for the bump to handle.

Thanks for the feedback Fauropitotto.

One other different thing I did about the same time this problem started was to do a few manual charges without 'bumping'. Perhaps that wrote a strange entry that interferes with the upload???

I'll wait to hear back from Kelly before I clear my BUMP's memory.

KevinB

[RevoKelly]

You will also see Android CCS 3.47 which includes the same Bump 3.10 firmware to better detect and prevent cache corruption problem, but in the case of Android you will most likely lose the history since the root cause must be corrupt cache in the Bump itself. Upgrade the app, try again to upload history. If it still hangs, on the Bump go into Settings and perform the Clear History Cache, then allow the upgrade to 3.10 to proceed. Let me know if you see any similar problems with 3.10+ .... hopefully we have it solved.

[RevoKelly]

You werent ignored - i just didnt have an answer yet

Some changes were made to begin caching more information with the cycle graph and those changes seem to trigger more frequent flash corruption problems. The latest firmware will help detect and prevent this condition.

[KevinB]

Did you just push 3.47/3.10 ? I checked this morning before I did the last test and didn't see the update. I have it now and will try what you posted above.
Thanks again for the superb support Kelly! Much appreciated.

KevinB

[RevoKelly]

Originally Posted by KevinB

Thanks for the feedback Fauropitotto.

One other different thing I did about the same time this problem started was to do a few manual charges without 'bumping'. Perhaps that wrote a strange entry that interferes with the upload???

I'll wait to hear back from Kelly before I clear my BUMP's memory.

KevinB

Oh, and thanks for pointing out the Manual operation step - it just might be the key to reproducing. I'll do more testing on that specifically.

[KevinB]

Just fyi, when it's downloading the new firmware, in the CCS, it has Downloading Firmware in the title bar of the window, but says Uploaded Cycle Graph 0 of 0 in the contents of the Firmware update window.

When it got to the reboot of the firmware update, the BUMP froze there. After a power cycle, I'm just getting a white screen. It gives three beeps when I power it up (via the USB port -- I pulled it from my case), but the white screen never goes away.

Now what???


KevinB

[KevinB]

Ok. I reloaded ver 3.05 via the Windows update app and I got rid of the white screen after that finished and I did a power cycle. I then connected via BT with my tablet and updated to 3.10 again. The window on the CCS displayed correctly this time, however, when the 3.10 download was completed, it again froze after saying it was rebooting, and after a power cycle, I was stuck at the white screen again.

KevinB

[KevinB]

Tried a different BUMP controller. The 3.10 firmware white-screens that one as well.

KevinB

[RevoKelly]

Originally Posted by KevinB

Tried a different BUMP controller. The 3.10 firmware white-screens that one as well.

KevinB

Rats ... makes me think i posted the wrong firmware with it - the debug version will whitescreen a production (not development) Bump unit. Checking now to see - will post again shortly.
If whitescreened, youll need to recover via USB interface to Windows firmware utility - just take latest version there and ill make sure there is a good Android app avail soon.

[KevinB]

Thanks Kelly. You had me worried there for a bit when my BUMP became a brick........before I read how to do the forced firmware update via the USB!

I'll try it again once you post the new version.

KevinB

[RevoKelly]

Yes, just confirmed - Bump firmware 3.10 is DEBUG not RELEASE version. Looks like a problem in my build scripts grabbed the wrong version when building Android app. Note 3.10 firmware in the Apple iOS app will be fine.

I just posted 3.48 / 3.11 versions to fix it.

Thanks for reporting the problem so quickly - no doubt it saved many others from the hassle.

Yes, to recover from a bad firmware load (like 3.10) just hold the touchscreen as you apply power. After about 10 secs, you'll hear a long beep - that means it has bypassed normal startup (which would load the bad image) and is ready to receive a new firmware image over USB. So just push the latest image from Windows firmware installer (it will be older) and when that completes, connect up with the new Android CCS 3.48 to push the new Bump/3.11 firmware and you will be good to go again.

Really sorry guys - this is my mistake and I know it's pain in the butt having to connect up via USB (especially if its mounted in a case).

Since this new Android app only contained the new Bump firmware image (no other Android CCS app changes), and that Bump 3.10 firmware has already been thoroughly tested in use with the Apple CCS app, I figured it would be safe to just push that Android CCS update straight to production instead of the normal route of beta team first ... well, lesson learned ... if something CAN go wrong ... ;(

[KevinB]

Hey.....no worries. Thanks again.

KevinB

[RevoKelly]

Ok, so figured out the problem with the build script, as well as the Bump image.
Look for Android CCS v3.49 with Bump v3.11.

[KevinB]

All the firmware flashing must have wiped out the stored logs on the BUMP. Nothing uploaded once I was able to connect to it again.
I ran a couple of new storage cycles, and the logs uploaded properly at the end of each. So, it looks like it's working like it should again.

Thanks Kelly!

KevinB

[KevinB]

To follow up, I tried a couple charge cycles without the tablet connected. When I did connect it, it uploaded the 2 cycles fine.

KevinB