RC-Monster Forums  

Go Back   RC-Monster Forums > Support Forums > Brushless

 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
Old
  (#31)
ReV:-O
RC-Monster Carbon Fibre
 
Offline
Posts: 333
Join Date: Aug 2008
01.01.2009, 11:00 AM

hi guys

just got back from day 2 of running, and this time my results seem more normal. runtime was about 30 minutes, which is still very good for two 5000mah packs.
MMM was warm, but the motor was hot. i have a handheld temp gauge but it was difficult to take readings with the body on, but i did my best. it was 120F, so i know i have not damaged anything. would it be better to get one of those on-board loop temp gauges by traxxas that i can just wrap round the motor? do those work well?
top speed was around 45-50mph with 22/65 gearing.

heres the thing im concerned about. This time, i ran the truck till the LVC cut in. The MMM stops the trottle when i try to accelerate, so i figured this was the LVC. no sounds or lights or anything, just throttle interuption.
anyway, so i stop running and hook my lipos up to my hyperion. i have the custom LVC set to 19.2v, thats 3.2v per cell just to be safe. I look at the first lipo, and sure enough each cell is about 3.2-3.3v. all is good. i look at the second lipo, and two of the cells are 3.2v, but one of them is 3.0v?? whats up with that? Technically the MMM LVC should have cut in sooner because the overall pack voltage would have been lower than what i programed it to cut off at. I am a little concerned now... not too concerned though. 3.0v is still ok right?

What i think i'll do now is charge both lipos up to 60% because i wont be driving it for a few days.
   
Reply With Quote
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On

Forum Jump







Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
vBulletin Skin developed by: vBStyles.com