UFDEX

micro FIKO Data Exchange (uFDEX) is a serial protocol and data transfer system used as mini-LAN in vehicles, marine, aviation, lab, home and office automation systems. uFDEX uses ATMEL and Atmel AVR embedded microcontroller technologies and may link into multiple RS-232, RS-422, RS-485 ports via one single entry point as defined under Common Hybrid Interface Protocol System (CHIPS).

In today's world of communication, most people knows LAN systems used in PCs but few people knows that it's also possible to build small LAN systems that in fact are based on RS (Recommended Standard) protocols like RS-232 or RS-485, where RS-232 links between PC serial port and equipment are normally limited to 16 meters or 50 feet and RS-485 are limited to 1,200 meters or 4,000 feet. uFDEX may also link to BlueTooth, Wi-FI or VHF for wireless communication.

Because RS-232 is normally a point-to-point communication protocol, uFDEX enables having several RS-232 connections to one and same RS-232 port by utilising a protocol structure via microcontrollers to handle all I/O port data and traffic with different baudrates if needed.

In this way uFEDX enables adding several devices to one single RS-232 port that may connect to embedded or desktop PC. This entry point can also be USB port by using USB to RS-232 converter.

Background

After several years of "Research and Developments" (R&D) in Europe, New Zealand and Thailand, in the 90's the FIKO Group and its research team led by the Norwegian (Trondheim) born Attila Sandor Fiko introduced the early stage of "Common Hybrid Interface Protocol System" (“CHIPS”) named Digital One Line Link or "DOLL". In 2003 the FIKO Group introduced the world first functionally working CHIPS, which today represent uFDEX version 1.0 (Update: released as version 2.0 in October 2006). The aim of such intensive R&D work was to enable multiple serial devices to communicate on one single entry point where the datastream is to be managed by uFDEX Device Manager software without having interface and communication problems that are normally introduced in mixed protocol systems.

The use of uFDEX

The main task in a uFDEX network is taken care of by uFDEX Master Switches which are small devices that runs on ATMEL microcontrollers and its similar to network switches found in i.e. PC LAN. Such Master Switches are secure and needs Username and Password to log into. Because the uFDEX protocol is text based, such login and control can also be made remotely using i.e. mobile phone SMS messaging.

As uFDEX acts as CHIPS, it also enables the use of the serial PS/2 PC keyboard interface to transmit and receive ASCII codes as means of data communications.

This gives advantages for use in example simulators or application software where key commands are needed for embedded and automated remote management of software function and controls or where several operators need access to the same software without the need of using several computers to do so. Some areas where this is used are in Microsoft Flight Simulator where all flight controls are managed via keyboard commands and in embedded PC's with keyboard interface integrated to the display frame.

uFDEX can be used as both Star Network and serial network where i.e. several branches of the star can be cascaded and in this way make it possible to use different form of serial standards like instance one Star Network for RS-232, another for RS-485, one for BlueTooth another for Wi-FI and so forth and at the end they can all connect into one single RS-232 or USB port making it the most flexible mini-LAN system for i.e. vehicles, lab's, hospitals, home and office automation. uFDEX combines short, long and wireless communication into one single protocol structure that can also connect into and communicate with the CANbus used in vehicles.

uFDEX and its ID structure

uFDEX version 2.0 uses unique HEX-based Product ID structure similar to what USB uses where the Product ID contains of 9 bytes in total. Out of this Vendor ID takes up 3 bytes, Switch ID 1 byte, Product ID 2 bytes, Device ID 2 bytes and SUB ID 1 byte.

Such Product ID structure can be i.e. 001A05020 where each Vendor ID can contain 256 products, 256 devices and 16 SUB ID's which means 16 devices of the same product in one uFDEX network branch. The max number of uFDEX devices of Vendor 001 would then be 001AFFFFF or 1,048,575 while uFDEX has the limitation of having 65,531 Vendor ID's as 3 bytes of Switch ID is reserved.

For compatibility with the uFDEX Plug'n Play architecture, each product must obtain Product ID from the inventor or use the prototype ID which is FFF in HEX or 4095 in DEC. Ready pre-programmed uFDEX ATMEL microcontrollers on PCB for prototyping is available where developers can also obtain DLL's and other development tools to handle the uFDEX protocol.

About the uFDEX Logo

The shown image is the official logo of uFDEX version 1.0. The logo indicates uFDEX Slaves (in black squares) and uFDEX Master (in white square) while the two lines on both sides of the Maser square are the symbol of network traffic. (Update: uFDEX version 2.0 uses the same logo as base, but has added more graphics to it)

Advantages in using uFDEX

The advantage of using uFDEX is in instrumentation where data from several instruments need to be linked into one single connection point like RS-232 or USB. Say instance in LAB's where there is several instruments installed and they might also use several communication ports. By joining all combinations of ports and protocols into uFDEX Master Switch and uFDEX Transparent COM devices, it is possible to collect such data into one single source like notebook or embedded PC.