blackheartxix
1 µW
- Joined
- Nov 15, 2022
- Messages
- 3
Hello guys, I have Fardriver 841800 and 84530, Im taking a look at the pin guides, and wondering what's the "boost" for and how to activate it and why it is in the same terminal with "Cruise"
blackheartxix said:Hello guys, I have Fardriver 841800 and 84530, Im taking a look at the pin guides, and wondering what's the "boost" for and how to activate it and why it is in the same terminal with "Cruise"
AdR said:I have a ND 96530. Do I need to have the 12V high brake hooked up to get regen braking, or can I get regen using the 5V low brake. Thx.
pwd said:AdR said:I have a ND 96530. Do I need to have the 12V high brake hooked up to get regen braking, or can I get regen using the 5V low brake. Thx.
You can get regen braking working with low brake.
ebike11 said:I have a new fardriver watercooled heatsink if anyone is interested
marsrover said:Well, I've got mine working somewhat. However there's a few issues people should really know about before buying one of these. Issues that would have made me buy something else.
1. Temperature sensor support. There are only presets, PTC, NTC230K, KTY84-130, Cacu?. If you have any of these sensors, good job things will be fine for you. I however use the KTY83-122 as that is the one that QS is using on nearly every single motor at the moment. A good controller would allow you to set an offset value so that any temp sensor could be used. But not fardriver. And to rub salt in the wound the most current android app 2.1.0 has kty83-122, kty84-122, and ntc100k as options, however selecting them does absolutely nothing.
So I email support. They told me to select "0- none" for temp sensor. A quick way to burn up a $1500 motor for sure. Can't have a problem with a feature if you just disable the feature![]()
2. Regen. As I use a hub motor it's important regen can smoothly work down to about 20 rpm. My previous controller allowed you to select the RPM regen would disable so you can still waddle or push your bike without it engaging. Well fardriver decided 100rpm was a suitable speed to instantly stop regen and no you can't change that value. For me that means good strong braking till 9mph then instant coasting. Very lurching experience, and unsettling as at lower speeds you don't know if grabbing the brake will make regen activate or you've got to grab more to get mechanical brakes going.
So I email support about this too. They tell me to turn off regen entirely. Can't have a problem with a feature if you just disable the feature![]()
3. Voltage cutoffs. Despite how the app may appear, many values can NOT be changed. High voltage cutoff is one of them. This is important as regen shouldn't happen on a full battery, if the user is using a BMS and high cell cuttoff get's triggered. Well that's a quick way to spike voltage in the controller and fry something. RIP sabvoton 96120 #1.
Ok fine, so maybe low voltage cutoff can be changed? Yes, but only the cutoff value, the recover (turn back on) voltage is fixed. Depending on your battery voltage this could pose a problem. Many values in the app are like this, if the app only showed what values could actually be changed. No-one would buy this.
I would email support, but I suspect I know what the answer to this one would be.
4. App differences. Version 1.3.7 found on the siaecosys website has values such as "temperature Coeff" that I can only assume adjusts the temp sensor calibration (but it's just displayed, you can't modify it). This has been since removed. MOE protection can be changed in 1.3.7 and 2.0.9, however 2.1.0 now says I need to "please use new BLE Module". Only there is no new ble module, and this is hardcoded and appears even when not connected to the controller.
Speaking of 2.0.9, on September 1st 2021 the app broke for literally everyone and gave a message "app expired, please download latest app". It sounds crazy but changing the date on your phone made it work again. So this is once again some hardcoded stuff that makes the app worse. And makes me worry that future versions of the app will continue to take away features. What happens if we don't get an update? Well I changed the date on my phone and found out.
On January 1st 2023 app version 2.1.0 is also going to "expire". Nanjang if you are reading this, changing the date to further out is NOT the solution. Remove the date check entirely, there is literally 0 reason for it to be there. Other than disabling the modification of "MOE protection" value. I see 0 changes to the app besides the date check being pushed further out.
This means between june 2021 (version 2.0.9) and september 2021 (version 2.1.0) there were ZERO improvements or tweaks to the app. I can only assume development has stopped and the lack of features I've complained about in this post will never be addressed. Consider this controller abandoned, but still in production.
Bottom line is this motor driver moves my motorcycle forward, it's got lots of power, and does control the motor well (except super low speed tourqe, kinda lacking there, assuming I need more tune time). The handling of every other basic feature such as regen and voltage cutoff values is absolute dogwater and nanjang should be ashamed of themselves for releasing such a half baked app while claiming the controller has features it just doesn't. If I could time travel back to last month when I bought this, I would slap myself and get a 3shul proper VESC based controller. At least then I'd know the vesc experience is properly feature filled, and has developers that actually respond to customer feedback.
4/10, would not buy again.