When a variable name contains TO the syntax highlighting will interpret and highlight it as a function.

Could you add support for the AWL extension? This is what Siemens S7 exports STL as.

The link to this repository in the extension details page appears to be broken, causes a "this file needs a app" dialog. I haven't gotten that on anyone else's extensions.

Is it possible to split editor to 2 sections, like Visual Studio does?
This would be a step closer to separate Declaration from Definition.

Current version of README file is autogenerated. Need an attention.

• Add screenshots of highlighted ST code
• Add installation istruction
• Add language description

With the 1.9.0/1.9.1 SymbolProvider changes:

1. may take excessive time for malformed comments/quoted strings in a VAR(_x) block
2. fails to mark CONSTANT variables
3. may show nonexistent '' variables from final comments or from comments separated from previous variable by two line breaks.

I will post a PR shortly.

With issue 1 under control, I was able to open a 32,000 line CoDeSys EXP file, and have a presentation of the approximately 4,000 symbols in under 2 seconds.

VAR and END_VAR incorrectly scope when run in to other identifiers in certain orders

VAR does not validate word break at end, END_VAR does not validate work break at either end.

VAR_x seem to be same as VAR

Looks like the \b is missing from the end of both the begin and end clauses.

The current STDocumentSymbolProvider (outline and breadcrumb feature) is unaware of comments and text strings, and will 'detect' symbols where none exists, and sometimes fails to detect them over small syntactical issues. It doesn't include global VAR's in addition to some issues with VAR's in general (modifiers). It also doesn't provide the data needed for breadcrumbs to work correctly.

It is a great start, though. I have been working on improving it for a few days, and may have drastic improvements done in a few more days.

I'm really interested in getting this to work in Visual Studio and not Visual Studio Code. Can anyone help me with that?

There are a lot of them. This is going to be a most growing part.

Note we only place here non math and arithmetic functions.

The document format feature change the duration literals to capital letters but according to IEC 61131-3 (and us) they should be in small letters. Example:
T#1s becomes T#1S
T#1ms becomes T#1MS

When formatting a file spaces are added where they shouldn't be added. A couple of examples:

Before a comment block
(* bla bla *)
becomes
<space>(* bla bla *)

Before and after ':=' and ':' when they are surrounded by tabs as well as after comments at end of a line
When you have something like this with tabs after the variable, :, type and :=:
VARIABLE_X<tab>: DINT := 0; (* comment *)
becomes
VARIABLE_X<tab><space>: DINT := 0; (* comment *)<space>

Hi team,

Just wonder if this plugin works for Beckhoff Structured Text codes?

Thank you!

Hi,
when i open the st code in vscode the auto keyword capitalizer is capitalizing also inside of the comments.

Hi,

Is it possible to debug the code somehow?

Hello,
Are they contemplated to open with vscode and the extension Structured Text language Support the Twincat 3 blocks *.TcPOU, *.TcDUT, etc...?
thanks you.

According to the IEC standard comments shall be surrounded by '(' and ')', this extension however uses '//' for line comments. If there are companies that deviate from the standard and actually use '//', perhaps this could be added as a configuration item?

Hello,
I have found if there is nested comment like:

(*
		bAddress				: BYTE;
		bLength				: BYTE; (* size of the data *)
		dwID				: DWORD; (* 32 bit long ID *)
*)

because of the first *), the rest of the commented code won't be seen as commented.
Could it be possible to fix this ?
Thanks
Edit: add image for better understanding:

The notification "This file not a structured text language!" keeps appearing everytime I change files for example python -> StCode file and vice versa. Can you make a configuration parameter for this or delete it completely?

$ node ./node_modules/vscode/bin/install
Detected VS Code engine version: 1.52.1
Found minimal version that qualifies engine range: 1.52.1
Fetching vscode.d.ts from: https://raw.githubusercontent.com/Microsoft/vscode/ea3859d4ba2f3e577a159bc91e3074c5d85c0523/src/vs/vscode.d.ts
Error installing vscode.d.ts: Error: read ECONNRESET
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Hi,
first of all, good job so far. I have found couple of things that are not working with my code.

For some reason, I might have configured vscode wrong but i cant get the syntax higlighting to work.

• TRUE is not higlihted

Also it has trouble dealing with brackets of called functions:

• the AND NOT and OR operators are not higlighted

Also I cant get the AutoFormat command to work.

":=" assignment operator should also be highlighted

CLK operator should also be highlighted

I think my vscode is somehow overriding the colors as the syntax highlighting doesn't look the same as in your examples.

It would also be good to choose our own prefixes like "v" for local variables and "p" for parameters. you could put that in the config json.

Thanks

In some themes, defaults included, the logical operators are not coloured.

To solve this I do one of the following:

• Change keyword.operator.logical.st to keyword.operator.logical.python in st.tmLanguage.json.
• Add keyword.operator.logical.st to the same block with keyword.operator.logical.python in dark_vs.json.

The first solution is not correct because this is not a python extension. I'm not sure why python is the only one that gets called out for clouring in the theme.

The second one is more proper but only affects the 1 theme and isn't something the extension can solve on it's own.

Another ST extension uses support.class.collection.st which I don't think is correct either.

Pretty minor issue and I have no idea how to fix it properly but would be nice to get it highlighting in all themes.

The semicolon(;) in REPEAR template should be placed after the END_REPEAR rather than the UNTIL expression. I tried this on both CODESYS V3.5 and Beremiz.

Hi Serhioromano,

I've also found an issue with the ** which is automatically changed to * *. Is there also an option, that you fix this?

By the way I have more topics for your grandious extension but I don't know if I can ask here for all these stuff and give you tasks, but I can't realize an extension by my own. Is there any interest from your side to realize some more stuff in this extension or should it be an running version and thats it?

Thanks for all your help and best regards
Chris

The formatter (capitalizer) has a couple issues, and exposes a grammar issue.

TYPE Bob : (* test *) STRUCT
        A, B : INT; //test
        b : INT; //test
    END_STRUCT
END_TYPE

