## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
• 11:43
kuh0005 labeled #407
• 11:43
kuh0005 opened #407
• 04:58
Talbourdet starred TcOpenGroup/TcOpen
• 03:04
jerrycchang starred TcOpenGroup/TcOpen
• 01:07

github-actions[bot] on GH-2368277188-0.6.0-alpha.836

• May 22 15:42

github-actions[bot] on GH-2364765759-0.6.0-alpha.836

• May 21 18:39

TomKovac on 381

box terminal viem added Merge branch 'dev' into 381 iXlinker update via locally cre… (compare)

• May 21 04:22
Helmoes starred TcOpenGroup/TcOpen
• May 21 01:06

github-actions[bot] on GH-2361345942-0.6.0-alpha.836

• May 20 01:06

github-actions[bot] on GH-2355390986-0.6.0-alpha.836

• May 19 01:11

github-actions[bot] on GH-2348992869-0.6.0-alpha.836

• May 18 13:18

github-actions[bot] on GH-2342193914-0.6.0-alpha.836

• May 17 05:41

github-actions[bot] on GH-2336395637-0.6.0-alpha.836

• May 17 01:05

github-actions[bot] on GH-2335511204-0.6.0-alpha.836

• May 16 11:13

github-actions[bot] on GH-2331369537-0.6.0-alpha.836

• May 16 10:45

PTKu on dev

• May 16 01:24

github-actions[bot] on GH-2329013906-0.6.0-alpha.835

• May 15 01:32

github-actions[bot] on GH-2325645245-0.6.0-alpha.835

• May 14 12:30

github-actions[bot] on GH-2322483743-0.6.0-alpha.835

• May 13 06:18
mgvora forked
Runtimevic
@runtimevic
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...
Peter
@PTKu
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
Peter
@PTKu

# Hi everyone! At this point, the repo is quieter than usual. We are working to make our legacy libraries compatible with TcOpen at this time, we also add new features and fixies. Stay tuned we will come back soon!

RGrabichler
@RGrabichler
Hey, i noticed something with the Inxton Compiler
when creating compiling, there appear two erros
there is a using directive: "using PlcTestConnector.Properties; , whicht doenst exit in this namespace
Twincat on 4024.20
when reusing "inxton -Vortex-Build", both errors appear again.
Peter
@PTKu
@RGrabichler in which project did you get those error messages? This may happen int older format of .csproj... also is the connector project named [PlcProjectName]Connector?
RGrabichler
@RGrabichler
this is my most recent test project
Peter
@PTKu
can you send also Connector project file (snapshot)
RGrabichler
@RGrabichler
Peter
@PTKu
snapshot of expanded connector project from solution explorer?
RGrabichler
@RGrabichler
like this?
Peter
@PTKu
Yes! thanks... sent you invite to teams
Peter
@PTKu
Looks OK... try to update TcOpenConnector to v 0.4.2-alpha.557 via NuGet manager... that should update also the compiler
Peter
@PTKu
Delete Properties/Localizations.resx file and run the builder again, that will resolve the issue. The problem is that the localizations were generated with incorrect project name the first time.
RGrabichler
@RGrabichler
thanks for the fast help!
this is the difference after deleting and running Inxton Compiler again