The diagram below illustrates some challenges we have in BSA – how does things glue together ? The small diagram have a single class “Customer”, a small state diagram and a Data Table – all providing different part of an application. Class as an example is a declaration of a “datatype” with attributes, methods and…
The diagram below show two sub-diagrams. Sub_Diagram1 is a standard function call while Sub-Diagram2 have multiple input signals each connected to a specific method in the diagram. Both are legal drawings “as is”, but they have conflicting precentation needs. In “Sub_Diagram1” is is natural to assume that we call a function “Sub_Diagram1”, while on Sub-Diagram2…
Copy & Paste is finally working as they should. BSA allows you to draw duplicated tags, but the compiler will raise it as an error, so paste do not change tag names like the “Start_68” below (yet) – I am not sure I want it to either because design and coding are different tasks and…
The diagram below is an “abstracted SDL” – or simplified SDL if you like – it is a flowchart with SDL heritage that is a very good way of writing a visual specification assuming you have a tool that support it. This is at core in PLD. This exact example send a message and wait…
One of the upcoming features is the capability to import C/C++ code into a BSA project – correction I only want to be able to read C/C++ so I can set up the BSA Repository to generate code that uses an external C/C++ library. This is one of many important features as you integrate high-level…
Fork and Join are part of UML State diagram heritage that I imported into PLD. The example below show a potential usage to take a signal, duplicate it to three threads and wait until they all are finished before you continue. Fork and Join are drawn as bars that can be horisontal or vertical –…
I am experimenting a bit with C++/PScript coding in PLD and you can see the mock-up below where I create 3 math functions. The diagram is named “Math” so the functions are Math.Pow2, Math.Abs and Math.Sin – two of them in C++ and one in PScript. Assuming the target is C++ you can add C++…
I am getting closer to finishing a Beta version of BSA as a pure Modeling tool. It helped a lot starting to use BSA on a PLC project and the visual dictionary UI is a step in the correct direction. What you see below is one of my remaining bugs. I removed connection points after…
The Dictionary part of BSA is quite important as your project grows because it is instrumental in keeping overview and re-using components. The content is always the same, but I decided that I needed at least two precentations of the Dictionary content that is selectable by buttons on top of the Dictionary folder itself. You…
BSA contains a build-in component “Communication Link” and I wanted to see how it would be to code this manually in BSA. As you code you can chose to code modules in target language , or you can code components in BSA itself as we do in this example. See discussion below the diagram. In…