Yes,
I know,
This guide is epic.
Sorry

But FSD v2 has accumulated so many functions by now, that this size is unavoidable.
Writing it took me several days.
From the morning to deep in the night.
Also English is not my native language.

So please be lenient with me, if you find a brain fart of mine in it.

Of course I will try to correct any mistakes you point out to me.

Yours truly
Ekuah

• Place down a programmable block. (will be called PB from here on)
  
• Load the script by selecting the block in the terminal GUI and click Edit and then Browse Scripts.
  
• The Fancy Status Displays v2 script should be in the list if you have subscribed to it.
  
• Select it, click Copy to editor than hit OK.

A single PB running Fancy Status Displays v2 can support multiple connected grids.

Caution when running multiple instances of Fancy Status Displays v2:

• when on different, non-connected grids It will run fine
  
  
• when on a single grid It will lead to issues.
  Don't do this. A single instance of FSD can control dozens of screens.
  
  
• when on different, but connected grids Special precautions have to be taken
  
  • (recommenced solution) Insert the line
    "FSD options:nosubgridLCDs"
    into the CustomData field of all the
    Programmable Blocks running FSD
  or
  
  • Change the FSD trigger word in the script
    from "ShowStats" to something different.
    So that every instance of FSD would react
    to other trigger words.
    (Caution, this can break the script!)

This script is for displaying certain information of various blocks on the any screen.
To define which information is to be shown you enter a list (a.k.a. Data-Set) into the the CustomData field of the block that provides the screen.
This can be any block that has a screen:

• LCDs
  
• Text panels
  
• Programmable blocks
  
• any Cockpit
  
• Flight seats
  
• Control stations

In the CustomData ShowStats indicate the beginning of the Data-Set.
This keyword tells the script to act on the screens of this block. Do a line break after it.
Caution:
Do a line break after it. ShowStats must stand alone in it's line.
Also observe the two capital 'S' in ShowStats.
This is one of the few keywords that is case sensitive.

Anything above ShowStats will be ignored and can be used for other purposes.

Into the next lines, you can type the list what should be displayed on this screen.

After the list you can close the Data-Set with EndStats
This was added for FSD being compatible to other scripts.
Caution:
The same rules as with 'ShowStats' apply to 'EndStats'.
EndStats must stand alone in it's line.
Observe the capital 'E' and 'S' in EndStats.

The basic Data-Set in the CustomData field of the block will be look like this:

Or when using with other scripts:

After the line with the ShowStats keyword you can start the list in the next lines defining what should be displayed on this screen.

You can use the full name of a block group:
(a partial name of a group will not recognized)
Displays all blocks contained in a group called "MyGroup".

Or you can use a part of the block name.
(the script searches for all blocks which contain the given string:)
Displays all blocks containing "Battery" (e.g.: Battery 1, Battery 2, Miner Battery)

The script will first try to find a block group with a matching name in all connected grids.
If that can't find any matches, it will try to find blocks with the string as part of the block name.
(Also in all connected grids.)

You can also string together different names with the '+' sign.
(the script make multiple searches for all blocks which contain the different strings:)
Displays all blocks containing ether "Battery 2" or "Battery 3"

Examples
Given are six batteries.
The 1st, 2nd and 5th battery are combined into a group also named 'Battery'.
The 1st, 3rd, 5th and 6th are located on the same grid as the PB.
The 2nd and 4th are located on a different grid than the PB.



Since the script looks first for the a group with the name 'Battery',
only the status of the 1st, 2nd and 5th will be displayed.
(The other batteries are not part of the group 'Battery')


Only the the status of the 3rd and 4th battery will be displayed.




Only the the status of the 5th and 6th battery will be displayed.
('Battery 3' is a part of 'Battery 32')



Only the the status of the 3rd, 4th, 5th and 6th battery will be displayed.
('Battery 3' is a part of 'Battery 32')






(* these blocks offer a second data source)

You can refine the search or modify the way something is displayed by using several modifier keywords.
These keywords must be separated from the Block/Group name(s) by a special character (lets call it the Separator). This can be ether a comma ',' or a colon ':' Upper / lower case of the keywords will be ignored.
(both work equally)

You only need the separator once.
There is no need to separate the keywords other than with a single space.
(both work equally)

Only the keywords after the Separator are recognized.
Keywords before the Separator will be ignored.
So you can use Blocks/Groups whose names match a keyword.
(Shows a Block/Group with the name "WideBar" with the modifier WideBar)

Only Blocks/Groups names containing the Separator will pose a problem.

like:
• "Thrustergroup:up"
  
• "Reactor 17,5"

Here are the Keywords that are recognized by FSD v2

• AddInfo
  
• AddSize
  
• AltCalc
  
• AltInfo=
  
• AltSymbol=
  
• AnalogBar
  
• BarColor
  
• center
  
• Clone:
  
• DigitalBar
  
• EndLine
  
• EndStats
  
• fastmode
  
• Filter(
  
• Fontsize=
  
• FrameColor
  
• Framerate=
  
• FSD options:
  
• Gap
  
• gfxEnd
  
• gfxStart
  
• Health
  
• IconColor
  
• IconCount=
  
• InfoColor
  
• Invert
  
• Layoutrate=
  
• left
  
• Length=
  
• NoCR
  
• NoGroups
  
• NoHeadline
  
• noIcons
  
• NoLineBreak
  
• NoNames
  
• NoPercentage
  
• NoScrolling
  
• NoStatus
  
• nosubgridLCDs
  
• NoSubGrids
  
• OnlySubGrids
  
• Optional
  
• Panel
  
• PercentColor
  
• Position
  
• Reference=
  
• right
  
• Scale=
  
• ScrollSpeed=
  
• sequence
  
• ShortBar
  
• ShowStats
  
• SingleIcon
  
• SmallBar
  
• SolidBar
  
• Sprite:
  
• SymbolColor
  
• TallBar
  
• Text:
  
• TextColor
  
• verbatim
  
• WideBar

The different modifiers will explained later.

You can narrow down the search by several methods.

By putting the block name in quotation marks
you will limit the search to block with exact name matches.
Will only show blocks with the name "Battery" (but not: Battery 1, Battery 2, Miner Battery)
There will also skips the search for groups. (since those require an exact name match anyway)

Adding the NoSubGrids keywords to prevent the search on subgrids
The keyword NoSubGrids will restrict the search to those blocks which are on the same grid as the programmable block running FSD v2 (PB).

Adding the OnlySubGrids keywords to restrict the search only on subgrids
The keyword OnlySubGrids will restrict the search to those blocks which are not on the same grid as the programmable block running FSD v2 (PB).

Adding the NoGroups keywords to skip the search for groups
The keyword NoGroups will ignore all groups in the search.

Examples
Using the situation from before, given are the six batteries.
The 1st, 2nd and 5th battery are combined into a group also named 'Battery'.
The 1st, 3rd, 5th and 6th are located on the same grid as the PB.
The 2nd and 4th are located on a different grid than the PB.



Only blocks with an exact name match will be shown.
In this case only the 5th battery.




Only blocks with an exact name match will be shown.
In this case only the 1st and 2nd battery.



Since the script looks first for the a group with the name 'Battery' and display only those blocks which are on the same subgrid as the PB, in this case the 1st and 5th battery.
(The other batteries are nether part of the group 'Battery nor on the same subgrid as the PB')
Will skip he search for groups and only looks for individual blocks with "Battery" as part of the name.
(Since all batteries have "Battery" as part of the name all of them will be displayed)
Will skip he search for groups and only looks for individual blocks with "Battery" as part of the name and are on the same grid as the PB.
(in this case the 1st, 3rd, 5th and 6th battery)


Only the the status of the 3rd battery will be displayed.
(since there is no Group named "Battery 2" and the 4th battery is on a different grid)




All the same. The status of the 5th and 6th battery will be displayed.
There is no Group named "Battery 3"
The 5th and 6th battery are on the same grid as the PB.
And 'Battery 3' is a part of 'Battery 32'



The status of the 1st and 2nd battery will be displayed.
The NoGroups is unnecessary.
(Since the use of quotation marks will automatically the search for groups)


Only the status of the 1st battery will be displayed.
(all other batteries are ether on a different grid or have no exact name match)

If a block with has multiple screens, you can define which information is shown on which screen.
By using the keyword Panel you will assign the following commands to a specific screen.
(Do a line break after it)
Shows you something at the first screen.

Shows you something different at the second screen and so on - you get the point.

Without this, everything will be shown on the first screen.
So can skip this if this block has only a single screen.

FSD v2 supports seven different display modes changing the way the information is displayed
These different modes are also triggered by keywords. Like in Refining the selection process these keywords must be separated from the Block/Group name(s) by the Separator character. Upper / lower case of the keywords will be ignored.

The (default) MultiIcon view
The Default view. Shows a line of icons representing each a single block individually.
Depending on how many blocks have to be displayed, the icons can take up several lines.




The SingleIcon view
Shows only a single icon as a summary, instead of each block individually.







The WideBar view
Shows a single wide bar as a summary, instead of each block individually.



The SmallBar view
Shows a single small bar as a summary, instead of each block individually.




The TallBar view
Shows a single vertical bar as a summary, instead of each block individually.




















The ShortBar view
Shows a single shorter vertical bar as a summary, instead of each block individually.









The NoIcons view
Displays the information only as a single textline without icons.

The bargraph display modes (SingleIcon, WideBar, SmallBar, TallBar, ShortBar and MultiIcon view)
normally segregate the bargraphs into bars.
There are the three ways to modify this behavior:

The default bargraph
Each single bar indicates a value of 10% (20% in SingleIcon and MultiIcon view). The remaining rest-value will be indicated as a partial bar.
The digital bargraph
Each single bar indicates a value of 10% (20% in SingleIcon and MultiIcon view). The remaining rest-value is rounded to decide if an additional full bar will be show or not.
The analog bargraph
The bargraph will be not segregated. Instead a single bar will be show. It's size and color will be proportional to the value.
The full bar
The is no real bargraph. Instead the area will be filled by a single bar. Only it's color will indicate the value.


The Invert option
Color of the bargraph itself usually changes from green over yellow to red.
On blocks with a critical low value the bar will start red at 0% and end green at 100%
(like the charge state of a battery)
On blocks with a critical high value the bar will start green at 0% and end red at 100%
(like the power load of a reactor)
The usage of the Invert keyword will flip this coloring scheme around.


The look of the vert. bargraphs can also be modified with NoPercentage and AltSymbol= keywords
NoPercentage
In the MultiIcon view you can suppress the percentage display with the keyword 'nopercentage'. Thisworks in the TallBar and ShortBar view too.

AltSymbol=
With the 'altsymbol=' command you can exchange the used symbol with one of the vanilla
Texture Sprites provided by KeenSWH.

Caution: The name of the used sprite should be put into quotations marks '"'.
Those two modifiers are not avaiable for the horizontal bargraphs, since these nether show a separate percentage number nor a symbol



Here are some of the vanilla Texture Sprites currently provided by KeenSWH
You can find the listing of the vanilla sprites here: github.com/malware-dev/MDK-SE/wiki/Sprite-Listing

In blocks with regular inventories you can refine the counting process by the usage of the filter option.
It's function have been expanded with the FSD subversion v37x.
The respective keyword is 'Filter('.

There are two different syntax version of this option.
One with only one filter condition:
And one with multiple filter conditions:
In the latter case, the first parameter must be the boolean operation that links the all filter conditions.
These can be:

• and (all filter conditions have to be met before the item is counted)
  
• & (same as 'and')
  
• or (one of the filter conditions have to be met before the item is counted)

The filter conditions are compared to the item types / namespaces.
You can find a list of the vanilla item types / namespaces here:
https://github.com/malware-dev/MDK-SE/wiki/Type-Definition-Listing#components

There are several available comparisons variants:

• +thingy (Item.Type must contain "thingy")
  
• -thingy (Item.Type must not contain "thingy")
  
• =thingy (Item.Type must be identical to "thingy")
  
• -=thingy (Item.Type must not be identical with "thingy")
  
• *thingy (Item.Type must end with "thingy")
  
• -*thingy (Item.Type must not end with "thingy")
  
• thingy* (Item.Type must start with "thingy")
  
• -thingy* (Item.Type must not start with "thingy")
  
• *thingy* (Item.Type must contain "thingy")

You have to choose one variant for each filter condition, but each condition can have a different variant.

Examples:
Counts only the volume of the ores in the blocks named Container

counts the volume all ingots except the stone-ingots (a.k.a. Gravel) in the blocks named Connector

counts the volume all ingots and all ores in the blocks named Refinery

The filter option string have be closed with a closing parentheses.

Normally the individual percentage values ​​and bar sizes in the bar graphs refer to the maximum value of the displayed unit. After that the average of the percentage values ​​and the bar sizes are calculated.
((Value 1 / Max_Value 1) + (Value 2 / Max_Value 2) +...+ (Value n / Max_Value n)) / n
This (old) calculation method can result in misleading bar sizes and values when using it on blocks with different maximum values.
(a 10% filled small reactor plus a 90% filled large reactor would result in a false combined 50% fill rate)

The AltCalc option
The old (legacy) method to calculate the average bar sizes and values should only be used on identical blocks. When averaging blocks with different maximum values the AltCalc keyword should be used. This will change the method of calculation to:
(Value 1 + Value 2 +...+ Value n) / (Max_Value 1 + Max_Value 2 +...+ Max_Value n)
Now even averaging blocks with vastly different maximum values will result in correct values and sizes.
The old calculation method is only left in for legacy reasons.

The Reference= option
With Reference= you can change the reference value for any block.
(Caution: only values > 0 are accepted)
This reference value has to given ether in liters, watts or watt-hours, depending on the used unit.

The Optional option
Some types of blocks have two different output modes displaying alternative data sources.
Batteries - Reactors - Hydrogen Engines - Refineries - Assemblers - Doors - Gates
By adding Optional to second data source will be shown.

Batteries, Reactors and Hydrogen Engines will switch from the 'power' load to the 'Fuel / Charge'.

Refineries and Assemblers will switch from the input inventories to the output inventories.

Doors and Gates will switch from the opening rate to the closing rate.




The AddInfo option
In old version of FSD you sometimes couldn't really distinguish which mode is shown.

In the MultiIcon view mode and the SingleIcon view mode you can add AddInfo to the options behind the Separator character.
That will help telling the two output modes (alternative data sources) apart, by putting one of the following small texts between the central symbol and the percentage value.

Thedefault info texts are:

• Charge / Load
  
• Fuel / Load
  
• Ores / Ingots
  
• Ingots / Items
  
• open / closed
  
• left / right
  
• Filled / occupied / empty

The AltInfo= option
You can define an alternative info text by using AltInfo= followed by the desired text.
In this case, you don't need to use the AddInfo keyword. The AddInfo option is activated automatically.
Caution:
Due to the limited space available, the info text should be kept short.

A specialty to the optional data sources are the many varieties of occupiable blocks.
Those can come with an own inventory:

• Beds
  
• Cockpits
  
• Control Seats
  
• Control Stations
  
• Crypods
  
• Flight Seats
  
• Passenger Seats

Without the Optional keyword the fill rate of the inventory will be displayed.
With the Optional keyword it will switch to the occupancy. 100% if the block is occupied, 0% if the block is not.

And then there are those blocks without an inventory:

• Benches
  
• Desks (with chairs)
  
• Toilets
  
• Bathrooms

Without the Optional our the Health keyword these wont be listed or displayed.
Only when you add the Optional keyword these will be listed/displayed as Cockpits.
As with the other occupiable blocks 100% means the block is occupied, 0% if the block is empty.

There are several options to spruce up the MultiIconview mode.

If there are more items than would fit in the width of the display, FSD will (in the default settings) display the items in several line. This line breaks can be suppressed by two methods.

The NoLineBreak option
When adding NoLineBreak behind the Separator, FSD will stop drawing icons at the end of the first line.

The noCR option
(this also works with all the other view modes)
Adding noCR behind the Separator will suppress the check if the end of the line is reached and will continue to draw even if it can't be shown anymore.

This is great way to 'squeeze' a last item into the line which would have been otherwise been mover to the next line.



The number of icons to be displayed can be adjusted in two ways.

The legacy method is done by just adding a number of # directly behind the block name you will set the number of icons to be displayed equal to the number of # used.

The # MUST be before the Separator (colon ':' or comma',')

The use of # directly behind the block name had lead to problems in some cases.
(Like when you had blocks with the names 'Thruster #1' and 'Thruster #2' and wanted to address them with 'Thruster #') In such a case use the IconCount option.





The new method uses the IconCount= option. It overrides the legacy method and ignores any # in the block name.
The integer number directly behind the = will set the number of icons to be displayed.
If you use 'IconCount=0' the number of icons will not be modified, but any # in the block name
will be ignored.
Caution: There has to be no space between 'IconCount', the equals sign '=' and the value.

If the number of icons to be displayed is higher than the number of blocks available, then the number of icons will be padded with missing block icons. (Red cross in a gray frame)

Both methods are a great way to highlight missing or destroyed blocks, which would be else be present


Bonus
The color of the frame around the bargraph indicates the status of the represented block

• Cyan means:
  Block is functional and working
  
  
• Dark Cyan means:
  Block is functional but not working
  
  
• Dark Red means:
  Block is non functional / damaged
  
  
• Gray with a Red Cross means:
  Block is destroyed or does not exist

The Health option
By adding ',health' to the options the additional bargraph will be displayed.

This bargraph indicates the integrity of the represented block.

This work with any block types.
No matter if the block type is supported or is unknown.



The AddSize option
Another additional information you can display in the default view mode are small indicators displaying the block size and their grid size.

The grid size is shown on the top right
and the bottom left corner.

• 1 big square indicates that it is large grid.
  
• 4 small squares mean that it is small grid.

If there are also block size variants available
(per given grid size), tiny letters on the top left and the bottom right corner indicate the variant.

• L stands for Large
  
• M stands for Medium
  
• S stand for Small

If a bargraph does not fill out the width of a display, and an identical bargraph would fit beside it, FSD will position the bargraphs in a line next to each other.

The EndLine option
Adding EndLine behind the Separator will prevent the positioning of the next bargraph next to the current one. Instead a new line below will be started.

The noCR option
As said before noCR also affects the bargraph view modes.
Adding noCR behind the Separator will suppress the check if the end of the line is reached and will continue to draw even if it can't be shown anymore.

Free positioning:
You can freely position all the icons, bars and texts with the Position(x,y) keyword.
The X/Y coordinates have to be separated with a comma and enclosed in round brackets.
Caution: There has to be no space between 'Position' and the opening bracket '('
This works with all the different display modes.
(The next item in the display list will be located on the left screen border again.)



Spacing between icons:
You can leave a gap between icons or bars that you have chained together with the '+' sign
This works only with in the default view mode

Apart from changing the font size, you can adjust the size of icons and the length of the bargraphs within certain limits.

The length of bargraphs can be adjusted with Length=(followed by a decimal number).
The used value will represent the length in pixels.
All bargraphs have different minimum lengths and length values below them will be ignored.
When not using Length= option or using it wrong the bargraphs will revert to their default length.
Those length are:
Caution: There has to be no space between 'Length', the equals sign '=' and the value.
From the scripts point of view the maximum length value would be 3.4*10^38.


The icon sizes in the MultiIcon view and the SingleIcon view can be changed by adding Scale=(followed by a decimal number) to the options set after the separator.
While the minimum scale is 0.5 , values below will be ignored.
It is highly recommended to keep the scale at 1.0 or above, because the readability decreases sharply below 1.
Caution: There has to be no space between 'Scale', the equals sign '=' and the value.
From the scripts point of view the maximum scale value would be 3.4*10^38.





Additionally in the MultiIcon view, the SingleIcon view, the NoIcons view and the just Text mode, you can set the the available width for the textlines with Length=(followed by a decimal number)

You can change the way the Textline (Headline) is displayed.
Headline modificators:
Caution: There has to be no space between 'Fontsize', the equals sign '=' and the value.

All modifiers can be combined with each other.

Center and Right work only with:
default view, SingleIcon, WideBar,
SmallBar and NoIcons views.
(there is no left/center/right on a vertical bar)

All other modifiers work with all display modes.

Additional text:
You can add a custom text to the textline / headline by using the Text: keyword.
Note the colon at the very end of the Text:

The Text: keyword must be the very last of the used keywords, because everything between Text: and the end of line will be used as text.

This can also be combined with NoHeadline option. Then only the characters after Text: will shown in the textline / headline.

When using just ,Text: without using any block/group name, only a simple textline / headline will be shown.
This can also be combined with Fontsize, left, center, right, Length= and individual coloring.
In those cases the modifiers/keyword must be placed between the Separator character and Text:

FSD can clone the text content of other displays. These texts can be fixed or could be generated by other scripts (like Automatic LCDs 2 by MMaster or Isy's Inventory Manager)

To select the text surface to be cloned, you address the display block by name, add the separator char and use the keyword Clone:.
(Caution: only text displays can be cloned, but not images or sprites)

If the block has more than one display surface and you want to clone from a different screen than from surface 0, then you can add the display number directly after the colon.
(Caution: There has to be no space between 'Clone' the colon ':' and the number)
(The surface count starts with 0)

The Position, FontSize and TextColor can be individually adjusted with the respective keywords.

Example:
This would clone the text contend of the first screen of the block 'LCD Panel' to the position (x=100 y=50) in an orange color with a font size of 0.5.


Hint: You can even clone the running status display of FSD itself onto any other display.

You can insert monospace graphics created with Whips image-converter:
The graphics section starts with:
,gfxStart(X-position,Y-position,fontsize)
The coordinates and fontsize have to be separated with commas and enclosed in round brackets.

gfxEnd indicates the end of the graphics section.

Caution: There has to be no space between 'gfxStart' and the opening bracket '('
Also there have to be a ',' or ':' in front of
'gfxStart' and 'gfxEnd'
The decimal point '.' can be used for all three values.
'gfxStart' and 'gfxEnd' are not case sensitive
You can find Whips image converter here: https://github.com/Whiplash141/Whips-Image-Converter

You can also build composite images out of the vanilla Texture Sprites provided by KeenSWH.
The command for this is:
,Sprite:"Name of the Sprite" X-position,Y-position width,height red,green,blue rotation

Caution: There has to be no space between 'Sprite' and the colon ':'.
Also there have to be a ',' or ':' in front of 'Sprite'.
The name of the sprite should be put into quotations marks '"'.
The decimal point '.' can be used for the position, height, width and rotational values.
The color components must be specified as integers with values ​​between 0 and 255.
'Sprite' is not case sensitive

Here are some of the vanilla Texture Sprites currently provided by KeenSWH
You can find the listing of the vanilla sprites here: github.com/malware-dev/MDK-SE/wiki/Sprite-Listing

You can define individual colors to every single element of every object on the screens.
Every color channel can have values between 0 - 255 so there are 16.7 million colors to choose from.

In the default view mode and the SingleIcon view mode the Texts, Icons, Percentage numbers, Frames and Bargraphs can be colored separately for single icons

By adding one or more of these keywords to the options behind the Separator character, the normal color will be overridden.


The RGB values have to be separated with commas and be enclosed in round brackets,
and have to be integer numbers between 0 and 255 (a.k.a. no floating point numbers)

Caution:
There has to be no space between '...Color' and the opening bracket '('








In the WideBar view mode and the SmallBar view mode only the Texts, Frames and Bargraphs can be colored separately, since there are no Icons or separate Percentage numbers are in these modes.

By adding one or more of these keywords to the options behind the Separator character, the normal color will be overridden.


The same rules about the RGB values, brackets, the missing pace between '...Color' and the opening bracket '(' etc. like for the default view mode and the SingleIcon view mode apply here too.


In the NoIcons view mode there is only the Headline to be displayed. So logically only TextColor(R,G,B) shows any result.


This also true when only using Text: after the Separator character without using any block/group name. (resulting in only a simple text line with the specified color)

You can assign several different display layouts to a single Screen and choose between them.
This way you can ether reduce the number of LCD Panels needed or greatly enhance the amount of information you can display with a given set of screens/panels.

To split the Data-Set into into different layouts, you encapsulate the relevant chunks each with ShowStats and EndStats.
Adding a number directly to ShowStats (within the same line but separated with a space from ShowStats) will indicate which layout is defined.
Hint:
'ShowStats' and 'ShowStats 0' mean the same layout and will indicate to the default display layout.

To change the display layouts, you have to define the sequence in which the layouts should be shown.
For this purpose (and many others) you can add a special keyword line starting with 'FSD options:' into the Custom Data field of the PB (running FSD v2) itself.
(you find more about this in the chapter Global Override Options)

The sequence is set by adding Sequence(layout sequence) to the 'FSD options:' line.
(since the PB has itself display panels, the 'FSD options:' line must be above any 'ShowStats' line)
This sequence will be valid for all displays controlled by this instance of FSD v2
If one of the layouts in the sequence is not defined in the Data-Set of a display, it will show the default layout (started by ShowStats or ShowStats 0).

The display layouts usually change automatically but can also be switched manually.
see the following chapter

You can manipulating the sequencer by starting the PB running FSD v2 with arguments.
(you find more about it in the chapter Controlling FSD v2 by running the PB with arguments)

There are four arguments influencing the active screen layout and the sequencing.
This will set the rate of changes for the screen layouts. (in changes per minute)
It will also override the default change rate or the rate set via FSD options:
A layout rate of 0 will stop the automatic change of layouts.

This will set the which screen layout will be displayed.
If this layout is not defined in a Data-Set the default layout will be shown.

This will switch to the next set of screen layouts.
If the last set was already displayed the layout number will wrap around to the first.

This will switch to the previous set of screen layouts.
If the first set was already displayed the layout number will wrap around to the last.

With a little trick, you can use one and the same layout on multiple positions of the sequence.
To so, add a additional 'ShowStats' line (with a different number) after the first 'ShowStats' line.
This trick is especially handy when having different counts of layouts in different displays.


Resulting outputs of the displays

You can overide individual LCD/Cockpit screen settings by using a special keyword line starting with 'FSD options:' in the Custom Data field of the Programmable block itself.
All keywords for this override options must be in a single line and this line must be located above an optional 'ShowStats' line or else the used keywords affect only the LCD panels of the Programmable block.

Avaible overide option keywords
Only 'FSD options:' is case sensitive. All other keywords for the overide options are not case sensitive. Different keyword can be strung together but must be seperated with ' ' , ',' or ':'
Caution: There has to be no space between the equal sign and 'Layoutrate' or 'Framerate'.

Options can be combined like in this example:

When using FSD options: the following keywords in the ShowStats section will act as toggle switches (a.k.a. inverting the setting again):

• optional
  
• addinfo
  
• addsize
  
• health
  
• noheadline
  
• nonames
  
• nolinebreak
  
• noscrolling
  
• nosubgrids
  
• nogroups

Example:

The programmable block running FSD v2 can be controlled via arguments:

• Open the terminal GUI, select the PB running FSD v2, type the argument into the textbox named 'Argument' and hit "Run".
  
• Select a button panel, sensor, timer etc. and in it's GUI, click "Setup actions", drag & drop
  the PB running FSD v2 into the toolbar and type in the argument.

In the config-section of the script, you can change some settings.
Open the programmable block via "Edit" so you can see the config and the code of the script.

Tags should only be changed if

• There is a conflict with another script
  
• You don't like the name and want to use other keywords

If you for example want to change the lcdtag from 'ShowStats' to 'DisplayStatus', the line must be modified like this:

If you want to save performance, you could change this line:
to
So the script will only update your screens every 2 seconds.

You can turn the rate up or down. But it due to visual reasons it should remain a fraction of the FpM.

These characters are used to separate the 'names' part from the 'option keyword' part in the Data_sets. Change these at your own risk!!!

You can change every color listed here. I've provided you with a list of colors you can use above the config-section.

If you want to change the headline from white to orange, make the line look like this:

You could also use RGB-values:

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=2353784231