ADL3 Problem

[adelaide]

I amhaving a problem getting the 4 buttons on my steering wheel working after upgrading my software/dash. Ialso purchased a new computer and installed the new versionof the Motec software. In dash mnager, while pushing the buttons, the softeare shown no activity while pressing the buttons. Any ideas are appreciated.

[YuriK]

Hi adelaide,
What version of the Dash mnager are you using? Can you PM me your configuration file?

Yuri

[adelaide]

Well it wasn the software afterall. It was a wiring issue. Thanks anyway. Cheers!!

[jhidley]

Yuri,

The latest version of DM for the ADL3 and probably the previous version have a bug with the User Conditions.

When you load a DM file that has a User Condition that results in an output channel being activated, the logic no longer works and the output channel never becomes activated. We made no changes to the wiring of the system. The only way I've found to fix the problem is to delete the User Conditions from the configuration file and redefine them. This seems to fix the problem, but I'm not sure 100% sure it fixes it for good. I'm worried that the next version of DM will still have the same bug. Since we have around 20 different DM files, it is a lot of work to go through and edit each file.

[YuriK]

Hello Jack,
Please send the configuration file you have problem with to yuri.khodos@motec.com.au
please also specify which user condition is causing the problem.

Thanks!

[YuriK]

Hi Jack,
Thank you for reporting this issue! We’ll fix it and will try to push the fix into the next release.
In the meantime I see that to re-enable user conditions you don’t really have to delete and re-write them,
it is enough to just open User Conditions Setup screen and click OK button, then send the configuration to the
dash and it should fix the problem.

Thanks!
Y

[jhidley]

Yuri,

I'll be able to test this and post my results on next Monday.

Thanks for the quick response.

[jhidley]

This problem has returned with version 5.40I of DM for the ADL3. I suspect that it was never fixed. This bug is not listed in the release notes for 5.40I or the previous version.