BASIL_NETWORKS


BANNER_Interactive_BUS_Protocol_Development_[IBPD]_System_Overview

 

HomeABOUTPRODUCTSSERVICESSUPPORTCONTACTARTICLESBLOG
SystemsPeripheralsInstrumentsResearchNetworksSoftwareProgrammersOEM
IBPD-SystemIBPD-CAMSIBPD-HardwareIBPD-CLADSIBPD-ProtocolsIBPD-Test Equip
 
 Main MenuInstall ProtocolsOpen ProjectCreate ProjectUser Buttons Encrypt/DecryptIBPD RegistrationSystem SpecificationsIBPD Demo

Banner_Common_UserButtonsLinks

User Button Links are always useful for the developer when calling custom applications for the development.  Each protocol incorporates eight user buttons and four system function links that the user may incorporate the Command Line Argument Development System.   The four system functions are reserved for future development as needed to supplement the associated protocols.   Each BUS protocols user buttons may be used as a shortcut to any application program on the system or accessible network.

User Link Buttons are fully programmable and the setup is saved in a user selected file to the [protocol]_BTN default directory, however the user may save the setup in any directory of choice.  Once the buttons are programmed and saved to a .BTN file, the user may then select to set this file as the default User Buttons at startup or may program each protocol to select a user file for the button configuration.

Functional Block Diagram of Each User Button
UserButtonDescription

    ChkBox_Enable - This will enable the button to be accessed in the Startup Dialog.
    Button Descriptor - This is a text string to characterize the button function. It may be up to 15 characters.
    Link Application - This is the Application to be run when the button is pressed.
    Command Line Argument - This is the Command Line Argument file or string argument to use as option for the Link Application.
    ChkBox_In-Line CLA - This flag will convert the CLA file from a multiple line of command arguments to a single string of command options.

 

Each button sections (3) through (10) may be enable or disabled separately, incorporates a Command Line Argument attachment field and a user descriptor text field.  Each button has two browse buttons one for the Application exe file and one for the command line attachment file if applicable.  The In-Line CLA flag allows the user to read CLA file into an internal buffer and convert it to a single line of command options as used in many compilers and assemblers command options. This allows the user to use the CLADS process to create command line arguments for many third party applications.  The maximum length of the CLA string is 8192 characters for the argument field and is auto horizontal scrolled.  Section (11) allows the user to preview the button text and to test each button prior to saving the configuration.  Command Line Arguments will be encapsulated in quotation ( " ) marks automatically during processing.  When entering data to the field do not add quotation marks.  Examples are shown in the dialog on the use of each button.  There are many third party application that are interactive during the development of a product.  These button links are an added feature to organize the development process.
 

USER_Buttons_Dialog

USER_BUTTONS_LINKS

1_MAIN MENU

    Return - Return to the calling program - this dialog is called from the Startup Main Menu for each BUS Protocol.

    Save Button Configuration - This allows the user to save the button Configuration file to a user name file.  The default directory for each protocol is [protocol]_BTN.

    Set Default Configuration - This will set the default Button configuration to the file shown in the Active Button descriptions. The file is copied to a default system startup file and does not call the file directly.

2_Active Button File

This is the active button file.  The user must load this file to see its configuration.  It is not loaded when the dialog is called, the current button configuration is loaded when the dialog is called.

3_ to (10)User Buttons

User Buttons as described above.

11_Preview & Test

This is the Preview and Test area.  It allows each button to be tested and to see that the button text is within the button parameters.

12_Status

This is the status of the last function executed.

13_Help - This Page

 
Copyright© 1990-2018 BASIL Networks, PLLC. All rights reserved
webmaster