JumpMaster Posted August 7, 2016 Author Share Posted August 7, 2016 I've found a bug when using Android 4.4 but I'm not sure if it's the one people are suffering with. I could scan for devices but the main window did not try to connect. (it doesn't receive the result from the scan window). Once I fixed that my Nexus 5 successfully connected to my KS16 as expected. I've pushed version 1.2.1 to the beta channel. Let me know if this helps. Link to comment Share on other sites More sharing options...
access_granted Posted August 8, 2016 Share Posted August 8, 2016 7 hours ago, JumpMaster said: I've found a bug when using Android 4.4 but I'm not sure if it's the one people are suffering with. I could scan for devices but the main window did not try to connect. (it doesn't receive the result from the scan window). Once I fixed that my Nexus 5 successfully connected to my KS16 as expected. I've pushed version 1.2.1 to the beta channel. Let me know if this helps. Thank you! Now It works for me. Link to comment Share on other sites More sharing options...
Chrisjones Posted August 8, 2016 Share Posted August 8, 2016 @JumpMaster Thanks for the App it's great. Just want to try to understand a few basic things that are maybe for newbies: I opened a csv generated from a ride and had something like this: date time speed voltage current power battery_level distance temperature fan_status 05/08/2016 18:29:33 0 66,03 3,12 206,01 100 0 22 0 05/08/2016 18:29:33 0 66,03 3,12 206,01 100 0 22 0 05/08/2016 18:29:33 0 66,03 3,12 206,01 100 0 22 0 05/08/2016 18:29:33 0 66,03 3,12 206,01 100 0 22 0 05/08/2016 18:29:33 0 66,02 3,23 213,24 100 0 22 0 05/08/2016 18:29:33 0 66,02 3,23 213,24 100 0 22 0 05/08/2016 18:29:33 0 66,02 3,23 213,24 100 0 22 0 05/08/2016 18:29:33 0 66,02 3,23 213,24 100 0 22 0 05/08/2016 18:29:33 0 66,03 3,08 203,37 100 0 22 0 As far as i remember: Volts (V) X Current (Amp) = Power (Watts/hour) is this correct? It seems as i see that numbers are corresponding. So now i have 15K lines with that for a ride of 13min21sec. I am trying to calculate consumption here: So if i take averages of those 3 columns i managed to get the following: (, is the decimal here!) Volts Amps Watts/h Averages 63,82 7,31 458,88 Time 00:13:21 Does that mean that in order to calculate my battery level i need to multiply 13m21 sec by watts/h in order to get consumption? and hence deduce battery level? In my case: 13min 21 sec is 0,2226 of an hour so 458 w/h X 0,2226 = 102 watts? So how does this relate to the battery of a MCM4 HS 340mh ? How can i then precisely calculate the consumption? i believe it indicates 90% battery level but that seem odd to me if i have 102watts consumed... Anyone to correct my newbies deductions? Thanks a lot! Link to comment Share on other sites More sharing options...
Chriull Posted August 8, 2016 Share Posted August 8, 2016 10 hours ago, Chrisjones said: @JumpMaster Thanks for the App it's great. Just want to try to understand a few basic things that are maybe for newbies: I opened a csv generated from a ride and had something like this: date time speed voltage current power battery_level distance temperature fan_status 05/08/2016 18:29:33 0 66,03 3,12 206,01 100 0 22 0 05/08/2016 18:29:33 0 66,03 3,12 206,01 100 0 22 0 05/08/2016 18:29:33 0 66,03 3,12 206,01 100 0 22 0 05/08/2016 18:29:33 0 66,03 3,12 206,01 100 0 22 0 05/08/2016 18:29:33 0 66,02 3,23 213,24 100 0 22 0 05/08/2016 18:29:33 0 66,02 3,23 213,24 100 0 22 0 05/08/2016 18:29:33 0 66,02 3,23 213,24 100 0 22 0 05/08/2016 18:29:33 0 66,02 3,23 213,24 100 0 22 0 05/08/2016 18:29:33 0 66,03 3,08 203,37 100 0 22 0 I hope you have the time data with more accuracy? You'd need the exact times to calculate the consumed energy. 10 hours ago, Chrisjones said: As far as i remember: Volts (V) X Current (Amp) = Power (Watts/hour) is this correct? It seems as i see that numbers are corresponding. No. Voltage(V) x Current(A) = Power (W) What you want to calulate is the used energy (Wh) 10 hours ago, Chrisjones said: So now i have 15K lines with that for a ride of 13min21sec. I am trying to calculate consumption here: So if i take averages of those 3 columns i managed to get the following: (, is the decimal here!) Volts Amps Watts/h Averages 63,82 7,31 458,88 Time 00:13:21 Does that mean that in order to calculate my battery level i need to multiply 13m21 sec by watts/h in order to get consumption? and hence deduce battery level? In my case: 13min 21 sec is 0,2226 of an hour so 458 w/h X 0,2226 = 102 watts? I'd assume with the average volts and amperes you won't get any real result. If the measurements are all with the same timeintervall you could use the average power (average of voltage x current for each measurement). If you then multiply this average with the time (in hours) you get the consumed energy in Wh. If the timeintervalls are not constant, you'd have to multiply each power value by the time to the next measurement and add up all this energy values. Also negative power values (regenerative breaking) should be treaded differently - some of this negative energy recharges the battery (imho a small percentage) and some is just wasted - so if you add this negative values to all the others you'd get too low consumed energy as result. Link to comment Share on other sites More sharing options...
Chrisjones Posted August 9, 2016 Share Posted August 9, 2016 Thanks for your reply @Chriull yes what i wanted to achieve is calculate my consumption in used energy wh for a km/mile How would you recommend measuring this? Thanks Link to comment Share on other sites More sharing options...
Chriull Posted August 9, 2016 Share Posted August 9, 2016 53 minutes ago, Chrisjones said: Thanks for your reply @Chriull yes what i wanted to achieve is calculate my consumption in used energy wh for a km/mile How would you recommend measuring this? one can calculate it as described in my previous post. Could als be implemented in the android app, so that it can be shown on the pebble warch. But since the power (voltage, current) values are not the average of the sampling period it will be just a more or less rough approximation. Link to comment Share on other sites More sharing options...
JumpMaster Posted August 11, 2016 Author Share Posted August 11, 2016 I've just uploaded version 1.3.0 to the beta channel. If there are no issues I'll push it to production tomorrow evening. After making the GUI I've added a custom notification so you no longer have to look at it! Battery percent, temperature, and distance are displayed, along with the three buttons as per the app. So you can connect to the wheel, start logging, or start the Pebble dashboard, straight from the lock-screen. I've also incremented the ride time and distance until the app is closed. So if the wheel is restarted half way through a ride, the ride time, distance, and top speed will no longer be reset. Here are some screenshots of the notification bar on Android 4.4 and 7.0 on a Nexus 5 and 5X. Both of these devices have a 1920 x 1080 resolution so I'm curious if the notification scales to smaller screens. If you're able to provide a screenshot on a smaller device or just let me know it looks OK that would be great. Link to comment Share on other sites More sharing options...
trya Posted August 11, 2016 Share Posted August 11, 2016 @JumpMaster Kevin, I just updated to 1.3.0 - and it wouldn't start at all ("Unfortunately WheelLog has stopped" - on startup, even before the main screen appears). Android 5.1.1 on Sony Xperia Z3v. Turning the wheel on before start doesn't change anything. PS. Sometimes I see main screen flashes before I get the message. Link to comment Share on other sites More sharing options...
HEC Posted August 11, 2016 Share Posted August 11, 2016 16 minutes ago, trya said: @JumpMaster Kevin, I just updated to 1.3.0 - and it wouldn't start at all ("Unfortunately WheelLog has stopped" - on startup, even before the main screen appears). Android 5.1.1 on Sony Xperia Z3v. Turning the wheel on before start doesn't change anything. PS. Sometimes I see main screen flashes before I get the message. Have you tried to clear the application data and cache under settings (apart of obvious reboot of the whole phone or force-stopping the app under settings)? Link to comment Share on other sites More sharing options...
trya Posted August 11, 2016 Share Posted August 11, 2016 Yes, I tried clear data/cach and "force stop" - it didn't help.I even tried the full re-install - same issue. Link to comment Share on other sites More sharing options...
Hansolo Posted August 12, 2016 Share Posted August 12, 2016 Same problem with 1.3.0 "WeelLog s'est arrêté" (WheelLog has stopped) on my SAMSUNG S7 (Android 6.0.1) I try without effect: - clear the cache - force stop - uninstall, install - restart my phone I use WheelLog with a KS-16 Link to comment Share on other sites More sharing options...
JumpMaster Posted August 12, 2016 Author Share Posted August 12, 2016 Thanks for your feedback. I've got the crash dumps from the Play Store and it's the custom notification. I've installed Android 6.0 on my Nexus and it has the same issue. Joy! Link to comment Share on other sites More sharing options...
Hansolo Posted August 12, 2016 Share Posted August 12, 2016 Great! Link to comment Share on other sites More sharing options...
JumpMaster Posted August 12, 2016 Author Share Posted August 12, 2016 Just pushed version 1.3.1 to the Play store awaiting approval by Google. If you're impatient... https://drive.google.com/file/d/0B_qIN0Xd80hCMTZPdW1ZZUE1UW8/view?usp=sharing Link to comment Share on other sites More sharing options...
Blunzn Posted August 12, 2016 Share Posted August 12, 2016 tried version 1.3.0 yesterday with my cheap Wiko Lenny 2 (5" 480 x 854) worked fine, although only the battery % could be seen. At the later try the app startet crashing. now with 1.3.1 everything works fine again and the notification are nice to read on smaller screens. nicely done! Link to comment Share on other sites More sharing options...
JumpMaster Posted August 12, 2016 Author Share Posted August 12, 2016 That's awesome thanks @Blunzn. Looks like the margin on the left is a little big. I'll reduce it for the production release. Link to comment Share on other sites More sharing options...
Hansolo Posted August 12, 2016 Share Posted August 12, 2016 Yes 1.3.1 is working. I can use it this evening meet up Link to comment Share on other sites More sharing options...
HEC Posted August 12, 2016 Share Posted August 12, 2016 4 hours ago, JumpMaster said: Just pushed version 1.3.1 to the Play store awaiting approval by Google. If you're impatient... https://drive.google.com/file/d/0B_qIN0Xd80hCMTZPdW1ZZUE1UW8/view?usp=sharing Fantastic! Works fine again on 4.4.2 - thanks. Link to comment Share on other sites More sharing options...
Jason McNeil Posted August 12, 2016 Share Posted August 12, 2016 @JumpMaster, stupid question: how do I review the App at Google Play? If you're participating as a beta tester, does Google not allow you to rate it? Link to comment Share on other sites More sharing options...
JumpMaster Posted August 12, 2016 Author Share Posted August 12, 2016 @Jason McNeil I have no idea. I only see the option to send beta feedback. I've pushed version 1.3.2 to production so feel free to leave the beta Next step will be to add a settings menu. First settings will be max speed for the outer arc in the GUI and a debug option that will log the raw Bluetooth output to file. That should help to add more wheels to the app. Link to comment Share on other sites More sharing options...
Battling Posted August 12, 2016 Share Posted August 12, 2016 Thank you @JumpMaster for those adds. All working for me. I appreciate the data retention until app is closed. Link to comment Share on other sites More sharing options...
trya Posted August 13, 2016 Share Posted August 13, 2016 Thanks, Kevin @JumpMaster! All is great again You plans to add the "settings" controls are much appreciated! Link to comment Share on other sites More sharing options...
koto Posted August 20, 2016 Share Posted August 20, 2016 @JumpMaster: I've just installed the app available on play store. It cannot communicate with ly gotway ACM. It just says: "Waiting for a wheel" oe something like that. How can I give you some logs or something similar ? Link to comment Share on other sites More sharing options...
EricGhost Posted August 20, 2016 Share Posted August 20, 2016 26 minutes ago, koto said: @JumpMaster: I've just installed the app available on play store. It cannot communicate with ly gotway ACM. It just says: "Waiting for a wheel" oe something like that. How can I give you some logs or something similar ? Try going to Android settings applications, select wheellog and give permissions for localization and archive Link to comment Share on other sites More sharing options...
EricGhost Posted August 20, 2016 Share Posted August 20, 2016 On 9 agosto 2016 at 2:47 PM, Chriull said: one can calculate it as described in my previous post. Could als be implemented in the android app, so that it can be shown on the pebble warch. But since the power (voltage, current) values are not the average of the sampling period it will be just a more or less rough approximation. Well if I understood the Wh concept you can calculate it by calculating the area of the power Watt(time)=AreaWatt curve, then you can divide by the time lapse of your run: AW=Wavg*Time, so Wavg=AW/Time. You have the average power of your ride, let's say 150W in 40minutes then you have to relate to the 60 minutes, to drain the same power in 60 min you should have used 150*40/60=100Wh, is it? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.