MoTeC Global Forum

I have been trying write Rx Script on Enumeration from DBC, I can't seem to get the script working.
Do I have to Rx them as Getinteger to local integer channel first than map a local enumeration channel?

Thanks,

Hi,

You can directly assign a channel from your RX code with the .GetEnum() function on your DBC signal. To make it work the DBC signal must have a value table (vt) assigned to it and the target channel must have the same vt assigned as Data Type (might also work by creating an enumeration data type identical to the vt but usually it is more convenient to work directly with the vt as it allows discontinuity in the key values, unlike the enumeration).

If you are not working with Value Tables, then you have to get the value of your DBC signal (either raw unsigned, scaled, or whatever is corresponding to you need and setup) and assign it with the .Set() function.

Are you sure .GetEnum() is available?

Loic wrote:Hi,

You can directly assign a channel from your RX code with the .GetEnum() function on your DBC signal. To make it work the DBC signal must have a value table (vt) assigned to it and the target channel must have the same vt assigned as Data Type (might also work by creating an enumeration data type identical to the vt but usually it is more convenient to work directly with the vt as it allows discontinuity in the key values, unlike the enumeration).

If you are not working with Value Tables, then you have to get the value of your DBC signal (either raw unsigned, scaled, or whatever is corresponding to you need and setup) and assign it with the .Set() function.

If you are using Build version 1.4.3.263 or later .GetEnum() will be available if the signal you are receiving has an associated value table in the dbc file.

I am using 1.4.4.898, under Library it does not have CanComms.xxxEnum
Is it normal?

adrian wrote:If you are using Build version 1.4.3.263 or later .GetEnum() will be available if the signal you are receiving has an associated value table in the dbc file.

Yes that's correct, you don't use the CANComms library if you are using dbc import.

If you go to Help>Manuals>Examples>DBC Import it details how to use the dbc import.