Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jun 18 19:52
    OGKamu starred TcOpenGroup/TcOpen
  • Jun 18 17:31

    TomKovac on TcoSequencerTestsMoved2PLC

    TcoSequencer Plc executed tests… (compare)

  • Jun 18 14:58

    TomKovac on TcoSequencerTestsMoved2PLC

    TcoSequencer PROTECTED OnRestor… (compare)

  • Jun 18 13:59

    TomKovac on TcoSequencerTestsMoved2PLC

    TcoSequencer Plc executed tests… (compare)

  • Jun 18 11:50

    TomKovac on TcoSequencerTestsMoved2PLC

    TcoSequencer Plc executed tests… (compare)

  • Jun 18 06:13
    kurogane96lua starred TcOpenGroup/TcOpen
  • Jun 17 15:50

    TomKovac on TcoSequencerTestsMoved2PLC

    sync Merge branch 'dev' into feature… tests T500-T504 and 5 more (compare)

  • Jun 17 09:14
    PTKu synchronize #186
  • Jun 17 09:14

    PTKu on 185-Implement_task_recorder_with_logic_compiler

    wip (compare)

  • Jun 16 15:38
    PTKu synchronize #186
  • Jun 16 15:38

    PTKu on 185-Implement_task_recorder_with_logic_compiler

    wip Merge branch 'dev' into experim… Add documentation for security … and 3 more (compare)

  • Jun 16 12:11
    runtimevic commented #178
  • Jun 16 11:18
    jozefchmelar commented #178
  • Jun 16 06:02
    jozefchmelar commented #178
  • Jun 15 16:19

    DejanMilicic on 169-RavenDB_repository_adapter

    switching to in-memory ravendb … Queryable implemented FilteredCountNvi (compare)

  • Jun 15 10:25
  • Jun 15 10:23
    royAbl starred TcOpenGroup/TcOpen
  • Jun 15 09:45
    ebw44 starred TcOpenGroup/TcOpen
  • Jun 15 09:12

    PTKu on 188-Add_documentation_for_security

    (compare)

  • Jun 15 09:11

    PTKu on dev

    Add documentation for security … (compare)

Jokinko
@jozefchmelar
Hello!
Runtimevic
@runtimevic
Hello Tomkovac, my name is Víctor, I think I can help develop the motion PTP axis for twincat 3...
Runtimevic
@runtimevic
Hello, I think that all the components should have a certain structure, for example like the motion PTP axis that I have sent to Tomas
estructure components: config o settings, status, commands, diagnosis o error, etc...
Runtimevic
@runtimevic
.- Config o settings,
.- Status,
.-Commands,
.-Diagnosis o error,
.- Etc...
example:
stControl: ST_AxisControl;
stStatus: ST_AxisStatus;
stConfig: ST_AxisConfig;
stError: ST_AxisError;
stInputs: ST_AxisInputs;
Peter
@PTKu
@runtimevic, these are important points. Some of the topics were addressed earlier. I am opening the discussion on this here: https://github.com/TcOpenGroup/TcOpen/discussions/61 there are also some info about the ideas incorporated so far.
Runtimevic
@runtimevic
@PTKu, I have already read all this and it is clear,
I mean we should have a clear and well defined PLC level structure

FUNCTION_BLOCK PneumaticCylinder EXTENDS TcoCore.TcoComponent, IMPLEMENTS IPneumaticCylinder
VAR_INPUT
inHomeSensor : BOOL;
inWorkSensor : BOOL;
END_VAR

VAR_OUTPUT
outMoveHomeSignal : BOOL;
outMoveWorkSignal : BOOL;
END_VAR

Peter
@PTKu
@runtimevic could you sketch an idea either in discussion or in a PR, that we can discuss?
Runtimevic
@runtimevic
what I have put above for example is a starting point:
.- Config o settings,
.- Status,
.-Commands,
.-Diagnosis o error,
.- Etc...
example:
stControl: ST_AxisControl;
stStatus: ST_AxisStatus;
stConfig: ST_AxisConfig;
stError: ST_AxisError;
stInputs: ST_AxisInputs;
that's why I sent it to Tomas, so that he could see how I think it should be a component with its well-defined structure and grouped with its data grouped by its category
That is why I also said that it is the component itself that must have its diagnosis and errors, but of course beforehand you have to define some basic structures for all the components, I think it is a good idea as a starting point for each component and that all the components have the same types of groups
Peter
@PTKu
I understand that. It is all good. It is just that info here might be lost after some time and we will lose track... it is better if we can keep it directly in discussions or issues on GH. You may update the document https://github.com/TcOpenGroup/TcOpen.Documentation/blob/dev/articles/Conventions/Conventions.md and PR that (it is in the documentation repo)
Runtimevic
@runtimevic

