Nanjing far driver controllers

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"

Im wondering this too haha
 
I’m having issues with my nd72530 controller when I brake and skid the back wheel. When the back wheel spins back up after braking I get an error. Anyone have a similar issue?
 
What error do you get? You can check with the Bluetooth mobile app or count the beeps? From there; you can look it up in the Fardriver manual.
 
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.
 
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.
 
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.

how to adjust the regen brake power it feels weak on my bike
 
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 :roll:

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 :roll:

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.


Fuk this shit man. Similar stuff here besides i cannot set proper pole pair either. All it allows for is 4 or some very high number like 26 for hubs. I'm disputing this shit and sending it back at sellers expense. Why the fk didnt i buy the fkin votol?
 
Can someone send me a proper setup for the 138 90H flux weakening regen and all for the 72(800)? I cant set pole pairs only 4 i cannot set the temp sensor for the 138 either. I can only try it with a small hub now for im waiting on the 138 but to be frank i dont wanna fiddle with this crap too much. I just wanna send it back and forget that i ever ordered this shit at this point. But if someone could send me a proper setup file who already gone through the muck and mire with this controller i'd appreciate it. Funny tho that i ordered it explicitly setup for the 138 and nothing is setup for it for obviously it cannot be setup.
 
I ran the auto learn with my nd72850 on a qs138v3 and it’s worked great after some tweaks.
 
I'm getting familiarized with this controller so maybe it's not just paperweight the temp sensor issue seems to be a problem but that can be solved i guess. However i still dont know what's true of this pole pair vs coil pair thing. Right now i only have a 46 magnet 51 coil hub to test it with no load so i set 23 pp the rpm seems to be ballpark alas i cant find the rpm meter to verify it. (However i seriously doubt that it would be coil pair for how do you set CP for a 51 slot motor...)

The controller seems to be fully functional but i'm having trouble with FW. I desperately need FW for the 138 at 72v otherwise my bike will be shit. I read the manual and this rpm conversion between hub and mid motor seems to be obsolete for as soon as i set high PP numbers the rpm values seem to adjust to lower hub values. So maybe that's just for the older versions... So it seems that i set fw values by assigning the current percentages to the different rpm levels. However at no load the motor doesnt seem to be able to surpass the base rpm no matter how i boost the high rpm value percentages but when it spins up and there is sufficient current it seems to be overspinning as it should. So it seems to me that FW only comes into effect on load and no load it always tapers back to base rpm (maybe for rotor protection purposes). Can someone confirm this? I cant really try this on load now and i'd need to know if this is a shitcontroller or a good controller for i'm running out of dispute time...
 
There is no explicit field weakening setting but how I understood it it is in the ratios in speed. I think that the % is the ratio to the max phaseamps and everywhere where it's above the max rpm without field weakening it's the field weakening amps. But be careful when testing and start with lower settings so you don't fry your motor.

All I had to do to get the motor running was an autosetup and tweak some settings, most importantly was disabling "Follow" under Functions.

At first the field weakening didn't work for me too because i was in mid speed and there was a max rpm set for it. I increased it and now it's working, even under no load
 
Thanx man you're a goddam genius. It was stuck in mid that's why it wasnt working. It field weax as charm now...i buy you a proverbial beer
 
However i still dont like this being stuck on 4 pole pair stuff i guess i'll have to differentiate for it and gotta make do with it showing 25% more rpm than reality...also the temp sensor stuff sux but it seems like a usable controller now...
 
That is strange that it doesn't allow for 5 pole pairs. I have the ND961800 with the QS180(that is a 4 pole) and out of curiosity I switched in the settings to 5 pole and it just stuttered, so I switched back to 4 pp.
Did you try other versions of the app?
 
No but i thought about using other apps. What do you mean by stutter? Did it accept 5pp? Mine just sets itself to 4 whatever i give it. At around 18 does it start to accept the value but up until 18pp anything i set it shows 4...

I just dont know where to get the other versions...

What about temp sensor? Does it accept 122kty?
 
https://youtu.be/Ghoutu9Sg70

https://youtu.be/HNDqLJDV5gE

This is the issue i'm facing except the burnt motor. No temp sensor no correct pp...(it's not my chan)
 
I'm starting to like this controller everything seems to work nicely and it's not so hard to understand. But this friggin pp issue...well PP only has an effect on the rev counter afaik so maybe i just have to divide all rpm data by 5/4...i surely wont run out of rpm because it seems to have ample rpm something like 9000 in the setup...and i want only 6k max on load...wherein it will show 7500...i mean i really hope it's like this...i wont jerk off too much to the rpm data anyway when i'm riding so who cares...but i'd defo jerk off to temp data but that can be solved by a proper kty i guess...
 
Meehh i cant change the overvoltage either...i guess the regen protect is tied to the overvoltage so how the fk am i supposed to set regen protect? Anyway i charge up a 20S now and see if this current 90v overvoltage is good for anything or not...i'm really feeling like sending this shit back again...The pp is not really a problem i tried it with 18pp setting which is 27% off from the current test motor i have and you can offset the rpm accordingly still plenty of rpm room to play with in the app so 25% off isnt really a problem.
 
There's other problems too i cannot set overvoltage nor motor temp data. The screenshot is from the old app and while the keyboard pops up when i click on them it can be seen that those data are different to the low volt protect that is black. So most likely those data in yellow couldnt be set in the old app either. The old app doesnt even connect to try it. Like what am i supposed to do not being able to set motor temp protect? The temp problem i could even swallow actually. But if overvolt sets the regen protect how do i set regen protect? It regens on my fully charged battery and there goes the controller...What a half baked controller.
 

Attachments

  • Screenshot_20221209-183432.jpg
    Screenshot_20221209-183432.jpg
    288.4 KB · Views: 172
Back
Top