Configuring the MVI56-PDPS Module

Set Up the Project

To begin, start ProSoft Configuration Builder. If you have used other Windows configuration tools before, you will find the screen layout familiar. ProSoft Configuration Builder's window consists of a tree view on the left, an information pane and a configuration pane on the right side of the window. When you first start ProSoft Configuration Builder, the tree view consists of folders for Default Project and Default Location, with a Default Module in the Default Location folder. The following illustration shows the ProSoft Configuration Builder window with a new project.

Your first task is to add the MVI56-PDPS module to the project.

1. Use the mouse to select "Default Module" in the tree view, and then click the right mouse button to open a shortcut menu.

2. On the shortcut menu, choose "Choose Module Type". This action opens the Choose Module Type dialog box.

3. In the Product Line Filter area of the dialog box, select MVI56. In the Select Module Type dropdown list, select MVI56-PDPS, and then click OK to save your settings and return to the ProSoft Configuration Builder window.


Adding a Project

To add a project to an existing project file:

1. Select the Default Project icon.
2. Choose Project from the Project menu, then choose Add Project. A new project folder appears.

Adding a Module

To add a module to your project:

1. Double-click the Default Module icon to open the Choose Module Type dialog box.
2. On the Choose Module Type dialog box, select the module type.

Or

1. Open the Project menu and choose Location.
2. On the Location menu, choose Add Module.

[MODULE]

The module section contains the data that applies to the whole module and includes the backplane data transfer parameters.

[Module]
Module Name : MVI69-PDPS Communication Module DEFAULT


[BACKPLANE]
The backplane section contains the data that applies to the backplane data transfer parameters.

[Backplane]
Read Register Count : 122
#Number of words to move from MVI to
#Processor (PROFIBUS Output)

Write Register Count : 122
#Number of words to move from Processor to
#MVI (PROFIBUS Input)

Block Transfer Size : 60
#Number of data words for I/O transfer
#(60, 120 or 240)


[PROFIBUS SLAVE]
The PROFIBUS Slave section contains the data that applies to the PROFIBUS Slave parameters.

Slave Address
0 to 125
The parameter specifies the node address on the PROFIBUS network for the slave emulated in the module. Each node on the network must have a unique address.

Swap Input Bytes
Yes or No
This parameter specifies if the data in the input data area of the module is to be byte swapped. If the order of the bytes in the words stored in the database is not correct, use this option. A value of Yes causes the module's program to swap the bytes in each word. A value of No indicates no byte swapping will occur.

Swap Output Bytes
Yes or No
This parameter specifies if the data in the output data area of the module is to be byte swapped. If the order of the bytes in the words stored in the database is not correct, use this option. A value of Yes causes the module's program to swap the bytes in each word. A value of No indicates no byte swapping will occur.

Comm Failure Mode
No xfer on fail
xfer on comm fail
This parameter sets the data transfer mode of the module's PROFIBUS output image to the internal database when a communication failure on the PROFIBUS interface is detected. If the parameter is set to "No xfer on fail", the output image will continue to be transferred. If the parameter is set to "xfer on comm fail", the output image will not be transferred and the last values will be retained.

Comm Timeout Multiplier
1 to 10
This parameter sets the communication timeout value for the module. The value entered is multiplied by 125 milliseconds to determine the actual timeout value. For example, a value of 1 specifies a communication timeout of 125 milliseconds.

Download the Project to the Module

In order for the module to use the settings you configured, you must download (copy) the updated Project file from your PC to the module.

To Download the Project File

1. In the tree view in ProSoft Configuration Builder, click once to select the MVI69-PDPS module.
2. Open the Project menu, and then choose Module / Download. The program will scan your PC for a valid com port (this may take a few seconds). When PCB has found a valid com port, the following dialog box will open.

3. Choose the com port to use from the dropdown list, and then click the Download button.

The module will perform a platform check to read and load its new settings. When the platform check is complete, the status bar in ProSoft Configuration Builder will be updated with the message "Module Running".

Read More »

Adding the Module to an Existing Project

1. Add the MVI56-PDPS module to the project. Right-click the mouse button on the I/O Configuration option in the Controller Organization window to display a pop-up menu. Select the New Module option from the I/O Configuration menu.

This action opens the following dialog box:

2. Select the 1756-Module (Generic 1756 Module) from the list and click OK.

