Hi Michael.
The flow is very simple (and not GUI-related). You do the following, in order:
1) taste-create-data-view
This is the main command to create a dummy .asn file with default ASN.1 types (and open it in a text editor - gedit, if memory serves). When you exit the editor, the corresponding AADL dataview is generated.
2) taste-create-acn-model
This creates a default ACN file corresponding to the ASN.1 file you created in step (1) (again, opening the ACN file in a text editor). When you are done, it will update the AADL DataView so that the ACN file is referenced.
3) taste-create-interface-view
This will spawn the Interface view editor, so you can create your interfaces. When you describe the interface parameters, you also specify whether NATIVE, UPER or ACN encoding will be used - see this screenshot:
I hope this helps you do what you need.
Kind regards,
Thanassis.
On 16/07/2013 12:54 μμ, Michael.Dumke@xxxxxx wrote:
Dear TASTE-users, I have a question concerning the encoding via CAN and I hope somebody can hint me into the right direction. I have a blackbox device that sends data via Ethernet, I want to specifically encode this data via ACN. My problem is I don't know the TASTE workflow for this, nor can I find a documentation on this. I just found that there is the program "taste-edit-acn-model" but I think I still miss parts of the stuff I have to do to get the encoding the way I want. For example I want to encode to "encoding IEEE754-1985-64" which should be 8 bytes, but the generated dataview-uniq.h still stats that 13 bytes are needed. Can anybody tell me how the workflow inside TASTE is, to get the ACN encoding working? Best regards Michael Dumke -------------------------- Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR) German Aerospace Center Institute of Space Systems | Robert-Hooke-Str. 7 | 28359 Bremen | Germany Michael Dumke Telephone +49 421 24420-1262 | Telefax +49 421 24420-1120 | michael.dumke@xxxxxx www.DLR.de