I got one minor inconvenience, I would love to solve.
I use the BRemote2 and MKS84100.
Basically it works great.
But there is some random hickup at times when engaging the motor, going from still motor to any rotation, where it will not startup or start only after a longer delay.
This is not always the case, just every other time, so I tend to just 'pump" with the trigger, going from 0 to 15% a few times, until the motor is spinning.
Once spinning that “delay” or something is gone.
Been using it like that for a while, thinking this would be some FOC parameter.
So I finally tried to solve it on land, but it never happens there. No delay no nothing.
Even adding friction to the motor does not reproduce it on land.
Anyone got an idea, what could be the cause or what to check?
What type of motor do you have, sensored or sensor-less?
Sounds like you have an issue that is typical for sensor-less motors…
The esc needs to know the relative position of the motor shaft from 0 to 360 degrees in order to sync and provide power to it. In order to achieve that it’s going to send power to the motor every time you push throttle, move the motor a couple of degrees ,send a voltage signal back to esc and keep on repeating the process until it’s synced.
In case you have a sensored motor your issue can be anything from FOC to baterry or ESC settings…
It could also be that the motor wires have contact to water somewhere, therefore the sensor-less feedback is off and the controller freaks out. That won’t happen on land with dry motor wires?
The faster the motor spins, the stronger the back emf feedback gets and the more likely it is to overcome some external resistance that drags it down. So it should get more stable at higher rpm.
And technically you have the highest current/torque load right at startup, certainly for the control algorithm trying to figure out where your motor is turning
Do you think low quality connection between remote and receiver could result it to feel unresponsive? Or would that just cause interruptions without changing response time?
If I increase RF power, would I have to do it on both sides or would increasing it on the remote do?
I would rule out connection issues between Tx and Rx, as this would be better at low speed / not moving and worse at high speed because of interference with the motor signals, also the remote would show you a bad connection on the display…
Which settings for Rx and Tx are you at regarding RF power?
My board is slightly below 40l, so well under water when not moving.
I was thinking that even the tiny bit of movement from very little throttle (like 2 kmh) might keep the board a bit higher, improving signal.
When stationary I don’t ever disconnect, but I’m at one dot at times.
It’s also the easiest option to change,(if I can get the remote to connect to USB long enough).
Will it be enough to change this on the remote or do the values need to match?
I got this figured out, it is the signal for sure.
I tried today, with the board in water, myself swimming next to it and it never happens.
Happy as this will be easy to fix with a configurable remote like the BRemote2.
Thanks for the feedback.
I assume RF will influence battery life?
I somewhat enjoy the current charging situation. Been using it for 10 days straight, around 2-3h daily and it is still at 4.0V. Probably could use it 4 weeks without charging.
Not really, no
Maybe 1% maximum
You can pretty much put this to 20 always in all builds
Only reason it is at -9 is so that the remote out of the box does not send strongly on the wrong frequency (EU868/US915) before you have a chance to configure it.
Fyi -9 =0.13mW and 20=100mW
So with 20 you will be sending about 770x stronger
And yes change only on TX will be solving your problem likely, the Rx power is only needed to send telemetry back, which is of secondary importance
