edca2001

Nicely done instructable, thanks for publishing it. It sure brings back a lot of memories.

This is an amazing project!

This is a great technique. I recently used it to print some flush text in a different color than the rest of the print. It turned out great! Thanks for describing it here.

I believe you could. I'm pretty sure the "Cycle Analyst" for example uses a shunt resistor, and certainly many controllers do. Depending on your controller you might be able to tap into it's current shunt if it has one.I think to keep things simple you would want to re-scale the battery voltage input to closer match the shunt resistor measurement so that you could still use a single reference voltage. It would be convenient to use the 1.1 Volt built-in reference on the ATMega.Of course you could switch to a completely different processor with programmable channel gains as well.

Nice, I'll have to print it and try it.

Thanks for the well done instructable.I was excited to see your title. I thought "maybe finally there are instructions that don't show AREF connected to VCC (or AVCC)!", but it was not to be. Do you have a reference that suggests this connection is required? I'm convinced it's a bad idea but I could be mistaken. My understanding is that the AREF pin is for connecting something other than VCC as an analog reference , and connecting VCC there could short to the internal 1.1V reference if I happen to load a sketch that switches to the internal reference source.

I wrote the directions assuming that the circuit would be tapped in at the battery. It might seem confusing if you're tapping in at the controller end.There should already be a wire between the red wire on your connector and the battery. Don't change those connections. Then add a new wire from either the controller end or the battery end of that wire to connect to the fuse.

Yes, exactly.

One terminal of the ACS712 should go to the black wire on the power connector of your controller shown in your picture. The other ACS712 connection should go to your battery (the negative terminal). Which of these connections are you missing at the moment? If you can post a picture of your battery setup it might help.

The only connections for this project are to the two battery wires. You do not need to connect to anything on your bike controller.

I assume when you start you have your battery (+) and (-) hooked up to your bike controller. The fuse for this project connects to the battery (+) along with the existing bike controller. This is labelled "TO BIKE" in the sketch. The (-) battery gets disconnected from the bike controller. Then the (-) battery goes to one side of the ACS712. The other terminal of the ACS712 goes to the bike controller terminal that had the (-) battery connection. This is labelled "TO BIKE" in the sketch as well.Maybe post a picture of your setup if this doesn't make sense.

Thanks for the tip IgorM54.

Those dashes mean the GPS has not established a location yet. Does it help if you go outside or change location?You could download a gps tester app and make sure the gps on your android device works in the location that you're testing.The speed from the gps relies only on the android device, not on the arduino circuit, so you can test them separately.

That should be all you need to do, is grant the rights that you mentioned.I assume that if you don't connect the bluetooth that the app runs fine, and shows speed, time, and distance travelled?What android version are your phones? Mine is a Moto G 1st generation with 5.1 lollipop. Your 2gen must be at least that. What version is the Huawei? It's possible that there is something in newer Android versions that I am not aware of that is causing a crash.I have two thoughts. First, Is there any way for you to get the logcat from one of the phones when the app crashes? There should be a message in there that might help.Secondly, I have made a few changes to the app that I haven't posted yet because I haven't been able to test them. If I send you a new apk, would you be willing to test ...

That should be all you need to do, is grant the rights that you mentioned.I assume that if you don't connect the bluetooth that the app runs fine, and shows speed, time, and distance travelled?What android version are your phones? Mine is a Moto G 1st generation with 5.1 lollipop. Your 2gen must be at least that. What version is the Huawei? It's possible that there is something in newer Android versions that I am not aware of that is causing a crash.I have two thoughts. First, Is there any way for you to get the logcat from one of the phones when the app crashes? There should be a message in there that might help.Secondly, I have made a few changes to the app that I haven't posted yet because I haven't been able to test them. If I send you a new apk, would you be willing to test it? Most of the changes were to make it work on android versions back to 2.3 gingerbread, but we might get lucky.

I will post the newer apk tomorrow night (in about 24 hours). Since the first version isn't working anyway, there won't be any harm in trying the new version.