3. Enter the Name, Description and Slot options for your application, using the values in the illustration above. You must select the Comm Format as Data - INT in the dialog box, otherwise the module will not communicate over the backplane of the CompactLogix rack.

4. Configure the Connection Parameters to match to the Block Transfer Size parameter in the configuration file. Use the values in the table corresponding with the block transfer size you configured.

5. Click Next to continue.

6. Select the Request Packet Interval value for scanning the I/O on the module.
This value represents the minimum frequency the module will handle scheduled events. This value should not be set to less than 1 millisecond.
Values between 1 and 10 milliseconds should work with most applications.

7. Save the module. Click OK to dismiss the dialog box. The Controller Organization window now displays the module's presence. The following illustration shows the Controller Organization window:

8. Copy the Controller Tags from the sample program.

9. Copy the User Defined Data Types from the sample program.

10. Copy the Ladder Rungs from the sample program.

11. Save and Download the new application to the controller and place the processor in run mode.


Read More »

Introduction

The main propose of this is explain how to set up a communication between an AB PLC and a Siemens PLCs using Profibus Protocol.

The equipment required to make the communication are enlisted below.

- CPU Siemens with a DP Port.
- PLC Allen Bradley capable to support a 3dr Party Profibus Module.
- Prosoft Module (Profibus DP Slave Communication Module).

The next image shows the architecture of the network that is suggested.

Set up the module on the Siemens network
To set up the module on the Siemens network we need to follow the steps below.

1.- Open Simatic Manager.

2.- Once opened, we should open the Project on File->Open. Next find and select Hardware like its show below.

3.- Double click on Hardware and it will open the HW Config program. Here is where we need to add a Prosoft Module GSD, the GSD file is named “PSFT0988.gsd”. to add the GSD file in the HW Config program we need go to the main menu and find tools, next we find and select the option Install GSD File as its show in the image below.

4.- Once the GSD file is installed we have to look forward in the explorer tree showed in the right side of the program (Hardware Catalog) to add it into the Hardware Config area as its show below.

5.- Now we need to assign to the module an address node to work in the network and also configure the decentralized periphery adding how many words input/output we are going to need. In the image below are showed an example of the words that we can use.

6.- Once we select the words that we need, we have to drag and drop the words into the decentralized periphery area, as its show below we select 16 words input and 16 words output to share information.

7.- Now we take note of the registers that were assigned to the inputs and outpus words, in the example above the registers assigned were:

Notice that those registers will be different depends on the project IO configuration!!!

8.- Now we have to put the information to share on these registers, input registers are information read it from an AB PLC and the Outpus registers are the information that you will write on the AB PLC.

Read More »

The Simulation_DT_1st Add-On Instruction adds a dead time and a first-order lag to an input variable.

Figure 10 - Simulation Example Definition Editor General Tab

Figure 11 - Simulation Example Definition Editor Parameter Tab

Figure 12 - Simulation Example Logic

Ladder Diagram Configuration

In this example, the instruction simulates a deadtime and lag (first order) process.

The Simulation_DT_1st instruction reads the control variable from the PID instruction. The PID instruction reads the SimOutput Parameter of the Simulation_DT_1st instruction.

Function Block Diagram Configuration

The PIDE instruction sends the control variable to the Simulation_DT_1st instruction. The Simulation_DT_1st instruction calculates an output and sends it to the PIDE instruction as the process variable

Structured Text Configuration

Simulation_DT_1st( Sim_DT_ST, My_PIDE_ST.CVEU, DT_Array_ST );
My_PIDE_ST.PV := Sim_DT_ST.SimOutput;
PIDE(My_PIDE_ST );

The Simulation_DT_1st instruction reads the control variable from the PIDE instruction and calculates an output.

The output goes to the process variable of the PIDE instruction.

Read More »

The Motor_Starter Add-On Instruction starts and stops a motor.

If the stop pushbutton is closed and the start pushbutton is pressed then:

· the motor gets the command to run.
· the instruction seals in the command, so the motor keeps running even after you release the start pushbutton.

If the stop pushbutton is pressed (opened), then the motor stops.

Figure 4 - Motor Starter Example Definition Editor General Tab

Figure 5 - Motor Starter Example Definition Editor Parameter Tab

Figure 6 - Motor Starter Example Ladder Logic

The following diagrams show the Motor Starter instruction called in three different programming languages.

