FHSW
2006-09-26 18:40:10 UTC
Our current status is: Working CAN communication under CANape 6.0
We do have a Vector Cancard XL that is prepared to work with LabVIEW and CANape which is connected via Vector 251 opto-cable with our device.
What we want to achieve is: Transferring functionality into LabVIEW 7.1, i.e. Sending and receiving messages (or signals?) using the Vector Driver for LabVIEW.
We have collected some questions related to this topic and would appreciate your help:
In CANape and some demo tools from the Driver XL Library from Vector they want to have IDs. Where do i get them from? Is there one ID per message, per signal or per device? What's the difference between message and signal? We ´re asking, because the Vector Driver requires a database (.dbc) in which specific messages AND signals have to be inserted.
We already figured out a possibility to create such a database out of our CANape project, but this results in a database with only one signal and two messages available. We are not sure, if the generated database is correct. How can we assure that?
In CANape everything works fine, we have a script which sets global variables to the device. But how does this work in LabVIEW under the use of this messages, signals respectively? Until this moment we don't see any relation between those global variables and the generated signals/messages. The global variables are defined in an .A2L database, obviously independent from that generated(.dbc) file. How could we test it?
Does anyone has experience with the Vector LabVIEW configuration tool, or the generated database and knows if it works? Has anyone worked with the (latest) Vector LabVIEW driver version (1.0) or transferred any CANape functionality into LabVIEW yet?
We appreciate any kind of help, whether you have experience with the whole problem or partially.
We do have a Vector Cancard XL that is prepared to work with LabVIEW and CANape which is connected via Vector 251 opto-cable with our device.
What we want to achieve is: Transferring functionality into LabVIEW 7.1, i.e. Sending and receiving messages (or signals?) using the Vector Driver for LabVIEW.
We have collected some questions related to this topic and would appreciate your help:
In CANape and some demo tools from the Driver XL Library from Vector they want to have IDs. Where do i get them from? Is there one ID per message, per signal or per device? What's the difference between message and signal? We ´re asking, because the Vector Driver requires a database (.dbc) in which specific messages AND signals have to be inserted.
We already figured out a possibility to create such a database out of our CANape project, but this results in a database with only one signal and two messages available. We are not sure, if the generated database is correct. How can we assure that?
In CANape everything works fine, we have a script which sets global variables to the device. But how does this work in LabVIEW under the use of this messages, signals respectively? Until this moment we don't see any relation between those global variables and the generated signals/messages. The global variables are defined in an .A2L database, obviously independent from that generated(.dbc) file. How could we test it?
Does anyone has experience with the Vector LabVIEW configuration tool, or the generated database and knows if it works? Has anyone worked with the (latest) Vector LabVIEW driver version (1.0) or transferred any CANape functionality into LabVIEW yet?
We appreciate any kind of help, whether you have experience with the whole problem or partially.