-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improved grammar, clarity, conciseness and accessibility
- Loading branch information
1 parent
df02e07
commit 0ab13e9
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
# Interacting with PLC Symbols | ||
|
||
After defining the symbols we can now begin interacting with them in C# .NET. | ||
Now that we’ve defined the symbols, we can begin interacting with them in C# .NET. | ||
|
||
In this section, we’ll leverage the [.NET Dynamic Language Runtime (DLR)](https://learn.microsoft.com/en-us/dotnet/framework/reflection-and-codedom/dynamic-language-runtime-overview) to create dynamic objects that represent each PLC symbol. These generated objects mirror the structure and data of the symbols on the PLC, including standard IEC61131 types defined in the PLC. For instance, the PLC symbol `"MAIN.nValue"` is accessed as `MAIN.nValue` in C#, allowing seamless interaction with your PLC's variables. | ||
In this section, we’ll use the [.NET Dynamic Language Runtime (DLR)](https://learn.microsoft.com/en-us/dotnet/framework/reflection-and-codedom/dynamic-language-runtime-overview) to create dynamic objects representing each PLC symbol. These objects mirror the structure and data of the symbols on the PLC, including standard IEC 61131 types. For example, the PLC symbol `"MAIN.nValue"` can be accessed as `MAIN.nValue` in C#, allowing straightforward interaction with your PLC’s variables. |