Figure 7 - Motor Starter Ladder Diagram

Figure 8 - Motor Starter Function Block Diagram

Figure 9 - Motor Starter Structured Text

Motor_Starter(Motor_Starter_ST, Stop_PB, Start_PB, Motor_Out_ST);
Read More »

Custom instruction help is generated automatically as you are creating your Add-On Instructions. The Logix Designer application automatically builds help for your Add-On Instructions by using the instruction’s description, revision note, and parameter descriptions. By creating meaningful descriptions, you can help the users of your instruction.

In addition, you can add your own custom text to the help by using the extended description field. You can provide additional help documentation by entering it on the Help tab of the Add-On Instruction Definition Editor. The instruction help is available in the instruction browser and from any call to the instruction in a language editor by pressing F1.

Writing Clear Descriptions

When writing your descriptions keep the following in mind:

· Use short sentences and simple language.
· Be brief and direct when you write.
· Include simple examples.
· Proofread your entries.

This is an example of the Extended Description Text field in the Help tab of the Add-On Instruction Definition Editor. This area lets you create directions on how to use and troubleshoot your instruction. The Instruction Help Preview window shows how your text will look as generated instruction help.

Documenting an Add-On Instruction

Follow these steps to create custom help for an instruction.

1. Right-click an Add-On Instruction and choose Open Definition.

2. On the General tab, enter a description and a revision note for the Add-On Instruction to explain the purpose of the instruction.

3. Click the Parameters tab and enter a meaningful description for each Parameter.

4. Right-click each routine located below the Add-On Instruction in the Controller Organizer and choose Properties.

5. Enter a description for execution of each routine.

a. For the logic routine, describe execution of the instruction when EnableIn is true.

b. For the EnableInFalse routine (if one exists), describe actions that will take place when EnableIn is false, such as any outputs that get cleared.

c. For the Prescan routine (if one exists), briefly describe actions that will take place during the Prescan routine, such as initialization of any parameters.

d. For the Postscan routine (if one exists), briefly describe actions that will take place during the Postscan routine, such as initialization of any parameters resetting any internal state of the instruction.

6. Click the Help tab of the Add-On Instruction Definition Editor and enter additional information in the Extended Description field.

The extended description can include the following information:

· Additional parameter information
· Description of how the instruction executes
· Change history notes

7. Review the Help format in the preview window

This is an example of the Logix Designer application generated help for the instruction. This information is gathered from the definition descriptions that you complete when defining an instruction.

Project Documentation

With RSLogix 5000 software, version 17 and later, you have the option to display project documentation, such as tag descriptions and rung comments in any supported localized language. You can store project documentation for multiple languages in a single project file rather than in language-specific project files. You define all the localized languages that the project will support and set the current, default, and optional custom localized language. The software uses the default language if the current language's content is blank for a particular component of the project. However, you can use a custom language to tailor documentation to a specific type of project file user.

Enter the localized descriptions in your project, either when programming in that language or by using the import/export utility to translate the documentation offline and then import it back into the project. Once you enable project documentation in application, you can dynamically switch between languages as you use the software.

Project documentation that supports multiple translations includes these variables:

• Component descriptions in tags, routines, programs, equipment phases, user-defined data types, and Add-On Instructions
• Engineering units and state identifiers added to tags, user-defined data types, or Add-On Instructions
• Trends
• Controllers
• Alarm Messages (in configuration of ALARM_ANALOG and ALARM_DIGITAL tags)
• Tasks
• Property descriptions for module in the Controller Organizer
• Rung comments, SFC text boxes, and FBD text boxes

If you want to allow project documentation on an Add-On Instruction that is sealed with an instruction signature, you must enter the localized documentation into your Add-On Instruction before generating the signature. Because the signature history is created after the instruction signature is generated, the signature history is not translatable. If the translated information already exists when you generate the Add-On Instruction signature, you can switch the language while keeping the signature intact because the switch does not alter the instruction definition, it only changes the language that is displayed.

For more information on enabling a project to support multiple translations of project documentation, refer to the online help.

Read More »

The Signature tab of the Add-On Instruction Definition Editor lets you manage the instruction signature, create signature history entries, and view the safety instruction signature, if it exists. Instruction signatures are applied to the definition of the Add-On Instruction. All instances of that Add-On Instruction are sealed when the signature is applied.

Generating, Removing, or Copying an Instruction Signature

On the Signature tab of the Add-On Instruction Definition Editor, click Generate to create an instruction signature or Remove to delete the instruction signature.

You must be offline to generate or remove an instruction signature. Both actions change the Last Edited Date.

You can click Copy to copy the instruction signature and the safety instruction signature, if it exists, to the clipboard to facilitate record-keeping.

Creating a Signature History Entry

The signature history provides a record of signatures for future reference. A signature history entry consists of the name of the user, the instruction signature, the timestamp value, and a user-defined description. You can only create a signature history if an instruction signature exists and you are offline. Creating a signature history changes the Last Edited Date, which becomes the timestamp shown in the history entry. Up to six history entries may be stored.

Follow these steps to create a signature history entry.

1. On the Signature tab of the Add-On Instruction Definition Editor, click Add to History.

2. Type a description, up to 512 characters long, for the entry.

3. Click OK.

To delete the signature history, click Clear Signature History while the instruction does not have an instruction signature. You must be offline to delete the Signature History.

Generating a Safety Instruction Signature

When a sealed safety Add-On Instruction is downloaded for the first time, a SIL 3 safety instruction signature is automatically generated. Once created, the safety instruction signature is compared at every download.

If the Logix Designer application detects an invalid safety instruction signature value, it generates a new safety instruction signature value in the offline project and displays a warning indicating that the safety instruction signature was changed. The safety instruction signature is deleted if the instruction signature is removed.

Viewing and Printing the Instruction Signature

When the instruction signature has been generated, the Logix Designer application displays the instruction with the blue seal icon in the Controller Organizer, on the Add-On Instruction title bar, and in the Logic Editor.

When an instruction is sealed, the instruction signature is displayed on the faceplate of the instruction in the Ladder Diagram Editor and the Function Block Diagram Editor.

Ladder Diagram

Function Block Diagram

You can turn off the display of the instruction signature in the Workstation Options dialog box of the Logix Designer application.

You can also view the instruction signature and the safety instruction signature on the Quick View pane of the Controller Organizer and on the Signature tab of the Instruction Definition Editor dialog box.

The Add-On Instruction name, revision, instruction signature, safety instruction signature, and timestamp are printed on the Add-On Instruction Signature Listing report. You can also choose to include the instruction signature, safety instruction signature, and signature history on the Add-On Instruction report by clicking Print Options on the Generate Report dialog box.

Read More »

You can apply source protection to your Add-On Instruction to protect your intellectual property or prevent unintended edits of a validated source.

With source protection you can limit a user of your Add-On Instruction to readonly access or prevent access to the internal logic or local tags used by the instruction. You can protect the use and modification of your instructions with a source key file when you distribute them.

You have two options when using source protection.

· Source Protected

Users without the source key cannot view any routine or local tags, or make any edits to the Add-On Instruction. Choose this option if you want to protect the source definition of an Add-On Instruction from the view of a user. This may be due to the proprietary nature of the algorithms or for strict revision control.

· Source Protected with Viewable Option

Users without the source key can view all components of the Add-On Instruction including its logic and local tags, but are prevented from making any edits to the instruction.

Enable the Source Protection Feature

If source protection is unavailable and not listed in your menus, you can enable it by using the RS5KSrcPtc.exe tool on your installation CD.

Read More »

You need to test and troubleshoot the logic of an instruction to get it working.

Before You Test

Before you start to test an Add-On Instruction, do the following.

1. Open a project to debug offline.

2. Add the Add-On Instruction to the project, if it is not already there.

Testing the Flow

1. Add a call to the instruction in a routine in the open project.

2. Assign any arguments to required parameters for your call.

3. Download the project.

Monitoring Logic with Data Context Views

You can simplify the online monitoring and troubleshooting of your Add-On Instruction by using Data Context views. The Data Context selector lets you select a specific call to the Add-On Instruction that defines the calling instance and arguments whose values are used to visualize the logic for the Add-On Instruction.

Follow these steps to monitor the logic.

1. Go into Run mode.

2. Right-click the instruction call and choose Open Instruction Logic.

The logic routine opens with animated logic for the specific calling instance.

Verifying Individual Scan Modes

The most straightforward method to verify Scan mode operation is to execute the instruction first with the Scan mode routine disabled, then again with it enabled. Then you can determine whether the Scan mode routine performed as expected.

Instruction	Description
True	This is simply the execution of the main logic routine.
False	In a ladder logic target routine, this entails placing an XIC before an instance of the instruction and evaluating instruction results when the XIC is false. In a Function Block target routine, this entails executing an instance of the instruction with the EnableIn parameter set to zero (0).
Prescan	Place the controller in Program mode, then place it in Run mode.
Postscan	With the controller configured for SFC Automatic Reset, place an instance of the instruction into the Action of an SFC. Run the SFC such that this Action is executed and the SFC proceeds beyond the step that is associated with this Action.

Read More »

You can change the class of a safety Add-On Instruction so that it can be used in a standard task or standard controller. You can change the class in a safety project if the instruction does not have an instruction signature, you are offline, the application does not have a safety task signature, and is not safety-locked.

You can also change the class from standard to safety so that the Add-On Instruction can be used in the safety task.

Changing the class of an Add-On Instruction results in the same class change being applied to the routines, parameters, and local tags of the Add-On Instruction. The change does not affect nested Add-On Instructions or existing instances of the Add-On Instruction.

If any parameters or tags become unverified due to the change of class, they are identified on the Parameters and Local Tags tabs of the Add-On Instruction Editor.

If any of the restrictions for safety Add-On Instructions are violated by changing the class from standard to safety, one of the following errors is displayed and the change does not succeed:

· Routines must be of Ladder Diagram type.
· Safety Add-On Instructions do not support the Postscan routine.
· One or more parameters or local tags have an invalid data type for a safety Add-On Instruction.

You must edit the parameter, tag, or routine types before the class change can be made.

Read More »

The EnableIn and EnableOut parameters that appear by default in every Add-On Instruction have behaviors that conform to the three language environments:
Ladder Diagram, Function Block Diagram, and Structured Text.

To execute the primary logic routine in any of the language environments, the EnableIn parameter must be True (1). In general, the EnableIn parameter should not be referenced by the primary logic routine within the instruction definition. The EnableOut parameter will, by default, follow the state of the EnableIn parameter but can be overridden by user logic to force the state of this Parameter.

If the EnableIn parameter of the instruction is False (0), the logic routine is not executed and the EnableOut parameter is set False (0). If an EnableInFalse routine is included in the instruction definition and it is enabled, the EnableInFalse routine will be executed.

EnableIn Parameter and Ladder Diagram

In the ladder diagram environment, the EnableIn parameter reflects the rung state on entry to the instruction. If the rung state preceding the instruction is True (1), the EnableIn parameter will be True and the primary logic routine of the instruction will be executed. Likewise, if the rung state preceding the instruction is False (0), the EnableIn parameter will be False and the primary logic routine will not be executed.

EnableIn Parameter and Function Blocks

In the function block environment, the EnableIn parameter can be manipulated by the user through its pin connection. If no connection is made, the EnableIn parameter is set True (1) when the instruction begins to execute and the primary logic routine of the instruction will be executed. If a wired connection to this parameter is False (0), the primary logic routine of the instruction will not execute. Another reference writing to the EnableIn parameter, such as a Ladder Diagram rung or a Structured Text assignment, will have no influence on the state of this parameter. Only a wired connection to this parameter’s input pin can force it to be False (0).

EnableIn Parameter and Structured Text

In the Structured Text environment, the EnableIn parameter is always set True (1) by default. The user cannot influence the state of the EnableIn parameter in a Structured Text call to the instruction. Because EnableIn is always True (1) in Structured Text, the EnableInFalse routine will never execute for an instruction call in Structured Text.

Read More »

The Scan Modes tab in the Instruction Definition Editor lets you create and enable execution of the routines for the three Scan modes: Prescan, Postscan, and EnableInFalse.

Prescan Routine

When the controller transitions from Program mode to Run mode or when the controller powers up in Run mode, all logic within the controller is executed in Prescan mode. During this scan, each instruction may initialize itself and some instructions also initialize any tags they may reference. For most instructions, Prescan mode is synonymous with scanning false. For example, an OTE instruction clears its output bit when executed during Prescan mode. For others, special initialization may be done, such as an ONS instruction setting its storage bit during Prescan mode. During Prescan mode, all instructions evaluate false so conditional logic does not execute.

The optional Prescan routine for an Add-On Instruction provides a way for an Add-On Instruction to define additional behavior for Prescan mode. When a Prescan routine is defined and enabled, the Prescan routine executes normally after the primary logic routine executes in Prescan mode. This is useful when you want to initialize tag values to some known or predefined state prior to execution.

An example would be setting a PID instruction to Manual mode with a 0% output prior to its first execution or initializing some coefficient values in your Add-On Instruction.

When an Add-On Instruction executes in Prescan mode, any required parameters have their data passed.

· Values are passed to Input parameters from their arguments in the instruction call.
· Values are passed out of Output parameters to their arguments defined in the instruction call.

These values are passed even when the rung condition is false in Ladder Diagram or when the instruction call is in a false conditional statement in Structured Text. When Function Block Diagram routines execute, the data values are copied to all wired inputs and from all wired outputs, whether or not the parameters are required.

Follow these steps to create a Prescan routine.

1. In the Controller Organizer, right-click an instruction and choose Open Definition.

2. Click the Scan Modes tab.

3. Click New for Prescan Routine.

4. From the Type menu on the New Scan Mode Routine dialog box, choose the type of programming language: Ladder Diagram, Function Block, or Structured Text.

5. Type a description of the Prescan behavior.

6. Click OK to create the routine and return to the Scan Modes tab.

7. Define if the prescan routine executes (or not) by checking or clearing Execute Prescan routine after the logic routine is prescanned.

The Prescan routine can now be edited like any other routine.

Postscan Routine

Postscan mode occurs only for logic in a Sequential Function Chart Action when the Action becomes inactive and the SFC language is configured for Automatic Reset (which is not the default option for SFC). When an SFC Action becomes inactive, then the logic in the Action is executed one more time in Postscan mode. This mode is similar to Prescan in that most instructions simply execute as if they have a false condition. It is possible for an instruction to have different behavior during Postscan mode than it has during Prescan mode.

When an Add-On Instruction is called by logic in an SFC Action or a call resides in a routine called by a JSR from an SFC Action, and the Automatic Reset option is set, the Add-On Instruction executes in Postscan mode. The primary logic routine of the Add-On Instruction executes in Postscan mode. Then, if it is defined and enabled, the Postscan routine for the Add-On Instruction executes. This could be useful in resetting internal states, status values, or de-energizing instruction outputs automatically when the action is finished.

Follow these steps to create a postscan routine.

1. In the Controller Organizer, right-click an instruction and choose Open Definition.

2. Click the Scan Modes tab.

3. Click New for Postscan Routine.

4. From the Type menu on the New Scan Mode Routine dialog box, choose the type of programming language: Ladder Diagram, Function Block, or Structured Text.

5. Type a description of the postscan behavior.

6. Click OK to create the routine and return to the Scan Modes tab.

7. Define if the postscan routine executes (or not) by checking or clearing Execute Postscan routine after the logic routine is postscanned.

The Postscan routine can now be edited like any other routine.

EnableInFalse Routine

When defined and enabled for an Add-On Instruction, the EnableInFalse routine executes when the rung condition is false or if the EnableIn parameter of the Add-On Instruction is false (0). This is useful primarily for scan false logic, when used as an output instruction in a Ladder routine. A common use of scan false is the setting of OTEs to the de-energized state when the preceding rung conditions are false. An Add-On Instruction can use the EnableInFalse capability to let you define behavior for the False conditions.

When the Add-On Instruction is executed in the false condition and has an EnableInFalse routine defined and enabled, any required parameters have their data passed.

· Values are passed to Input parameters from their arguments in the instruction call.
· Values are passed out of Output parameters from their arguments in the instruction call.

If the EnableInFalse routine is not enabled, the only action performed for the Add-On Instruction in the false condition is that the values are passed to any required Input parameters in ladder logic.

Follow these steps to create an EnableInFalse routine.

1. Right-click the instruction and choose Open Definition.

2. Click the Scan Modes tab.

3. Click New on EnableInFalse routine.

4. From the Type menu on the New Scan Mode Routine dialog box, choose the type of programming language: Ladder, Function Block, or Structured Text.

5. Type a description of the EnableInFalse behavior.

6. Click OK to add an EnableInFalse routine to the Add-On Instruction definition.

7. Define if EnableIn False routine executes (or not) by checking or clearing Execute EnableInFalse routine.

The EnableInFalse routine can now be edited like any other routine.

Read More »