Nucular electronics - complete kit for ev!

j bjork said:
:shock:
Can you run 200pA on a 6fet?
I thought that would be 125pA max as a 12f is 250pA and a 24f 500pA
Oops, I meant 12Fet...the LMX64 has the 12f. So I should be safe up to 250A, sounds about what I would have expected.

Can the turtle icon mean that I'm hitting my batteries LVC?

Cheers
 
VasiliSk said:
Your battery was at low voltage for some time, power was limited

ps. welcome to a turtle club
Ok that makes sense.

Yeah my battery is only 14S5P Sanyo GA's, so drawing 50A is right at it's limit and it doesn't like it.

Next time you should include a duck icon for me. :p

Cheers
 
Cowardlyduck said:
VasiliSk said:
Your battery was at low voltage for some time, power was limited

ps. welcome to a turtle club
Ok that makes sense.

Yeah my battery is only 14S5P Sanyo GA's, so drawing 50A is right at it's limit and it doesn't like it.

Next time you should include a duck icon for me. :p

Cheers
well said, there should be an intermediate set of animals gradually limiting the current until reaching the cursed turtle
squirrel>duck>ca so we won't get the turtled in the middle the highway. why not a cheeta for 100% SoC :bolt:
 
Got a while running the bike with the 24F but at this moment I can't ride the bike. The auto setup goes well but when I try to ride the bike under load it 's just hiks and somtimes runs fine but then again it won't. Put in 3 new sets Hall sensors but notting seems to work. Without load te motor runs fine but with load it just not runs smootly. What is wrong it did run 3 mounts without a issue. And now it won't.
 
When I do a autosetup the bike runs perfect and everthing is oke. But when the bike is with the rear wheel on the surface it starts hiking and is non drive. Who can help me this problems started out off nowhere, and I can't find a solution.
 
you should share your config file
 
It helped, a full reset and then a auto setup and the bike is running like before. You are my Hero. :wink:
 
Xtr6 said:
It helped, a full reset and then a auto setup and the bike is running like before. You are my Hero. :wink:

Glad you got it working :bigthumb:
Nucular very rarely fails. Robust controllers, usually just a matter of figuring out the set-up, firmware updates and settings
 
VasiliSk said:
ps. welcome to a turtle club
Latest firmware solved my issues with LR measurement on QS138 70H
QS138_70H.jpg

Vasili, since you are very familiar with QS138 70H, what extra settings do you recommend to make after auto setup + LR for best performance with Nuc24f?
 
I'm also interested in QS138 70H settings, so far it's the best controller I've had for throttle response.

Has anyone else noticed the controller temp on display reading ~10C low with the new firmware?
 
No, mine always indicates the correct temperature and here 10° is not the controller temperature.
 
JTR said:
Has anyone else noticed the controller temp on display reading ~10C low with the new firmware?
Mine is ~7-8C higher on all three QS motors I have.
 
JTR said:
I'm also interested in QS138 70H settings, so far it's the best controller I've had for throttle response.

Has anyone else noticed the controller temp on display reading ~10C low with the new firmware?

With older firmware 0.7.* (firmware the does not show the resistance value on the sensor menu) my motor temp and controller temp were identical. Since updating to 0.8.2 (or higher) the motor temp at resting is always around 10F higher / controller 10F colder. Using NTC 10K B:3950 temp probes in the motors. Again, resting temps were indentical as you can see in one of the pictures and then with newer 0.8.2 firmware the values are a bit off. I think once NTC motor probe gets up to operating temp, it becomes accurate due to the Beta value. The controller temp is accurate since the resting temp is closer to what the controller temps show.
 

Attachments

  • 20220615_152649.jpg
    20220615_152649.jpg
    1.7 MB · Views: 1,203
  • 20211102_204707.jpg
    20211102_204707.jpg
    1.9 MB · Views: 1,203
Thank you for all the hard work, appreciate the update. Stay safe.

Noticed a new feature, "Added out of control detection logic". Tested it, does not work. Wife nearly got me with the weed-whacker. The big one. Binford 6100, 2800 lashes per minute. Used the standard initiation phrase " Going with the guys to the casino for a few beers". Display remained exactly the same, no beeps, nothing. Just a fraction of a second away from the whole crimson mist-flying flesh thing. Needs a little tweaking.
 
Hi there. I just updated a controller to v0.8.7, it worked. After that, I want to update the display to v0.71b, but it takes ages, so my impression is that it's not working.

What's the usual amount of time for a successfull display update ? I already successfully dit it on another display, do not remember such a delay, so I can't figure out what's wrong. Any idea ?
 
Real-time update video.
From 4min 55 seconds for the LCD display.
[youtube]5Fj337qf7dY[/youtube]
 
Salut Pitmix

The usual method does not work, I have no clue about what happens
 
Super strange : it finally worked after formatting the sd card in an android phone instead of windows 10 / diskpart.
 
I hate to admit defeat, but I can't figure out how to enact the v0.8.7 new feature "Added configuration import with button".

When I look at Button configs there's nothing about "import config".
I've just updated to latest FW and although I've had my Nuc for a year or more I've only just got it setup in a bike, so I'm a newbie in terms of finding my way around in this thing.

I'm hoping to be able to hit a button and select a different config file to load.

Thanks.
 
VasiliSk said:
You can setup port to CL1..5 to 'Config Load 1'

Thanks Vasili.
Unfortunately I don't understand your shorthand.
When you say Port, what do you mean?
And CL means what?

I see Hot key 1-4, IO 1-8 and CAN 1-16. But no "Port" and no "CL".

Feeling a bit dumb here. :oops:
 
Back
Top