Dedicated speed sensor/controller

[yooper2001]

I have a geared hub with 5.7 to 1 reduction. It has 20 internal magnets. So when I use the Hall sensors for speed calculation, I have to set the magnets to (20*5.7) 114.. or in my case 100, and reduce my speed ratio setting to 89% because it has a 100 magnet motor limit.
With this set, I am +-1 MPH at 20 mph.

Only thing is that no speed when coasting...because of the motor clutch.

I have a dedicated speed sensor in the hub that grounds the 5v from the controller white wire whenever the EXTERNAL SINGLE magnet passes the sensor...even when coasting.

Now when I set the magnets to 1.... i have to set the speed ratio back to 100 percent, And I get perfect speed under power again.
The problem is that when I first turn the bike on....speed while coasting works for a minute or two...then stops and drops to zero while coasting also...it is not using the Hall sensors, because the magnets and speed ratio set for the dedicated speed sensor would make the speed while powered inaccurate. The speed is spot on while powered, so it can still read the dedicated speed sensor...it just doesn't want to show speed while coasting (Even though it did it upon start for a minute)

The question is.....is this my display....or the controller?

The display is the Haytrix H8. (Protocol 2 ...Big fancy screen to see watt usage)

The controller is a 26a generic protocol 2 made by Hudamzky.

Anyone knowledgeable enuff to know which piece of equipment controller or display is responsible for actually calculating the dedicated speed sensor speed output? Like I said...works while motor is powered just not while coasting.
I live on a hilly area...and the speedometer and odometer are not accurate a quarter of the time due to coasting.

Thanks in advance.

 

[amberwolf]

Soudns like it might have the same type of fallback to motor halls when signal count drops too low that hte Phaserunner does.

The solution to that is to install more magnets on the wheel and set the number of poles appropriately. It also makes the very-low-speed readings more accurate. This won't fix other possible causes, though.

On SB Cruiser I mounted three to the front wheel by using gorilla glue to attach little magnets off old badge holders to the spokes:


As for which thing does the calculations...best guess is the display, but it's no certainty. They could easily do it in either one. They could take the speed from both sensors and send it to either or both MCUs, and either or both might do this calculation.

Could even be that the firmware of one is not realy compatible with the ohter, so that after some amount of time, the data recieved by the display from the controller doesnt' match what it iexpects, so it stops accepting it and does whatever it's fallback is.

It could even be shitty programming, so that even if it's set to use the wheelspeed sensor data, if it stops reading the halls, it blanks the speed because it thinks the speed is zero despite the continuing WSS data.

 

[yooper2001]

Incompatible probably because low speeds work fine when low but not coasting, works fine at all speeds as long as it's not coasting.

Well...I bought myself a cheap 20 amp ali express sine wave controller that I was gonna use, but had a bad mosfet out of the box....and i just found out my kids got me the mosfet for my stocking. Took a month to come in....I guess I'll do my first controller mosfet replace (I Worked in an electronics lab) and see if maybe its the controller on Thursday!

I guess it's a good filler for time until the rim, spokes, hub, and truing stand get here.... (Damn you sphere mods)

Thanks for getting me out of my blue screen of death mindset.