CAN Wideband Setting Overflow error

[Emil]

Greetings,

I've just upgraded from a G4+ to a G4X and wanting to get the wide band controller to work the way it was working on G4+.

The external wide band controller is wired in to CAN2, mode=user defined, Channel1=Receive User Stream 1, mode=Receive user stream1. It has its own CAN ID and the format it normal.

This configuration is okay on G4+ however as soon as I add Frame 1 = Lambda on G4X, it throws setting overflow error 8. If I delete the frame, the error goes away.

The frame 1 is configured with Parameter=Lambda1, Start pos=8, width=16, unsinged, 1,1,0. Exact same configuration in G4+.

 

Is there a reason for the setting overflow error? Firmware version 6.16.15.

Thanks

[Adamw]

It works a bit different in G4X as pretty much any input or output can be via CAN.  So in your user CAN stream, change the received parameter to CAN Analog 1 or similar (not Lambda 1).

Then in the analog inputs section, go to lambda 1 and set the "Lambda sensor control" to CAN analog 1.  Leave calibration set to none I think.

[Emil]

Thanks @Adamw, interestingly it created the frame with that without the setting overflow error.

Frame is now configured with Parameter=CAN Analogue 1, Start pos=8, width=16, unsigned, 1,1,0.

When I select Lambda1, sensor control to CAN Analogue 1, the setting overflow returns.

Where to from here? Thanks

[Emil]

The help file seems to suggest what you mentioned but I guess there's still a problem in my config. I can see the values on CAN Analogue 1 on runtime values.

Generic CAN Wideband

To use a generic CAN Lambda device you will need to setup a custom CAN stream.

You can either set the relevant Lambda (1 or 2) to Link CAN and then have the CAN stream write directly to the runtime or have the CAN stream write to a CAN analog and select that CAN analog as the source and the appropriate calibration (None calibration will pass the value straight through).

[Adamw]

Can you attach your map, Ill have a quick play around.  Cant say i've personally done it with a 3rd party device yet.

[Emil]

Certainly, attached are both G4+ (2020 03 23) and G4X (2020 04 25) maps.

Thanks

2020 04 25 - Backup.pclx 2020 03 23 - Backup.pclr

2020 04 25 - settings overflow.pclx

[Adamw]

Ok, it looks like it needs to be scaled down to correct resolution as its received.  So set divider to 1000 should do it.

This is sending a value of "1100" via CAN.

 

 

Edit, added later:

I think I found where the problem is.  It does actually work when set to Link CAN the way it suggests in the help file note you attached, but it now needs a divider of 1000, it didnt in the G4+.  I will pass that on to engineering and either get them to fix it or fix the help file note.

So this set up will work too:

[Emil]

Perfect, thanks Adam. I am away from the car now, I will try this out on Tuesday and post an update.

Thanks

[Emil]

@Adamw once again, thank you for your support. I can confirm with 1000 divider the error is gone.

On another note, it is running really rich - we will have to look at calibration data.

 

Thanks for you support!

[Adamw]

I discussed this with Engineering the other day, the way the value is stored and used in the ecu has changed to make it more flexible so this is intended behavior and is just something I didnt come across until now.  Hopefully when the test calculator and help file is updated that will make it more clear.  This applies to all parameters that arent scaled 1:1 such as wheel speeds, the received data now needs to be scaled to make it match the final display value/units when received.