Summary: The Current State of Product Development
The industry has no single system or place for multiple protocol controllers, especially multiple controllers from a single USB port. Most of the time the developer is burdened with putting together a quick temporary protocol controller and has to program all the unique codes for the device to be programmed. The difficulty comes in the repeatability and reliability of the controller and the software protocols storage. The IBPD System allows a easy central repository of multiple protocols with the ability to add protocols as required at any time. The IBPD System keeps track of all the devices and software protocols and setups in a simple one click database for each protocol. The databases are easily stored on a network server for multiple access and the release version may be encrypted and stored for safe keeping. The added 16 bit logic analyzed and the dual channel digital storage oscilloscope add the needed test capabilities for testing multiple protocols in real time. The IBPD System is a great time saver as well as organizing protocols, firmware, device communication software protocols with easy recall for minimum reliable reuse and setup. One of the many features that stand out in today's laptop and desktop operating system world is that the IBPD System runs on Win2K, Win XP SP3, Win7 Sp1 32/64 bit and Win8.x, 32/64 bit Windows operating systems. Developers, entrepreneurs, educational institutions and manufacturers will benefit for the ease of setup and organization features of the IBPD System. When using the IBPD System in a test and measurement environment, easily test different sensors with different protocols at the same time with ease, store the test data in files then use your own computational API's or ours to process the resultant data.
We are now deep in the age of Embedded architecture applications and the industrial environment in this area is extremely factious. We are experiencing multi-processors embedded in what use to be simple appliances, entertainment systems and the list goes on and on. With the outsource of device fabrication manufacturers are able to make changes to the device architecture easier and more frequently to keep up with feature demands, especially now since these new fab houses have a more flexible manufacturing processing to offer. Development pressures are high for larger companies to get the product on the market. As many of us are aware fast changes and release to market before being well tested always happens with risks attached. The lost time for rework and the disappointment of the customer is not something that is easily repaired especially when updating development tools to handle fab and hardware changes. Building trust with development tools is a time and experience proposition between the tool manufacturer and the developer using the tool.
Embedded systems require a Quality of Service, QoS that depends on two major areas, the hardware and software communication. The hardware QoS at the chip level is now very high, we are still working on the manufacturing level with lead free solder etc. to increase the reliability for commercial applications. The software however depends on communications to control what ever processes it is attached to. This requires high reliability protocols that are capable of not only maintaining communications but doing it securely to prevent hacking and other type intermitting intrusions.
In this Information age the core of information stability and quality are the "protocols". The number of different protocols are in the hundreds and that is for those that have been published, proprietary and trade secret protocols are another issue altogether and the industry may never know the number being used. Standard published protocols are always being updated and new specifications are being published to keep up with the demands which are many and still growing, protocols are the keystone arch that insure the quality and stability of the transfer and make it useable for user interfacing. To give a short example and credit to the individuals that created this list of just the Automated Serial Protocols types along with a List of Data Rates from Wikipedia gives us a hint of the magnitude of the importance of stable high reliability in the protocol arena. Without stable secure protocols there would be no Internet or Information highway. We would still be in the "Maybel at the switchboard, connect me to Bertha please" era. Focusing on both Hardware and Software there are protocols for many of our daily transactions. Hardware protocols are very well defined such as the ATM (Asynchronous Transfer Mode) OSI (Open System Interconnect) the Internet hardware part of the IP-Internet Protocol and the list goes on and on. Within the protocol there is a unique data pattern that defines the type of data being transfers such as the Internet TCP for FTP(File Transfer Protocol), SMTP (Small Mail Transfer Protocol) and many others. Manufacturers of products today are limited in scope to the standard protocols both hardware and software and are reluctant to incorporate a new protocol to the industry unless you are one of the huge companies that have the resources to start a consortium such as the PCI and PCI express bus consortium, or the SanDisk and USB type consortiums. For the internals of a product's communication protocol that connects to the Internet or through a WiFi or Bluetooth, the software protocol used within the product is open to the developer. With the new IoT, Internet of Things, there are many discussions continually on why one should or should not use a new protocol that is not in the book of standards. One of the main reasons to use a protocol is data security, however many developers use a protocol because it is simple to use and cost effective. Whether it is liked or not liked data security comes in last many times and is weighed by business risks. The TCP Internet OSI protocol was not designed for security it was designed to be able to talk to two computers many miles away. In the late 1970's and early 1980's ARPA transferred the "Internet" over to private business. The protection of information and intellectual property from being compromised at the hardware root level already started to be discussed. As an example, today many years later and over a billion users shows clearly the complexity of the protocol security issues; just by the looking at the number of data breaches of "secured data" over the Internet.
Protocol security both hardware and software has evolved to become a very high priority for today's developers of IoT and other connected devices. The publics level of common technology knowledge has increased and with it comes the malicious hackers that commit illegal acts using protocol intrusion technology. An example of this new hardware/software breed of hackers is the discovery of the back door to running Malicious Code Execution in PCI ExpansionROM in the PCI BUS architecture, this backdoor was inherent from the inception and took a while to become common knowledge. The developer today is required to insure product security from hackers in software as well as hardware which is a huge task in itself. Looking at the breaches that are being published today, there are logical reasons these breaches are happening and will continue to happen. The business model for product development is broken and has been for many years. Developers are required to use COTS development tools that will cut the development time to put the product on the market, then to make matters worse,only simple performance tests for operational functionality are performed and very seldom if at all for security; security is a risk management issue.
The IBPD System Solution
Our solution to handle multiple protocols while reducing equipment costs and conserve space is the IBPD (Interactive BUS Protocol Development) System which was designed by developers for developers always keeping the developers point of view with proven hardware technology for a fast plug and play setup. The IBPD System incorporates a standard USB driver that is compatible to Windows operating systems from Win2K to Win8.x. Standardizing allows the development lab to upgrade the Windows OS without having to be concerned if the new OS upgrade will run your current development software. Along with the standard USB interface we have developed a standard universal serial, serial-parallel universal protocol controller that will handle many standard protocols while also allowing the developer to create custom protocols to add additional protection to their intellectual property and designs.
The purpose of the IBPD System is to organize the different protocols into a simple to use system that will save time and expenses when developing products. The organizing of these protocols are on a choose the ones that apply for your current needs and then add the protocols as they are required without having to purchase a piece of equipment for each protocol. This saves money and most important development time.
The hardware and software development for the IBDP System is on a continuous roadmap for instituting many known common protocols while allowing companies to develop their own internal protocols for security. Our initial release is the IBPD System which incorporates two universal protocol ports that will handle hundred of serial/serial-parallel type protocols, a slave I�C device, a slave SPI device for standard communications, dual 16 bit byte controlled digital I/O port, a simple CPU type Device I/O port are the standard protocols of the initial release of the IBPD System Model-100/110 controllers.
The IBPD System addresses product development needs required in a development lab environment where the BUS hardware protocol design as well as the software protocols for devices have to be carefully tested and validated. The IBPD System incorporates organizational features for the developer to easily maintain a multiple number of devices and protocols in a database format designed specifically for each BUS protocol. Database files include device protocol directories, unique setup parameters for programming each device, datasheet directories, revision and creation file data and where-used category information. Databases and associated files are at the users discretion as to where to store them, locally or in a network server. User defined directories for each project and protocols are only a click away. This allows the developer to immediately recall the device, setup all programming parameters and test the device with a click of the mouse. No complex setup processes or special codes to type in to setup a test for a product.
The IBPD System allows the user to handle several protocols at one time in a single desktop or laptop using only one USB port. With the demands of today's real world interface sensing many development projects now incorporate multiple protocols to meet the demands. The IBPD System addresses both COTS and custom real world programming requirements. The standard default drivers support inexpensive COTS hardware that are easily replaced and are available globally through standard distribution.
The IBPD System also includes test instrumentation giving the developer the necessary tools to test the performance and quality of the protocols in real time. We all understand that testing the protocol bus is not an option it is a requirement, that is why we include a full featured 16 bit digital logic analyzer with selectable sampling rates up to 20 nanoseconds, a 1 Megx16 static RAM Buffer in order to collect enough samples to see the entire digital protocol data and timing. For the analog side the IBPD System includes a full featured two channel DSO (Digital Storage Oscilloscope) with selectable timing up to 10ns sampling rate max, 1 meg static RAM buffer for each channel, AC/DC coupled 1,2,5,10 scaling, 100Vmax with 10x probes included. To connect the IBPD System to the real world standard screw terminal boards ( IBPD System Push Terminal Board Connector PTB50, PTB3040 ), are included to simplify installation and increase flexibility. For use in a pre-production or production environment custom interface connector boards are available to add any external interface requirements to the unit under test which allows easy setup and storing when changing product lines in manufacturing or for use with third party contract manufacturing.
The IBPD System software also supports some COTS USB devices to help those developers that are building test equipment to reduce cost. The IBPD System control software has included standard drivers that will support the FTDI device UMB232H-B and will always be a simple test standard for this system allowing immediate Plug&Play for quick testing and evaluations. The only two protocols that are supported for the UMB232H-B are the I�C and the SPI. All other protocols are interfaced with custom hardware/firmware unique to the IBPD System. The intuitive IBPD System software for developers is the focus of this product introduction with the Digital Logic Analyzer and the Digital Storage Oscilloscope as test instrumentation along with the protocols give a complete universal test tool in a small 8x4x1.5" package ready to use. The IBPD software also includes a ANSI C library for the UMB232H-B device as well as a complete Command Line Argument Library for the protocols to run the IBPD System from the command line in the background with or without dialogs. A typical IBPD System Command Line Mode for use with third party data collection programs that accept the standard EXE command line like: IBPD-SYS.exe "/CMD = Prgm256byteEEPROM.cla". There are a series of Command Line Argument (CLA) commands that allow the control and setup of the IBPD System with a single command line argument (*.CLA) file.
The fact remains that there are several specific hardware type protocols that are stable and widely used throughout the industry. What generally changes over time are the specifications to the protocol, as an example, JTAG (IEEE 1149.1) and IJTAG (IEEE P1687), the USB 1.0, 2.0, 3.0 and the next level in the works USB4.0. This applies to all technology as the demand for features and flexibility and security are ever changing. The IBPD System addresses these development needs directly by incorporating a Module Design Methodology (MDM) for interface BUS architecture and software protocol development and debugging. As the protocol speeds and functionality change the IBPD System update process will introduce new software when required new hardware to accommodate these changes.
There are many hardware BUS type programmers on the market that will program devices for just about any standard hardware BUS protocol "for use in a production environment" and they do that type of production programming very well. As product developers the lab environment is quite different. The IBPD System addresses development needs required in a development lab environment where the BUS hardware protocol architecture design as well as the software protocol has to be carefully implemented and tested and validated.
The IBPD-System Organizational and Development Features
BUS Architecture & Protocol Database Features:
Databases and associated files are at the users discretion as to where to store them, locally or on a network server. The IBPD System initializes a default set of directories for the user to get familiar with the system. Each BUS protocol architecture has its own " Default Directories Setup" function to easily organize the database files as well. Default directories may be changed for each product developed allowing easy organization of the development process an fast setup. This allows developers to immediately recall the device, setup all programming parameters and test the device with a click of the mouse. No complex setup processes or special codes to type to setup a test for a product. The entire setup process may be executed using BASIL Networks CLADS creating a shortcut link in command line form.
Another important feature of the IBPD System is the encryption methodology that allows encryption for the data files, configuration files, shortcut files and Command Line Argument files to keep your product development files safe. The IBPD System has been tested with a 50 Foot Active USB 2.0 extension for control room capability.
Interactive BUS Protocol Development (IBPD)System Solutions Product Line
Register to download a free Working Demo
BASIL Networks, PLLC is now offering this longevity Solutions product line exclusively to the industry. OEM and product manufacturers interested in owning this entire product line exclusively please inquire below to setup a meeting, demonstration and accessory roadmap. The product is offered with a custom brushed aluminum black anodize enclosure screened with manufacturers logo and labels. All Intellectual Property (IP) and copyrights along with on-line Web manuals and product presentations associated with the design will be transferred with the sale.
This product is an original design and will not be duplicated in order to insure exclusive rights to the buyer. The intellectual property and its unique applications of this product line are patentable. Other protocols for this system are negotiable, training to takeover the accessory and other protocol development under a contracted time frame is also available.
Standard and custom protocols, accessories and device development offered at a fraction of the base IBPD initial system insures the longevity and product reuse to reduce TCO.
Copyright� 1990-2016 BASIL Networks, PLLC. All rights reserved