Nanjing far driver controllers

amberwolf said:
GumbaLL said:
hi all,
is there a standalone RPM display for Far Driver, other than the blue booth one? (dont want to turn on the app/ use bluetooth all the time)
Cant seem to find a display for e-motorbike to show RPM for that matter either ..
TX

RPM, or road speed?

If RPM, do you mean wheel RPM, motor RPM, etc?

There's various ways to get and display various data, once we know what you need to measure.

For curiosity: If RPM, why do you need that data? (meaning, what use is it to you?)

Hi Amberwolf,
I mean RPM at the motor, just like how the bluetooth one displays it but would be nice to have a dedicated one without needing to hook up the phone all the time.
its just a nice to have i suppose. like with cars, i get accustomed to know RPM at the motor at what speed im at.
 
Then you could use something like this:
https://www.amazon.com/Digital-Display-Tachometer-Inductive-Proximity/dp/B078N2VN75
though which sensor you could use might vary depending on the motor design and placement.

There's a bunch of these kinds of things in different styles and with different kinds of sensors; that's just the first google hit on
https://www.google.com/search?q=rpm+sensor+and+display
another possible search is
https://www.google.com/search?q=tach+sensor+and+display
or
https://www.google.com/search?q=tachometer+sensor+and+display
 
Hi, I have a fardriver 961800 and im thinking of using it with a 28s battery. Has anybody tried this? Or I should stick with 26s?
 
On page 25 in the manual they claim 28s "ternary lithium battery" (before that is lead acid, after comes Lithium iron phosphate battery)

From what I heard 121,5v is where it trips for overvoltage, I sure hope that is correct as I plan to use one on 30s when I couldent get a 1081800
 
AMP ADRENALINE said:
I have a ND 721200B Far driver that is using an Encoder type sensor. NJD Y2915 to be specific.
The wiring harness is different from the Fardrivers I have seen here. I attached some photo's.
The wiring diagram is a little vague at best. I have been waiting for a response for the factory to
make a wiring diagram of the entire wiring harness but no response yet. We don't want to make
a wrong connection and burn up the controller.

So I have a couple questions to be sure, try to get this working sooner than later..
The contactor has a L- wire. What does this stand for? Contactors we use have a 12v coil and the two main contacts.
If we run the ignition wire to turn it on, that's 72vdc thru the contactor. Not sure that is right.

The throttle has it' s 5v/ signal out and it's own ground. Forward/ Reverse/ Low brake and High brake don't. I want to
assume these go thru a switch and then to Battery Ground. Is this the case? Some other controllers have a separate ground
for these type accessories. That for any help. FYI. This is going on a Custom Mid Motor setup not a Hub motor.

Thanks for all this very valuable information, these documents will help me a lot. :bigthumb: :bigthumb: :bigthumb:
 
j bjork said:
On page 25 in the manual they claim 28s "ternary lithium battery" (before that is lead acid, after comes Lithium iron phosphate battery)

From what I heard 121,5v is where it trips for overvoltage, I sure hope that is correct as I plan to use one on 30s when I couldent get a 1081800

But 30s would be way over 121.5v
 
eee291 said:
The battery has to be under 115V when fully charged, you may also have trouble with regen.

Thats what the spec sheet says but that could also be just so consumers dont go overboard
 
rivvs said:
Hi, I have a fardriver 961800 and im thinking of using it with a 28s battery. Has anybody tried this? Or I should stick with 26s?

Hi have you tried 28s with the controller yet?
 
ebike11 said:
eee291 said:
The battery has to be under 115V when fully charged, you may also have trouble with regen.

Thats what the spec sheet says but that could also be just so consumers dont go overboard

My Fardriver controller (ND96850) stops working over 121.5V and shows an error. I tried this with a regulated power supply.
As this is only a software limit , it could be that the parts inside the controller can do a little bit more. My controller stopped working bevore at around 90V as it told me it was a ND72850, after flashing the right firmware it has the limit now set to 121.5V.
It could also be that they build only one version and limit the max volts with the firmware, but who nows.

But I killed two 90V rated Sabvotons (72150 and 72260) with a 21S battery, using flux weakening and regenerative braking.
If you want to use flux weakening than you should have a few volts more left to the (real) limit.
My two dead Sabvotons had cost me more than the Fardriver ND96850. :wink:
 
dominik h said:
ebike11 said:
eee291 said:
The battery has to be under 115V when fully charged, you may also have trouble with regen.

Thats what the spec sheet says but that could also be just so consumers dont go overboard

My Fardriver controller (ND96850) stops working over 121.5V and shows an error. I tried this with a regulated power supply.
As this is only a software limit , it could be that the parts inside the controller can do a little bit more. My controller stopped working bevore at around 90V as it told me it was a ND72850, after flashing the right firmware it has the limit now set to 121.5V.
It could also be that they build only one version and limit the max volts with the firmware, but who nows.

