Whether "J2735_201601_ASN.asn" file is free to download or payable?
If it free, from where can I download?
If it is payable, how much it costs?
Kindly reply
Thanks,
Gajalakshmi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Gentlemen:
Please be aware that the ASN.1 specification is not, and has never been, "free" - it is provided as a courtesy for the purchasers of that SAE DSRC J2735 standard. Purchasing the document grants you the right to use the provided source. Otherwise you can of course type in in by hand. Please remove the above link. Plus, as that edition is now out of date, so you really should not use that one. The SAE sells the ASN both with and without the rest of the standard (which you will need to understand the various normative content rules), see https://www.sae.org/standardsdev/dsrc/
As to the issues with compiling this specification relating to unions and lists (#68) that is pretty much gone now. When I revised the specification 2015 (I am the editor of J2735), I took pains to remove any remaining nested structures and also to make any use of SEQUENCE OF its own Type Definition. This results (IMO) in cleaner generated C code in this tool and in other tools.
However in the current J2735 standard we now make extensive use of parametrization functions as well as UPER encoding. The core issue is that this tool however does not support the parametrization features. The basic reason the committee went this way was to allow a cleaner way for regional extension for this message set, which is expected to be adopted as legal requirement for vehicle safety both in the US and in other countries. We needed a way to separate the legal issues from the evolving technical ones. This was done after debating the harm it might cause some tool chains for many months, and there are many on the committee who are advocates for "VLM asn1c" and hope that it may still be used.
--
Regards, David Kelley
SAE DSRC Message Set Editor, J2735
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
However, I don't have binary data of DSRC message for verifying codec's correctness. So if anyone can give me some raw data of DSRC message will be helpful.
I purchased J2735-201603.ASN for this asn1c enhancement. I am aware of aforementioned legal issue and won't redistribute the spec nor the ASN file. But I think the raw data of DSRC messages themselves are neutral.
Any feedback is welcomed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has anyone tried using asn1c for automotive dedicated DSRC? I tried to compile the SAE J2735 dictionary ASN file, but received an error as following:
ASN.1 grammar parse error near line 50 (token "IDENTIFIED"): syntax error, unexpected TOK_capitalreference, expecting '}'
Cannot parse "J2735_201601_ASN.asn"
I’m using asn1c-0.9.27 on Ubuntu 14.04. I get the same error for the online compiler as well. Thanks in advance for the help!
I think I tried compiling the DSRC definition and that it worked. I'll look into that again.
Sent from my iPhone
Can you post the source?
Check out Bug 68 as well: https://sourceforge.net/p/asn1c/bugs/68/
Last edit: Stefan Gudmundsson 2016-04-15
The .asn file in the Bug 68 link compiled for me as well. I might be able to use it.
Last edit: AWD 2016-04-26
I'm also facing same issue.
@Andy Dun, Are you able to compile J2735_201601_ASN.asn?
Dear All,
Whether "J2735_201601_ASN.asn" file is free to download or payable?
If it free, from where can I download?
If it is payable, how much it costs?
Kindly reply
Thanks,
Gajalakshmi
Dear Gajalakshmi,
I attached J2735_201601_ASN.asn. This is a last free version. I have the same problem with compilation. Could you please take a look?
Best regards,
Aleksey Boychev
Attachment was deleted.
Last edit: Aleksey Boychev 2016-07-01
Gentlemen:
Please be aware that the ASN.1 specification is not, and has never been, "free" - it is provided as a courtesy for the purchasers of that SAE DSRC J2735 standard. Purchasing the document grants you the right to use the provided source. Otherwise you can of course type in in by hand. Please remove the above link. Plus, as that edition is now out of date, so you really should not use that one. The SAE sells the ASN both with and without the rest of the standard (which you will need to understand the various normative content rules), see https://www.sae.org/standardsdev/dsrc/
As to the issues with compiling this specification relating to unions and lists (#68) that is pretty much gone now. When I revised the specification 2015 (I am the editor of J2735), I took pains to remove any remaining nested structures and also to make any use of SEQUENCE OF its own Type Definition. This results (IMO) in cleaner generated C code in this tool and in other tools.
However in the current J2735 standard we now make extensive use of parametrization functions as well as UPER encoding. The core issue is that this tool however does not support the parametrization features. The basic reason the committee went this way was to allow a cleaner way for regional extension for this message set, which is expected to be adopted as legal requirement for vehicle safety both in the US and in other countries. We needed a way to separate the legal issues from the evolving technical ones. This was done after debating the harm it might cause some tool chains for many months, and there are many on the committee who are advocates for "VLM asn1c" and hope that it may still be used.
--
Regards, David Kelley
SAE DSRC Message Set Editor, J2735
Hi, All,
I just fixed problems found during processing DSRC's ASN file in one github pull request, this repository maintained by mouse07410 which contains several useful features not merged into Lev Walkin's master yet.
Now the C code can be generated and compiled.
However, I don't have binary data of DSRC message for verifying codec's correctness. So if anyone can give me some raw data of DSRC message will be helpful.
I purchased J2735-201603.ASN for this asn1c enhancement. I am aware of aforementioned legal issue and won't redistribute the spec nor the ASN file. But I think the raw data of DSRC messages themselves are neutral.
Any feedback is welcomed.