[noeryan]

Tango Charlie: Thanks for the encouragement! I'm needing it right now.

Its turning into something crazy... Since the throttle is variable, there are countless possibilities for the throttle position at each section...

On the UP side, I ran the GPS for a while and it actually found the proper altitude!!! It might have just been grumpy the night I was testing it earlier. It did quite well, got within a few feet... Maybe it just needed to get a few good satellites to triangulate? I'm not a GPS wizz. I do know it takes it a few minutes to get its altitude bearings.

I'm thinking to fix the throttle position problem, I'm going to need to fix either throttle on or throttle off for now and get it working.

Here is situation:

Engine Force is getting looped for the first section from 100 through 9000 Newtons in increments of 100 Newtons. The different forces are getting put into the diff eqs and velocities are being calculated at the end of each section which are then being filtered through the following:

Velocity must be greater than 0 and less than Speed Limit (whatever you choose)

Sometimes with the given force it never makes it the distance of the section of route so that number gets thrown out as well. (thrown out means = 0)

So this gives me a window of forces that are usable for that section which I set into a matrix... example:

EF = [0, 0, 0, 400, 500, 600, 0, 0, 0] means that the first 100, 200, and 300 Newtons wouldn't make the trip, also 700, 800, and 900 Newtons made the vehicle travel too fast.
Also saved are the Velocities which would look like V = [0, 0, 0, 2.3, 4, 7, 0, 0, 0] (zeros are again just place holders).

That was the easy part!

Now, working on section 2, we can't use an initial velocity of 0 because we aren't going 0. So we use one of the possible velocities we could be going which are [2.3, 4, or 7]. So we would want to pick 2.3 for the first one and use it to calculate our data for section 2... record this data somewhere and find the possible EF's that keep the V between 0 and Speed Limit so that means for each V from section 1, I have a spread of V's for section two... its a pyramid effect. That is a pain in the butt to code. PLUS, after doing all of those calculations only a few sequences of EF's will be eligible to satisfy the section of the route to be calculated to find the minimum EF for the section.

Is that understandable? I'm sorry I'm not very good at explaining the problem. The MATLAB code is not uploadable! Any ideas?

PLEASE HELP WITH THE LOGIC OF THIS PROCESS!

** MATLAB file extension: .m file **