Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Geonjae-Joo
    @Geonjae-Joo
    image.png
    image.png
    I think I got that right.
    first jpg is from bosch iot suit credential
    Kevin Olotu
    @kolotu
    this looks a bit different in my subscription - but I think the password that you need to use is the one in the "messaging" object. In the previous screenshot with your parameters, you used the one from the "device_registry" - could you give it a try?
    Geonjae-Joo
    @Geonjae-Joo
    Oh!!!! it's working! Thank you so much
    Kevin Olotu
    @kolotu
    awesome - you're welcome, glad I could help
    Geonjae-Joo
    @Geonjae-Joo
    hi @kolotu . would you help me out one more time?
    I got vorto middleware up and running. I did the making IM and creating mapping specs, exactly as I told on the tutorial, and mounted them right. But I got the error as snippet .
    image.png
    image.png
    image.png
    Jens Reimann
    @ctron

    Hi @ctron, are you referring to the Functionblock mapping or to the payload mapping?

    I guess both :)

    Kevin Olotu
    @kolotu
    @Geonjae-Joo the error looks as if the AMQP connection is not configured properly, however I have never seen this error before and can't provide a more helpful hint unfortunately
    Kevin Olotu
    @kolotu

    @ctron just for differentiation here - the functionblock mapping is for adding platform-specific attributes to a functionblock (design time), while the payload mapping maps device payload into a normalised format (runtime)

    An example for the functionblock mapping is this one: https://vorto.eclipseprojects.io/#/details/org.apache.plc4x.examples:SimulatedPLC:1.0.0 (background information can be found here: https://github.com/JulianFeinauer/ditto-mqtt/blob/master/blog/blog.md)

    For the payload mapping, I'd refer you to the basic tutorial: https://github.com/eclipse/vorto/blob/development/docs/tutorials/create_mapping_pipeline.md

    There is no modbus specific example yet.

    Jens Reimann
    @ctron
    Ok I see … so the functionblock mapping amends the existing model with "custom" (e.g. modbus) specific information?! So I could read that when starting up my application, introspec the model, find the modbus specific information by using the functblock mapping, and then start performing my modbus specific communication? … In a nutshell? :) … or did I get that wrong?
    Kevin Olotu
    @kolotu
    perfect summary :)
    Jens Reimann
    @ctron
    thanks for your help! :) … Now I know how I can proceed.
    Kevin Olotu
    @kolotu
    In the blog I linked above is the description which APIs to use for the introspection and also a code example
    Jens Reimann
    @ctron
    good to know … you don't have any Rust based examples I fear? :)
    Kevin Olotu
    @kolotu
    no sorry - but I'd gladly accept them as contribution ;)
    Jens Reimann
    @ctron
    good answer :)
    Jens Reimann
    @ctron
    I see some changed behavior on the GET /rest/mappings/specifications/<model>/exists endpoint. That used to return a JSON structure with the information that the item exists. Now it seems to return 404 … is that intentional?
    Kevin Olotu
    @kolotu
    @ctron since when can you observe that change? The system hasn’t been changed since the beginning of December, so any change in behaviour would be very unexpected
    Jens Reimann
    @ctron
    I am pretty sure that last test way before that
    might be around novemeber, or even before
    Kevin Olotu
    @kolotu
    Ah okay - I can check the last changes for that specific API. But in general APIs that are not /api/v1/ are not guaranteed to be stable
    Jens Reimann
    @ctron
    which is ok :) … I just wanted to check if that was intentional
    Kevin Olotu
    @kolotu
    Sure :) so from the git commit history, this change has been propagated to that API by a change that was aimed at introducing some caching mechanisms and to unify responses for models that are not present or cannot be accessed because of missing permissions. It was intentional, but I wasn’t aware that this specific API was also affected :)
    Jens Reimann
    @ctron
    ok … thanks for looking this up. So I can keep the logic that "404" means not found now?
    Kevin Olotu
    @kolotu
    Yes exactly - this logic will not change any time soon
    Jens Reimann
    @ctron
    good to know :) thanks!
    Kevin Olotu
    @kolotu

    Dear users,
    The models of the Vorto Repository (https://vorto.eclipseprojects.io) will be moved to a new repository structure. This structure will be a folder-structure on the Vorto Github (https://github.com/eclipse/vorto/tree/development/models).

    Public Models
    All publicly released models will be automatically migrated to Github. The files on Github will be the Vortolang file, a JSON representation of the model and the image of the model.

    The migration will be carried out on 31 March 2021.

    The official Vorto Repository will be shut down by 30th June 2021. The transition period between 31/3/2021 and 30/6/2021 of 13 weeks will be granted so that users are able to adapt their applications that currently use the APIs of the Vorto Repository to use the Github APIs instead.

    The source code and Docker container remain available for anyone, who wants to host an own instance of the Vorto Repository.

    Private Models
    The migration will not include the private models in the Vorto Repository. Those models need to be made public before the migration so that they can be transferred.

    Or they have to be saved manually following these few steps:

    1. through the UI (see screenshot below)

      • Login to the Vorto Repository
      • open your model
      • click on the 'Vorto DSL' option in the 'Downloads' section
    2. through the API

    Creating / editing models
    To create or edit models on Github, you can follow the standard Github workflow by creating a fork and subsequently a pull request with your changes. If you want to use the Vorto tooling to write / edit a model, you can follow this manual here: https://github.com/eclipse/vorto/blob/development/models/Repository_As_Editor.md

    Please let us know in case you need any support from the project committers.

    image2021-2-17_9-49-56.png
    Kevin Olotu
    @kolotu
    At the end of May 2021, I'm going to resign as project lead and committer of the Eclipse Vorto project, as I'm going to start a new job, which won't leave me the time to continue this work. In case somebody is interested in taking over the project lead of Vorto, please feel free to reach out to me - I would be glad to discuss handover options with you.
    Jens Reimann
    @ctron
    Does that mean that Vorto is dead? What is the idea behind the combination of Ditto + Vorto?
    Is that combination still something that is considered a solid foundation for the future?
    Kevin Olotu
    @kolotu
    @ctron I‘m a bit confused about „a combination of Ditto + Vorto“ - what do you mean by that?
    Jens Reimann
    @ctron
    I think Vorto is an essential component in translating device payload into the Ditto format, right?
    Kevin Olotu
    @kolotu
    Ah okay, now I get your point. So all tools that are currently available, will remain available. Just the Vorto repository will no longer be publicly hosted - the models will remain available on Github. But as of now, there is nobody, who will continue to develop and drive Vorto after May, unless someone wants to take over the Vorto project.
    Jens Reimann
    @ctron
    yes, but the public APIs, currently hosted by the vorto project will cease to function, right? Including all the examples, demos, etc that use the public Vorto instance, like dashboards etc …
    Kevin Olotu
    @kolotu
    Yes that is correct. It is however still possible to use the source code or the pre-built docker image to host your own repository to use the APIs.
    But the public instance will not be available in future, so everything using that instance will no longer work.
    Jens Reimann
    @ctron
    sure, that is always an option
    Alexander Wellbrock
    @lionax_gitlab
    Did anyone else experience a drop of the whole repository on upgrading from 0.12.6 to 1.0.0? I think that happened already in the past upgrading from 0.11 to 0.12 but I don't know what I did back then to upgrade Vorto without loosing all repo contents :D I only changed to version number of the container image and did the database migrations manually, did I miss something?
    t-gauss
    @t-gauss
    Hello @lionax_gitlab , by manually migrating the database you mean you ran the migration scripts (e.g. https://github.com/eclipse/vorto/blob/development/repository/migration/migrate_db_0xx_to_013_MariaDB.sql)? When we updated the live repo back then we didn't loose the repository contents. Did you try to reindex?
    Alexander Wellbrock
    @lionax_gitlab
    @t-gauss hey there, yes, kind-of: I had to do my own migration inspired by those provided in the repo since I'm using mysql 8 which is not compatible with the H2 or MariaDB migrations. I did not yet try to reindex, I'll try that
    Alexander Wellbrock
    @lionax_gitlab
    How do I configure the eclipse ditto plugin from the vorto github repos generators directory to display the thing-json and schema selection? I've compiled the generators with the generator-runner into a container image and configured that in vorto via the "PLUGINS=" env as shown in the docs (key, type, api-ver, URL) but A) the name and icon don't match with the one from vorto.eclipseprojects.org and B) the generator does not allow configuration and returns an error that one of the two has to be selected
    t-gauss
    @t-gauss
    Sorry for the late response. I fear I cannot be of much help here. If its not too much effort you might want to try the local lambda approach (https://github.com/eclipse/vorto/blob/development/generators/generator-lambda/Readme.md)? In the past this worked for me and I was also able to see the icons an the radio buttons for selecting the format. However I have not tried with the current state.
    Alexander Wellbrock
    @lionax_gitlab
    @t-gauss no problem. Thanks for the hint
    t-gauss
    @t-gauss
    Dear users,
    just a friendly reminder: We are planning to shut down the Vorto repository by June 30 (see also @kolotu s post from March 19).