BASIL_NETWORKS


IBPD System - CLADS

 

HomeABOUTPRODUCTSSERVICESSUPPORTCONTACTARTICLESBLOG
SystemsPeripheralsInstrumentsResearchNetworksSoftwareProgrammersOEM
IBPD-SystemIBPD-CAMSIBPD-HardwareIBPD-CLADSIBPD-ProtocolsIBPD-Test Equip
 
Main MenuAuto Create HexModify Hex BlockCLA ConfigureCreate ShortcutCLA Commands CfgUser ButtonsDefault DirectoriesRTF Editor

BANNER_CLADS_Startup_MainMenu

The Command Line Argument Development System contains a series of dialogs that allow the user to create command line arguments for applications programs that support command line argument operations.  The CLADS include the following dialogs that are common to all protocols.  The use of CLA's in the Test & Measurement area is very useful for calling user APIs from within other applications like LabView, MatLab, MathCad, 7-Zip, Compilers and Assemblers etc.  The CLADS button in the Main Menu calls the general purpose CLADS dialogs for the user to apply this to just about any application without any protocol requirements.  Incorporated also are the standard data handling routines applied to Intel Hex data format and standard byte binary data files.

The Command Line Argument Development System (CLADS) is a unique tool for software and hardware developers to maintain and organized hardware,devices software, protocols and programming environments in a single source.  The CLADS Main Startup Dialog menu is the central dispatch for developing general Command Line Argument commands and command links.  The CLADS section is setup as a general purpose development system that does not incorporate any of the IBPD System protocols.  There are subtle differences from using the protocol incorporated CLADS and the general purpose CLADS.  These are the complete removal of all device and programmer databases that keep track of the individual protocols being used with CLADS.  The protocol CLADS links default to the IBPD-[1][2]xx.EXE file since they CLA files will not work anywhere else.  The general purpose CLADS allows the user full flexibility to create and link their own API's in command mode.  There are several 밨eserved for System buttons that are deactivated to the user and will be used for future additions to the program.

The CLADS Main Menu incorporates just two functional groups (1) and (2), and a Status bar , Help and About group (3).

BANNER_CLADS_Startup_Dialog

CLADS_STARTUP_MAIN_DIALOG

 

1_MAIN MENU

This group allows the user to create Intel Hex files or Binary files both are incorporated in the IBPD System program. This Menu is available to all protocols and is tailored to each protocol in order to allow simultaneous BUS protocol functionality.

    EXIT - Terminate the Program - This will terminate all of the protocols activated from this dialog except the User Button applications that have been activated.

    Modify / Create Hex Block - This Function allows the user to instantly modify a block of Intel Hex formatted data and send it to the selected device for testing the protocol.  This function also allows the creation of hex blocks manually as then save them in either Intel Hex or Binary format.  The function also allows the insertion of hex block before / after a selected block in the file.

    Auto Create Binary To Hex File - This function allows the user to create Intel Hex formatted files from standard binary files.  It is primarily used for larger files where the  Modify/Create Hex Block (3) function would be too cumbersome to manage the data entry.

    Make/Edit Command Line Argument (CLA) File - This function allows the creation of the Command line Argument File that is used to run the IBPD-SYS in Command Line Mode (Run Silent).  It allows easy command constructs and places them in a single CLA file.  From the Main Startup the user is allowed to access the available protocols installed in the IBPD System in any order using the main protocol CLA file commands.   This allows the user to create the specific CLA file while in the selected protocol and then combined several protocol CLA files in a single main CLA file for activation.  All BUS protocols are selected from the main startup menu.

    Create Command Line Argument (CLA) Shortcut - This is the general utility the allows the creation of a shortcut with a selection of where to put the shortcut. This is another organizational feature of the IBPD System. The user may also select a unique shortcut icon for the shortcut.

    Make/Edit Command Line Argument (CLA) Commands - This function is one of the added features of the that make up the Command Line Argument Development System (CLADS).  This function allows the user to create their own commands to be user in their application.

    Set Default Directories - This functions allows the user to setup default directories for each protocol for easy management of multiple protocols and multiple projects.

    Configure User Buttons - This allows the user to configure each of the user programmable buttons.  This is unique for each protocol as well, which allows linking of user programs for the protocol.  These buttons may also be activated in the Command Line Mode through the CLA file for operation.

    RTF Editor - This is a general purpose RTF editor for user information.  This editor is incorporated into every protocol and linked each protocol database and data files in order to allow instant recall of the files configuration information.   Each protocol has its own document area.

 

Top

File Extensions for Creating Command Line Mode Command Files Dialog  [ Each BUS protocol has their own group ]

Command Config File Lists [.LST]

These files contain a list of Command Files (*.CMD) and are saved in the [protocol]_LST Directory

Command Config Files [.CMD]

These files are the Command Configuration Files and contain programming information for products and devices that include the Data_Filename[.dat][.hex] name.

 

 

Command Line Arg File Lists [.CLL]

These files contain a list of Command Line Argument Files (*.CLA) used within the selected protocol. They allow multiple command execution by protocol.

Command Line Arg Files [.CLA]

These are the Command Line Argument files which include all the command line arguments to be processed in the IBPD System. used as "filename.exe"  "cla_file.cla"

 

 

CLA Commands File Lists [.CML]

These files contain a list of Command Line Arguments Command Files.

CLA Commands Files [.CLC]

These files are the Command Line Arguments set of Commands the pertain to each protocol.

 

 

Device Database Files [.DBX]

These Files are the device database files for the IBPD System.  They are unique for each protocol.

Default Text Files [.TXT]

These files are convenient text files for templates for devices and database files.

Default Text Files [.PDF]

These files are convenient device datasheet files for the devices listed in the database.  The standard format is PDF, however may be any document format type.

 

 

Data Files [.HEX]

The actual data file used inside the Command_Filename.cmd, this is a Intel Hex Format data file. The IBPD System supports both Binary and Intel Hex Formatted files.

Data Files [.DAT]

The actual data file used inside the Command_Filename.cmd, this is a binary byte Format data file.  The IBPD System supports both Binary and Intel Hex Formatted files.

   

Button Configuration Files [.BTN]

This is where the user stores the user configuration of the user buttons for each protocol and or project for one click setup.

   

Encrypted Files [.ENC]

These are encrypted files that are the CLA and CMD and data files. The IBPD System has three directories for these files.

     DataFile Dir [protocol]_DAT

This is the directory where the encrypted Data files are stored.

     Encrypt Directories [protocol]_DIR

This is a list of directory paths used to keep track of the encrypted directory and file locations.

   

System Database Files [.DBZ]

These files are used by the system for initial global and individual protocol settings.

System ProtocolSpeed [.SPD]

These files are used by the system for initial global and individual protocol settings.  These are the Protocol BUS speeds for various protocols.

System Directories Files [.DIR]

These files contain default and user directories configurations and may be global or set for individual protocols and projects.

System Header Files [.H]

These are created header files for use internally for the users programs.

Top

 

User_Interface_Buttons_Links

(3)User Programmable Buttons

The user Programmable Buttons set of eight are unique for each protocol available in the IBPD System.  The programmable buttons allow the calling of third party software and also allows a Command Line to be attached if the application program allows command line mode operations.  A quick block diagram overview of features for each button:

USER_BUTTON_FEATURES

    User Programmable Button - Available to the user to link other programs.
    User Programmable Button - Available to the user to link other programs.
    User Programmable Button - Available to the user to link other programs.
    User Programmable Button - Available to the user to link other programs.
    User Programmable Button - Available to the user to link other programs.
    User Programmable Button - Available to the user to link other programs.
    User Programmable Button - Available to the user to link other programs.
    User Programmable Button - Available to the user to link other programs.

    Reserved For System - This set of Reserved for future buttons are used for future special programming features to be developed.


BANNER_Status_Help

(5)Dialog Status and Info

This is a common status information field, help menu and about access area.  This area is standard for all dialogs where the user may access the help for the active dialog.

    Dialog Status Bar - Shows the error if any of the current user selection.
    About The IBPD-SYS - Calls the About this program dialog
    Local Help Menu - Calls up this link for the program

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