Exporting custom data sets to SDL
Posted: Fri May 11, 2012 10:42 amon a m600 when exporting two custom data sets in the ecu manager software i have found that if you have custom set 1 checked and custom set 2 checked and have channels added to both sets and exporting this comms template for the use in a SDL dash the software will save custom set 2 with the same CAN transmit address as custom set 1.
so when you try to add these two sets in the SDL dash manager it will create a conflict.
What I did was go into the ADL2 dash manager find the custom set "2" in the file folder that was exported and load it and edit the CAN hex address to 6F0(1776) instead of 5F0(1520) (which custom set 2 was saved as) but this is the default for custom set 1... resave this file (so you can move it to the SDL dash manager folder, reopen SDL dash manager and you can now load both templates with no conflict.
now the data that the ecu is transmitting on CAN 6F0 can be received by the SDL.
this seems to only be a problem for SDL dashes as they have no "advanced" tab to click and edit their CAN properties.
hopefully this helps someone in the future.
so when you try to add these two sets in the SDL dash manager it will create a conflict.
What I did was go into the ADL2 dash manager find the custom set "2" in the file folder that was exported and load it and edit the CAN hex address to 6F0(1776) instead of 5F0(1520) (which custom set 2 was saved as) but this is the default for custom set 1... resave this file (so you can move it to the SDL dash manager folder, reopen SDL dash manager and you can now load both templates with no conflict.
now the data that the ecu is transmitting on CAN 6F0 can be received by the SDL.
this seems to only be a problem for SDL dashes as they have no "advanced" tab to click and edit their CAN properties.
hopefully this helps someone in the future.