Hi! thank you for great app!
Couple of things I would love to see in future versions.
Being a RaceDAC user, I have a possibility to connect anything as input channel and log it with RaceChrono. It would be great to have a possibility to change names of the channels and assign custom units to them for better look in live gauges screen.
Also I would love to see some data as dials, bars or graphs, so in future possibility to choose presentation of channel data will also be really great. I love the simple black/white/red gauge style you have in pro version.
Finally, creating live gauge screens with specific channels in specific presentation with peak/hold/warning functions would be nice logical development of these features.
Comments
I have the Peak/hold/warning on my short term TODO list. I was supposed to do this during spring but as always I'm late with my schedule. Also I'm planning to have configurable dials for all of the data (not only RaceDAC), so you could choose from digital, analog etc. for live data and for exported videos.
The RaceDAC channel naming is something everyone using RaceDAC wants, but so I have considered it to complicate the user interface too much for what it does, and how many users will actually use it.
-Antti
It work in horizontal orientation
https://googledrive.com/host/0B5vzNcc4yVa8cmdwMHJwRFd1S1U/Screenshot_2014-06-11-22-24-19.png
https://googledrive.com/host/0B5vzNcc4yVa8cmdwMHJwRFd1S1U/Screenshot_2014-06-11-22-24-40.png
http://hexenberg.free.fr/racedac/RaceDACconfig_.apk
You should contact them to post the link on RaceDAC site. It's very useful.
Aol,
One more thing I noticed working with RaceDAC. Maybe it's the same with OBD data, I don't know... I have TPS or brake channels configured to show 0-100 values. Also i have pressure channels which are configured like 0-100 (0-10Bar). Since for RaceChrono these all are just values (although I don't know how it treats OBD data), we end up with log where 7000 rpm and 50"%" TPS and 3.5 bar of fuel pressure (recorded as "35") are shown on the same Y axis scale.. Is it possible to scale axis for each data channel? I don't really care that this will delete numbers on Y axis, in any case there are values of each channel at specific moment.
With current setting I can't really analyse most of the data in RC, but I can expor to for visualisation without further modifications.. I can reset all RaceDAC calibrations and analyse raw values - then they will be scaled nice, but then I loose possibiluty to analyse absolute values of the channels and every time I export data I need to modity it for video overlay...
But still being able to name the channels in RaceChrono would be SUPER handy!
So this has been made into a moot point, as Dashware can scale the channels and do math with them. Although it would still be nice to display the logged channels in a better format in the live RC display on the phone/dash....
It seems that now you can't use analogue presentation for most channels, I couldn't figure out how to get RaceDAC g-sensor data displayed correctly (only one axis selectable and it seems that data scale is not matching gauge expectations, so nothing is visible if analogue presentation is selected for G channel)
Do you plan to improve RaceDAC compatibility?
Like long awaited channel naming/custom channel units, availability of analog/graph presentation for all channels and simple settings of this presentation. Now, as I understood, analog gauge settings are tied to channel type like RPM channel of RaceDAC. It set up to show data in x1000 gauge. I have speed on this channel and it's configured to output data in km/h, do it's impossible to use analog presentation here since it's not configurable. Again, as I understood, other RaceDAC channel (except for G sensor as mentioned above) do not have any "type" assigned at all, so only digital presentation available, even if channel configured to output simple 0-100% data.
PS. you should use the RaceDAC firmware that outputs -1.000 for -1G and +1.000 for +1G. The early versions of RaceDAC outputted raw integer values from accelerometer. Make sure you're using that as I'm not going to fix the range in the client side.
I understand that working on new RaceChrono features may be more interesting and rewarding than fixing RaceDAC related stuff, but maybe you can update this some time soon?
Just to remind, I have several issues/features requests that will make my life as RaceChrono+RaceDAC user easier:
Issue (only one in fact): G-gauge in graph mode is not working when datalogger channels are selected, althoug in value mode normal values are shown (-1.2....1.2)
Features request: #1 Digital channel is fixed to be "RPM". I have speed channel connected there and in video overlay it still tries to show my 150 km/h as 150 RPM on 5000 RPM gauge. At the same time #2 digital channel where my RPM is connected can't be congfigured to be analog gauge. Ok, easiest solution is just to swap the input wires, but it would be great to see the same options for other eight channels anyway. So, I would really loved to see customizable gauges for datalogger with modifiable gauge names, options for analog presentation for every gauge and possibility to assign them to different groups for axis scaling/presentation purposes. Because axis problem is still there and when I add, for example, my AFR channel to the presentation with typical values 900-2200 (100x scaled AFR values), my 0-100 brake and throttle channels are lost on graph screen.
The necessity to add 10x..100x multiplier to get resolution from "only integer" output of RaceDAC is on their side. unfortunately it's probably to much to ask you add some math manipulations with the values from datalogger...
All this is needed to use video overlay features of RaceChrono to full extent. Because now it works great with basic GPS data and probably standard OBD channels, but totally unusable with RaceDAC if you want something that is not looking like bare values. I have to export values to .csv, adjust some values in excel and then use some other software to make video overlay. RaceChrono now already can make it all, it just lacks some flexibility working with RaceDAC data.