<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Codesys on Sagatowski GmbH</title>
    <link>https://www.sagatowski.com/tags/codesys/</link>
    <description>Recent content in Codesys on Sagatowski GmbH</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 16 Dec 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.sagatowski.com/tags/codesys/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CODESYS is not open-source</title>
      <link>https://www.sagatowski.com/posts/codesys_is_not_open_source/</link>
      <pubDate>Tue, 16 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sagatowski.com/posts/codesys_is_not_open_source/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;../../images/2025_12_16_codesys_is_not_open_source.png&#34; alt=&#34;2025_12_16_codesys_is_not_open_source.png&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;From time to time I see posts and comments on the web saying that CODESYS is open-source.&#xA;Normally I ignore making corrections, but last week something weird happened.&#xA;We were involved in a bidding for a contract, where the buyer selected an integrator which of one of the selection criteria for the other system was that they used the open-source IDE/runtime CODESYS.&#xA;It didn&amp;rsquo;t say open.&#xA;It said &lt;strong&gt;open-source&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OSCAT basic library in TwinCAT</title>
      <link>https://www.sagatowski.com/posts/oscat_basic_library_in_twincat/</link>
      <pubDate>Mon, 01 Jan 2018 00:00:00 +0000</pubDate>
      <guid>https://www.sagatowski.com/posts/oscat_basic_library_in_twincat/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve done development in TwinCAT for some time, you&amp;rsquo;ve most likely come across at least one of the &lt;a href=&#34;http://www.oscat.de/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;OSCAT libraries&lt;/a&gt;.&#xA;These are open source libraries developed in accordance to the IEC61131-3 standard.&#xA;They provide a total of three different libraries; OSCAT-Basic, OSCAT-Building and OSCAT-Network.&#xA;I&amp;rsquo;ve so far only used the OSCAT-Basic library, which provides function blocks and functions for engineering, mathematics, string handling, time/date and much more.&#xA;There is only a small problem with using the OSCAT-Basic library in TwinCAT – there is a broken reference in it!&#xA;What follows is a guide on how you can fix this so that you can fully utilize this library in TwinCAT.&lt;/p&gt;</description>
    </item>
    <item>
      <title>61131-3 PLC on the cheap</title>
      <link>https://www.sagatowski.com/posts/61131-3_plc_on_the_cheap/</link>
      <pubDate>Sun, 06 Nov 2016 00:00:00 +0000</pubDate>
      <guid>https://www.sagatowski.com/posts/61131-3_plc_on_the_cheap/</guid>
      <description>&lt;p&gt;3S-Smart Software Solutions has since pretty long had a Raspberry Pi (RPI) target image available for their CODESYS runtime.&#xA;The intention was to create something that you could buy very cheap, primarily for students and such to learn how to program 61131-3.&lt;/p&gt;&#xA;&lt;p&gt;As I&amp;rsquo;m primarily working with TwinCAT 3, which is based on CODESYS, I&amp;rsquo;ve been thinking about building a really cheap 61131-3 compatible PLC based on the RPI and the CODESYS target.&#xA;I didn&amp;rsquo;t just want it to be one board laying around in my home, but I also wanted it to have the &amp;ldquo;industrial&amp;rdquo; feeling, and luckily I found a perfect development board + case for me to initialize the project.&#xA;Now that it&amp;rsquo;s finished, I have a PLC running an EtherCAT master in the CODESYS runtime for almost no money at all.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
