-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for COMPARAM-SUBSET #92
Conversation
@andlaus I can add a test by using the sample PDX from https://github.com/sebastianwilczek/CANoe-Configurations/tree/master/Ethernet/Diagnostics/EthernetDiagnostics/ODX Creating a full com param configuration using python sounds like an overkill. |
if @sebastianwilczek can confirm that the file can be distributed under the MIT license, yes. If we can't get that affirmation, a second repository (
I agree. at least in the short and medium term ;) |
instead of defining them from scratch, we simply read them from the .odx-cs fragments shipped with the ODX standard. Signed-off-by: Andreas Lauser <andreas.lauser@mbition.io> Signed-off-by: Gerrit Ecke <gerrit.ecke@mbition.io> Signed-off-by: Alexander Walz <alexander.walz@mbition.io>
Hey everyone, not sure about the context here, but the linked repository is only a modified version of the configuration files used by CANoe, developed and owned by Vector Informatik GmbH: https://www.vector.com/int/en/download/?tx_vecdownload_downloaddetail%5Bdownload%5D=92521 As far as I can tell, they do not list any form of license (in context of MIT or otherwise), so unfortunately I can not tell you whether you may use any of the files in your processes. |
I tested this PR with our internal files written by candela studio, and it seems that after this PR, the send and receive IDs ( |
@sebastianwilczek: okay, I suppose we should ask vector then. I'll keep you updated. |
…e is defined ... some of the comparam fragments shipped with the ODX standard only specify a unit without any scaling. Assuming that these files are correct, we should not complain about this either? Signed-off-by: Andreas Lauser <andreas.lauser@mbition.io> Signed-off-by: Gerrit Ecke <gerrit.ecke@mbition.io> Signed-off-by: Alexander Walz <alexander.walz@mbition.io>
should be correct now |
@andlaus I think you forgot to commit the |
thanks to [at]kayoub5 for the catch. Signed-off-by: Andreas Lauser <andreas.lauser@mbition.io> Signed-off-by: Gerrit Ecke <gerrit.ecke@mbition.io> Signed-off-by: Alexander Walz <alexander.walz@mbition.io>
@andlaus FYI, you push directly into a fork if the author enabled it (checked "Allow edits by maintainers") So feel free to push changes directly to my branch. |
thanks for the offer, but I think it is less confusing if I don't do this (I always get slightly dizzy if some of my PRs change without my intervention...) |
btw, I now get the following warning:
I assume that this is caused by the fact that the ECU can be interacted with using multiple protocols (DoIP and CAN). I guess that fixing this requires a full understanding of the protocol concept and should thus be left for another day? |
ok, I've tested this with our internal files, and it seems to work without the |
moar fixes for mercedes-benz#92
We can do that in a different PR, this one is too loaded as it is |
You can cross check this by checking that the different com params point to different proto stacks It could even be different CAN buses. |
@andlaus anything blocks merging this? |
no. nice work, thanks! |
The reason for these were that CANdela uses different communication parameter specifications than the ones specified by the `odx-cs` files that are shipped with the ODX standard. This resulted in a different ordering for some of the complex communication parameters (albeit with all required fields being present). Fortunately, with mercedes-benz#92 merged, this became unnecessary. Signed-off-by: Andreas Lauser <andreas.lauser@mbition.io> Signed-off-by: Alexander Walz <alexander.walz@mbition.io>
No description provided.