Hello, I have 2 linear potentiometers, which are connected to the race ECU.
Is there an ECU channel, where I can map these with 1 decimal places and maybe with ‘mm’ Unit? (data recieved via 500Hz canbus channel, but ADU can only read it at 100Hz I think)
Unit is not priority, but it should have 1 decimal place.
I need it to be able to display min max value easily, without any additional functions or match channels.
Thanks
you can define all of that when creating the CAN input. You can always use a number or math channel to translate units as well. It will depend on how the data is being sent though; if the ECU sending it is sending round numbers then you can add a decimal point to the value but it will always be ‘0’
Display min and max where? on the dash you just define the min and max of the bar graph or whatever you’re using to display it, same idea when setting up a graph log for post session review.
What kind of vehicle is this and what ECU is the data being sent from?
The ADU can log 125hz over CAN I believe and 500 hz if the sensors are wired into it directly.
Calibration files for both ADU and ECU would be beneficial to aid in answering the “how do I” type questions
Thanks for the effort, but you are missing the whole point.
Of course i can modify and min/max everything with math channels, but the whole point is to avoid it, as the project is already at the limit with everything (enum, function, canbus input, page size, alarm).
When I use built in ecu.xy channels, ADU can automatically show me the min and max values for them.
Why would I use bar graph, it doesn’t show the min and max value over the session, thats just the visualisation of the current value on a scale.
It’s a world championship level race ecu, which sends most data at 100Hz, but some critical channels for the shifter and suspension are sent at 500Hz.
In the ADU canbus preview, it shows 99-101Hz for me usually, and the logger is also using 100Hz, even if I set it to 500Hz logging.
The manual doesn’t state, that canbus inputs can’t be used for more than 100Hz, but I sadly think this is the case.
Where did you get the 125Hz number from?
fyi:
example of 100Hz logging:
This is more context then, you’re original question was too vague to provide a better answer.
What are you using for log analysis? the min and max value achieved in a session could be pulled in that software if you are limited on ADU resources.
DataMaster does this on the runtime values list. It also has math channels.
The ecu.xy channels aren’t really modifiable, but they can be overridden. When you’re creating the CAN import select ‘over ride existing channel’ at the top and you can select a ecu.xy, it unfortunately doesn’t let you rename said exu.xy channel but if you chose like ‘ecu.user1’ and fudge the number coming in that might work.
The intended way is number channels, but as stated you’re full up.
I had to go back and check, 125hz is now out of date information on newer firmware versions. What I was remembering was the export limit, it’s now 100hz with a 500 frames per second overall limit on each CAN bus; irrelevant, my mistake.
100hz incoming might very well be the limit.
Are you allowed to put the travel sensors direct to the logger or does the series dictate they have to go to the spec ECU?
they could be wired to ADU as well, but the current loom has it to ECU, and has some buttons to zero it easily. Later, if I need 500Hz for some calculations, I could wire to ADU, but it’s not a priority.
I know about the ECU channels, I checked all of them yesterday, none of them have mm as Unit. I used FuelLevel and FuelLevel2 as a free ecu.xy channel, which has 1 decimal place. Just used custom Units in the display Textbox.
The original goal was to have the min/max values on ADU, right after the session, before analysis on PC, so I can see the total travel right away.
Did the same with tyre pressure and tyre temp as well. (Analog1-2,egt1-2)
Now they will have the wrong name and unit in datamaster, but i can remember 5-6 channels. The decimal places were wrong anyway, so…
it’s been 2+ years, and there is still no sync between ADU channels and DataMaster (units, decimals, and enumerations or flags)
Maybe in a few years … Still, pretty good featureset, but there are a lot of ways to improve. I guess it’s unfair to compare them to Motec and similiar, which obviously have much bigger budgets.
you can create channel alias in DM, would resolve the names being wrong.
Yeah I think the dev team has been pretty busy on EMU Pro DI stuff, the ADU software has had a few leaps since DM was updated. hopefully on their to-do list.
I checked the ECU channels with Lightclient, and 1 multiplexed channel read between 240-300Hz.
When I checked in ADU, it displays 199Hz, so I think ADU can read data at 200Hz from CANBUS0.
Not sure if it’s usable in real life, as this channel had 24 multiplex, thats why it had such a high rate, 24 multiplex times 10Hz. Not sure why did light client read it as over 300 sometimes and why did adu read it 199.
Still, pretty cool.
EDIT:
after further analysis (downloaded complete trace log), adu reported the correct Hz value (200,0Hz). LightClient had incorrect and fluctuating reading. Makes me think ADU can go over 200Hz on canbus. Messages were 3.6 than 6.4ms one after the other, so maybe it should avarage them out like ADU or something, but this is obviously a very minor thing.