But I killed two 90V rated Sabvotons (72150 and 72260) with a 21S battery, using flux weakening and regenerative braking.
If you want to use flux weakening than you should have a few volts more left to the (real) limit.
My two dead Sabvotons had cost me more than the Fardriver ND96850. :wink:

At least you get an error message for overvoltage and not instant smoke if you happen to overvolt
 
AMP ADRENALINE said:
I have a ND 721200B Far driver that is using an Encoder type sensor. NJD Y2915 to be specific.
The wiring harness is different from the Fardrivers I have seen here. I attached some photo's.
The wiring diagram is a little vague at best. I have been waiting for a response for the factory to
make a wiring diagram of the entire wiring harness but no response yet. We don't want to make
a wrong connection and burn up the controller.

Would you, by any chance, have a picture of the other side of your sensor?
I've got myself a sensor for the ME1507, which looks very similar aside from the PCB shape and connector positioning. Unfortunately I cannot find any kind of documentation and I really don't want to mess anything up because it was already very difficult to get the sensor in the first place...

Basically I'm trying to determine the pinout in order to make myself a cable, but the PCBA has no markings to indicate what's what.... :cry:
Is there any way for you to tell me which pin is going where? Would be amazing, thanks in advance for your help!

Here is the version I got, I tried to find the datasheets for these components but no success:
6b472bcb26c34f16b759637573db2b6f.jpg
 
rivvs said:
Hi, I have a fardriver 961800 and im thinking of using it with a 28s battery. Has anybody tried this? Or I should stick with 26s?

I have a 96530 that I run on 28s. Anyone know how I can increase the strength of the regen? Is it StopBackCurrent and MaxBackCurrent?
 
LCLabs said:
I have a 96530 that I run on 28s. Anyone know how I can increase the strength of the regen? Is it StopBackCurrent and MaxBackCurrent?

I'd be curious myself as I only get maybe 25 - 35A regen at most and is for sure not as strong as my old Kelly KEB in regen.
 
Scottydog said:
LCLabs said:
I have a 96530 that I run on 28s. Anyone know how I can increase the strength of the regen? Is it StopBackCurrent and MaxBackCurrent?

I'd be curious myself as I only get maybe 25 - 35A regen at most and is for sure not as strong as my old Kelly KEB in regen.

I bumped mine from 4 and 6 (StopBackCurrent and MaxBackCurrent) to 10 and 14 and felt a difference. Is yours set to 25? The FarDriver regen feels more aggressive than my Sabvotron.
 
LCLabs said:
I bumped mine from 4 and 6 (StopBackCurrent and MaxBackCurrent) to 10 and 14 and felt a difference. Is yours set to 25? The FarDriver regen feels more aggressive than my Sabvotron.

I have mine at something like 40 and 50 but only get maybe 30A in use. On the stand if I rev to full speed I can see the difference, but not when riding. I think these regen changes make more difference when the motor is spinning near to it's top rpms.
 
MMD said:
So I tried the Fardriver on my ktm where normally the Votol sits. This is the worst controller I every used in my life! The throttle delay is ridiculously dangerous!! When releasing the throttle the rpm keeps rising for about 0.5/1sec until it drops down.

I just got a 841800 and experienced the same problem. I happen to know people who work directly with the factory and they told me this is a firmware issue, there's a bug in the firmware. So this has nothing to do with any parameter you've set up, you've basically done nothing wrong, and no version of the app will fix that (well at least none does as of today).
I've been told that the only solution is to send it back to the factory for reprogramming, but I've also been told that they probably won't do it since they don't care about DIYers at all. Great.

The only hope I still have is that the seller (which was not the factory), told me that I can try to flash a different version of the firmware. I hope it won't brick the controller and that this will solve the issue. I will report here after I try, so wish me good luck...

Meanwhile I cannot recommend people to use this product anymore, so I will edit my post in the first page. The product itself is great when it works, but the documentation is horrible, the app is not reliable, the firmware seems buggy in a dangerous way and worst of all we don't get any kind of support by the factory.
It's getting harder and harder to find decent controllers, I don't understand why we should go through these kind of hassles, what a pain.
 
If someone could get them to release their code as open-source, I'd guess some of the remarkable people around here could fix it, then the company itself could still make plenty of money selling their hardware, in fact even more than they do now, because users could use the OSFW version instead of whatever "broken" factory version it ships with. ;)

I realize it will never happen...but it would certainly fix the problem.
 
