adding CAN signal names as an another column in the table

[RepMat]

Hi,
i have an output table which list all the can signals. i wanted to add a column with its corresponding signal name. how to do it?.

The dbc file is available (I cannot share it)

how to import the dbc?

[GerdW]

Hi RepMat,

---

@RepMat wrote:

i have an output table which list all the can signals. i wanted to add a column with its corresponding signal name. how to do it?.

The dbc file is available (I cannot share it)

how to import the dbc?

---

You can read the DBC file with any text editor as it is pure text.

You can parse the DBC quite easily on your own to get the relation between message ArbID and signals within…

Does the PCAN driver come with a DBC file import function?

[RepMat]

no, i have the pcan basic.it doesnt have candb import. it is sold as another addin and unfortunately i dont have this addin. would it be possible to use xnet can drivers to import this dbc and display the corresponding signal in the column?

[GerdW]

Hi RepMat,

---

@RepMat wrote:

would it be possible to use xnet can drivers to import this dbc and display the corresponding signal in the column?

---

I guess so, I never worked with XNet. (I only used the old NI-CAN or "direct" implementation on FPGA level…)

You may ask Hooovahh (or read his blog)!

[ZYOng]

You can use the NI-XNET Database Editor and its API.

See shipping examples at Help >> Find Examples >> Hardware Input and Output >> CAN >> NI-XNET >> Databases

[Minions]

It is simple enough to get the symbol names from the .dbc file.  The issue you might have is that PCAN may not provide a field that can differentiate which symbol is being accessed.

The data shown in your chart shows:

> Date-Time Stamp

> Hex Data

> CRO/DTO Address (Sender or receiver address)

> Type (CAN Data versus other)

> Extended (29-bit versus 11-bit identifiers)

> Echo (Repeat signal on bus)

None of these points to the address of a particular CAN variable (CHARACTERISTIC or MEASUREMENT).  

[RepMat]

i couldnt completely understand you..even the ID is not a characterestic of a signal?

[GerdW]

Hi RepMat,

---

@RepMat wrote:

even the ID is not a characterestic of a signal?

---

A (standard) CAN message can have upto 64 bit payload, so it can carry upto 64 signals (each on one bit).

You only see the complete messages in your last image, but you need to decode the payload of each message.

(IMHO it doesn't make sense to show signal names in an additional column…)