LabVIEW
LabView dbc-Translator
Crosspost. Was the conversion library I linked to not sufficient? Also do you still have a month if you posted that 2 weeks ago?
Hi irfan,
how are you related to the OP christruk?
@irfangojak wrote
I have a dbc-File, which needs to be converted, but I do not know where I am making my mistakes, because it cannot be properly converted. I could send the dbc-File that i have become from my company to You. Maybe it could work out.
How do you want to convert that dbc file? What is the target/goal format?
What have you tried so far?
Where are you stuck?
Hi irfan,
@irfangojak wrote:
to make the dbc file I got from my employer as a copy of what a dbc file looks like from customers we get from a battery system testing firm. In this case, the dbc file must be converted into resources (data) that would be readable for the BaSyTec system (battery system used as software for testing batteries, overcharging and discharging batteries), so that all important information such as SOC can be seen. - State of Charge, resistance, current, voltage and other things that come in the dbc file as CAN information).
You need to ask those BaSyTec provider of how their "resources file" need to look like - this is a LabVIEW forum with LabVIEW users!
Again I have to ask:
How does the result need to look like? Can you provide examples?
What kind of data does that BySaTec software expect? Why don't they support DBC files when they apparently have access to the CAN bus?
@irfangojak wrote:
If you want I can send that dbc file, so you can take a look at what it looks like and what the best solution would be.
This should have been done 3 weeks ago, with your first message in this thread…
Hi Irfan,
@irfangojak wrote:
BaSyTec systems are relatively old (from the 90s of the last century) and unfortunately do not support "Charge Current Limitations". Therefore, the current value must be extracted from the CAN file.
Which "current value" do you want to "extract" from your CAN DBC file?
Do you even know what a DBC file contains? A DBC file just contains definitions of messages sent over a CAN bus, and definitions of the signals within those messages. It does NOT CONTAIN any actual measurement data!
@irfangojak wrote:
BaSyTec must obtain this information, what are the tolerances of the battery power supply in a particular system.
The power supply should be a part of that BaSyTec battery tester system, so "BaSyTec" should also know the tolerances of that power supply.
What kind of "tolerances" are you talking about?
@irfangojak wrote:
The CAN program cross-section must also be achieved via Gustav Klein.
Who is Gustav Klein? And what is a "cross section" of a "CAN program"???
@irfangojak wrote:
With the help of LabVIEW program, it is necessary to convert the dbc file into HEX CODE which BaSyTec will understand. Crypt.
As said before: a DBC file contains just the definitions of messages and signals, which are transferred over a CAN bus. Which kind of "HEX CODE" to you want to receive after your "cenversion"???
What do you mean by "Crypt."?
@irfangojak wrote:
The CAN message should be understood by the BaSyTec system.
So that BaSyTec system is able to listen to your CAN bus? Then it should be able to read DBC files on its own to know how to "understand" CAN messages!
@irfangojak wrote:
To your question: "What type of data is needed for BaSyTec to" understand "what current limits are, the answer would be - most often it is HEX CODE"
This is no answer to my question, as "HEX CODE" doesn't mean anything to us.
I hate to repeat myself, but I need to:
How do you want to convert that dbc file? What is the target/goal format?
What have you tried so far?
Where are you stuck?
Can you provide example data (DBC file) and an example of the expected "result after conversion"? Don't forget to provide anexample and explanation of that "HEX CODE"…
