|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: [FTC]: 0.0v on Ext Battery Problem
I believe that RobotC will not attempt to run the DC motors and servos if the battery voltage is too low.
How do you know the battery is charged? Have you checked it with a meter? At a practice session last fall, another team wanted to borrow a battery (or charger can't remember which) because theirs was not working. It showed full on the charger, but would not run the robot. It turned out the fuse was blown in the battery cable. I replaced their fuse and everything worked fine. |
|
#2
|
|||||
|
|||||
|
Re: [FTC]: 0.0v on Ext Battery Problem
i'll try it but im preety sure the battery we used was good and the fuse was good
|
|
#3
|
||||
|
||||
|
Re: [FTC]: 0.0v on Ext Battery Problem
We should verify that the motor and sensor setup in ROBOTC matches the wiring on the robot.
1. Please post a copy of your ROBOTC code. 2. Provide a description of how the motor and servo controllers are wired. For example. NXT Sensor Port 1 is connected to Motor Controller 1. Motor Controller 2 is connected to Motor Controller 1. Servo Controller 1 is connected to Motor Controller 2. |
|
#4
|
||||
|
||||
|
Re: [FTC]: 0.0v on Ext Battery Problem
Another thought. . . try replacing the cable between the NXT and the first controller.
|
|
#5
|
|||
|
|||
|
Re: [FTC]: 0.0v on Ext Battery Problem
I missed the post where you said the lights on the controllers were on (I am used to a mix of lighted and non-lighted controllers).
Micheal's suggestion to verify the connection between the brick and the first controller is good. I would expand that to include verifying that all data cables are connected properly (fully inserted and in the correct order). I would also double check that all the power wires between controllers are good also. It may help to put the robot up on blocks, command it to move and then wiggle all wires plugged into the controllers to verify that you don't have a loose connection. |
|
#6
|
|||||
|
|||||
|
Re: [FTC]: 0.0v on Ext Battery Problem
I will see because i don't know it that the problem because when the battery isn't plugged in it registers OFF when i plug a battery in it registers 0.0v so i think it's a code, firmware, config file, or Template problem because i remember seeing this problem before with RobotC 2.00.
|
|
#7
|
|||
|
|||
|
Re: [FTC]: 0.0v on Ext Battery Problem
There is a variable that contains the average battery voltage. If you are somehow overwriting that variable, this could be the cause. Have you tried running with an un-modified template?
|
|
#8
|
|||||
|
|||||
|
Re: [FTC]: 0.0v on Ext Battery Problem
must say i fixed it, i had the motor controller that had the batttery wired into it not plugged into the first port
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [FTC]: Bluetooth Problem with LabView/FTC Controller Station | James Dowd | FIRST Tech Challenge | 8 | 27-10-2009 10:40 |
| [FTC]: [FTC]: RobotC Template Problem (causing an FMS issue) and Potential Servo Prob | PackersFan | FIRST Tech Challenge | 11 | 26-01-2009 21:25 |
| [FTC]: [FTC]: Replacing Fuse for Battery | fqzeng | FIRST Tech Challenge | 4 | 18-11-2008 20:04 |
| [FTC]: First problem with FTC and LabView.....? | PhilBot | FIRST Tech Challenge | 5 | 07-11-2008 10:36 |
| [FTC]: FTC Servo-Motor Problem with Labview | dnhansen | FIRST Tech Challenge | 1 | 26-10-2008 00:43 |