kylerlaird
10 W
This problem has been vexing me for over a month. I think I finally narrowed it down. I need to talk through it...
I'm now building a 26" fat tire Mongoose. I a similar 20" Mongoose. It's a VESC controller, Sempu T9 pedal sensor, 48V battery, and eBikeling front hub.
The Sempu sends about 1.5V for torque at rest. I tweak the controls, everything is good, then I take it out for a test and it's buggy.
After much testing on the stand, I finally realized that the problem comes when I zip tie the Sempu cable to the frame (right before I take it out for a ride). The torque sensor output will go low (~0V) sometimes. I assumed it was a bad connector. I switched cables to the controller a few times. I went through three other T9s. The problem remains.
It doesn't feel like a typical bad connection. It's much more subtle. There's a short cable with a connector coming from the T9. It mates to another cable that goes up to the controller. If I press those connectors up against the frame and roll it just right, the torque voltage takes a dive. The cadence sensor still works, though, so I don't think it's a power cable issue.
This sensor works with "wireless" (inductive) power. I've been thinking that it could be an interference problem. Tonight I tried replicating the motions that were causing failure against other pieces of metal (like the bike stand). No effect. It's only when I hold the connectors against the frame.
But why the frame??? Ah ha! The motor! I finally disconnected the motor and the problem ceased. I'm guessing that motor noise is disrupting the torque sensor's wireless power when the cable is in some positions.
This analog/RF stuff is not my forte. Do I need to provide a better ground between the frame and fork? Throw a choke on the cable? Shield the cables? Offer a sacrifice to Telsa?
I'm now building a 26" fat tire Mongoose. I a similar 20" Mongoose. It's a VESC controller, Sempu T9 pedal sensor, 48V battery, and eBikeling front hub.
The Sempu sends about 1.5V for torque at rest. I tweak the controls, everything is good, then I take it out for a test and it's buggy.
After much testing on the stand, I finally realized that the problem comes when I zip tie the Sempu cable to the frame (right before I take it out for a ride). The torque sensor output will go low (~0V) sometimes. I assumed it was a bad connector. I switched cables to the controller a few times. I went through three other T9s. The problem remains.
It doesn't feel like a typical bad connection. It's much more subtle. There's a short cable with a connector coming from the T9. It mates to another cable that goes up to the controller. If I press those connectors up against the frame and roll it just right, the torque voltage takes a dive. The cadence sensor still works, though, so I don't think it's a power cable issue.
This sensor works with "wireless" (inductive) power. I've been thinking that it could be an interference problem. Tonight I tried replicating the motions that were causing failure against other pieces of metal (like the bike stand). No effect. It's only when I hold the connectors against the frame.
But why the frame??? Ah ha! The motor! I finally disconnected the motor and the problem ceased. I'm guessing that motor noise is disrupting the torque sensor's wireless power when the cable is in some positions.
This analog/RF stuff is not my forte. Do I need to provide a better ground between the frame and fork? Throw a choke on the cable? Shield the cables? Offer a sacrifice to Telsa?