AUTOSAR

AUTOSAR

Posts 1-3 of 3
  • User photo
    Henning Riedel
    The company name is only visible to registered members.
    Limitation of ARtext or AUTOSAR?
    Hello again,

    1.)
    I currently try to get into Artop (as my other post already shows ;) )
    artext-1.2 demonstrator
    arunit-0.7.3 demonstrator
    I tried to follow the videos on ARtext, but there are some things not working as in the video.
    (besides all the Exceptions that come up now an then in the error.log.)

    e.g. they just start to create an swcd or ecuc file and enter some text and in their video, all AUTOSAR types etc. show up in context assist. Well, I don't get anything shown, it can't even find types like uint8, uint32, or AUTOSAR.EcuDefs.Can.

    It only works, if I first include the ECUConfigurationParameters.arxml file at project creation.
    Looks like the schema/metamodel is not loaded.

    2.)
    I already seen in the generated Rte code at work (using some other tool),
    and also, when trying to write an ecuc file: Why can't I enter numbers in hex or octal notation?
    e.g. CAN IDs and filter masks are usually exchanged in hex, I've only seen decimal usage in DBC files, which is also tedious to find out. Does AUTOSAR only allow numbers as decimal or is hex allowed?

    3.)
    I wonder is, if you could categorize the "Elements" submenu?
    From A like "Alias Name Set" to X like "Xcp Pdu" .. a long list to scroll through.


    Regards,
    Henning
    • 12 Nov 2011, 1:52 pm
  • Dr. Sebastian Benz
    Dr. Sebastian Benz
    The company name is only visible to registered members.
    Re: Limitation of ARtext or AUTOSAR?
    Hello Henning,

    my comments are inline.

    Henning Riedel schrieb:
    Hello again,
    1.)
    I currently try to get into Artop (as my other post already shows ;) )
    artext-1.2 demonstrator
    arunit-0.7.3 demonstrator
    I tried to follow the videos on ARtext, but there are some things not working as in the video.
    (besides all the Exceptions that come up now an then in the error.log.)
     
    e.g. they just start to create an swcd or ecuc file and enter some text and in their video, all AUTOSAR types etc. show up in context assist. Well, I don't get anything shown, it can't even find types like uint8, uint32, or AUTOSAR.EcuDefs.Can.
    That sounds strange. I have to admit that these problems are new to me. Please note that you can only reference elements that are defined in the same project. If these problems persist, please file a bug with an example project: https://www.artop.org/bugs/enter_bug.cgi

    It only works, if I first include the ECUConfigurationParameters.arxml file at project creation.
    Looks like the schema/metamodel is not loaded.
    That is the intended behavior, you need to include the ECU parameter definitions in your project in order to instantiate them.

    2.)
    I already seen in the generated Rte code at work (using some other tool),
    and also, when trying to write an ecuc file: Why can't I enter numbers in hex or octal notation?
    e.g. CAN IDs and filter masks are usually exchanged in hex, I've only seen decimal usage in DBC files, which is also tedious to find out. Does AUTOSAR only allow numbers as decimal or is hex allowed?
    We haven't included support for hex / octal notations, because nobody requested them yet. Feel free to file a feature request: https://www.artop.org/bugs/enter_bug.cgi

    3.)
    I wonder is, if you could categorize the "Elements" submenu?
    From A like "Alias Name Set" to X like "Xcp Pdu" .. a long list to scroll through.
    Do you mean the elements menu in the tree viewer? This is indeed quite inconvenient. However,
    the goal of Artop is not to provide a fully functional AUTOSAR tool, but to provide a common infrastructure that tool vendors can use to create their AUTOSAR tools. The tree viewer is just an example for how to use the Artop API. Therefore, it is unlikely that the treeviewer will improve mich over time.

    Best Regards,

    Sebastian
    • 13 Nov 2011, 3:03 pm
  • User photo
    Henning Riedel
    The company name is only visible to registered members.
    Re^2: Limitation of ARtext or AUTOSAR?
    Dr. Sebastian Benz schrieb:
    Hello Henning,
     
    my comments are inline.
     
    Henning Riedel schrieb:
    Hello again, 1.)
    I currently try to get into Artop (as my other post already shows ;) )
    artext-1.2 demonstrator
    arunit-0.7.3 demonstrator
    I tried to follow the videos on ARtext, but there are some things not working as in the video.
    (besides all the Exceptions that come up now an then in the error.log.)
     
    e.g. they just start to create an swcd or ecuc file and enter some text and in their video, all AUTOSAR types etc. show up in context assist. Well, I don't get anything shown, it can't even find types like uint8, uint32, or AUTOSAR.EcuDefs.Can.
     
    That sounds strange. I have to admit that these problems are new to me. Please note that you can only reference elements that are defined in the same project. If these problems persist, please file a bug with an example project: https://www.artop.org/bugs/enter_bug.cgi
     
    It only works, if I first include the ECUConfigurationParameters.arxml file at project creation.
    Looks like the schema/metamodel is not loaded.
     
    That is the intended behavior, you need to include the ECU parameter definitions in your project in order to instantiate them.
    Ok, that sounds right for an ecuc file then.
    But when I create a new ARtext project and add a new swcd file, I assume I should get the default AUTOSAR types (Platform_Types, Std_Types, ComStack_Types etc. pp.)

    e.g.
    --- sample.swcd
    package mypackage

    interface senderReceiver mySRFaultIf {
    data Adc_ChannelType adcChannel
    data uint8 myData1
    data float32 chnValue
    }

    ----

     
    2.)
    I already seen in the generated Rte code at work (using some other tool),
    and also, when trying to write an ecuc file: Why can't I enter numbers in hex or octal notation?
    e.g. CAN IDs and filter masks are usually exchanged in hex, I've only seen decimal usage in DBC files, which is also tedious to find out. Does AUTOSAR only allow numbers as decimal or is hex allowed?
     
    We haven't included support for hex / octal notations, because nobody requested them yet. Feel free to file a feature request: https://www.artop.org/bugs/enter_bug.cgi
    Ok, I'll do.
    Nobody really uses hex notation yet?
    Or do you really convert them to decimal all the time?

     
    3.)
    I wonder is, if you could categorize the "Elements" submenu?
    From A like "Alias Name Set" to X like "Xcp Pdu" .. a long list to scroll through.
     
    Do you mean the elements menu in the tree viewer? This is indeed quite inconvenient. However, the goal of Artop is not to provide a fully functional AUTOSAR tool, but to provide a common infrastructure that tool vendors can use to create their AUTOSAR tools. The tree viewer is just an example for how to use the Artop API. Therefore, it is unlikely that the treeviewer will improve mich over time.
    Sure, it's just a demo, but for someone trying to get into AUTOSAR it is hard to get around.
    Learning in private, I have no access to our tools at work, which require a license.
    And, unfortunately, I do not have the time at work to learn on AUTOSAR. There, I only try to get around all the hassles we have/get with it and the tools and get the SW to do what I expect.

    Regards,
    Henning
    • 13 Nov 2011, 9:40 pm