Go to Post Programmer says autonomous will work 100% perfectly...Great way to clear the room of all mechanicals and all but the boldest electricals - EricH [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 12-08-2015, 18:29
jojoguy10's Avatar
jojoguy10 jojoguy10 is offline
Programming/Controls Mentor
AKA: Joe Kelly
FRC #0997 (Spartan Robotics) and FRC #2990 (Hotwire Robotics)
Team Role: Mentor
 
Join Date: Jan 2013
Rookie Year: 2010
Location: Corvallis, OR
Posts: 298
jojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant future
Estimated Drive Time in Dashboard

Hey CD,

Ha anyone ever tried putting an "Estimated Drive Time" in the dashboard? I think it would be cool to use at competitions to know how long the battery *should* last.

Joe Kelly
__________________

2013 and 2014 - Student (FRC#2990), Programmer (LabVIEW)
2015 and 2016 - Mentor (FRC#2990), Programming (LabVIEW)
2017-Current - Mentor (FRC#997), Controls/Programming (Java)
2015-Current - A/V Volunteer at Oregon events
  #2   Spotlight this post!  
Unread 13-08-2015, 10:13
TheHolyHades1 TheHolyHades1 is offline
Registered User
no team
 
Join Date: Jan 2014
Rookie Year: 2010
Location: usa
Posts: 145
TheHolyHades1 is a jewel in the roughTheHolyHades1 is a jewel in the roughTheHolyHades1 is a jewel in the rough
Re: Estimated Drive Time in Dashboard

I'm not sure the calculation would be a simple one, or even possible beyond very rough guesses. The problem is that depending on the way the match is played, your current draw can vary significantly, thus affecting battery life.

For example, I inadvertently left a robot idling overnight and it was still on, but the battery was down to about 6V. This was almost a 10 hour period. I would hazard a guess and say that the immediate battery voltage reading is "good enough."
  #3   Spotlight this post!  
Unread 13-08-2015, 19:47
jojoguy10's Avatar
jojoguy10 jojoguy10 is offline
Programming/Controls Mentor
AKA: Joe Kelly
FRC #0997 (Spartan Robotics) and FRC #2990 (Hotwire Robotics)
Team Role: Mentor
 
Join Date: Jan 2013
Rookie Year: 2010
Location: Corvallis, OR
Posts: 298
jojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant future
Re: Estimated Drive Time in Dashboard

Thanks for your reply!

I didn't expect it to be easy :-)

I'm hoping to maybe use this on Summer robots when we don't really have a "replace per match" basis.

Just an idea.
__________________

2013 and 2014 - Student (FRC#2990), Programmer (LabVIEW)
2015 and 2016 - Mentor (FRC#2990), Programming (LabVIEW)
2017-Current - Mentor (FRC#997), Controls/Programming (Java)
2015-Current - A/V Volunteer at Oregon events
  #4   Spotlight this post!  
Unread 13-08-2015, 21:24
thatprogrammer's Avatar
thatprogrammer thatprogrammer is offline
Registered User
AKA: Ahad Bawany
no team (None)
Team Role: Programmer
 
Join Date: Apr 2014
Rookie Year: 2014
Location: Florida
Posts: 610
thatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond reputethatprogrammer has a reputation beyond repute
Re: Estimated Drive Time in Dashboard

You could set a time that only runs when the joystick to move the robot is moved beyond a certain point (0.1?), and when buttons for mechanisms are held. If your mechanisms are somewhat autonomous, you could set the timer to count when the motor controllers for these objects are set to .1 or higher.
Note: You can count the amount of times a piston is used and use a seperate timer for when the compressor runs.

Last edited by thatprogrammer : 13-08-2015 at 21:25. Reason: Thought about pneumatics.
  #5   Spotlight this post!  
Unread 13-08-2015, 21:59
timytamy's Avatar
timytamy timytamy is offline
Registered User
AKA: Tim
FRC #3132 (The Thunder Down Under)
Team Role: Electrical
 
Join Date: Nov 2009
Rookie Year: 2010
Location: Australia
Posts: 293
timytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant future
Re: Estimated Drive Time in Dashboard

I've been very interested in using the current monitoring capabilities of the PDP, combined with the voltage readings and some sort of model of a SLA battery to achieve something along those lines.

There are all sorts of non-linear properties to batteries, not to mention each battery will be different, but I think it could be interesting to see how close one could get to an accurate prediciction given just the KoP electronics.
__________________
Tim W
FIRST® Team 3132 - The Thunder Down Under
Sydney, Australia
Website | Facebook | Youtube
  #6   Spotlight this post!  
Unread 14-08-2015, 19:56
TheHolyHades1 TheHolyHades1 is offline
Registered User
no team
 
Join Date: Jan 2014
Rookie Year: 2010
Location: usa
Posts: 145
TheHolyHades1 is a jewel in the roughTheHolyHades1 is a jewel in the roughTheHolyHades1 is a jewel in the rough
Re: Estimated Drive Time in Dashboard

Quote:
Originally Posted by timytamy View Post
I've been very interested in using the current monitoring capabilities of the PDP, combined with the voltage readings and some sort of model of a SLA battery to achieve something along those lines.

There are all sorts of non-linear properties to batteries, not to mention each battery will be different, but I think it could be interesting to see how close one could get to an accurate prediciction given just the KoP electronics.
You might be able to simplify everything and just assume that batteries plugged in when the robot is turned on are at full charge, and then just use the current monitoring to figure out remaining charge, and apply some sort of derivative to extrapolate the remaining drive time. That might work well enough for a first guess, at least?
  #7   Spotlight this post!  
Unread 15-08-2015, 10:01
BenGuy's Avatar
BenGuy BenGuy is offline
Co-Driver - 3641 - Flying Toasters
AKA: Ben
FRC #3641 (The Flying Toasters)
Team Role: Operator
 
Join Date: May 2014
Rookie Year: 2014
Location: South Lyon, Michigan
Posts: 219
BenGuy is a glorious beacon of lightBenGuy is a glorious beacon of lightBenGuy is a glorious beacon of lightBenGuy is a glorious beacon of lightBenGuy is a glorious beacon of lightBenGuy is a glorious beacon of light
Re: Estimated Drive Time in Dashboard

Quote:
Originally Posted by TheHolyHades1 View Post
I'm not sure the calculation would be a simple one, or even possible beyond very rough guesses. The problem is that depending on the way the match is played, your current draw can vary significantly, thus affecting battery life.

For example, I inadvertently left a robot idling overnight and it was still on, but the battery was down to about 6V. This was almost a 10 hour period. I would hazard a guess and say that the immediate battery voltage reading is "good enough."
Like a car guesses how many miles until empty, that value could be dependent on the current rate of discharge that is constantly re-averaging itself as it continuously takes in more data, then the average and all data is wiped clean when robot is restarted - Just like a car.
__________________



Ben Wolak
The Flying Toasters Website

Team YouTube
Team Twitter

The real problem with computers is that they do what you tell them to do, not what you want them to do.
  #8   Spotlight this post!  
Unread 15-08-2015, 10:52
jojoguy10's Avatar
jojoguy10 jojoguy10 is offline
Programming/Controls Mentor
AKA: Joe Kelly
FRC #0997 (Spartan Robotics) and FRC #2990 (Hotwire Robotics)
Team Role: Mentor
 
Join Date: Jan 2013
Rookie Year: 2010
Location: Corvallis, OR
Posts: 298
jojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant futurejojoguy10 has a brilliant future
Re: Estimated Drive Time in Dashboard

Great ideas! I'll have to look into them for this upcoming season!

Thanks!

P.S. I wonder if it's possible to check the current with the old cRIO system. I knw you can through the CAN network on the Jaguars. Is there a good way to basically add all of the current and use that as "total" amperage?
__________________

2013 and 2014 - Student (FRC#2990), Programmer (LabVIEW)
2015 and 2016 - Mentor (FRC#2990), Programming (LabVIEW)
2017-Current - Mentor (FRC#997), Controls/Programming (Java)
2015-Current - A/V Volunteer at Oregon events
  #9   Spotlight this post!  
Unread 15-08-2015, 13:51
TheHolyHades1 TheHolyHades1 is offline
Registered User
no team
 
Join Date: Jan 2014
Rookie Year: 2010
Location: usa
Posts: 145
TheHolyHades1 is a jewel in the roughTheHolyHades1 is a jewel in the roughTheHolyHades1 is a jewel in the rough
Re: Estimated Drive Time in Dashboard

Quote:
Originally Posted by BenGuy View Post
Like a car guesses how many miles until empty, that value could be dependent on the current rate of discharge that is constantly re-averaging itself as it continuously takes in more data, then the average and all data is wiped clean when robot is restarted - Just like a car.
Well, I suggested using a full charge because apparently there's non-linearity associated with the battery voltage (unlike gasoline, I'm assuming). That said, as suggested above, a simple model of an SLA battery might do the trick.
  #10   Spotlight this post!  
Unread 15-08-2015, 13:53
TheHolyHades1 TheHolyHades1 is offline
Registered User
no team
 
Join Date: Jan 2014
Rookie Year: 2010
Location: usa
Posts: 145
TheHolyHades1 is a jewel in the roughTheHolyHades1 is a jewel in the roughTheHolyHades1 is a jewel in the rough
Re: Estimated Drive Time in Dashboard

Quote:
Originally Posted by jojoguy10 View Post
Great ideas! I'll have to look into them for this upcoming season!

Thanks!

P.S. I wonder if it's possible to check the current with the old cRIO system. I knw you can through the CAN network on the Jaguars. Is there a good way to basically add all of the current and use that as "total" amperage?
You can also get the current running through each individual TalonSRX via CAN. I think the new PDB also communicates the current back through CAN, so it might be possible to just use the new PDB along with the old cRIO and get all of the current monitoring through CAN, either via the motor controller or the PDB itself?
Closed Thread


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

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

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 03:15.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi