Indigresso Wiki

Open Source Stuff for DASH7

User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

opentag:apps:client_mpipe [2011/10/07 17:34]
jpnorair created
opentag:apps:client_mpipe [2011/10/07 20:03] (current)
Line 1: Line 1:
 ====== MPipe Client App ====== ====== MPipe Client App ======
-The Blinker ​app is a [[opentag:​apps:​main|built-in application]] for [[opentag:​main|OpenTag]] that has two sub-applications: +The **MPipe Client ​app** is a [[opentag:​apps:​main|built-in application]] for [[opentag:​main|OpenTag]] that builds onto a [[http://​​wiki/​POSIX|POSIX]] platform. ​ It is an implementation of an OpenTag client console — not a server — so it does not manage a [[dash7_mode_2:main|DASH7]] stack, ​it just manages an [[opentag:​system_arch|MPipe connection to an OpenTag server]] (which manages the DASH7 stack).
-  - Beacon Device: All it does is send beacons +
-  - Receiver DeviceAll it does is listen for beacons+
-The Blinker app is useful for testing ​the following OpenTag ​functions+The MPipe Client implements ​the following ​parts of the [[opentag:​otlib|OpenTag ​Library (OTlib)]]
-  * Basic TX and RX +  * [[opentag:​alpapi|ALP]] Client 
-  * Beacon Cycle routine +  * Buffers 
-  * File System usage with beacons +  * CRC 
-  * Application-level ​synchronization ​(optional)+  * NDEF 
 +  * Queue 
 +  * POSIX MPipe Driver (not actually part of OTlib) 
 +===== What You Get ===== 
 +==== Command Line App ==== 
 +''​otclient''​ is the name of the MPipe Client App.  It is POSIX C and it runs in a POSIX shell. ​ Using it is kind of like using POSIX command line apps ''​ftp''​ or ''​cu''​ or other ones similar to these, as ''​otclient''​ has a series of commands that can be used to send ALP messages (and especially ALP-API messages) from the cilent to the server. ​ The server will run tasks based on the input messages from the client (the tasks often have something to do with creating DASH7 dialogs between the server and other DASH7 devices). ​  
 +==== Python-based GUI App ==== 
 +**I am working slowly on the Python-based GUI App.  This crazy high-level ​programming is weird to me, so if you are a Python developer and you want to do something really cool for the OpenTag/​DASH7 community, or you just want to be involved in a Python project that will look good on a resume, please [[:​jp_norair|contact me]].**\\ 
 +''​otgui''​ is the name of the GUI front-end for ''​otclient''​ that also includes some more convenient data display features ​(such as a table of [[dash7_mode_2:​dataelements|ISF configuration files]] with all the data elements broken-out for easy access).  ''​otgui''​ is written in [[http://​|Python]] using [[http://​|wxPython]] as the GUI toolkit, and it is portable to Linux, Mac, and Windows. 
 +==== Some other type of GUI App ==== 
 +Please [[:​jp_norair|contact me]] if you want to make a different type of front-end for ''​otclient''​.
 ===== Platforms Supported ===== ===== Platforms Supported =====
-All completedofficial platforms support the Blinker Demo.+Anything with a POSIX layer and a [[http://​​programming/​tty/​index.php|TTY interface]]. ​ LinuxMac OS X, and anything else UNIX are POSIX OSes, so they work quite naturally. ​ Getting MPipe Client working on Windows requires a POSIX compatibility layer such as [[http://​​|MinGW]].
 ===== Files Involved ===== ===== Files Involved =====
-The normal group of application files, stored in directory ''/​Apps/​Demo_blinker/​Code'',​ are used with the Blinker Demo.+The normal group of application files, stored in directory ''/​Apps/​Client_MPipe/​Code'',​ are used with the MPipe Client The platform drivers are stored in ''/​Platforms/​POSIX''​
-=== Headers === 
-  * Basic Build Configuration (build_config.h) 
-  * Application Configuration (app_config_blinker.h) 
-=== C Files === 
-  * Main application file (blinker_main_[platform-name].c) 
-  * Beacon device subroutines (blinker_beacon.c) 
-  * Receiver device subroutines (blinker_receiver.c) 
 ===== Build Instructions ===== ===== Build Instructions =====
-Blinker Demo works fine with debug or release modes of operation. ​ There are no special instructions for building except that the ''​BUILD_MODE''​ preprocessor definition from ''/​Apps/​Demo_Blinker/​Code/​build_config.h'' ​should be set to ''​BLINKER_MODE'' ​(0) or ''​RECEIVER_MODE'' ​(1) in order to build for one mode or the other.+Make sure to change ​''/​Apps/​Client_MPipe/​Code/​build_config.h''​ to the parameters that make sense for the HW you are using. ​ really, the only important attributes are the Endian-ness and the size of a pointer (OpenTag cares about these things). ​ After that, just build like a normal POSIX apps. 
 +The ''​otclient'' ​app will be installed into ''​/​usr/​local/​bin'' ​of your machine.
-===== Default Configuration ===== +<​code>​ 
-The Blinker Demo uses a pretty minimal configuration,​ so it is good for testing just the basics of OpenTag for early versions of ports. ​ You can see the full configuration file at ''​[[opentag:​files:​Apps:​Demo_Blinker:​Code:​app_config_DemoBlinker.h|/Apps/Demo_Blinker/Code/​app_config_DemoBlinker.h]]'',​ which follows the [[opentag:​configuration|normal configuration format]].+$ cd [base-dir]/Apps/Client_MPipe 
 +$ make otclient 
 +$ make install 
-The configuration allows the following application usage 
-  * Filesystem is read/write only (no create/​delete). 
-  * ALPs are disabled, so you have to[[opentag:​apps:​demo_blinker| configure]] setup parameters at build-time. 
-  * MPipe is enabled, and used to log activity for blinker (notifications of beacon) and receiver (notifications of reception). 
-  * - 
opentag/apps/client_mpipe.txt · Last modified: 2011/10/07 20:03 by jpnorair