Standard CAN Stream

V3 BETA TESTS
1

Are there any changes (or additions) due to the standard CAN stream output in V3, or already made but not yet documented?

Previously I used states in OUTFLAGS1 to get the current parametric output values, however now these have been replaced with functions, will these also change in the standard stream?

Also wondering if PPS will be sent out (as TPS, or a new value) versus the V2 stream. I assume DBW POS / DBW TARGET will remain the same?

If not, I can send them out on a custom CAN message, but any clarification would be appreciated. Thanks

2

The standard stuff is the same. Old DBW pos is TPS now and old TPS is PPS now…was fixed with last firmware.
As i understood the target is to be in line with V2…so if u notice something strange i guess u should report it here and it will be fixed according V2 docu.

3

It is angle befor TDC. 300-400 deg at low rpm / low air flow is a typical value for most the engines and the angle decreases with RPM and load.

4

Thank you. I see that in the stream now.

If someone is able to clarify regarding the new function states vs. old parametric it would be good.

Thanks

5

Actually the virtual and parametric outpus are alwyas zero.
There are two options: map functions 1-8 to parametric and virtual outputs, or we add additional frame with more data like functions and others/

6

If an additional frame is possible, that would be great - I use the state of functions with other products as CAN input and a logger so I can see when the state changes in relation to everything else :+1:

7

Would something like the below suggestions work for additions/changes to the standard CAN stream for V3 moving forwards?

I have tried to think of fields that are more commonly used, and that would be useful for others too (when using this data for other equipment, dashboards, loggers etc).

The lambda target from table is useful to compare the difference in actual target to the table target so you know there is a fuel correction being applied at any moment.

In the case of using an external (OEM) fan controller, the DC value of the coolant fan strategy would be helpful. At the moment I have a workaround with a manual table configured on PWM1 with CLT vs VSS, as the DC for PWM1 is in the existing standard stream. But this means you cannot take advantage of the coolant fan strategy, like hystersis and turn off when cranking etc.

Even if the function states were changed, this would be massively helpful, as I would no longer need to use the user defined CAN stream for those, and in turn free up those custom channels for other data.

______________________

BASE ID + 3 - Byte 3, LAMBDACORR - Is this going to remain as a base of 100%, or switch to a base of 0% and become signed, to follow the rest of V3? I run an offset of -100 at the moment, but just checking.

OUTFLAGS1 - Fn 1 > Fn 8 - Replace paramentric/virtual states.

ERRFLAG - 11 DIFFCTRL, 12 DSG, 13 EWG, 14 OILP - Add additional error flags?

______________________
Base ID + 8

Bit Idx Name Length Data Type Resolution Unit
0 OUTFLAGS5 8 bits Bitfield
1 FLAGS2 8 bits Bitfield
2 VE 16 bits Unsigned %
4 (New Channel?) Effective Fuel Pressure 8 bits Unsigned 0.0625 bar/bit bar
5 Acc. Enrichment % 8 bits Signed 1%/bit %
6 Lambda Target From Table 8 bits Unsigned 0.01%/bit %
7 Coolant Fan DC 8 bits Unsigned 1%/bit %

______________________
OUTFLAGS5

Bit Idx Name
0 Fn 9
1 Fn 10
2 Fn 11
3 Fn 12
4
5
6
7

______________________
FLAGS2

Bit Idx Name
0 F. Short Term Trim
1 F. IAT Correction
2 F. Warmup Correction
3 I. Custom Correction 1
4 I. Custom Correction 2
5 I. Custom Correction 3
6
7
8

Thanks for your feedback. We didnt decide how we extend the stream yet.
I will keep you posted

1 Like