IBPD-I2C CtrlrIBPD-I2C SlaveIBPD-SPI CtrlrIBPD-SPI-SlaveMore Protocols


The IBPD System additional protocols handles two types or additions.   Standard protocols that are able to be controlled by the universal protocol controllers that are standard with the USB-100 and those that require custom hardware to incorporate.  There are many standard protocols that are compatible with the universal controllers standard in the IBPD System.  Protocls are compiled for the registered system and the updates are shipped with all the Command Line Arguments Commands for that protcol.  

The following roadmap of the selected protocols is a flexible one and will change as the demands increase for other protocols.   As each protocol is completed it will be published here on this page as well as the BASIL Networks WWW home page.  If you want to be on the e-mail list to get first notice and incentives to be the first to purchase just join our e-mail list .  There are always incentives to purchase new protocols with big discounts for the first block of sales as well as the latest updates for the entire IBPD System purchased for those that have a release greater than 2 revisions.

The following shows the current protocols available and the roadmap for protocol development.  This roadmap may change with new additions or the sequence of development depending on the industries demands.  To keep up to date on our development we will send you an e-mail when we post new protocols for the system.  Just sign-up for update notifications.


The 1-Wire physical protocol layer Is a single wire BUS system designed by Dallas Semiconductor Corp which was acquired in 2001 by Maxim Integrated Products.  It provides low-speed data transfer and power over a single wire.  1-Wire is similar in concept to I2C but with lower data rates and longer range.  Digital Thermometers and weather instrumentation.  A network of 1-Wire devices with an associated master controller is called a MicroLAN.   One distinctive feature of the bus is the possibility of using only two wires: data and ground.   To accomplish this, 1-wire devices include an 800 pf capacitor to store charge, and to power the device during periods when the data line is active.


Enhanced Serial Peripheral Interface developed by Intel Corporation is an enhanced SPI interface for both client and server platforms.  The frequency of the BUS clock is fixed at 33 MHz, fixed LPC bandwidth of 133 Mbps.


Microwire, [μWire ], is a 3Mbps Full-Duples, three wire interface standard, a predecessor of SPI and a trademark of National Semiconductor.   It's a strict subset of SPI: half-duplex, and using SPI mode 0 [CPOL=0, CPHA=0].  Microwire chips tend to need slower clock rates than newer SPI versions 2 MHz vs. 20 MHz.  Some Microwire chips also support a three-wire mode, which fits neatly with the restriction to half-duplex.


In telecommunications, RS-232 is a standard for serial communication transmission of data. It formally defines the signals connecting between a DTE (data terminal equipment) such as a computer terminal, and a DCE (data circuit-terminating equipment, originally defined as data communication equipment), such as a modem.  The RS-232 standard is commonly used in computer serial ports.  The standard defines the electrical characteristics and timing of signals, the meaning of signals, and the physical size and pinout of connectors.  The current version of the standard is TIA-232-F Interface Between Data Terminal Equipment and Data Circuit-Terminating Equipment Employing Serial Binary Data Interchange, issued in 1997.

An RS-232 serial port was once a standard feature of a personal computer, used for connections to modems, printers, mice, data storage, uninterruptible power supplies, and other peripheral devices.  However, RS-232 is hampered by low transmission speed, large voltage swing, and large standard connectors. In modern personal computers, USB has displaced RS-232 from most of its peripheral interface roles. Many computers do not come equipped with RS-232 ports and must use either an external USB-to-RS-232 converter or an internal expansion card with one or more serial ports to connect to RS-232 peripherals. Nevertheless, RS-232 devices are still used, especially in industrial machines, networking equipment and scientific instruments.


Single Line -Standard configuration.  The protocol is handled through the Universal Protocol Controller - many of the ISP (In System-Program) systems have their own JTAG programmers build in.  Using the command line mode of these controllers through CLADS and the User programmable buttons devices may be programmed with a single click through the IBPD System.

16/32/64 (SerDes) Serializer/Deserializer

This function allows testing of Serialize / Deserialize high speed transmission lines. It will allow the testing of bit transfers of 32/64 bit I/O through high speed up to 3G bps.  Higher speeds are being looked into and we will be offering a 3G / 6G / 10G bps interface for HD video.

TCP/IP IPv4 / IPv6

This function will allow the testing and communication with TCP/IP connections.  It will test both local LAN and Remote WAN networks with trace capability along with many other features.  It is also in development at this time and is scheduled to be released.


This is the 802.11a,g,n, ac, ad, af, ah type Wireless transceivers used in many wireless device.


This Function allows the user to test the parameters of the Bluetooth wireless transmission / reception for data integrity and quality.   It addresses 802.15.4 MAC WPAN as well as the standard Bluetooth 802.15.1.


This protocol section covers RFID protocols and code structures.

In-Vehicle LIN

Single Line -Standard configuration.  OBD vehicle database where available

In-Vehicle CAN

Single Line -Standard configuration. OBD vehicle database where available


The following Video and data streaming protocols are being evaluated for consideration into the IBPD System protocl pevelopment.  Streaming data over the Internet is in a continuous state of development as the bandwidth becomes more and more prescious to providers to maintain a QoS for their customers.   We will be updating these protocols as we talk to the developers and companies that own them in order to present a true development environment tool.  There are many articles on the Internet explaining these and several other data streaming protocols and we will setup a link to the best of these articles for understanding these protocols and integrating them into the development process.


ENet evolved specifically as a UDP networking layer for the multiplayer first person shooter Cube.

Cube necessitated low latency communication with data sent out very frequently, so TCP was an unsuitable choice due to its high latency and stream orientation.  UDP, however, lacks many sometimes necessary features from TCP such as reliability, sequencing, unrestricted packet sizes, and connection management.  So UDP by itself was not suitable as a network protocol either.  No suitable freely available networking libraries existed at the time of ENet's creation to fill this niche.

UDP and TCP could have been used together in Cube to benefit somewhat from both of their features, however, the resulting combinations of protocols still leaves much to be desired.  TCP lacks multiple streams of communication without resorting to opening many sockets and complicates delineation of packets due to its buffering behavior.  UDP lacks sequencing, connection management, management of bandwidth resources, and imposes limitations on the size of packets.  A significant investment is required to integrate these two protocols, and the end result is worse off in features and performance than the uniform protocol presented by ENet.

ENet demands no royalties and doesn't carry a viral license that would restrict you in how you might use it in your programs.  ENet is licensed under a short-and-sweet MIT-style license, which gives you the freedom to do anything you want with it (well, almost anything).

UDP Data Transfer [UDT]

UDT is a reliable UDP based application level data transport protocol for distributed data intensive applications over wide area high-speed networks.   UDT uses UDP to transfer bulk data with its own reliability control and congestion control mechanisms.  The new protocol can transfer data at a much higher speed than TCP does.  UDT is also a highly configurable framework that can accommodate various congestion control algorithms.

UDT is Licensed under BSD/LGPL for Free BSD OS.

SCTP - Stream Control Transmission Protocol




CCP - Datagram Congestion Control Protocol




RSCP - Relay Caster Streaming Protocol




File Catalyst


Mass Transit HP V


Reserved For Future Use

We have reserved several buttons for future attachments that are to be determined.


Copyright 1990-2016 BASIL Networks, PLLC. All rights reserved