Introducing the Bump Controller CCS mobile app

[HEXAHYDRATE]

Haha this setup was far from free lol.

Here is a pic of the battery screen I think you wanted Kelly. Sent another error report too.

I will try some different batteries now and see what happens.

Be back with those results shortly...

[HEXAHYDRATE]

Yes you were right Kelly it is just that particular battery info totally sends it for a loop lol.

I tried another brand 2200 3S 35C and it worked flawlessly. And also just tried a couple 6S with no problems.

What's the odds that was the 1st one I tried lol???

[RevoKelly]

We're proud to announce the latest release of the Bump Controller CCS app which now includes fully-automated battery history upload and graphing.

Features included in this release:

Android CCS App 3.09
* FEATURE: Battery History upload and display
* FEATURE: New Settings->Battery History setting to enable/disable upload to the device
* FEATURE: Entire content area is now scrollable (more room for viewing graphs)
* FEATURE: New 'Pack' subview tab replaces 'Info' (for better organization with graphs)
* FEATURE: Increased max battery capacity from 32Ah to 65Ah
* BUGFIX: Fixed navigation problem returning from Settings screen
* BUGFIX: Multi-pack BumpTags not working from mobile app

Bump Firmware 2.15
* FEATURE: Battery History logging and upload over Bluetooth
* FEATURE: "Upload Batt Hist" settings checkbox to enable/disable logging and upload
* FEATURE: Watts display
* FEATURE: New 'Pack' subview tab replaces 'Info'
* FEATURE: Increased max battery capacity from 32Ah to 65Ah
* FEATURE: Charge max now defaults to 10% of discharge max for LiXX tag setup
* FEATURE: Low-level safety checks on PowerLab operation status
* BUGFIX: Multi-pack BumpTags bumped on mobile device fails
* BUGFIX: 'Back' or 'Clear' doesn't always work when charge is complete
* BUGFIX: 'UpdTag' shown even when Analyze is stopped (should only show on complete)
* BUGFIX: Additional debug to isolate first/last cell IR bug

NOTE: Make sure you enable the new battery history feature on the Bump Controller (in Options), as well as on the mobile device where you want the history to be stored (in Settings). Once it is enabled, it will automatically upload after the operation completes, or the next time you bluetooth connect to your Bump.

Tools->Battery History opens the history view, or you can also touch any battery in setup (after bumping) and in the popup menu select History - this will open the same history view, but with that battery selected.

This is a base feature set - lots more stuff will be coming in the future. Next up will be ability to delete individual cycle graphs or batteries from your history. After that the ability to backup/restore/export all history data, and replace a faulty BumpTag with a new one without losing history data. We'll also be imporving the UI to add search/sorting/filtering capabilities to make it faster to find the pack you're looking for.

As usual, let me know about any issues and we'll get them fixed as quick as possible - the more help and detail you can provide, the faster we can fix them.

[HEXAHYDRATE]

When will the update show up in Google Play?

[pctomlin]

Thanks for all the hard work you guys put in to keep improving the Bump Controller. Been flawless since getting back from the original noise issue.

[HEXAHYDRATE]

I got the updates and tried it out. Pretty cool for sure.

The only problem I notice so far, is the display when I go to logged battery info and "select battery".

The battery I select has 2 or maybe more lines of text in the 2 boxes at the top of the screen. One long box and one short. The second line of text is cut off and I can't quite see it enough to read. And it will not let me swipe the screen to scroll lower.

Also Kelly, I got the app to crash again with the new firmware using the battery configuration we discussed earlier, and is pictured in a post above as you requested. And I did send another error report to Google Play using the new firmware as you asked.

[RevoKelly]

Originally Posted by HEXAHYDRATE

Yes you were right Kelly it is just that particular battery info totally sends it for a loop lol.

I tried another brand 2200 3S 35C and it worked flawlessly. And also just tried a couple 6S with no problems.

What's the odds that was the 1st one I tried lol???

Found the root case for this crash - it will be fixed in the next bugfix release, probably in about 1 week.

[RevoKelly]

Originally Posted by HEXAHYDRATE

I got the updates and tried it out. Pretty cool for sure.

The only problem I notice so far, is the display when I go to logged battery info and "select battery".

The battery I select has 2 or maybe more lines of text in the 2 boxes at the top of the screen. One long box and one short. The second line of text is cut off and I can't quite see it enough to read. And it will not let me swipe the screen to scroll lower.

Also Kelly, I got the app to crash again with the new firmware using the battery configuration we discussed earlier, and is pictured in a post above as you requested. And I did send another error report to Google Play using the new firmware as you asked.

Yeah, the display still needs to be optimized for mobile phones - if you view it with limited horizontal space, it doesn't work as well. We'll get this tweaked over the next couple weeks to ... probably reduce font size and remove some of the info to make sure it fits.

[HEXAHYDRATE]

I found another crash bug.

I tried 1 battery and the logs were uploaded and I was able to view graphs etc.

I tried a second different battery. Charge was completed and logs were once again uploaded.

But now as soon as I select battery history the app crashes consistently.

2 more reports sent to Google Play for this crash.

[RevoKelly]

Originally Posted by HEXAHYDRATE

I found another crash bug.

I tried 1 battery and the logs were uploaded and I was able to view graphs etc.

I tried a second different battery. Charge was completed and logs were once again uploaded.

But now as soon as I select battery history the app crashes consistently.

2 more reports sent to Google Play for this crash.

Looked at the crash report and this is actually the same bug, just hitting it in a different way. I'll be posting a fixed version mid-week.

[shadco]

So should we stay away from 2.15 then?

