pdf wrote:I think I understand what you are doing and I think this is a very important tool. It is a bit confusing to figure out what assumptions are made, what the fields represent, and where the output is found. I want to take a closer look at this but as a first pass, more documentation (which I understand is tedious) would be helpful.
pdf wrote:I am using MS Excel to open the file and can't see the equations so I don't know what some of the fields are. I have the following questions:
1) I am confused by the "time" column. Is this the time (in seconds) spent traversing an increment in distance at the predicted speed and power output? I think it must be because it does not accumulate. If so, then the route time is calculated by summing the incremental times. Is that correct?
2) Also, the "step" column is confusing. The units at the top of the column are given as "100m" and the first value is "0.1". Is this therefore 10 meters (0.1 100 meter units)? I am confused because the last "step" is "33.6" for the return trip and the total distance for the trip is 33.6 km. That would indicate the units are 1000m for a unit step (33.6 steps of 1000 meters each).
3) Is the distance the linear distance along the path or the distance along a horizontal reference axis, not accounting for vertical distance changes?
I would like to run a case with one of my setups (a 9C 2810 laced in a 26" wheel, Lyen 18FET controller, 72V LiPO) with very low but constant (that is, independent of grade) crank power input. The fact that I can't see equations in the fields, just values makes me think that I am not going to be able to do with with Excel. I have used Open Office, but don't have it currently. Should the spreadsheets be fully functional in Excel (if you know)? I think the answer is "no" based on the fact that I can't see the formulas (only values) in the cells.
Thanks. I have some suggestions
pdf wrote:I don't think people understand what is does yet.
pdf wrote: I think one way to add functionality would be to generate graphs of different variables as a function of distance, for example, speed vs distance, current versus distance, power vs distance... That way you could get a feel for what the performance would be like all along your route.
pdf wrote:I think this is a great tool and I understand exactly what you are doing. It allows people to size their batteries for a given route. It would also be nice to look at current as a function of time, to find the max. current draw to help size the controller.
pdf wrote:As I said, I think this is a great tool. I did download OpenOffice, again. I found it could be a bit buggy and I work with students, all of whom have Excel. I think people might be downloading this and opening it with Excel like I did. If so, it messes up the formatting and you can't find things. For example, the "Totals" table is far away from the rest of the data and most people haven't even seen it and that is where the most useful information is
amoras wrote:Actually is the other way around!
You must enter the current on Ebike.ca simulator to able to retrieve the motor data, so you already know the max current that the controller limits. That's why I believe a human effort analysis versus ebike cost+weight is the main goal to follow. You shouldn't design an Ebike to a max current, you must design an Ebike to a maximum effort you want to give, and only then you will find your maximum current.
pdf wrote:So why not just pick a controller with a high maximum on the Ebike simulator, run the route simulator and see what the actual maximum current is? Doesn't the current limit in the simulator just limit the power like this? "If current greater than max current, set current to max current." If so, then just pick the largest controller you can and see what the maximum required current on the route is.
Users browsing this forum: Bing [Bot] and 7 guests