Dui said:
MMD said:
So I tried the Fardriver on my ktm where normally the Votol sits. This is the worst controller I every used in my life! The throttle delay is ridiculously dangerous!! When releasing the throttle the rpm keeps rising for about 0.5/1sec until it drops down.

I just got a 841800 and experienced the same problem. I happen to know people who work directly with the factory and they told me this is a firmware issue, there's a bug in the firmware. So this has nothing to do with any parameter you've set up, you've basically done nothing wrong, and no version of the app will fix that (well at least none does as of today).
I've been told that the only solution is to send it back to the factory for reprogramming, but I've also been told that they probably won't do it since they don't care about DIYers at all. Great.

The only hope I still have is that the seller (which was not the factory), told me that I can try to flash a different version of the firmware. I hope it won't brick the controller and that this will solve the issue. I will report here after I try, so wish me good luck...

Meanwhile I cannot recommend people to use this product anymore, so I will edit my post in the first page. The product itself is great when it works, but the documentation is horrible, the app is not reliable, the firmware seems buggy in a dangerous way and worst of all we don't get any kind of support by the factory.
It's getting harder and harder to find decent controllers, I don't understand why we should go through these kind of hassles, what a pain.

Same thing here, I have tried a lot but havent been able to get any decent throttle control.
Im copying some of the text from my most recent test in my yamaha thread here:
I have been out again trying to tune the throttle behavior, I havent been very successful..
It is a disaster, the throttle behaves like a rubber band. The softer you set it, the worse the backlash.

The only almost rideable setting I have found is sport, throttle rate 224, ECO Coeff 8. (the most aggressive setting possible)
Then the throttle is super twitchy, you cant really walk with the bike and just hold a little throttle to not have to push.
It will move from off to a little wheel spin on gravel. But when up to some speed it is relatively responsive with not too bad backlash. (Meaning not still pulling very much after throttle release)

The ECO Coeff seems totally useless, anything other than 8 is totally powerless. At least when you are in sport mode (I didnt try in other modes)

I tried ECO throttle also, it is very smooth from a stand still. But then if you twist the throttle a bit more you will have crazy rubberband effect, a big wheelie that keeps rising after throttle release :shock:

I tried messing with the "Release throttle" setting again, still I am not sure if it does anything. 7 for sure was not better than 0..
I also tried the speed Ki/Kp settings, not sure if there was any difference.

The regen at throttle release helps, but if I use that the throttle dosent always react afterwards :eek:
How do you know what firmware's are good and what are bad?

Edit, here is what it says on mine:

nKXt5as.jpg
 
j bjork said:
How do you know what firmware's are good and what are bad?

Absolutely no idea, sorry. :|
I'm currently discussing with the seller of the controller, which in turns discusses with the factory. Hopefully they will find a solution...
Yesterday the seller sent me a .hex file, which I believe was a new firmware. But since his answers to my questions were a bit too vague for my taste I did not try to flash it (in fear it would brick the controller) and asked him to confirm with the factory one more time today after re explaining him the issue as best as I could. I really hope he got it and he'll be able to explain it to the factory so they send me a corrected version...

I won't lie, I have very little hope at this point. I do know some people who managed to fix the issue by having it reflashed so I know for sure this is doable, but I'm not sure it is doable in my case since I'm just a DIYer, not someone who has a company with nice forecasted sales volumes.
Anyway, let's hope it'll be fixed this evening...
 
j bjork said:
Do you know if the throttle release setting has any effect on the ok (or your) firmware?
It dosent seem to do anything on mine.
I am in contact with siaecosystems too now, I will see what they say.

Nope, it did nothing on my controller, at least nothing really noticeable to fix the issue. I tried every possible thing, none worked.

Today, a good news and a bad news:
-Good news is that the .hex file they sent me did fix the throttle lag issue, now the controller behaves just like any normal controller, no weirdness anymore! Great!
-Bad news is that this update somehow made the bluetooth unresponsive. I can connect to the bluetooth module, but then it doesn't manage to communicate with the controller, so basically I can't change any setting.... Tried to reinstall the app several times, tried different versions of the app on different phones... Same result.
I don't know who does the firmware at Nanjing Fardriver factory but he needs to step up his game a notch, it's getting annoying now.

So, now we are sure that the problem lies in the firmware, there's no fiddling around with the settings in the app that can solve the throttle lag issue, at least as of today (maybe they'll release an app that will allow to set the throttle lag by ourselves someday, who knows, but right now it's not possible).
So anyone having this issue, the only fix you could hope for is for a new, stable firmware to be released.

I can't share the firmware they sent me to you guys just yet because it is clearly not stable, but I will if I get one that works. That being said, I'm not sure that flashing a random firmware made for me will work, it is possible that every firmware has to be matched with the controller serial number, I don't know.
 
Back
Top