I found with my own software, the first thing people do is select every single parameter, then ask why the refresh rate is so slow. Never at any point do they think to try reducing number of parameters! At least this way, we seem to kind of maintain a similar refresh rate regardless.In-Tech wrote:It really does sound good, Tazzi. The ability to lower the pids polled and increase the frame rate is awesome. AE is about the only reason you would need to monitor that fast. TPS, MAP, RPM(maybe), AFR. If there is a way to monitor external AFR/Lambda and TPS/MAP at 25hz, what a gift
The stuff you do always impresses
If resolution becomes an issue, we can add some sort of priority system where a specific number of PIDs can be manually polled to increase their display rate.
Last few things to add in left:
1) Dash display. This is not ideal in anyway currently, have to right click and then select the desired PID to display for that gauge. This wouldn't be so bad except I have not implemented a save dash configuration yet.
Eventually there will be some sort of option to select pre-saved dash setups. If a PID previously selected is not available for that vehicle, it will simply leave that gauge blank.
2) Add an auto log saving functionality, also allow exporting into a different format such as CSV.
Exported files will likely have a csv setup of: Time/Date, Parameter Name, Unique ID, Value, Units
The "to-do" list for everything else is absolutely huge still do, but after having the above done, I will feel good for an initial release.