I understand that. It is all good. It is just that info here might be lost after some time and we will lose track... it is better if we can keep it directly in discussions or issues on GH. You may update the document https://github.com/TcOpenGroup/TcOpen.Documentation/blob/dev/articles/Conventions/Conventions.md and PR that (it is in the documentation repo)

@PTKu , All this of the conventions is very good, but I think that at this point you have to go deeper and make a basic structure grouped by classes for the proper functioning of the components and that they can also work by themselves,

Thomas who has seen the PTP shaft structure that I propose to also tell your opinion....
TcOpen Conventions 0.3 version : structure components proposal
Peter
@PTKu
The structure you propose seems good to me... we will need to have it written somewhere for the others as a reference. If you can write it down please in the conventions (later we can move it in a separate document) then we can have single point to look into. We will need to prototype more components to understand that the structure is abstract enough, then we can enforce the structure in the TcoCore.TcoComponent (abstract base of all components).
Runtimevic
@runtimevic
The structure you propose seems good to me... we will need to have it written somewhere for the others as a reference. If you can write it down please in the conventions (later we can move it in a separate document) then we can have single point to look into. We will need to prototype more components to understand that the structure is abstract enough, then we can enforce the structure in the TcoCore.TcoComponent (abstract base of all components).
@PTKu , I have written it to you here, I don't know if you like it here, or should I have made a pull request first?
https://github.com/runtimevic/TcOpen.Documentation/blob/dev/articles/Conventions/Conventions.md
Peter
@PTKu
@runtimevic We will need to describe in more detail what those items should represent... I will try to write down something... then we discuss...
RGrabichler
@RGrabichler
Hallo Guys,
I tried to follow the five steps, "how to get started with tcOpen" and got the following msg
Peter
@PTKu
image shows some browser with duckduckgo (great search engine, I use it personally too :))
@RGrabichler we are fixing some issues with the build script right now... if you are getting errors there just give us a moment to fix it... I will notify you when done
RGrabichler
@RGrabichler

Error in task CopyInxton. Exec: Error executing command
& $dotnet restore TcOpen.build.slnf

.

Error: 12.05.2021 20:40:52:

  • ~~~~~~~~ [<<==>>] Exception: Assert: Call stack was corrupt. Expected copyinxton, but got nugetrestore.
    build.ps1 failed
ok @PTKu
Peter
@PTKu
if you are getting errors there it should not be a problem... provided that you get something like this at the end https://github.com/TcOpenGroup/TcOpen/blob/initial-dev/assets/pics/build.png
successul build
ahh...
no there is something else as well
RGrabichler
@RGrabichler
what i posted, are the last lines
Peter
@PTKu
yes... right... let us fix it will tell when ready... then we will check again
RGrabichler
@RGrabichler
ye thanks
Peter
@PTKu

Build script should be fixed on this end...
There are some updates to readme:

Use this if you have VS2019 Professional edition...

cd your_tcopen_folder
.\pipelines\runbuild.ps1 -properties @{"buildConfig" = "Debug";
                                      "isTestingEnabled" = $false;
                                      "msbuildVerbosity" = "minimal";
                                      "publishNugets"= $false;
                                      "updateAssemblyInfo" = $false;
                                      "msbuild" = "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MSBuild.exe";
                                      "dotnet" = "C:\Program Files\dotnet\dotnet.exe";
                                      "devenv" = "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.com"}

Use this if you have VS2019 Community edition...

cd your_tcopen_folder
.\pipelines\runbuild.ps1 -properties @{"buildConfig" = "Debug";
                                      "isTestingEnabled" = $false;
                                      "msbuildVerbosity" = "minimal";
                                      "publishNugets"= $false;
                                      "updateAssemblyInfo" = $false;
                                      "msbuild" = "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe";
                                      "dotnet" = "C:\Program Files\dotnet\dotnet.exe";
                                      "devenv" = "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\devenv.com"}
Peter
@PTKu

Hi guys! We are working on moving from AzurePipelines to GitHub Actions. If you are experiencing issues with building the repo, report here please.

Runtimevic
@runtimevic
Hello, Hi,
create a Cylinder proposal STRUCT......
proposal of component structure, for example the cylinder component has been chosen, but the PTP axis could also have been made, I hope this helps to make everything clearer ...
Runtimevic
@runtimevic
Hello, new proposal component STRUCT...
FUNCTION_BLOCK Cylinder IMPLEMENTS ICilinder
VAR_INPUT
Config : ST_Cyl_Config;
AutoControl : ST_Cyl_AutoControl; // Control signals from internal automated logic
ManControl : ST_Cyl_ManControl; // Control signals from HMI
END_VAR
VAR_IN_OUT
IO : ST_Cyl_IO; // Contains IO based in & outputs
END_VAR
VAR_OUTPUT
Status: ST_Cyl_Status; // I personally think DIAG can be embedded int the status struct, like so;
// Status.Diag.CylHealth
// Status.Diag.Error
END_VAR