IQANDesign seems to ignore the resolution and offset information from DBC files on import (these parameters appear to only be used if you are using the internal J1939 database and not an imported one). Its seems odd not to utilize this information for generic CAN modules when its already provided in the DBC file. I could use a math channel to manually scale the values, but it seems like an opportunity for error when those factors were defined when the database was originally created and should just carry through.
I checked both 5.04 and 6.01 and they both present the same behavior. I feel like this kind of straddles the line between bug report and feature request. If there are practical reasons this is not done (e.g. wildly wrong values were put in the DBC file and IQAN would be forced to use them causing an error, the CAN database dialog would have to do some imported data validation, etc), I can understand, but a reasonable fallback strategy would seem to be default to resolution of 1 and offset of 0.
Thanks for your help.
Customer support service by UserEcho