CAN Transmit (TX) .dbc file import

[Billy_C]

@Jan_Matlag_ECUMASTER
picking back up on this after I played around more the features you mention here

@Jan_Matlag_ECUMASTER

Just for your information - we recently added a “Save as DBC file…” button for custom CANbus TX Frames.

If you want to both save and load a CANbus TX Frame, you can consider to use the menu “File / Export part…” command.

This doesn’t really do the trick exactly

RE: “Save as DBC file…”
Setup complex CAN TX stream one by one and then export each ID one at a time. Lets say you have 64 16bit CAN TX channels to a datalogger of some kind or PDU or anything really, (not already in the ecosystem of previously used devices). EACH channel has to be setup one at a time, then each DBC has to be exported per ID, 4 separate DBC files.

RE: “file/ export part…” command.
you are saying this?

That’s pretty self explanatory, these TX frames don’t exist yet so nothing to export/import.

EMU Pro is really charting the path on this so I know it’s in the early stages and more will come. This should probably come sooner than later though. RX Can stream DBC works fantastic!

example DBC generated from a python script that I made

NOTE: Warning reason not specified here, it should be via a highlight or something

The top lines are actually intended to be EMU Pro TX frames, so they are there… so close

It could look like this, two more fields and all the required info would be satisfied

[Jan_Matlag_ECUMASTER]

OKAY. I’m now understand what you want - import from 3rd party DBC for TX messages.

[Billy_C]

Or just do the “pro” stream with this until you have time to develop a dedicated checkbox???

.dbc files are cake to create, then manually setup the mapping for the first time, save that.. both files on EMU website and you’re in good shape

[Billy_C]

An added benefit to that method is a crazy huge “pro” stream that may conflict with some planforms out there might NEED to be partially edited based on the setup. That would allow a way to make everyone happy.

[Sujaemon]

I also support the request in this thread.

Additionally, I would like to see the Tx side settings have the same degree of flexibility as the Rx side.

Editing data configured in the EmuPro CAN stream (i.e., knowing the ID) might be problematic, but if we could simply select enable/disable using checkboxes—similar to the DBC import screen—users could manually add only the disabled items and assign them to different IDs. Wouldn’t this allow for extremely flexible configuration