(100% ignorant take since I’ve never tried one. But yuck anyway.)
2 Likes
Yes it is. Love it
2 Likes
I’d happily pay $300 for the maytech one if it had 100% signal reliability.
4 Likes
You’d think out of all the things Maytech could fuck up, it wouldnt be signal reliablity on a remote with tons of experimental features of which all work impressively well.
5 Likes
Flashy features sell remotes.
1 Like
Upgraded to 5.3 now that I’m programming my vesc for the first time in forever. I am having an issue that I don’t remember having before. Upon startup, there is a very slight cogging in sensor mode. I haven’t been on the mountain board for a while, but I remember it being smoother than this.
Is this normal?
1 Like
Cogging is very normal without sensors. Where are your sensors?
Sensors are connected, and the vesc tool picked them up. I just checked and they’re plugged into the correct side of the vesc too. Sensors are at the back of the motor can
Hmm okay so I did both detections individually and seems like one of them is getting some faults but the other is fine
try swapping which side of the esc the motors are connected to
1 Like
Alright thanks I’ll give that a try. I poked through the enclosure and found that one of the sensor cables was maybe slightly pinched. I did free it and ran the detection again. This time it picked up both motor hall sensors, so that’s good. But there is a still a little bit of the cogging, albeit slightly improved.
I haven’t tried it loaded yet, so idk if I’m just being picky. This is happening at like 0.1% throttle
I realized I said sensorless in my first post. I actually meant hall sensor mode (whoops). I switched the phase wires and sensor cables around to the opposite motors and I’m still having the cogging issue. It sounds pretty terrible when I throttle up and then gradually reduce throttle to almost nothing
Also I quickly tried hfi and that also sounds like it cogs. So I think probably not sensor related
Did a little bit of a dive into some forum literature. Rolled back to 5.2 and cogging seems to be gone
2 Likes
If your running a unity in that kaly you’ll need to turn off phase filter first then do detection .
1 Like
In this particular board I have an old flipsky 6.6. It can’t really use any new fancy features I think, so I won’t need the most recent firmware. But in the event that I do update, I imagine the same rule might apply?
That is good to know though. I have a unity that is still running stock firmware and could probably use an update 
Don’t update a vehicle if it’s working fine and you’re not adding anything
4 Likes
That was more or less why I haven’t updated the unity yet. I did like the focbox UI, but I’m definitely interested in playing around with some stuff on the vesctool.
The 6.6 I only updated because I built a new PC and the new vesc tool that I had to download wouldn’t let me do anything at all without updating to 5.3. Only after reading through some stuff did I realize I can download an old tool from the forum
…despite Trampa claiming otherwise.
5 Likes
I have the original flipsky 75100 with 5.2 firmware. I am unable to get throttle input working as the vesc Tool 3.01 is asking for a firmware update when I try to use input wizard
But I read online the original flipsky 75100 firmware cannot be upgraded without sending it to Flipsky? Is that true ? If not anyone have clear instruction as flipsky videos are not clear where the bootloader and firmware files are located.
My Domino throttle is working fine when connected to the vesc COMM using 3.3v,GND and ADC1 pins but vesc Tool is not showing the throttle input but the throttle is working greas as seen through my logic analyzer connected on the vesc COMM lines
Vesc is connecting fine and reading battery v etc but throttle input not reading at all.
Any one experienced something similar ?
1 Like
3 Likes