Sorry if this has already been indicated, but I thought of another feature I'd like:TickTock said:I am in, of course. The features I am most interested in (in order of importance) are:
- 1) Access to all three canbus's (canbusi?) simultaneously
2) Ability to read individual cell-pair voltages
3) Tone proportional to brake_pressure*rpm (no tone below a certain threshold)4) Ability to log all three canbus's
- i) nice-to-have: geiger-counter style audible cue (chirps are all one frequency, but rate of chirps changes with wasted friction power)
5) Ability to flash own firmware
- i) nice-to-have: Automatically log in continuous loop mode (overwriting oldest log file on sdcard) so latest log will be available as evidence in the event of accident
ii) nice-to-have: ability to exclude certain frequent but uninteresting messages6) Ability to configure message decoding and display
- i) nice-to-have: I know you plan to keep the firmware proprietary but perhaps providing a shell with basic canbus read/write and display subroutines would help kick-start a separate OpenSource project without exposing your "special sauce." This should improve your sales volume
7) Ability to source user-definable messages onto a canbus (probably required for access to individual cell pair voltages and resetting DTCs)
8) Separate user-definable display from main display (I log gids, battery voltage, etc every morning but then switch to a different mode for driving)
TickTock said:Sorry if this has already been indicated, but I thought of another feature I'd like
TomT said:I do hope that people realize that every additional feature likely dictates an increase in price and/or a decrease in how soon the device will be available...
TickTock said:Sorry if this has already been indicated, but I thought of another feature I'd like
TickTock said:Sorry if this has already been indicated, but I thought of another feature I'd like:TickTock said:I am in, of course. The features I am most interested in (in order of importance) are:
- 1) Access to all three canbus's (canbusi?) simultaneously
2) Ability to read individual cell-pair voltages
3) Tone proportional to brake_pressure*rpm (no tone below a certain threshold)4) Ability to log all three canbus's
- i) nice-to-have: geiger-counter style audible cue (chirps are all one frequency, but rate of chirps changes with wasted friction power)
5) Ability to flash own firmware
- i) nice-to-have: Automatically log in continuous loop mode (overwriting oldest log file on sdcard) so latest log will be available as evidence in the event of accident
ii) nice-to-have: ability to exclude certain frequent but uninteresting messages6) Ability to configure message decoding and display
- i) nice-to-have: I know you plan to keep the firmware proprietary but perhaps providing a shell with basic canbus read/write and display subroutines would help kick-start a separate OpenSource project without exposing your "special sauce." This should improve your sales volume
7) Ability to source user-definable messages onto a canbus (probably required for access to individual cell pair voltages and resetting DTCs)
8) Separate user-definable display from main display (I log gids, battery voltage, etc every morning but then switch to a different mode for driving)
9) Status logging: Every time the car is started, log an entry in a table of all programmed paramters (date, gids, SOC, ODO, GOM, bars, efficiency, battery voltage, temperature, tire pressure, etc). Also log when requested via the control buttons.
The beauty of LEAFSCAN is the user upgrade ability. I can release LEAFSCAN with an initial set of features then add new features as needed/wanted in the future. In addition, the LEAFSCAN will be user-extensible, without needing to learn full-scale software development.TomT said:I do hope that people realize that every additional feature likely dictates an increase in price and/or an increase in how long it will be before the device is available...
Unfortunately this is doubtful. Each home-built system is usually unique, and there is no data standard (is there is even data to begin with) from the various EV components.Lightnme said:Would the Leaf Scan be able to be made compatible with DIY EV's that use off the shelf components for both A.C. & D.C. systems?
If so, that could be another bump in revenue for the Leaf Scan; perhaps as an EVSCAN? There's no fully developed instrument like yours
that is well received I don't think, for home built EV's.
Jim
Ingineer said:A smartphone interface has been requested ad-nauseam and I am not convinced this is a good idea. At first thought, It sounds neat to have access to this information on your phone, but you have to realize that you'll want to have this available every time you drive. This means everytime you get into the car, you'd have to pull your phone out, launch the app, wait for it to connect, plug it in to your charge cord (to keep your battery from dying), put it into a mount/cradle, then when you stop, reverse this procedure. If you also want to use your phone for nav or music, as some people do, that just adds to the complexity. When you take calls, the app will disappear, and in fact, you may not even be able to use bluetooth for your call, as it will be in use by the data link to the car.
I'll be happy to include as many of these as you like. Just give me the formulas youd like to see implemented, and I can add them to the list.garygid said:A miles per Pack-kW "meter" will vary in basically the same way as the Pack-Amps, but give more useful information.
With Pack-Amps, neither higher nor lower is "better", although with Speed and Pack-Voltage relatively constant, then "lower" is "better", but it does not easily help you adjust your speed for longer range.
With mi/kWh, then "more" is "better", it varies as rapidly as Pack-Amps, but it easily shows the beneficial effects of changing speed. One still has to mentally calculate "Remaining Range" from an estimate of the Pack's remaining "usable" kW-hours.
In the same manner, an "instantaneous" Estimated Remaining Range meter will also vary in the same "fast" manner, AND show directly-usable information, essentially no mental-math needed.
My current plan is to use Velcro to mount it in the recess at the left side of the dash where that tiny window is. Maybe it's just my driving position, but I can't see anything out that window except a short narrow slit of light, so it's a pure waste.adric22 said:I keep wondering if there is some place better it could be installed in a Leaf.
Great idea - me too.planet4ever said:My current plan is to use Velcro to mount it in the recess at the left side of the dash where that tiny window is. Maybe it's just my driving position, but I can't see anything out that window except a short narrow slit of light, so it's a pure waste.
Enter your email address to join: