Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Scorpius fuel algorithm upgraded
#1

Hi Guys,
    Up until now there’s been 3 ways slot car systems work out fuel consumption.
1. Time or laps. Very primitive and not very realistic.

2. Throttle position. Does not take into account sensitivity knobs on the controller. Trigger lag, sometimes you move 5mm or more before the car even starts to move. Doesn’t take into account the motors natural throttle map ie the motors power map is probably not linear.

3. PWM. This is the pulse wave modulation signal (0-255) given to the car decoder to execute after all previous manipulations have taken place. ie sims, throttle limiting and throttle mapping. However you could run any motor and the system wouldn’t know the difference. So the PWM method is the best we have but can we do better?

4. Current detection. At the end of the day the car uses real energy, in this case electricity. Why not use this data to calculate fuel usage?
But how to calculate it and how to gather the information required to process the algorithm?
Because we have a purpose made current sensing resistor in the circuit of the new MPD, we can calculate fuel 100 times a second based on how much energy the motor actually  uses, nothing else matters. So if you’re using big motors or are heavy handed you will use more fuel and therefore will have to pit and have a longer refuel time.
So there you have it. Virtual fuel based on real energy consumption . 
Another world first by Team Scorpius. Cool
[attachment=33165]
[+] 2 members Like ScorpiusWireless's post
Quote
#2

Motor power used is the only logical way.

Life is like a box of Slot cars... Cool Drinkingcheers
Quote
#3
Wink 

It is. It’s a no brainer. Ive only seen one non logical argument against the concept. It’s simply based on the reality of 1:1 which has always been the basis of Scorpius design philosophy. If they don’t like this concept then they don’t get 1:1 reality. Bigger motors or an over active trigger style will require more refuelling. The majority get it. Oh and yes you need the hardware put in place to measure current draw. On top of that a competent firmware engineer, which we know are rare in this industry.
That’s only going to happen for Scorpius users, and hence the anxiety. 
Variation of electric motors is a reality however so small. The fact one motor is slightly faster than another, well hello that’s 1:1 too. 
And that motor will burn more fuel and justifiably so. If a team or individual wants to select motors based on current draw, ie less current draw to save pit stops then it will be a faster motor. There’s your 1:1 reality punch again. 
Anyone wanting the PWM method (currently only Scorpius can do this anyway so we have all bases covered) over the current draw method doesn’t realise a slower motor needs more pwm to keep up  which in turn will end up using the same amount of fuel anyway.
So the counter argument is illogical. 
In any case we will have both methods available which will be the benchmark.  Wrench

Rick

www.scorpiuswireless.com
[+] 2 members Like ScorpiusWireless's post
Quote
#4

Furthermore it’s not uncommon for a competitive individual or team test 5-10 motors for speed and use the best one. Will the same people go through 10 motors to get the slowest one in order to use less fuel? Well it’s possible but unlikely. People will take speed over fuel any day.
And in both scenarios that’s up to the end user. And if someone is willing to go the trouble and expense and get a better result good for them. That’s the nature of competition. Isn’t it? 
The obvious thing missed with PWM advocates is apparently you will be able to use a bigger motor if allowed  ie more RPM and not be penalised in any way in regards to fuel consumption. That’s totally illogical.
In any case Scorpius will be the only wireless system will fuel anyway  Cool

www.scorpiuswireless.com
[+] 1 member Likes ScorpiusWireless's post
Quote
#5

I'm sure A Gillespie will concur ??
Quote


Possibly Related Threads...
Thread / Author Replies Views Last Post

Forum Jump:


Users browsing this thread: 1 Guest(s)