[thecarfixer]

Following on from my auto to manual conversion, the only module I haven’t done a default code to since I changed the VO is the DSC module, as I get a comms error whenever I try to run SG_Codieren against the DSC.

I gather there’s some slight changes between auto and manual so would like to get it coded. Do I have to use an ICOM, or is there something I’m doing wrong? All other modules work with NCSExpert.

Thanks.

[user0086]

DSC56 is very picky. Try coding it with the original FA to see if it is the setup or just unsupported coding.

[blax123]

Icom needed for R5X 2nd generation

[thecarfixer]

Icom needed for R5X 2nd generation

For the DSC specifically?

Because I don’t for the other modules, apart from anything on the MOST bus.

[Node]

Main problem with some modules is that they need large (as in 128 to near 250 bytes) data packets. ICOM handles that without any issues. 100% of chinesium DCANs DO NOT. They just truncate data (around 120-ish or 140-ish bytes, that was years ago so I do not remember actual number) and OF COURSE you will get errors.

To solve this you could reflash your cable with ediabaslib firmware. That is IF your cable is built using PROPER hardware inside of it and not cheaped down to death components.

Thats solves 95% of cases of modules not working with such cables.

[blax123]

R5X 2nd Gen DSC is unfortunately not compatible with DCAN. With ediabaslib firmware not too.

[thecarfixer]

I’ve been looking for a good reason to buy an ICOM…

But then we get into genuine ICOM vs clone etc.

I’ll do some reading, but are there any threads with details about how to navigate this minefield and make the right choices?