.

[HEXAHYDRATE]

You are ok to go with 2.15

I seem to have some unique circumstances that are causing crashes for me.

At worst you will not be able to view your logged battery history without crashing. A feature you do not currently have right now anyways so no big deal. But it should work fine for you. I'm special apparently lol.

And if you do have an issue just mention it here and it will be fixed pretty quickly. Its the reason I don't mind taking my time to provide feedback. I would be blowing hot air to alot of other companies.

[iscripter]

I am confused and I would like to know what is the latest firmware version for the BumpControl. In your post above you state the latest release is version 2.15 but on my BumpControl Windows firmware update app it lists version 1.54 as the latest version.

Is the latest 2.15 version only available through the Android app???

[RevoKelly]

Originally Posted by iscripter

I am confused and I would like to know what is the latest firmware version for the BumpControl. In your post above you state the latest release is version 2.15 but on my BumpControl Windows firmware update app it lists version 1.54 as the latest version.

Is the latest 2.15 version only available through the Android app???

Sorry for the confusion - we are currently working to fix a bug in the WIndows Firmware Upgrade Utility, so the latest firmware has not yet been posted there. We should have it fixed in a couple days.

[iscripter]

Originally Posted by RevoKelly

Sorry for the confusion - we are currently working to fix a bug in the WIndows Firmware Upgrade Utility, so the latest firmware has not yet been posted there. We should have it fixed in a couple days.

Thanks for the quick reply. Patiently waiting for the update.

[KevinB]

Hi Kelly.

Just a couple questions on how the battery logging is supposed to work.....

- If you have logging enabled on the BUMP, how many charge cycles can you do before you need to upload to a tablet ( or loose data ) Or is it really meant to be connected to a tablet whenever a charge is taking place ?

- If you upload to one device, does that clear the logs in the BUMP? Or can you then upload the same data to another device?


Thanks,

KevinB

[RevoKelly]

Originally Posted by KevinB

Hi Kelly.

Just a couple questions on how the battery logging is supposed to work.....

- If you have logging enabled on the BUMP, how many charge cycles can you do before you need to upload to a tablet ( or loose data ) Or is it really meant to be connected to a tablet whenever a charge is taking place ?

- If you upload to one device, does that clear the logs in the BUMP? Or can you then upload the same data to another device?


Thanks,

KevinB

Depending on the size/length of the operations, the Bump will cache about 100 cycles before running out of space. You will see a pop-up message if that happens so you wI'll know to connect and upload if your concerned about losing history data.

Once it is uploaded to one device, then it is removed from the Bump. Support for multiple devices, if/when that happens, will be by syncing between those devices, not by uploading to multiple, since that would waste space on the Bump.

[KevinB]

Perfect! Thanks Kelly,

Is there still plans to implement the ability to add our own battery names to the BUMP tag, rather than it just showing the battery ID?
Even if the "friendly" name was limited to 8 or 10 characters, it would be much more meaningful than the tag ID.

Just fyi.... (not important, just letting you know).... since the last app update, even if I set the Alert setting to Silent, I still get a sound from my phone or tablet when the charge completes. It's some default sound on the device because it's different between my two devices. If you actually pick an Alert sound, it plays that one. But if you pick None, even though it shows Silent, it still plays an alert.

Thanks for all the great work on this app so far!

KevinB

[RevoKelly]

Originally Posted by KevinB

Perfect! Thanks Kelly,

Is there still plans to implement the ability to add our own battery names to the BUMP tag, rather than it just showing the battery ID?
Even if the "friendly" name was limited to 8 or 10 characters, it would be much more meaningful than the tag ID.

Just fyi.... (not important, just letting you know).... since the last app update, even if I set the Alert setting to Silent, I still get a sound from my phone or tablet when the charge completes. It's some default sound on the device because it's different between my two devices. If you actually pick an Alert sound, it plays that one. But if you pick None, even though it shows Silent, it still plays an alert.

Thanks for all the great work on this app so far!

KevinB

The plan is to be able to set the 4-digit ID to whatever you want. So it will still be limited to 4 hexidecimal digits, but at least you can come up with your own pack numbering scheme ... so for example if i have 6 of the exact same pack, then I would number them 001A thru 001F. If you typically had more than 6 of a certain pack, then maybe use 2 digits for the "type" and 2 digits for the "number" .... so something like 0101 thru 0108.

That number doesn't have to be unique across all of your packs either - it is only for your reference. So the number could just be used to identify the "number" of that specific kind of pack. So, for example, I have a dozen 6S 5000's all simply numbered 0001-0012 and some 3S 2200's numbered 0001-0010.

This approach seems to align pretty well with what alot of guys already do (manually) if they want to track the history of a pack - they write some relatively small/short number on the pack. Minimizing the length (to 2-bytes in this case) avoids wasting valuable BumpTag storage space.

I'll add that Alert bug to the list to be fixed.

[RevoKelly]

Just posted new software with the following changes - mostly about fixing the problem with Analyze producing bad Fuel tables.


* Android 3.10
* FEATURE: Sorting of batteries in history (by chemistry, cell count, then capacity)
* FEATURE: Delete buttons added for both batteries and graphs (in history)
* FEATURE: Bump Firmware 2.16

// Firmware 2.16
// - FEATURE: Support for Wiring Mode and Regen Discharge PowerLab settings
// - FEATURE: Per-PowerLab options configuration (Apply and ApplyAll choice)
// - BUGFIX: Fuel sometimes invalid after Analyze Cycle
// - BUGFIX: BT connect during Analyze Cycle causes it to stop before final charge