Most graphical programming software environments such as Sedona Framework use block-like elements as their functions, which are referred to as Components. Using a graphical editor like the free Sedona Application Editor (SAE) lets you configure and link Components together to create the wiresheet logic running in your Sedona device. To make programming easier and keep things organized, components are grouped by similarity of their functionality into Kits which are basically containers of alike Components. All Kits are released by software developers in an even larger container called the Component Bundle. The Component Bundle usually supports several Sedona devices and it is updated as new devices or device functionality is released by the manufacturer. New Component Bundle means new Kits, new Kits means new Components, and new Components means new functionality to you! This is the foundation of graphical programming.

What different Components do for you, and why you would connect them together should be the first question you ask yourself, especially if you are a beginner. Even the advanced BAS programmers out there would have to familiarize themselves with new functionality made available to them (in the form of Components) before they can begin writing their wiresheet application. Becoming familiar with all components available to you and their specific functionality is a great place to start. This information is available in the SAE Help menu, as well as in online videos and detailed documentation such as The Sedona Open Control Reference Manual.

Some kits may not come pre-installed on your Sedona device from the factory, or there may have been a recent update to the Component Bundle from the device manufacturer. In case you are not sure if you have all kits installed on your Sedona device, you could check the Kit Manager in the SAE tool. The Kit Manager allows you to add/remove compatible kits from your device. Hardware independent kits such as CControls_Function2; CControls_HVAC; and CControls_Math can be installed on your Sedona device using the Kit Manager.

2 Responses

  • Nasser Dollah

    Zdravko, love the blog.
    I think a great subject would discussing the pros and cons of programing using simulator versus live.

    • znetsovCC

      Thank you Nasser! I agree, contrasting between programming on real controllers vs. software simulated controllers would be a great topic! What are some of the advantages/disadvantages you have recognized between the two?
      One disadvantage I recognized is that you cannot really close the loop between you inputs and outputs, so in the case of a PID, it will keep winding up because it is seeing no effect of its output on its input. One simple way to get around this is to force your input value in the direction you expect it to go.


Leave a Reply

Your email address will not be published. Required fields are marked *