need help. We have one DAQ system which is supports only .dbc file to take data from PLC. So, How can we get .dbc file from B&R Plc?
Out of the box, I do not see any solution for you. What’s more, I do not know if you have a project or just a field B&R PLC you want to connect to. If you have a project, maybe we can discuss in more detail what hardware you have and what you can get out of it. Usually, it works the other way around: you have an EDS file of a CANopen device, and you just import it into the project. Long story short, you can try to describe in more detail what you have, or you can get in touch with local B&R support and discuss your use case with them.
Yes we have Project. and we are using C80 power panel with X20 Modules. So we have HBK DAQ system and it supports only .dbc file to take data from Our PLC (C80). SO please suggest how can it possible?
As mentioned in my previous comment, I’m now aware of this functionality, so I’m almost sure that this is not supported by AS itself. But maybe someone here has found some workaround. So C80, CAN open, AS project available, ..and you need .dbc file..so anyone here who has found some workaround for this use case? @VipulKukadiya if you do not receive any suggestion in next couple of days, please get in touch with local B&R support.
Hi,
I’ve no experience with it, but many years ago I heard about it.
So I totally agree to Jaroslav: it’s not supported by Automation Studio to export or import .dbc
As I understood right, you need to provide a dbc file to your customer, correct (you don’t wont to import one)?
If so, I assume you know which CAN based messages are availiable on your system. How are these existing CAN messages are handled in your software? Is it programmed by ArCAN (“low level” CAN), or J1939, or anything else?
DBC (DataBase CAN) is a data model describing the raw CAN data, and it’s mostly used in automotive applications.
dbc files are ASCII based descriptions of those CAN messages, including information like “name” (how is a datapoint shown in a DBC environment), “id” (the layer 2 CAN ID a message is using), if it’s a cyclic value (e.g. sensor) or an event value, the scaling of the raw value, and so on.
DBC is a “human readable” format, so in theory you should have the possibility to design one (or to hire a service provider with experience in that field to create it).
As I’ve no practical experience with it, I’ve no idea how much effort has to be invested, it definitely depends on which protocols are used today in your project, how the data is organised, how much CAN “datapoints” have to have available, and so on.
I just googled the topic DBC, and from my understanding here’s a website that could be useful to gain a first (very basic) understanding on how DBC works:
Best regards!
Everything said so far is absolutely correct. I’ve worked with dbc files in the past (though it was going the other way - creating code to read CAN data based on the structure defined in the dbc file). You will need to look at your CAN communication code to understand how the data is being packed together, and then translate that structure into the format of a .dbc file.
I just want to add that this is probably a good use case for AI. When I was working with dbc files, I needed a script that would run through the file and extract a list of CAN IDs and offsets, then convert that into a data structure that could be read by ArCan. However, if you give a model your CAN communication code it can probably give you a good head start in making your file. Of course, you’ll want to test that before calling it a day.
I think this is a good workaround, thanks all for your thoughts and ideas.
Thanks for your prompt reply.
Thank you Jaroslav.Kovar
you are welcome. So what is your final solution?