(* Bool Word Struct Constant 

when formatted:

Note there are multiple issues.

1. It capitalized a broken comment. The comment doesn't end, and that lack of an end trips up the regex used to detect keywords, while ignoring comments and quoted strings.
2. It thought the start of the comment was a parameter list for a function call or operator END_TYPE so it moved it. 'keywords' and the 'end' block keywords should be excluded from this treatment.,
3. The TM grammar changed the scope of the keyword END_TYPE when it has a parenthesis behind it. Since END_TYPE is a rigid keyword, it should appear very high in the processing in the grammar file, above anything that utilizes a more generic form.

The VAR_ keywords, but not VAR or END_VAR, seem to be missing from the capitalization behavior. This is not shown above.

Нужно тут выписать все правила которые нужно проверять и их чекать. Можешь добавить в комменте что ты думаешь нужно проверять, я добавлю в список сюда.

• - Переменная ни где не используется
• - Переменная не определена
• - Объявление не закрыто ;

Like #10, I would like to suggest getting rid of the auto inserts of most all keyword pairs. Only happens when they are entered in all uppercase, but that's how I am used to typing them, even though CoDeSys will automatically upper case them for me. This would include PROGRAM, FUNCTION, STRUCT, TYPE and ACTION at least that I have found. I think they cause more problems. Snippets are the way to go. They could use some improvement though.

Snippets prefixes should be unique for each snippet, so that a user can determine a precise input for a specific snippet. For instance, 'func' is used for both FUNCTION and FUNCTION_BLOCK. I know I can type 'func' and press tab and I will get the snippet for FUNCTION, but getting to FUCNTION_BLOCK will require navigation of the intellisense menu. It should just be 'down' one, but that's not certain. Instead a prefix of 'funcb' would be enough. The same would hold for FOR and FOR BY, and all the VAR's

I am writing a TwinCat 2 project ,and the IDE is so hard to use, can use this and how ? thanks.

Не совсем уверен что мы это осилим. Хотелось бы анализ и подчказывать какие есть переменные у фукционального блока. Что бы когда точку нажимаешь, выпадали именно эти переменные.

In the below example, one of the function calls doesn't color or scope as a function call. I can see from the syntax file that this is because of overzealous capture of 'to' instead of hard coding all the known data type converters with something like DWORD_TO_(?:BYTE|WORD|INT|DINT) etc... Otherwise you will scope and theme the invalid DWORD_TO_DWORD

	IF Engine_OilPres_kPa >= 65534 THEN
		EngineOilPresMsg := SEL( Engine_OilPres_kPa = 65534, '*N/A*', '*ERR*' );
	ELSIF DisplayUnits_Mgr.EngUnits = 1 THEN
		EngineOilPresMsg := DWORD_kPa_TO_STRING_kPa( Engine_OilPres_kPa );
	ELSE
		EngineOilPresMsg := DWORD_kPa_TO_STRING_bar_2d( Engine_OilPres_kPa );
(*	ELSE
		EngineOilPresMsg := SEL( DisplayUnits_Mgr.EngUnits = 1, DWORD_kPa_TO_STRING_bar_2d( Engine_OilPres_kPa ), DWORD_kPa_TO_STRING_kPa( Engine_OilPres_kPa ) ); *) (* Doesn't Work! causes access violation *)
	END_IF
(*	EngineOilPresMsg := SEL( Engine_OilPres_kPa >= 65534, SEL( DisplayUnits_Mgr.EngUnits = 1, DWORD_kPa_TO_STRING_bar_2d( Engine_OilPres_kPa ), DWORD_kPa_TO_STRING_kPa( Engine_OilPres_kPa ) ), SEL( Engine_OilPres_kPa = 65534, '*N/A*', '*ERR*' ) );*)

When formatting several missing features poped up

Two important rules from PLCopen.org:

• No space before semi-colon ';'
• No space before colon ':' . One space after if not located at line end

Example 1:

VAR_INPUT
test: BOOL:=TRUE;
testNumberTwo:    BOOL   :=    TRUE   ;

becomes:

VAR_INPUT
test: BOOL := TRUE;
testNumberTwo:    BOOL   :=    TRUE   ;

but should be:

VAR_INPUT
	test: BOOL := TRUE;
	testNumberTwo: BOOL := TRUE;

or (maybe via setting):

VAR_INPUT
	test: BOOL		:= TRUE;
	testNumberTwo: BOOL	:= TRUE;

Example 2:

CASE test OF
	1   :
		// something
	2:
		// something

becomes:

CASE test OF
	1   :
		// something
	2 :
		// something

but should be:

CASE test OF
	1:
		// something
	2:
		// something

Example 3:

(*Comment*)
IF (something) THEN (*Comment*)

becomes:

(*Comment *)
IF (something) THEN (* Comment *)

but should be:

(* Comment *)
IF (something) THEN (* Comment *)

Issue

On this line change csb to csa:

I don't not know if this is possible in VS Code to fix:

After typing (, the ) is auto inserted past the cursor, so if the next key is * for a multi line comment, a matching * should be auto inserted after the cursor before the ) so the result becomes (*|*) (where the | is the cursor).

Maybe the same thing could be done for /*, but there you would need to do the */ after the * in /* is typed.

Right now it is for *_TO_* to highlight function like BOOL_TO_REAL. CСгккуте упуч can highlight anything. Make it more restrictive like (BOOL|REAL|TIME)_TO_(BOOL|REAL|TIME).

Hi serhioromano,

I am using your program and it works really nice, but I have an issue using the formatter. How can I set um, that <> isn't change to < >?

Thanks at first and BR
Chris

Often times in robotics / automation the term TCP is used to abbreviate "Tool Center Point".

However, this conflicts with the TCP ... END_TCP auto-completion.

I notice that code is auto-created the instant I type TCP in all upper-case, regardless of what follows.
I am requesting that the auto-completion of TCP ... END_TCP be made optional.

This would save me some sanity and would be greatly appreciated!

For example, I desire to type TCP_X (in general TCP_<>) without a TCP ... END_TCP block getting auto-created.

Thank you for your consideration.
Thank you for your VS code extension. I really appreciate what you have created here!

It doesn't seem like these Keywords are supported, or at least they dont work consistently.

• END_PROPERTY
• SET (For Property)
• GET (For Property)

Is it possible to add support for CLASS / END_CLASS, especially in the context of the outline feature?
I tried it myself and added CLASS / END_CLASS wherever FUNCTION / END_FUNCTION is used, but I broke the syntax highlighting feature and did not get the outline feature working.

I work on some programs for AX9 PLC and the extension of program files is .vpl . It will be nice that the extension could be configured to support highlight for different file extensions.

Hi @philippranzhin,

You were a collaborator for another ST extension. You had few good ideas. I invite you to join this extension development. Please post your issues here and I'll try to improve extension.

typing in VAR causes END_VAR to be instantly inserted, yet there is more to type, such as _INPUT.

Code snippets already exist to choose from, but the auto insert of END_VAR prevents them from being selected successfully, because the END_VAR that was auto inserted gets left after selection. The code snippets works successfully if you type 'var' or stop before typing the R and make the selection then.

The grammar has escape patterns for quoted strings, indicated as \\\\. in the grammar. These would be C style escapes, and they do not seem to be part of the IEC 61131-3 standard.

For reference:
https://www.fernhillsoftware.com/help/iec-61131/common-elements/literals-string.html

Upper or lowercase letter are allowed.

But I see no support for them in the grammar.

Regarding implementation, from what I can tell, invalid combinations are not supported, and for instance in CoDeSys, they are flagged as an error.

Sample presentation (similar to CoDeSys)

Current grammar: (gets out of sync)

Do your environments actually support C style escapes, or is this a mistake? This would be a concern for cross platform compatibility of code, if all systems do not utilize a single standard, there are already enough extensions to the standard to make things difficult.

These character escapes also appear in the comment sections of the grammar. They could potentially cause a user unexpected issues:

/*///////// this comment doesn't close \\\\\\\\\*/ oh no this is still comment...

I don't know of any systems that allow this, so I don't think this is correct.

Function name or maybe other place contains a keywords will be auto formatted to Upper characters.
for example:
FUNCTION test_return_exit will be auto formatted to FUNCTION test_RETURN_EXIT.

Is it a possibility to add a setting to exclude the ST language support from different files or directories.

The data type WORD and its relatives are not scoping/coloring.

I noticed in the tmLanguage file that instead WORLD appears. Maybe your ST variant supports some kind of WORLD type I am not aware of, so I have included a REGEX for it here:

\b(BOOL|BYTE|(?:D|L)?WORL?D|U?(?:S|D|L)?INT|L?REAL|TIME(?:_OF_DAY)?|TOD|DT|DATE(?:_AND_TIME)?|STRING|ARRAY|(?:POINTER|REF)\\sTO|ANY)\b

If you did not intend WORLD as a type, remove the L? in WORL?D. :)

I also included any number of white space between POINTER or REF and the TO. I also included TOD and DT because CoDeSys supports those as aliases to TIME_OF_DAY and DATE_AND_TIME respectively.

Hi @Serhioromano,
to get nice and structured text, I need a linter in this extension. So in best case I want some text in the VS console, when naming of a variable is not right. Don't know if you can implement it? If you can do it I can put all linting-Tasks in a tabular here.

Best regards and stay safe
Chris

Even though we are supposed to use capital letters in keywords such as IF, ELSIF etc we have a lot of files where these are written in lower case (if, elseif...). However the syntax highlighting only check for these words in capital letters.